Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Apr 27, 2026

  1. GitHubDisruption with Copilot chat and Copilot Coding Agent

    On April 22, 2026, between 15:16 UTC and 19:18 UTC, users experienced errors when interacting with Copilot Chat on github.com and Copilot Cloud Agent. During this time, users were unable to use Copilot Chat or Copilot Cloud Agent. Copilot Memory (in preview) was not available to Copilot agent sessions during this time. The issue was caused by an infrastructure configuration change that resulted in connectivity issues with our databases. The team identified the cause and restored connectivity to the database. Copilot Chat and Cloud Agent for github.com were restored by 18:16 UTC. Remaining regional deployments were restored incrementally, with full resolution at 19:18 UTC. We have taken steps to prevent similar infrastructure changes from causing these kinds of database operations in the future.

    Resolved

  2. GitHubDisruption with some GitHub services

    On April 22, 2026, between 09:00 UTC and 22:05 UTC, the Copilot coding agent and pull request comment event processing were degraded. During this period, approximately 0.5% of total pull request and issue comments mentioned @copilot (~23,000 invocations), explicitly requested work from the Copilot coding agent but were not acted upon.<br /><br />Creating, viewing, and replying to pull request comments was unaffected, and other Copilot<br />functionality continued to operate normally. The impact was limited to @copilot mentions on pull request comments not triggering Copilot coding agent runs, and to some downstream systems not receiving new pull request comment events during the impact window.<br /><br />The cause was a serialization error that prevented pull request comment events from being published to downstream consumers, including the Copilot coding agent. This was related to the same class of issue as incident #4295 on April 20, affecting a another event type.<br /><br />We mitigated the incident by deploying a fix that restored event publishing, after which the Copilot coding agent and other downstream consumers resumed processing pull request comment events normally.<br /><br />We are working to complete our audit of related event schemas, migrate remaining consumers to use<br />the updated identifier fields, and improve monitoring to detect drops in publishing on critical event topics, to reduce our time to detection and mitigation of issues like this one in the future.

    Resolved

  3. MongoDB CloudIncrease in Billing for Backup Usage

    We have resolved the issue that caused the overage and usages should be reflected correctly by April 28th. If you still see incorrect usages after this date, please reach out to us.

    Resolved

  4. Zapier500 error when viewing upcoming invoices

    The issue affecting invoice access and downloads has been resolved. Service was fully restored at 18:30 UTC on April 27, 2026. At 17:20 UTC an outage from the Databricks App caused invoices to fail to load or download from the Billing and Invoices Page. Databricks released a fix for their outage and invoices are functioning as normal. If you attempted to view or download any invoices during this time, you can retry that action now. We apologize for the inconvenience this caused and appreciate your patience while the issue was resolved. If you have any questions, please reach out to our Support Team - https://zapier.com/app/get-help

    Resolved

  5. Box[Medium] Issues with Box Search

    After further monitoring, this incident is now considered resolved. Search with metadata has been restored to full functionality. If you continue to experience any issues, please contact Box Support at https://support.box.com.

    Resolved

  6. Box[Medium] Issues Accessing the Admin Console Dashboard

    After further monitoring, this incident is now considered resolved. The Admin console service has been restored to full functionality. If you continue to experience any issues, please contact Box Support at https://support.box.com.

    Resolved

  7. Help ScoutConnection Issues

    Our team has identified and resolved the issue, and performance is now stable across the board. We'll continue to monitor all services over the next few hours. Thank you for your patience while we resolved this.

    Resolved

  8. Intercom - AUErrors on the REST API in Australia

    On April 27, 2026, between approximately 11:14 UTC and 12:52 UTC, customers hosted in our Australia region experienced errors and timeouts when using the Intercom REST API. Requests to the API would fail with timeout errors. Fin, the Intercom Inbox, and the Messenger were not affected during this window. Confirmed that the fix implemented resolved the issue, service is operating normally.

    Resolved

  9. ElasticElevated Error Rates and Latency — EU West Region

    The connectivity issues affecting a subset of customers in our AWS EU West (Paris) region have been resolved. Failed probes recovered at 11:36 UTC following remediation of an issue with our underlying cloud infrastructure provider. We are no longer observing any elevated error rates or latency in the region. We apologise for any inconvenience caused and will conduct a post-incident review.

    Resolved

  10. TrueLayerSandbox Signup+ Degraded Performance

    We experienced an issue affecting Signup+ requests in the Sandbox environment due to unexpected responses from a third-party provider. The issue has been resolved and normal service has been restored. Impact start time: 17/03/2026, 01:00 UTC Impact end time: 24/04/2026, 17:30 UTC Client actions: None

    Resolved

  11. E2BTemporary Usage Spike and API Errors

    We identified and resolved an issue that caused a temporary spike in reported usage for some teams, which may have resulted in billing limit errors. Systems are now operating normally.

    Resolved

