Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Oct 1, 2026

  1. AblyElevated API Errors

    On October 1, a distributed denial-of-service \(DDoS\) attack caused elevated token-request errors across all Ably Realtime regions for approximately six minutes and intermittent unavailability of [ably.com](http://ably.com). We restored token-request service by increasing capacity and added targeted traffic-blocking and rate-limiting rules to mitigate the attack. We are strengthening endpoint protection and reviewing our firewall controls to reduce the risk of recurrence.

    Resolved

  2. GitHubCopilot Code Review is unable to complete reviews

    On September 28, 2026, between 19:23 UTC and 22:08 UTC the Copilot Code Review service was degraded and pull request reviews did not complete in all environments. On average, approximately 70% of requested reviews did not complete. Reviews requested during this window were not automatically retried, and users needed to re-request a review from their pull request. This was due to a change in a dependent service that stopped delivering data Copilot Code Review needs to complete a review. Review completion is an inherently delayed signal, because each review job takes time to start and finish, so it took longer to detect the impact.<br /><br />We mitigated the incident by reverting the change.<br /><br />We are working to add a faster signal for reviews that fail to complete, add deployment validation that confirms a Copilot Code Review completes end to end, improve how we track internal dependencies between services, and make our deployment pipeline more reliable to reduce our time to detection and mitigation of issues like this one in the future.

    Resolved

  3. DeepgramElevated API errors

    Between 19:29 and 19:39 UTC, some API requests failed with HTTP 500 errors or timed out. This happened in two short bursts of about 1-2 minutes each, during a planned update to our authentication service. Services have recovered automatically and this issue is resolved.

    Resolved

  4. ReplitIssue loading integrations page

    The issue affecting loading of the integrations page has been resolved. Integrations should be functional again. If you are still seeing issues loading or using integrations, please contact support and we will help investigate.

    Resolved

  5. DaytonaSandbox listing (GET /sandbox)

    This issue has been resolved. All sandboxes, including those created during the incident, are now correctly returned in list results. The issue was caused by a disruption in the internal service responsible for indexing sandbox data. The underlying cause has been addressed, and we have taken steps to prevent a recurrence. We apologize for any inconvenience this may have caused.

    Resolved

  6. SnykSnyk CLI Scans Degraded

    No further impact has been observed during our monitoring period. The Snyk Incident Response has been stood down.

    Resolved

  7. Box[Medium] Issues with Box Hubs Shared Links

    _Notice and disclaimer: Box is providing this preliminary information subject to further review and analysis. To the best of our knowledge, this is the current state and we may update as more information is confirmed._ Between August 27, 2026 at 11:18 PM PDT and August 28, 2026 at 2:48 AM PDT some customers may have been unable to access Box Hubs using shared links. Other Box functionality, such as file and folder access, was not broadly affected. The issue occurred as a result of a recent code change in our ongoing effort to improve performance. We were able to resolve the issue by rolling back the change so traffic returned to the previous behavior. We are conducting a full engineering postmortem, including a review of our deployment and configuration practices, to reduce the chance of similar issues in the future. Our overview is subject to change with further analysis and findings. In the event our continuing investigation yields further substantive findings, we may publish additional analysis after the conclusion of the full engineering postmortem. 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

  8. GitHub[Retroactive] Actions workflow run failures after deployment gate approvals

    On October 1, around 02:00 UTC, an isolated infrastructure failure caused GitHub Actions to lose execution state for a small number of existing workflow runs. Affected runs may remain stuck, fail deployment approvals, or return errors when cancelled. Service connectivity has recovered, but the lost state cannot be restored by retrying an approval. If you're affected, you can trigger a new run or contact GitHub Support with links to your stuck runs so we can unblock them. Once cleared, select "Re-run all jobs." This preserves the workflow run ID but starts a new attempt, rebuilds artifacts, and requires fresh deployment approvals. Before rerunning, check whether any deployment steps already completed to avoid repeating changes.

    Resolved

  9. Box[Critical] Issues with All Files Page, Box Notes, API calls, logins and downloads

    From approximately 06.39 AM to 06:44 AM US Pacific time, we observed an issue impacting All Files Page, Box Notes, API calls, logins and downloads. Our systems automatically detected and corrected the underlying issue. There is no current impact and no further updates will be provided here. If you continue to experience any issues, please contact Box Support at https://support.box.com.

    Resolved

  10. SinchPost-Incident Notification - RTCx Services - US

    We experienced an issue causing degradation for RTCx services in the US region. The issue was identified and a fix deployed to resolve the issue Incident Start Time: 2026-10-01 8:00 UTC Incident End Time: 2026-05-06 9:36 UTC Impact: Some traffic could have been delayed and/or rejected If you have any questions, please contact support@sinch.com

    Resolved

  11. OVHcloud - Public Cloud[US-EAST-LZ-MIA][Network] - Localzone incident notification

    We are pleased to inform you that the incident affecting our LocalZones offering has been resolved. <b>Start time :</b> 01/10/2026 05:06 UTC <b>End time :</b> 01/10/2026 07:26 UTC <b>Root Cause :</b> A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.

    Resolved

  12. StripeElevated API errors

    From 02:24–02:27 UTC, we saw a brief increase in HTTP 5XX processing errors. This is now resolved.

    Resolved

Sep 30, 2026

  1. ElasticReplication bug causing slow recoveries

    This issue was resolved in the 9.5.3 release of Elasticsearch.  Customers running versions 9.5.0, 9.5.1, or 9.5.2 of Elasticsearch are advised to update to a newer version as soon as possible.

    Resolved

Older incidents