Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Jan 29, 2026

  1. Intercom - AUFin for Salesforce Errors

    Customers using Fin for Salesforce can resolve this issue by going into Fin Settings, then Salesforce Integration, and then clicking reconnect. This operation must be performed by the cluster. We have confirmed that all customers following this process have seen recovery.

    Resolved

  2. Intercom - EUFin for Salesforce Errors

    Customers using Fin for Salesforce can resolve this issue by going into Fin Settings, then Salesforce Integration, and then clicking reconnect. This operation must be performed by the cluster. We have confirmed that all customers following this process have seen recovery.

    Resolved

  3. Intercom - USFin for Salesforce Errors

    Customers using Fin for Salesforce can resolve this issue by going into Fin Settings, then Salesforce Integration, and then clicking reconnect. This operation must be performed by the cluster. We have confirmed that all customers following this process have seen recovery.

    Resolved

  4. GranolaTranscription failures on Granola mobile

    Our transcription provider for iOS notes is back up and running, so your notes should begin to transcribe/summarize. It may take some time to process the backlog, so if you're having issues then please wait a few minutes and then try pressing 'end' on the note again. If you're having problems, get in touch at hey@granola.so "hey@granola.so": mailto:hey@granola.so!

    Resolved

  5. HubSpotEmail events and workflow enrolment delayed

    We're resolved the issue causing event processing delays since 1:30 AM EST (UTC -05:00) on Jan 29, 2026. These delays affected tools such as email events, workflow enrollment and CRM updates in HubSpot.

    Resolved

  6. BufferIssue Publishing Posts to X/Twitter

    The issue affecting publishing to X has been fully resolved, and all systems are now operating normally. We appreciate your understanding and apologise for any disruption this may have caused. Please let us know if you continue to experience any issues.

    Resolved

  7. SnowflakeAWS - US West (Oregon): INC0150440

    Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site: [https://community.snowflake.com/s/article/INC0150359-and-INC0150440](https://community.snowflake.com/s/article/INC0150359-and-INC0150440)

    Resolved

  8. ZapierIntermittent throttling errors when pulling a trigger sample

    We are happy to report that the issue has been resolved and we are no longer seeing reports of issues from our customers. There's no action to take, and loading sample trigger data should now be working as expected. Please let us know if you're still seeing issues or have questions!

    Resolved

  9. BunnyStream API/Upload, Storage and CDN Partial Outage

    This was caused by an upstream network provider experiencing a network outage. While CDN traffic was not affected, supporting services such as Stream, Storage and our Core API may have been intermittently returning timeout errors. This has now been rectified and plans are in motion to further build redundancy into these products.

    Resolved

  10. ElevenLabsIncreased Conversation Latency

    LLM error rates have normalized, and Gemini-2.5-Flash conversation latency is back within expected ranges. We’ll continue monitoring closely. Improvements accommodating reduced cloud provider have been implemented, and will be live shortly.

    Resolved

  11. CanvaDownload issues for designs with uploaded images

    Thank you for your patience and understanding. As a workaround, you can try the following steps: - Remove the affected image from your design - Re-add the image to the design - Re-apply any photo edits - Try downloading again

    Resolved

Jan 28, 2026

  1. Box[Critical] Issues with Multiple Box Services

    We recently addressed issues affecting Box. We would like to take the opportunity to further explain these issues and the steps we have taken to keep them from happening in the future. ‌ On January 7th, 2026 between 5:10 PM and 5:50 PM PST, some customers experienced elevated errors and timeouts across multiple Box experiences, including Login, Uploads/Downloads, Box Notes, and the Public API. These issues were caused by a series of changes that triggered a request storm that overloaded our caching fleet. We resolved this by initially rate limiting background traffic and then rolling back the changes. ‌ **Analysis** On January 6th, a new feature was deployed that increased the utilization of one of our cache backends. That feature, in isolation, did not cause any problem. On January 7th, at 3:30 PM PST, another application change was rolled out that increased the traffic on the same system. Combined, these two changes significantly decreased our capacity buffer on some of our cache systems. ‌ On January 7th at 5:00 PM PT, another unrelated application change was released which created a short traffic spike in the cache system. This spike would have been handled without problems in a normal situation, but the reduced capacity buffer in our cache system created some temporary slowness and retries. Unfortunately, one critical code path that had been migrated to a newer infrastructure had a more aggressive retry policy than the old one. As a result, a retry storm increased the traffic progressively to our caching infrastructure. This traffic increase was not evenly balanced, as it was mostly targeting the few servers that were suffering under the load. The peak impact window was felt between 5:30PM and 5:50PM. ‌ To resume normal operations, we deprioritized some background traffic to increase the capacity of our cache system, and rolled back the changes that were causing the elevated traffic. ‌ **Corrective Actions** Box has initiated the following corrective actions: * Implemented a more conservative retry control policy \(to prevent retry amplification during partial failures\) * Improved handling of cache-related failures to reduce cascading effects * Enhanced monitoring and alerting of our capacity buffers to identify the impact of sudden traffic spikes on our cache systems ‌ We are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter.  ‌ Sincerely, The Box Team

    Resolved

  2. GitHubRegression in windows runners for public repositories

    On Jan 26, 2026, from approximately 14:03 UTC to 23:42 UTC, GitHub Actions experienced job failures on some Windows standard hosted runners. This was caused by a configuration difference in a new Windows runner type that caused the expected D: drive to be missing. About 2.5% of all Windows standard runners jobs were impacted. Re-run of failed workflows had a high chance of succeeding given the limited rollout of the change.<br /><br />The job failures were mitigated by rolling back the affected configuration and removing the provisioned runners that had this configuration. To reduce the chance of recurrence, we are expanding runner telemetry and improving validation of runner configuration changes. We are also evaluating options to accelerate the mitigation time of any similar future events.

    Resolved

  3. GitLabGitLab.com Pipelines Cannot be RunService Disruption

    We have identified and disabled a feature flag that was the cause. Error rates have returned to normal. Additional information can be found in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21160

    Resolved

  4. BitbucketDisrupted Bitbucket availability in eu-west-1

    On January 28, 2026, affected Bitbucket Cloud users in eu-west-1 may have experienced some service disruption. The issue has now been resolved, and the service is operating normally for all affected customers.

    Resolved

  5. EtsySite Issues

    This incident has been resolved. If you are still experiencing an issue, please let us know in our Etsy Forums (https://community.etsy.com/t5/Technical-Issues/bd-p/bugs).

    Resolved

  6. JiraDegraded performance of Jira, JPD, and JSM in eu-west-1

    On Jan 28, 2026, Jira, Jira Product Discovery, and Jira Service Management users in eu-west-1 region may have experienced delays in viewing recently submitted updates on the web page and/or mobile apps. Updates continued to process successfully during the incident.  There are no actions needed from customers.  The issue has now been resolved, and the service is operating normally for all affected customers.

    Resolved

  7. RD StationErro ao acessar dashboards personalizados

    O erro ao acessar os dashboards personalizados no RD Marketing, RD CRM e RD Conversas foi resolvida com sucesso. Caso você note que sua conta ainda contém alguma inconsistência, por favor, entre em contato com nosso Time de Suporte através da nossa Central de Ajuda - http://ajuda.rdstation.com/.

    Resolved

Older incidents