Apr 26, 2026

  1. GitHubIncident with Pull Requests

    On April 23, 2026, between 16:05 UTC and 20:43 UTC, the Pull Requests service experienced a regression affecting merge queue operations. PRs merged via merge queue using the squash merge method produced incorrect merge commits when the merge group contained more than one PR. In affected cases, changes from previously merged PRs and prior commits were inadvertently reverted by subsequent merges.<br /><br />During the impact window 2,092 pull requests were affected. The issue did not affect pull requests merged outside of merge queue, nor merge queue groups using the merge or rebase methods.<br />It took approximately 3 hours and 33 minutes to identify the issue. The change completed deployment at approximately 16:05 UTC, and we became aware at 19:38 UTC following an increase in customer support inquiries. Because the issue affected merge commit correctness rather than availability, it was not detected by existing automated monitoring and was identified through customer reports.<br /><br />The regression was introduced by a new code path that adjusted merge base computation for merge queue ref updates. This code path was intended to be gated behind a feature flag for an unreleased feature, but the gating was incomplete.<br /><br />As a result, the new behavior was inadvertently applied to squash merge groups, producing an incorrect three-way merge. This caused subsequent squash merges to revert changes from earlier pull requests and, in some cases, changes between their starting points.<br /><br />We mitigated the incident by reverting the code change and force-deploying the fix across all environments. After resolution, we identified affected repositories and sent targeted remediation instructions to repository administrators with step-by-step recovery guidance.<br /><br />The regression was not identified during internal validation. Existing test coverage primarily exercised single-PR merge queue groups, which did not exhibit the faulty base-reference calculation. Because automated checks did not validate merge correctness for multi-PR squash groups, the defect surfaced only in production.<br /><br />To prevent recurrence, GitHub is expanding test coverage for merge correctness validation. We are broadening automated coverage for merge queue operations, including regression checks that validate resulting Git contents across supported configurations, so issues affecting merge correctness are caught before reaching production.<br /><br />We are committed to ensuring the correctness and reliability of merge queue operations. These actions will reduce the risk of similar regressions and improve confidence in future changes to the Pull Requests service.

    Resolved

  2. SupabaseInadvertently disabled pg_graphql for some projects

    A modification to existing projects was deployed due to the recently communicated Data API and pg_graphql changes. https://github.com/orgs/supabase/discussions/45329 This modification was supposed to disable pg_graphql for projects that had not seen usage in the last 30 days. Due to a misconfiguration, this targeted more projects than intended. We are deeply sorry for the inconvenience and have since addressed the issue. For those using pg_graphql actively, you may have seen pg_graphql extension is not enabled in the logs for your project and you can safely re-enable this. If you have been impacted, or you are unable to re-enable pg_graphql, please contact success@supabase.io

    Resolved

  3. KlaviyoAPI 503 Errors

    We confirmed that all API activity has been stable since the fix was released. Any requests that returned 503 errors during the outage window will need to be retried. This incident has been resolved.

    Resolved

  4. NetlifyIncreased errors on Image CDN

    We experienced an elevated rate of errors on the Image CDN across Standard as well as High Performance Edge Networks. The errors started around 03:55 UTC. The recovery began around 04:55 UTC.

    Resolved

Apr 25, 2026

  1. TrueLayerPLN Payments Settlement Delays

    You may have experienced delayed settlement for PLN Payouts during the timeframe specified. The service has now recovered and Payouts are settling at normal rate. Impact start time: 25/04/2026, 19:30 UTC Impact end time: 25/04/2026, 20:00 UTC Client actions: None

    Resolved

Older incidents