Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Jul 31, 2026

  1. KeeperEU KeeperPAM router and gateway connections

    # Post-Incident Report **July 31, 2026** ## Summary On July 30, 2026 at 11:33 PM CT, the KeeperPAM connection routing service in the EU region started throwing errors. The Router/Gateway errors lasted approximately 12 hours and 45 minutes, with full service restored at approximately 12:18 PM CT on July 31. During this window, the main Keeper EU platform \(vault access, authentication, and all other Keeper services\) remained fully operational throughout. ## What Happened On July 22, a routine deployment to our connection routing service \(“Keeper Router”\) included an updated dependency that changed how the service retrieves its startup configuration. A misconfiguration in the endpoint caused EU region to look for a FIPS endpoints, which are not available. As a result, when service containers in the EU region restarted following the deployment, they were unable to retrieve their startup configuration and entered a failed state. Two factors allowed this failure to go undetected for over a week. First, existing containers continued serving traffic while replacement containers silently failed to start, so there was no immediate customer impact from the July 22 deployment. QA also passed all production verification tests. Second, the configuration-load failure was logged at INFO level rather than ERROR or CRITICAL, so no PagerDuty alerts were generated. On the night of July 30, the last healthy containers cycled out, the service's load balancer had zero healthy targets, and the endpoint began returning HTTP 503 errors. Automated health-check monitoring detected the outage within seconds and paged our on-call team. ## What We're Changing 1. **Alerting on failed container rollovers.** We are deploying CloudWatch alarms across all regions and environments that fire when container tasks repeatedly fail to start, to detect silent deployment failures. 2. **Log severity for startup failures.** Any failure to load required startup configuration will now log at ERROR/CRITICAL severity instead of INFO which trigger the proper actionable alerts. We apologize to our EU customers for the disruption.

    Resolved

  2. SnowflakeINC20000106

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

    Resolved

  3. GrafanaPartial Read Outage for Loki in prod-us-east-4

    We are investigating a partial read outage affecting Loki in prod-us-east-4. Between 19:41 UTC and 19:50 UTC, a significant portion of read queries may have failed or returned errors. The issue has been identified and service has been restored. We are continuing to investigate the underlying cause and will provide additional information as it becomes available.

    Resolved

  4. BrazeEU02 Currents Data Latency

    This incident is resolved. As of 15:18 ET / 19:18 UTC, we have fully processed the backlog of jobs, and our EU02 Currents connectors are all again processing within normal latency ranges. No data was lost, and all Currents events have been sent to their destinations.

    Resolved

  5. ElevenLabsSIP call failures

    After our recent mitigation steps, our engineers have traced SIP call failure rate as it has returned to baseline. We will publish a complete root cause analysis shortly.

    Resolved

  6. LinodeService Issue - Host Job Performance Degradation - Several Regions

    On 27 July 2026 at 3:30 UTC, Akamai observed an increase in errors when connecting to the Linode hosting database, primarily affecting Block Storage volume attachments. This resulted in host job failures and limited customer impact, with some users experiencing error messages and interrupted workflows. Elevated timeout rates were noted in logs for certain data center locations, coinciding with the incremental rollout of a new feature flag. Initial investigation revealed intermittent packet drops from the database proxy to client hosts during the TLS handshake. The current theory suggests that a DDoS-protection limit related to path MTU packet too big ICMP messages was reached. When the proxy sent TCP packets with a large MTU, the expected ICMP messages were dropped by Dallas gateway routers due to exceeding the configured allowable rate. This caused database proxy TCP connections to timeout to Compute Hosts. The issue was triggered by the enablement of the new feature flag, which changed the routing path and removed MTU clamping before packets reached the gateways. To mitigate the issue, Akamai rolled back the recent network change across affected Compute sites, starting at 20:50 UTC. As of 22:57 UTC, the rate of service restarts returned to pre-incident levels. Akamai is also planning a change to increase the allowable threshold for packet too big ICMP messages. This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing and any information herein is subject to change.

    Resolved

  7. BitbucketBitBucket Site fails to Load

    On July 31, 2026, affected Bitbucket Cloud users for some customers may have experienced failures loading the site and impacts to associated pipelines. The issue has now been resolved, and the service is operating normally for all affected customers.

    Resolved

  8. SupabaseIssues with Edge Function Deployment

    A preventative fix (Supabase CLI v2.111.0 ) has been released to ensure that new Function deployments are not affected. As the underlying issue has been addressed and new deployments should no longer be affected, we are resolving this incident. All impacted users are now able to re-deploy their Functions again. In exceptional cases, Support will continue working directly with customers who require additional remediation.

    Resolved

  9. MakeScenarios execution degraded

    We’re reaching out to let you know that the issue affecting scenario execution has been resolved, and most of the previously disabled scenarios have been re-enabled. Remaining affected scenarios will be handled individually. System execution has stabilized and normal operations have resumed.

    Resolved

  10. Neones-2102196

    Between 14:47 UTC, July 30, 2026, and 12:26 UTC, July 31, 2026, a subset of customers may have experienced errors during account creation. The issue only impacted new account registrations. The issue has been fully resolved, and all services are operating normally. We apologize for any inconvenience this may have caused. If you require further details about this incident, please submit a support ticket.

    Resolved

  11. HashiCorpapp.terraform.io is not loading

    Our Engineering team has resolved the issue with app.terraform.io "app.terraform.io": http://app.terraform.io loading correctly. It should now be operating normally. If you continue to experience any problems, please open a ticket with our support team.

    Resolved

Jul 30, 2026

Older incidents