Pulsara had 6 outages in the last 2 years totaling 51h 35m of downtime — averaging 0.2 incidents per month.
There were 6 Pulsara outages since August 3, 2024 totaling 51h 35m of downtime. Each is summarised below — incident details, duration, and resolution information.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
At 11:30 MT, we observed an issue affecting the viewing of images uploaded by our imaging partners. We have identified the root cause and are currently preparing a resolution. We anticipate deploying the fix later this evening. Once deployed, all previously uploaded images will be viewable again.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The Pulsara Calling feature is temporarily unavailable because our third-party partner is down. Pulsara is investigating this issue and will update the Pulsara Status Page when more information is available.
Pulsara's third-party video platform has restored all services, and Pulsara Calls are working. Pulsara will continue to monitor this issue.
This incident has been resolved.
The Pulsara platform was temporarily unavailable from approximately 15:44 to 15:46 US Mountain time today. A crash of a cloud vendor component resulted in errors for all application functionality. Automatic monitoring and recovery systems were initiated. All systems are back online, and normal operations have resumed.
We have identified and are monitoring an issue with Google Firebase Cloud Messaging (FCM) affecting a small number of notifications sent to Android devices. FCM is aware of this issue and is providing status information on their Firebase Status Dashboard (https://status.firebase.google.com/incidents/PTWWAYPjkjPapM4qkGY2) We will post updates here as they become available from Firebase. Please Note: this does not affect any Apple devices.
We are continuing to monitor for any further issues.
Google FCM incident status page has announced that they have mitigated this issue and are currently monitoring it. As Pulsara opened this incident as a helpful way of providing transparency to this event, we will close out this incident now. For further information, please visit https://status.firebase.google.com/incidents/PTWWAYPjkjPapM4qkGY2. As always, Pulsara will continue monitoring all third-party services to ensure our product is running.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved. Pulsara will provide RCA information on this incident when it becomes available.
**Incident Summary:** On 08/27/2024, our web application experienced an error that prevented some users from accessing their account information. This issue occurred due to a mismatch between the API responses from our older web application and the newer server. **Impact:** Some users could not log in to access their account information or perform actions that required user authentication. **Resolution:** The issue was resolved after completing the web upgrade, including a parsing error fix. We apologize for any inconvenience this incident may have caused. We have already taken steps and remain committed to improving our systems and processes to prevent similar issues in the future.