Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Apr 15, 2026

  1. StripeCanadian payouts delay

    We have confirmed with our banking partner that the issue has been resolved. All impacted Canadian payouts scheduled for April 14th have successfully posted on the same day. Thank you for your patience.

    Resolved

  2. Webflow[RESOLVED] Reports of intermittent 5xx errors on some hosted sites and issues accessing Webflow services

    This incident that started at 14:15 UTC on April 14th is now resolved. By 16:21 UTC on April 14th, the issue was mitigated for the overwhelming majority of customers (~96%). For a full timeline, details on root cause and action items, you can refer to the following blog post prepared by our CTO, Allan Leinwand: webflow.com/blog/april-14-webflow-incident-report We know this incident caused serious disruption, and sincerely appreciate your patience while we worked to resolve it.

    Resolved

  3. LaunchDarklyDegraded connectivity for server-side SDKs in EU region

    Between approximately 9:37 PM and 9:46 PM PT on April 9, 2026, some customers using server-side SDKs in the EU region may have experienced longer than normal initialization times or timeouts when connecting to LaunchDarkly. The issue resolved. No action is required from customers. Server-side SDKs automatically reconnect and recover from transient connectivity issues.

    Resolved

  4. Liquid WebSecurity Hardening - Magento “PolyShell” File Upload Vulnerability Enhancements

    Our engineering teams have completed the planned security enhancements and hardening efforts related to the Magento "PolyShell" unrestricted file upload vulnerability across our managed environment. With these measures now fully implemented, we consider this incident resolved. As security is a shared responsibility, we recommend that customers review their Magento installations, ensure all updates and patches are applied, and take additional steps to further secure their applications. If you have any questions or require assistance, please reach out via chat or support case.

    Resolved

  5. SnowflakeAzure - East US 2 (Virginia): INC0155020

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

    Resolved

Apr 14, 2026

  1. TrueLayerDelayed Settlement for EUR Payments

    We experienced a degraded performance on our Payments products. You may have experienced delays in EUR Payment settlement. The service has recovered and payments are settling in a timely manner. Impact start time: 14/04/2026, 21:03 UTC Impact end time: 14/04/2026, 21:49 UTC Client actions: None

    Resolved

  2. ZapierSlack Triggerred Zaps: Delays in triggering

    We have successfully resolved the intermittent delays affecting Slack-triggered Zaps that began around Friday, April 11th. Our engineering team identified and deployed a fix, and Slack triggers are now operating as expected. If you continue to experience any delays with your Slack-triggered Zaps or have any questions, please don't hesitate to contact our support team at https://zapier.com/app/get-help We appreciate your patience while we worked through this issue.

    Resolved

  3. GitHubProblems with third-party Claude and Codex Agent sessions not being listed in the agents tab dashboard

    On April 9, 2026, between 22:59 UTC and April 10, 2026, 13:24 UTC, the Copilot Mission Control service was degraded and did not display Claude and Codex Cloud Agent sessions in the agents tab dashboard. Customers were unable to see, list, or manage their third party agent sessions during this period. The underlying agent sessions continued to function normally. This was a visibility and management issue only, and no HTTP errors were generated. The API returned successful responses with incomplete results, with an average error rate of 0% and a maximum error rate of 0%. This was due to a code change that introduced a filter which inadvertently excluded third party agent sessions.<br /><br />We mitigated the incident by reverting the problematic code change and deploying the fix to production.<br /><br />We are working to add automated monitoring for dashboard content visibility and improve integration test coverage for third party agent session listing to reduce our time to detection and mitigation of issues like this one in the future.

    Resolved

  4. ConfluenceDisrupted Rovo availability for Automation rules

    On April 14, 2026, affected users may have experienced some service disruption with automation rules that use Rovo agents. The issue has now been resolved, and the service is operating normally for all affected customers.

    Resolved

  5. JiraDisrupted Rovo availability for Automation rules

    On April 14, 2026, affected users may have experienced some service disruption with automation rules that use Rovo agents. The issue has now been resolved, and the service is operating normally for all affected customers.

    Resolved

  6. Intercom - USFin is experiencing issues

    The issue affecting Fin AI Agent and Fin Voice in the US region has been resolved. All services are operating normally. What happened:  Between 11:18 and 12:20 UTC on April 14, 2026, a database issue prevented Fin from generating conversation parts in the US region. This affected Fin AI Agent across Messenger, Inbox, and Workflows. Fin Voice experienced an issue where it was unable to hand over conversations to teammates and would terminate calls with an error message at the escalation point. At 12:20 UTC we implemented a mitigation to enable Fin to start delivering answers to customers again. New conversations, or conversations where a customer messaged to Fin again would receive an answer but pre-existing conversations or conversations that had been actioned by a teammate would not receive a reply. At this point escalations from the Fin AI Agent and Fin Voice to customer support teams were not functioning as expected.  At 13:00 UTC Fin AI Agent and Fin Voice were functioning as normal for new conversations. At approximately 13:05 UTC we retried any pending Fin conversations that had not yet been actioned by a teammate on workspaces. EU and AU regions were not impacted by this incident. What's next: Reporting data for affected customer workspaces may be incomplete for the duration of the incident window. We are investigating a method for backfilling this data and will provide a follow-up update once that is complete. A full root cause analysis will be forthcoming once all details of the incident have been established. We apologize for the disruption to your business.

    Resolved

  7. RenderSome Render Workflows tasks are not being scheduled

    Affected customers have been contacted directly. If you would like more details, please contact support at [support@render.com](mailto:support@render.com) or reach out through the chat widget in the Render dashboard.

    Resolved

  8. BufferIssue Publishing PDF Carousel Posts to LinkedIn

    The issues with Publishing PDF Carousel Posts have been fully resolved, and this is functioning as expected again. If you encounter any further problems, please don’t hesitate to reach out to our team.

    Resolved

  9. StripeElevated Swish errors

    Between 10:11 - 10:50 UTC there was a disruption with the Swish payment method causing increased error rates for Swish transactions. The issue was external to Stripe and is now resolved.

    Resolved

  10. New RelicIssue when querying live edge data in the US region

    Between 10:30 AM and 2:40 PM UTC on April 13th, some customers may have experienced an issue to query live edge data and some customers may have noticed stopped synthetic monitors in the US region. The issue is now resolved and impacted services have returned to normal operations.

    Resolved

Older incidents