Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Apr 29, 2026

  1. SegmentAudience Preview Failures

    Summary: From 10:20 AM to 3:00 PM PDT on April 27th, a global Databricks Compute outage resulted in failed audience preview queries across external workspaces. Details: The disruption was caused by an upstream infrastructure failure at Databricks, which prevented some preview queries from executing successfully. This issue was localized to the dashboard preview tool; real-time event delivery and audience activations were not impacted. Resolution: The underlying compute issue has been resolved by the vendor. We have confirmed that preview functionality is fully restored and operating normally.

    Resolved

  2. TrueLayerEUR Payouts Degraded Performance

    We experienced an issue with EUR payouts. Clients may have seen delayed creation and settlement of payouts. The issue is resolved and normal service is restored. Impact start time: 29/04/2026, 10:35 UTC Impact end time: 29/04/2026, 10:45 UTC Client actions: None

    Resolved

  3. HashiCorpHCP Boundary control plane degradation

    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. HootsuiteAssignment issues in Inbox 2.0

    This incident has been resolved. The Inbox 2.0 assignment functionality is now loading correctly for all users. We apologize for any inconvenience this may have caused.

    Resolved

  5. LoomDegraded performance of Loom app

    The Team has identified the root cause and the issue has now been resolved, and the impacted services are operating normally. Team will continue to monitor the impacted services.

    Resolved

Apr 28, 2026

  1. InngestIncreased function execution latency

    Performance on all shards is back to normal levels. The degradation was caused by a change that aimed to improve concurrency metrics for Inngest accounts. The change, while out for a full 24 hours and fairly benign, began to compound and produced slowness for some queue shards within our system earlier today. We have reverted that change and are working to understand the performance impact of this change.

    Resolved

  2. TrueLayerDelayed Payments and Payout Settlements

    You may have experienced delays in Payment and Payout settlement during the timeframe below. This has now been resolved, Payments and Payouts are settling in a timely manner. Impact start time: 28/04/2026, 21:00 UTC Impact end time: 28/04/2026, 21:40 UTC Client actions: None

    Resolved

  3. ZapierService delays and timeouts across Zapier.com

    The performance issues that caused delays and timeouts on Zapier.com "Zapier.com": http://Zapier.com have now been resolved. Our systems have remained stable, and signing in, loading account information, and running Zaps should behave normally. During the incident, some customers may have seen slower responses, failed actions, or delayed trigger processing while we reduced load and shipped the fix. Everything should now be caught up; if you still see anything unexpected, try running your Zap again. If you need help with a specific Zap or account, contact our Support team: https://zapier.com/app/get-help

    Resolved

  4. SupabaseEdge Functions: Several users reported 503 errors with SUPABASE_EDGE_RUNTIME_ERROR error code

    Incident Summary A health check designed to prevent Out-of-Memory (OOM) conditions began closing some incoming connections, which led to 503 errors for a subset of users. These errors were initially surfaced under a generic SUPABASE_EDGE_RUNTIME_ERROR code. Timeline & Actions Sunday, 26: Issue detected as user reports of 503 errors increased. Investigation into root cause began. Monday, 27: Introduced a more accurate error code (SUPABASE_EDGE_RUNTIME_SERVICE_DEGRADED) and implemented infrastructure changes to mitigate impact. Tuesday, 28: Adjusted conditions for returning 503 responses to be less aggressive. Prepared a “retry-on-degraded” mechanism (not yet deployed). Current Status Mitigations are in place and improvements to error handling are ongoing. Further resilience enhancements will be deployed shortly.

    Resolved

  5. ZapierUsers are unable to access Admin Center.

    We can confirm that the Admin Center is now loading as expected, and the issue is now resolved. If you're still unable to load the page, you may need to reload the page and/or clear your browser's cookies and cache. If you're experiencing any issues with this was not resolved by clearing browser cache and cookies, please reach out to our support team here: https://zapier.com/app/get-help

    Resolved

Older incidents