Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Nov 17, 2025

Nov 16, 2025

Nov 15, 2025

Nov 14, 2025

  1. TrelloTrello automations delayed

    On November 14, 2025 Trello users may have experienced delays on the execution of Trello automations. The issue has now been resolved, and the service is operating normally for all affected customers. Note: All automations identified as impacted by this incident will be automatically rerun, no customer actions are needed to rerun these automations.

    Resolved

  2. CerebrasPartial Service Disruption

    Between 06:05 AM PST and 09:25 AM PST users experienced partial degradation with Llama-3.3-70B. We have deployed a fix and the issue is now resolved.

    Resolved

  3. TypeformTypeform Renderer - Intermitent submission errors

    We are glad to inform you that the fix has been implemented and the incident resolved. We will run a problem investigation to understand what happened and how to prevent it from happening again. Thanks for your understanding & sorry for any inconvenience this has caused.

    Resolved

  4. ChargebeeAPI Service Degradation

    We experienced a brief API service interruption between 13:00 and 13:01 UTC due to an issue on the AWS platform. The impact was very minimal. We apologise for any inconvenience caused.

    Resolved

Nov 13, 2025

  1. HubSpotHubSpot may be unavailable for some users

    Between 01:53 PM (UTC -06:00) and 02:45 PM (UTC -06:00), some customers in all affected regions experienced issues with CRM tools. This was caused by a server impairment. As of 02:45 PM (UTC -06:00), our CRM 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

  2. BugsnagSymbolication issues

    This issue will have affected mapping files uploaded between 09:32 UTC yesterday and 13:00 UTC today, causing any events relying on those source maps to not symbolicate properly and create new groupings. This is now resolved, so any uploaded mapping files, including those uploaded in that time frame, will now successfully symbolicate any new events. Unfortunately old events affected by this will not be symbolicated retroactively, but any new events with matching source maps will be symbolicated and return to their previous error groupings.

    Resolved

  3. BugsnagBroken email links

    Emails sent from bugsnag.com between 10:30 UTC on 30th November and 13:00 UTC on 1st December may contain broken links. For collaborator invite emails with broken links, please reach out to your BugSnag organisation administrator to resend the invite from the BugSnag dashboard.

    Resolved

  4. BugsnagEmail outage

    This incident has been resolved. Unfortunately all emails that would have been delivered during this outage have been lost - please accept our apologies for any inconvenience caused by this. BugSnag uses a third-party supplier to deliver emails. That supplier had temporarily suspended our account and they have acknowledged that this was due to a false positive with their internal tooling. Please rest assured that we are taking steps to ensure this does not happen again in the future.

    Resolved

  5. BugsnagIssues with the Error Reporting API

    We experienced a spike in traffic between 19:47 UTC and 19:51 UTC, which caused issues with the Error Reporting API. There may be gaps in your events for this time period, although some platform specific notifiers will retry sending events.

    Resolved

  6. BugsnagIssues with the Traces and Spans API

    We experienced issues with the Traces and Spans API between 15:43 UTC and 16:00 UTC. There may be data loss in your performance metrics for this time period, although BugSnag's Performance SDKs will retry sending trace and span data.

    Resolved

Older incidents