Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Feb 13, 2026

  1. GitHubIncident with Copilot

    On February 10, 2026, between 10:28 and 11:54 UTC, Visual Studio Code users experienced a degraded experience on GitHub Copilot when using the Claude Opus 4.6 model. During this time, approximately 50% of users encountered agent turn failures due to the model being unable to serve the volume of incoming requests.<br /><br />Rate limits set too low for actual demand caused the issue. While the initial deployment showed no concerns, a surge in traffic from Europe on the following day caused VSCode to begin hitting rate limit errors. Additionally, a degradation message intended to notify users of high usage failed to trigger due to a misconfiguration. We mitigated the incident by adjusting rate limits for the model.<br /><br />We improved our rate limiting to prevent future models from experiencing similar issues. We are also improving our capacity planning processes to reduce the risk of similar incidents in the future, and enhancing our detection and mitigation capabilities to reduce impact to customers.

    Resolved

  2. Miro - USCalls to Public API and MCP server are failing

    The performance degradation affecting Public API and MCP Server has been fully resolved. We apologize for the inconvenience caused and appreciate your understanding. If you continue to experience any issues, please reach out to our support team.

    Resolved

  3. Miro - AUCalls to Public API and MCP server are failing

    The performance degradation affecting Public API and MCP Server has been fully resolved. We apologize for the inconvenience caused and appreciate your understanding. If you continue to experience any issues, please reach out to our support team.

    Resolved

  4. Miro - EUCalls to Public API and MCP server are failing

    The performance degradation affecting Public API and MCP Server has been fully resolved. We apologize for the inconvenience caused and appreciate your understanding. If you continue to experience any issues, please reach out to our support team.

    Resolved

  5. ZapierUpstream errors with Airtable authentications

    We are pleased to confirm that this incident has been resolved. All Airtable Zaps and connections are back to normal. Impacted customers have now received an email with a timeline of events, actions taken, and next steps (if any). If you have any questions or need assistance, please reach out to our Support team at: https://zapier.com/app/get-help.

    Resolved

  6. GitHubIncident with Codespaces

    On February 12, 2026, between 00:51 UTC and 09:35 UTC, users attempting to create or resume Codespaces experienced elevated failure rates across Europe, Asia and Australia, peaking at a 90% failure rate.<br /><br />The disconnects were triggered by a bad configuration rollout in a core networking dependency, which led to internal resource provisioning failures. We are working to improve our alerting thresholds to catch issues before they impact customers and strengthening rollout safeguards to prevent similar incidents.

    Resolved

  7. LaunchDarklyData attribution issues with Experimentation

    We have fixed the data attribution issues where running experiment iterations were receiving incorrectly attributed data. This incident is now resolved and results for active experiments are now accurate.

    Resolved

  8. EntireDelayed Checkpoint updates

    The upstream infrastructure issue has been fully resolved. All core services including login and signup are operational. Remaining background processing tasks have been completed.

    Resolved

Feb 12, 2026

  1. MintlifyIntermittant issues with page loads

    We have restored the caching layer that was removed and have seen continued return to normal error rates and latency. If you are experiencing issues with page renders, please reach out to us at support@mintlify.com "support@mintlify.com": mailto:support@mintlify.com

    Resolved

  2. GitHubIncident with Actions

    On February 9th, 2026, between 09:16 UTC and 15:12 UTC GitHub Actions customers experienced run start delays. Approximately 0.6% of runs across 1.8% of repos were affected, with an average delay of 19 minutes for those delayed runs.<br /><br />The incident occurred when increased load exposed a bottleneck in our event publishing system, causing one compute node to fall behind on processing Actions Jobs. We mitigated by rebalancing traffic and increasing timeouts for event processing. We have since isolated performance critical events to a new, dedicated publisher to prevent contention between events and added safeguards to better tolerate processing timeouts.

    Resolved

  3. ZapierChange History Not Displaying

    This issue has been resolved. Between 14:42 and 18:00 UTC on February 12, some users were unable to view the Change History panel in the editor. All systems are now operating normally. If you experienced issues during this time, please refresh your browser. Need help? Contact Support: https://zapier.com/app/get-help

    Resolved

  4. ZapierAI Features Degraded — Chatbots & Agents

    This incident has been resolved as of 2026-02-12T15:38:00 UTC. Agents and Chatbots can now successfully add and sync table-based knowledge sources. If you encountered errors during the incident, please re-add and sync your knowledge sources. Need help? Contact Support: https://zapier.com/app/get-help

    Resolved

  5. GitHubNotifications are delayed

    On February 9th notifications service started showing degradation around 13:50 UTC, resulting in an increase in notification delivery delays. Our team started investigating. <br /><br />Around 14:30 UTC the service started to recover as the team continued investigating the incident. Around 15:20 UTC degradation resurfaced, with increasing delays in notification deliveries and small error rate (below 1%) on UI and API endpoints related to notifications. <br /><br />At 16:30 UTC, we mitigated the incident by reducing contention through throttling workloads and performing a database failover. The median delay for notification deliveries was 80 minutes at this point and queues started emptying. Around 19:30 UTC the backlog of notifications was processed, bringing the service back to normal and declaring the incident closed.<br /><br />The incident was caused by the notifications database showing degradation under intense load. Most notifications-related asynchronous workloads, including notifications deliveries, were stopped to try to reduce the pressure on the database. To ensure system stability, a database failover was executed. Following the failover, we applied a configuration change to improve the performance. The service started recovering after these changes.<br /><br />We are reviewing the configuration of our databases to understand the performance drop and prevent similar issues from happening in the future. We are also investing in monitoring to detect and mitigate this class of incidents faster.

    Resolved

  6. BufferIssue with scheduling threaded posts

    The issue with scheduling threaded posts has been fully resolved, and it’s functioning as expected again. If you encounter any further problems, please don’t hesitate to reach out to our team.

    Resolved

Older incidents