Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Feb 4, 2026

  1. BunnyCDN Log Delivery Delay

    A fix has now been applied and near real-time log delivery has now been restored. There is separately a backlog of requests that is being processed (but does not affect current real-time logs delivered).

    Resolved

  2. LovableIssues connecting Supabase through connectors

    We've successfully resolved the issue with Supabase connector functionality. The fix has been deployed and all users should now be able to connect to Supabase without any problems. Thank you for your patience while we worked on this.

    Resolved

  3. SnowflakeAzure - Central US (Iowa): INC0150687

    Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site: [https://community.snowflake.com/s/article/INC0150687](https://community.snowflake.com/s/article/INC0150687)

    Resolved

  4. Confluent CloudConfluent Cloud Service Outage

    The issue has been resolved and services are operating normally. The root cause was a networking configuration change in the us-west-2 region that caused client connection issues starting at approximately 21:33 UTC, resulting in intermittent service disruption across several Confluent Cloud services, including Kafka, Flink, Metrics API, Logging, Provisioning, and Authentication. The change was reverted, and as of 00:20 UTC, services have been fully restored.

    Resolved

  5. ZapierLinkedIn Ads - All Triggers - Missing Webhooks

    We're happy to report that the LinkedIn team has successfully completed replaying the missed hooks for the New Lead Gen Form Response (Sponsored content) trigger that occurred during the incident window (Jan 27th, 8:21 UTC until Jan 29th, 01:32 UTC). If you have any questions or need assistance, please reach out to our Support team at https://zapier.com/app/get-help

    Resolved

Feb 3, 2026

  1. InngestSubset of customers experiencing function execution delays

    System latency for function execution has returned to normal levels for the affected users. The incident has been resolved. The cause of the incident was due to increased load causing congestion. We applied changes to the system to reduce congestion, resulting in increasing throughput. We also re-distributed some affected users in an effort to mitigate impact. Our team's planned to roll out new infrastructure in the coming weeks and is accelerating that plan to aim to roll it out later this week to increase overall capacity.

    Resolved

  2. GitHubDegraded Experience - Failing to finalize some CCA Jobs

    Between 2026-01-30 19:06 UTC and 2026-01-30 20:04 UTC, Copilot Coding Agent experienced sessions getting stuck, with a mismatch between the UI-reported session status and the underlying Actions and job execution state. Impacted users could observe Actions finish successfully but the session UI continuing to show in-progress state, or sessions remaining in queued state.<br /><br />The issue was caused by a feature flag that resulted in events being published to a new Kafka topic. Publishing failures led to buffer/queue overflows in the shared event publishing client, preventing other critical events from being emitted. We mitigated the incident by disabling the feature flag and redeploying production pods, which resumed normal event delivery. We are working to improve safeguards and detection around event publishing failures to reduce time to mitigation for similar issues in the future.

    Resolved

  3. HashiCorpErrors configuring SSO for HCP tenants

    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

  4. GitHubIncident with Codespaces

    On February 2, 2026, GitHub Codespaces were unavailable between 18:55 and 22:20 UTC and degraded until the service fully recovered at February 3, 2026 00:15 UTC. During this time, Codespaces creation and resume operations failed in all regions. <br /><br />This outage was caused by a backend storage access policy change in our underlying compute provider that blocked access to critical VM metadata, causing all VM create, delete, reimage, and other operations to fail. More information is available at https://azure.status.microsoft/en-us/status/history/?trackingId=FNJ8-VQZ. This was mitigated by rolling back the policy change, which started at 22:15 UTC. As VMs came back online, our runners worked through the backlog of requests that hadn’t timed out. <br /><br />We are working with our compute provider to improve our incident response and engagement time, improve early detection before they impact our customers, and ensure safe rollout should similar changes occur in the future. We recognize this was a significant outage to our users that rely on GitHub’s workloads and apologize for the impact this had.

    Resolved

  5. GitHubIncident with Actions

    On February 2, 2026, between 18:35 UTC and 22:15 UTC, GitHub Actions hosted runners were unavailable, with service degraded until full recovery at 23:10 UTC for standard runners and at February 3, 2026 00:30 UTC for larger runners. During this time, Actions jobs queued and timed out while waiting to acquire a hosted runner. Other GitHub features that leverage this compute infrastructure were similarly impacted, including Copilot Coding Agent, Copilot Code Review, CodeQL, Dependabot, GitHub Enterprise Importer, and Pages. All regions and runner types were impacted. Self-hosted runners on other providers were not impacted. <br /><br />This outage was caused by a backend storage access policy change in our underlying compute provider that blocked access to critical VM metadata, causing all VM create, delete, reimage, and other operations to fail. More information is available at https://azure.status.microsoft/en-us/status/history/?trackingId=FNJ8-VQZ. This was mitigated by rolling back the policy change, which started at 22:15 UTC. As VMs came back online, our runners worked through the backlog of requests that hadn’t timed out. <br /><br />We are working with our compute provider to improve our incident response and engagement time, improve early detection before they impact our customers, and ensure safe rollout should similar changes occur in the future. We recognize this was a significant outage to our users that rely on GitHub’s workloads and apologize for the impact this had.

    Resolved

  6. VantaVanta web app temporarily unavailable

    The Vanta web app was unavailable from 1:51 PM EST to 2:08 PM EST (17 minutes) due to a configuration change related to a third-party vendor outage. This change has been rolled back and the incident is now resolved.

    Resolved

  7. OneSignalDashboard failing to load

    Cloudflare is having an issue with a recent worker build that rolled out. We have rolled back to a previous build and dashboard.onesignal.com is working again. We will continue to follow along at https://www.cloudflarestatus.com

    Resolved

  8. BrazeUS02 Dashboard and SDK increased errors

    We can confirm service have continued to remain stable and the issue is now considered resolved. Impact: SDK: Engineers observed an increase in SDK errors between 10:25 ET and 10:36 ET. The SDK will automatically retry failed requests and no action is required. Dashboard: Engineers observed an increased in Dashboard errors between 10:26 ET and 10:43 ET. Dashboard users may have experienced timeouts and dashboard errors during this window. Message sending and the REST API were not impacted by this issue.

    Resolved

Older incidents