Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

May 13, 2026

  1. CloudsmithIssue with Cloudsmith webhooks

    We've identified and mitigated the issue affecting webhooks. Webhook delivery is now recovering, and queued events will begin to backfill automatically. During this period, you may see an increased volume of webhook activity as pending events are processed. We'll continue to monitor the recovery closely and provide further updates if needed.

    Resolved

  2. SupabaseEdge Traffic Issues

    We've determined that the connectivity issues are isolated to users accessing Supabase through Mullvad VPN and potentially other VPN providers. The root cause appears to be network disruptions involving a specific colocation/transit provider used by Mullvad, rather than an issue with Supabase or Cloudflare infrastructure. We've reached out to Mullvad support, but as this is dependent on external providers, there are no further mitigation steps we can take internally. Users experiencing issues are advised to avoid affected VPN networks or contact their VPN provider directly for support. The incident is now resolved

    Resolved

  3. SnykReporting PDF Degraded

    Snyk engineers have successfully deployed a mitigation to address the reporting issues. PDF reports are now generating as expected. We have concluded the incident response.

    Resolved

  4. PostHogError Tracking Ingestion Lag

    Incident came from a caching issue on proguard mappings, a fix has been deployed and the ingestion lag is now back to normal.

    Resolved

  5. GitHubCCR and CCA failing to start for PR comments

    On May 7, 2026, between 04:12 UTC and 06:13 UTC, Copilot Cloud Agent and Copilot Code Review Agent sessions for pull requests were delayed or failed to start.<br /><br />The issue was caused by follow-up recovery work from a separate Pull Requests incident (https://www.githubstatus.com/incidents/f5pb5d5mr9yh). As part of that recovery, we ran a large database migration, which caused replication delays on several replica hosts.<br /><br />Although those replicas were not serving user traffic, our safeguards correctly treated the elevated replication lag as a signal to slow down writes to the affected database cluster. As a result, some pull request background processing was temporarily delayed. That processing is responsible for sending the internal events that Copilot agents use to begin work, so affected agents did not start until the database replicas caught up.<br /><br />The system recovered once replication lag returned to normal and pull request processing resumed. We are reviewing how this safeguard interacts with recovery migrations so we can reduce the chance of similar secondary impact during future incident recovery work.

    Resolved

  6. HootsuiteHootsuite Inbox - Delayed messages

    We can confirm that the issues related to delays experienced within the Hootsuite Inbox have been resolved. Thanks for your patience while our team sorted this out.

    Resolved

  7. ZapierFacebook Lead Ads Error: "Unsuported get request. Object with ID "..." does not exist, cannot be loaded due to missing permissions or does not support this operation"

    Between approximately 1:20 AM UTC and 10:38 AM UTC on May 13, 2026, Zaps using Facebook Lead Ads experienced failures due to an upstream issue with Meta’s Facebook Lead Ads API. During this time, Facebook Lead Ads Zaps were unable to process new leads. Some Zaps may have been automatically turned off due to repeated errors. Meta has resolved the issue on their end, and error rates have returned to normal. Your Zaps should now be functioning as expected, and new leads from Facebook will resume flowing through normally. Zaps that were automatically turned off have been re-enabled, and failed runs have been replayed. If you’re still experiencing issues, contact Support: https://zapier.com/app/get-help

    Resolved

  8. BuildKiteError rates increasing

    Additional capacity was added to our redis caches. This triggered a failover between UTC 15:10 - 15:14 and there was a spike of errors on the REST and GraphQL APIs. Customers would have seen some errors in the Buildkite UI during this period as well. We have been monitoring the situation since then and things have returned to baseline.

    Resolved

  9. LinodeConnectivity Issue - NL-AMS

    We haven’t observed any additional connectivity issues in our NL-AMS data center, and will now consider this incident resolved. If you continue to experience problems, please <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance.

    Resolved

  10. TrueLayer EUR Payments Degraded Performance

    We experienced a degraded performance on our Payments products. You may have experienced delays in EUR Payment settlement. Regular processing timings have resumed. Impact start time: 13/05/2026, 07:50 UTC Impact end time: 13/05/2026, 08:02 UTC Client actions: None

    Resolved

  11. BuildKiteAWS us-east-1 single availability zone outage

    ## Service impact On 8th May 2026 UTC, between 00:00 and 07:30 UTC, some customers would have seen intermittent errors and latency spikes across many areas of the platform. ## Incident Summary The AWS availability zone incident in `use1-az4` triggered our automatic availability failover mechanisms on database and cache clusters, as per AZ-failure tolerant design. During the failover we saw some isolated request errors that were handled by client-side retries in the agent. Customer workloads were either entirely undisrupted or in the worst case saw elevated latency for a period of up to 5 minutes. Throughout the incident we monitored customer impact and prepared additional resources in a healthy availability zone to manually failover to if the automated systems proved insufficient. These were not necessary, and all our infrastructure self healed.

    Resolved

  12. SnowflakeAzure - West US 2 (Washington): INC0156645

    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/INC0156645](https://community.snowflake.com/s/article/INC0156645)

    Resolved

May 12, 2026

Older incidents