Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Sep 9, 2026

  1. SnowflakeINC20000188

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

    Resolved

  2. GitHubIncident with Grok Copilot AI Model Provider

    Between 13:22 and 17:11 UTC on September 03, 2026, GitHub Copilot experienced degradation affecting several Grok models, including Grok 4.5 and Grok 4.6. Users encountered elevated error rates, but other models were not affected. The degradation was caused by an issue with an upstream model provider. GitHub engineers detected the issue through automated monitoring, displayed in-product warnings for the affected models, and coordinated with the provider. Service returned to normal after the provider implemented a mitigation.

    Resolved

  3. GitHubDisruption with Copilot Code Review

    On September 4, 2026, between 20:04 and 22:26 UTC, GitHub Copilot code review experienced an increased failure rate. Affected pull request reviews failed to complete or post review comments.<br /><br />The incident was caused by a change to the service’s authentication permissions that prevented it from submitting affected reviews to the GitHub API. We reverted the change and restored normal operation by 22:26 UTC.<br /><br />We apologize for the disruption.

    Resolved

  4. SnykImports and PR Checks Degraded

    Snyk engineers have deployed the mitigation to all environments, which has resolved the Invalid Credentials errors for customers using the GitHub Cloud integration. No further errors observed during the monitoring period. The incident has been stood down.

    Resolved

  5. Intercom - AUMessenger Help Articles not displaying

    This issue should now be resolved and all services are restored to normal functionality. Please don’t hesitate to reach out to team@fin.: mailto:team@fin.aiai if you have any further questions or if you’re still seeing any unexpected behaviour

    Resolved

  6. Intercom - EUMessenger Help Articles not displaying

    This issue should now be resolved and all services are restored to normal functionality. Please don’t hesitate to reach out to team@fin.: mailto:team@fin.aiai if you have any further questions or if you’re still seeing any unexpected behaviour

    Resolved

  7. Intercom - USMessenger Help Articles not displaying

    This issue should now be resolved and all services are restored to normal functionality. Please don’t hesitate to reach out to team@fin.: mailto:team@fin.aiai if you have any further questions or if you’re still seeing any unexpected behaviour

    Resolved

  8. JamfFailure in a shared authentication component caused configuration profile delivery and MDM device communication to return errors for managed Apple devices in the US and EU

    Symptoms: Partial interruption with configuration profile delivery and MDM device communication. Managed devices fail to receive or update configuration profiles, and MDM commands and device check-ins fail. Affected devices remain in a pending state and do not apply configuration changes. Customer Impact: * Affected Services: Configuration profile delivery to managed devices; MDM device communication (check-ins and commands) * Affected Regions: US and EU * Business Impact: Service degradation — configuration changes not applied for the duration. No data loss and no incorrect changes to device configuration. Actions: Jamf engineering identified a failure in a shared authentication component used by configuration profile delivery and MDM communication, and restored service by reloading that component and cycling the affected application instances. Workaround/Customer Actions: No customer action required. Devices retry automatically and apply pending configuration profiles once requests succeed.

    Resolved

  9. UpstashIntermittent DNS Resolution Errors for Upstash Vector in US East (us-east-1)

    Upstash Vector experienced a brief DNS resolution issue in the US East (us-east-1) region lasting approximately 20 minutes. During this period, new DNS resolution attempts may have failed. Existing connections and clients with cached DNS records were not affected. The issue has been resolved, and DNS resolution is operating normally.

    Resolved

  10. SnowflakeINC20000190

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

    Resolved

  11. SupabaseBrief connection disruptions in us-east-1 (N. Virginia)

    Between 05:50–06:05 UTC some customer using Supavisor in us-east-1 may have experienced brief dropped connections or connection disruptions. This issue was caused by an unexpected restart of Supavisor instances in the affected cluster. We apologize for any disruption caused.

    Resolved

Sep 8, 2026

  1. LiveKitIdentified increased agent join latencies in eu-central

    **Root Cause** A configuration change introduced a formatting error in the startup settings for the server pools that run hosted agents in our eu-central region. Newly provisioned servers failed to start, so the region could not add capacity. Agents that were already running were unaffected, but new agent deployments, version rollouts, and automatic scale-ups were delayed or stuck pending until the change was reverted. **Timeline \(UTC\)** `2026-09-04 23:56` - Configuration change deployed. The error only affected newly provisioned servers, so there was no immediate impact. `2026-09-05 18:07` - New servers began failing to start. Impact begins, intermittent at first. `2026-09-05 22:23` - Our monitoring alerted us to agent deployments stuck pending and we began investigating. `2026-09-06 00:50` - We identified the malformed startup configuration and reverted the change. `2026-09-06 01:17` - New capacity provisioned successfully, all pending deployments recovered, and we validated the fix. **Scope of Impact** Limited to hosted agents in our eu-central region. During the impact window, new agent deployments and rollouts were delayed or stuck pending, and automatic scale-up was blocked. Agents already running continued to serve sessions normally, and we estimate that, at the peak, roughly 1% of agent instances in the region were affected. No other regions or products were affected. **Mitigations and Follow-ups** * The faulty configuration change was reverted and provisioning has been stable since. * We are adding alerting for new servers that fail to start via this failure mode, which today fails silently. This lets us detect this class of failure directly and validate future changes to server provisioning quickly. We appreciate your understanding and are committed to continuously improving our platform's reliability. If you have any questions, please reach out to our support team.

    Resolved

  2. TrueLayerEUR Payouts Delayed Settlement

    We experienced a service degradation with EUR payouts. Clients may have seen delayed payment settlements. The service degradation impacting EUR payouts has been resolved, and SEPA Instant processing has fully recovered. Transactions that were rerouted to standard SEPA Credit Transfer during the degraded performance window will settle according to standard scheme processing timelines Impact start time: 08/09/2026, 20:58 UTC Impact end time: 08/09/2026, 21:30 UTC Client actions: None

    Resolved

Older incidents