Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Feb 20, 2026

Feb 19, 2026

  1. TrueLayer PLN Payments Settlement Delays

    Upon further investigation, we have identified that the settlement delays are due to a maintenance window. All withdrawal requests initiated during this maintenance window will be processed after the maintenance ends. Impact start time: 19/02/2026, 21:10 UTC Impact end time: 19/02/2026, 23:30 UTC Client actions: None

    Resolved

  2. GitHubIncident with API Requests

    On February 11, 2026, between 13:51 UTC and 17:03 UTC, the GraphQL API experienced degraded performance due to elevated resource utilization. This resulted in incoming client requests waiting longer than normal, timing out in certain cases. During the impact window, approximately 0.65% of GraphQL requests experienced these issues, peaking at 1.06%. <br /><br />The increased load was due to an increase in query patterns that drove higher than expected resource utilization of the GraphQL API. We mitigated the incident by scaling out resource capacity and limiting the capacity available to these query patterns. <br /><br />We're improving our telemetry to identify slow usage growth and changes in GraphQL workloads. We’ve also added capacity safeguards to prevent similar incidents in the future.

    Resolved

  3. GitHubDisruption with some GitHub services

    On February 11 between 16:37 UTC and 00:59 UTC the following day, 4.7% of workflows running on GitHub Larger Hosted Runners were delayed by an average of 37 minutes. Standard Hosted and self-hosted runners were not impacted. <br /><br />This incident was caused by capacity degradation in Central US for Larger Hosted Runners. Workloads not pinned to that region were picked up by other regions, but were delayed as those regions became saturated. Workloads configured with private networking in that region were delayed until compute capacity in that region recovered. The issue was mitigated by rebalancing capacity across internal and external workloads and general increases in capacity in affected regions to speed recovery. <br /><br />In addition to working with our compute partners on the core capacity degradation, we are working to ensure other regions are better able to absorb load with less delay to customer workloads. For pinned workflows using private networking, we are shipping support soon for customers to failover if private networking is configured in a paired region.

    Resolved

  4. KernelAuthentication Provider Outage

    Our authentication provider has confirmed the incident is resolved. Dashboard access at dashboard.onkernel.com is fully restored. The core API, browser sessions, SDKs, CLI, and MCP server were unaffected throughout this incident.

    Resolved

  5. ClerkFull Outage

    We've observed stable operations and are marking this incident as resolved

    Resolved

  6. GitHubDisruption with some GitHub services

    Between February 11th 21:30 UTC and February 12th 15:40 UTC, users in Western Europe experienced degraded quality for all Next Edit Suggestions requests. Additionally, on February 12th, between 18:40 UTC and 20:30 UTC, users in Australia and South America experienced degraded quality and increased latency of up to 500ms for all Next Edit Suggestions requests. The root cause was a newly introduced regression in an upstream service dependency.<br /> <br />The incident was mitigated by failing over Next Edit Suggestions traffic to unaffected regions, which caused the increased latency. Once the regression was identified and rolled back, we restored the impacted capacity. We have improved our quality analysis tooling and are working on more robust quality impact alerting to accelerate detection of these issues in the future.

    Resolved

  7. GitHubIntermittent disruption with Copilot completions and inline suggestions

    Between February 11th 21:30 UTC and February 12th 15:40 UTC, users in Western Europe experienced degraded quality for all Next Edit Suggestions requests. Additionally, on February 12th, between 18:40 UTC and 20:30 UTC, users in Australia and South America experienced degraded quality and increased latency of up to 500ms for all Next Edit Suggestions requests. The root cause was a newly introduced regression in an upstream service dependency.<br /><br />The incident was mitigated by failing over Next Edit Suggestions traffic to unaffected regions, which caused the increased latency. Once the regression was identified and rolled back, we restored the impacted capacity. We have improved our quality analysis tooling and are working on more robust quality impact alerting to accelerate detection of these issues in the future.

    Resolved

  8. TrelloDegraded performance of Trello

    On February 19, 2026, Trello users may have experienced performance degradation. The issue has now been resolved, and the service is operating normally for all affected customers.

    Resolved

  9. KeeperUS GovCloud Region - Login Errors Resolved

    Maintenance in the GovCloud region was scheduled to begin at 8:00 PM PST with a planned duration of 30 minutes. During the maintenance window, certain services required additional reconfiguration beyond the original scope. Core services were restored within the planned 30-minute window. However, due to the extended reconfiguration activities, some users experienced API errors during login for approximately 15 minutes following service restoration.

    Resolved

  10. GitHubDegraded Performance in Webhooks API and UI, Pull Requests

    On February 9, 2026, between 07:05 UTC and 11:26 UTC, GitHub experienced intermittent degradation across Issues, Pull Requests, Webhooks, Actions, and Git operations. Approximately every 30 minutes, users encountered brief periods of elevated errors and timeouts lasting roughly 15 seconds each. During the incident window, approximately 1–2% of requests were impacted across these services, with Git operations experiencing up to 7% error rates during individual spikes. GitHub Actions saw up to 2% of workflow runs delayed by a median of approximately 7 minutes due to backups created during these periods. <br /><br />This was due to multiple resource-intensive workloads running simultaneously, which caused intermittent processing delays on the data storage layer. We mitigated the incident by scaling storage to a larger compute capacity, which resolved the processing delays. <br /><br />We are working to improve detection of resource-intensive queries, identify changes in load patterns, and enhance our monitoring to reduce our time to detection and mitigation of issues like this one in the future.

    Resolved

Feb 18, 2026

  1. HoneycombPartial query outage in EU1

    Between 22:10 and 22:40 UTC on Feb18, 2026 Honeycomb experienced a partial query outage in our EU environment. The incident has been resolved, and we are continuing to investigate the contributing factors.

    Resolved

Older incidents