BugsnagDelays in Unity and Default event processing
This incident has been resolved.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been solved.
Resolved
This incident has been solved. Filtersets should now be appearing in the dashboard
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
There was an issue with the BugSnag Upload API between 22:20 UTC and 22:25 UTC.
Resolved
Intermittent issues with availability of Upload API
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
We experienced a brief outage, resulting in our release and hooks endpoints returning 5xx response's for a few minutes.
Resolved
This incident has been resolved.
Resolved
From 26/09/2024 10:00 AM UTC to 30/09/2024 10:00 AM UTC there was an issue where one of our services failed to correctly fetch and apply source maps from remote storage. This issue resulted in mapping files not being applied to certain frames in some events.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
The BugSnag Error Reporting API encountered a small period of increased latency, and an elevated rate of 502 responses between 1:55am - 2:00am UTC on Tuesday, 3rd of December. Events that were attempted to be reported during this time may have been lost, but some notifiers will have retried and successfully reported events that initially failed.
Resolved
This incident has been resolved
Resolved
Degraded performance between 17:15 and 17:40 UTC which included a backlog in Unity event processing. Customers may experience delays in integration processing (e.g. webhooks) between 17:15 and 18:02 UTC.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
The incident has been resolved
Resolved
This incident has been resolved.
Resolved
Purge requests were not executed between 2025-11-12 23:00 UTC and 2025-11-13 05:00 UTC. The issue has been mitigated, and purge functionality has been fully restored. All purge requests that failed during the impact window are being automatically retried.
Resolved
This incident has been resolved.
Resolved
The issue has been resolved.
Resolved
This incident has been resolved.
Resolved
We had approximately 1 hour of full downtime, where the Asana application was unavailable for most of our users. There was no data loss or security vulnerability. A routine configuration change affected the Asana application globally. While refactoring the configuration consumption, we missed an unintended side effect, causing the app to fail loading in all regions. We reverted the change and restarted servers for full recovery.
Resolved
This incident has been resolved.
Resolved
Between 13:40 and 14:10 UTC, a subset of Crowdin Enterprise users experienced server errors when attempting to access projects via the web interface (UI). The issue affected users with specific project configurations. Access via the API remained operational. The service was fully available for translators, though. Our team identified and deployed a fix for the underlying server issue. The problem is resolved, and project access is fully restored. If you were affected by this issue, please refresh your browser page to ensure full functionality. We apologize for the inconvenience.
Resolved
Between 6:40pm - 6:54pm CET we experienced an infrastructure issue that affected scenario executions in the us1.make.com zone as follows: - Scenarios scheduled to run in the affected time interval were delayed by up to 18 minutes. - Scenarios that are triggered by a webhook were not executed. - Webhooks sent to the affected zone during the aforementioned time interval may not have been received. Most source systems that sends data to Make implement a retry mechanism and webhooks will be redelivered to Make. In addition to the above, login on the zone was also affected. The zone is now stable, and we are continuing to monitor the situation
Resolved
Between 04:53 PM (UTC +00:00) and 05:55 PM (UTC +00:00), some customers in Canada experienced issues with HubSpot tools. This was caused by a production configuration change. As of 05:55 PM (UTC +00:00), our HubSpot tools are working properly and the incident has been fully resolved. HubSpot conducts a thorough review after each incident to understand the cause and prevent it from happening again. Learn more about HubSpot's commitment to reliability at www.HubSpot.com/reliability. The information on this page reflects our understanding of the incident and impact at the time of the update.
Resolved
We identified an issue with sending messages. The issue is resolved. We're looking into the root cause
Resolved
This incident has been resolved.
Resolved