Istoricul incidentelor Pypestream

We are continuing to see issues with services that use AWS in our platform and our solutions experiencing instability and facing partial outage.

We are continuing to investigate this issue.

All the solutions are operating normally.

This incident has been resolved.

We are currently investigating this issue.

Our solutions are continuing to function with elevated error rates. These error rates can be attributed to network connectivity issues in the US-EAST-1 region. We continue to monitor the situation closely.

Based on the latest update from AWS, all the solutions are operating normally.

There is currently a global GCP / Google issue impacting all internet traffic and websites. Due to these issues, some of your solution features are being impacted and may result in slow loading or inability to load.

We are continuing to investigate this issue.

This incident has been resolved.

We are currently investigating the issue.

All systems operational.

We are currently investigating this issue.

We are continuing to investigate this issue.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We are currently investigating this issue.

We are continuing to investigate this issue.

This incident has been resolved.

We are currently investigating this issue.

We are continuing to investigate this issue.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

Pypestream has identified an issue impacting external API calls and logging into the platform. This issue is being actively worked on and we will be providing a resolution time as soon as possible. We will be providing periodic updates until the issue is resolved, upon which a Root Cause Analysis will be documented and shared. If you have any questions or would like to request additional information, please let us know.

The Pypestream platform has now been stabilized and users are now able to log in. A Root Cause Analysis will be documented and shared shortly. Thank you for your patience as we worked through this issue. If you have any questions or would like to request additional information, please let us know

We're investigating an issue with logging into Pypestream components.

This incident has been resolved.

We are currently investigating this issue.

The issue has been identified and a fix is being implemented.

This incident has been resolved.

We are investigating intermittent issues with chats escalating to Web Pype Manager

We are continuing to investigate this issue.

We identified one of our WPM containers was stuck in an unhealthy position. We are in the process restarting the unhealthy node and recover chats.

Systems should all be up and running again we are monitoring a few chats that where routed to the unhealthy node to make sure they restart on the new healthy nodes.

As of now all systems are operational please open a ticket if you experience issues.

We are currently investigating the issue.

AWS Infrastructure in our VPC collapsed and took down 3 of our RIAK DB VMs we are now working to recover from backups and resyncing nodes.

We are continuing to work on rebuilding 3 nodes.

We are still working on recovering data machines were rebuilt and working on synchronizations.

A fix has been implemented and we are monitoring the results.

Pypes are all restored and Solutions are all back and loading we are now monitoring as system rebalances

Solutions are back up please work with your Customer Success or Customer Experience Contact if you are seeing issues.

We are currently investigating the issues around the deployment of R7.33.0 to Sandbox. We will revert with an update in due course.

Thanks all for your patience. The issues are now resolved.

We are currently investigating this issue.

Issue with RabitMQ memory has been resolved

This incident has been resolved.