Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Jan 17, 2026

  1. ElevenLabsSTT Credit Usage Overreporting

    " A fix has been deployed to prevent inflated per-request charges affecting a subset of Speech-to-Text requests. The issue has been fully resolved. " "We are calculating the impacted usage during the incident window and will refund the missing credits to all affected accounts to correct the overcharging. "

    Resolved

  2. CerebrasPartial Service Disruption- API Key Error

    Between 4.25 PM PT and 5.45 PM PT, developers experienced minor service disruption due to API Key Error. The issue has been identified and resolved, normal service operation is restored.

    Resolved

Jan 16, 2026

  1. KernelDegraded Browser Creation

    We've addressed the issue and restored service. We'll continue to monitor and provide updates if needed.

    Resolved

  2. GitHub[Retroactive] Incident with GitHub Copilot (GPT-5 model)

    From January 14, 2026, at 18:15 UTC until January 15, 2026, at 11:30 UTC, GitHub Copilot users were unable to select the GPT-5 model for chat features in VS Code, JetBrains IDEs, and other IDE integrations. Users running GPT-5 in Auto mode experienced errors. Other models were not impacted. We mitigated this incident by deploying a fix that corrected a misconfiguration in available models, rendering the GPT-5 model available again. We are improving our testing processes to reduce the risk of similar incidents in the future, and refining our model availability alerting to improve detection time. We did not status before we completed the fix, and the incident is currently resolved. We are sorry for the delayed post on githubstatus.com.

    Resolved

  3. MintlifyDelayed Updates to Documentation

    Post-Mortem Update: Impact: Updates to customers documentation did not display. Timeline: - Jan 15th 17:15 PR merged for caching feature flags - Jan 16th 06:29 Incident Declared - Jan 16th 06:59 L2 Cache Disabled, updates displayed correctly - Jan 16th 08:04 L2 Cache PR merged, and enabled Root Cause: A recent PR introduced caching for feature flags, which changed the feature flag getter to return a Promise. This required adding `await` at every call site, but one reference was missed. One flag controlled whether cache invalidation targeted dev or prod. This change incorrectly lead the flag to evaluated as `true`, which lead to triggering revalidations against our dev environment Steps to resolve: To fix this immediately, we triggered a kill switch to directly hit our Layer 1 cache. While we patched a fix to our servers revalidation code. When the fix to our internal caching solution went live we Action Items: - Adding synthetic end to end tests for making sure the cache gets purged on updates. Previously our update tests only verified that the update was completed and not that the cache was reset.

    Resolved

  4. HashiCorpSAML configurations may break on updates

    Our Engineering team has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team.

    Resolved

  5. BufferIssue Publishing Posts to X/Twitter

    The issue with X/Twitter posts has been fully resolved, and all systems are now operational. We appreciate your understanding and apologise for any disruption this may have caused.

    Resolved

  6. ZapierLinkedIn apps returning "Requested version 20250101 is not active" error

    The incident affecting LinkedIn actions in Zap runs has been resolved. Between approximately 07:59 AM UTC and 11:55 AM UTC on January 16, 2026, some users experienced errors impacting Zap runs. These issues may have caused Zap runs to fail during this window. As of 11:55 AM UTC, the affected services returned to normal operation. Zap runs that encountered errors during the incident window have been automatically replayed, and we have not observed ongoing customer impact since resolution. If you have any questions or need assistance, please don’t hesitate to reach out to our support team: https://zapier.com/app/get-help

    Resolved

Jan 15, 2026

  1. BufferIssues with LinkedIn's API

    LinkedIn is functioning normally and has remained stable throughout our monitoring. As such, we're marking this incident as resolved.

    Resolved

  2. GitHubClaude Opus 4.5 model experiencing degraded performance

    On January 14th, 2026, between approximately 10:20 and 11:25 UTC, the Copilot service experienced a degradation of the Claude Opus 4.5 model due to an issue with our upstream provider. During this time period, users encountered a 4.5% error rate when using Claude Opus 4.5. No other models were impacted.<br />The issue was resolved by a mitigation put in place by our provider. GitHub is working with our provider to further improve the resiliency of the service to prevent similar incidents in the future.

    Resolved

  3. ZapierCreating new Zaps via Forms Actions panel seeing errors

    We are happy to report that the issue affecting the ability to create zaps from the actions panel in Forms has been resolved. Earlier today, some users encountered a generic error message (“Something went wrong”) when attempting to create new zaps from the Forms actions panel. Existing zaps and other methods for creating zaps were not affected. Our engineering team identified and corrected a broken link that was causing this error, which was related to a recent product rebrand. Functionality has been fully restored, and users can now create zaps from the Forms actions panel as expected. We apologize for any inconvenience this may have caused.

    Resolved

  4. GitHubGitHub Copilot failures

    On January 13th, 2026, between 09:25 UTC and 10:11 UTC, GitHub Copilot experienced unavailability. During this window, error rates averaged 18% and peaked at 100% of service requests, leading to an outage of chat features across Copilot Chat, VS Code, JetBrains IDEs, and other Copilot-dependent products. <br /><br />This incident was triggered by a configuration error during a model update. We mitigated the incident by rolling back this change. However, a second recovery phase lasted until 10:46 UTC, due to unexpected latency with the GPT 4.1 model. To prevent recurrence, we are investing in new monitors and more robust testing environments to reduce further misconfigurations, and to improve our time to detection and mitigation of future issues.

    Resolved

  5. HoneycombIncreased Latency and Errors for Events Ingest

    We observed a period of increased latency accompanied by a higher-than-normal error rate in some event ingest requests in the US. The service has since stabilized and is operating normally. We are continuing to monitor the system and are evaluating improvements to reduce the impact of similar conditions in the future. We apologize for the disruption and appreciate your patience.

    Resolved

  6. HubSpotMarketing email editor and page editor not loading

    Between 05:25 AM (UTC +00:00) and 07:00 AM (UTC +00:00), some customers in North America, Europe experienced issues with content tools, marketing tools. This was caused by a load balancer impairment. As of 07:00 AM (UTC +00:00), our content tools, marketing 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

Older incidents