Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Jul 26, 2026

  1. monday.comDelay in Automations

    There was an automations incident in the AUS Region. This caused some automation delays during this time. It has been successfully resolved.

    Resolved

  2. CodecovPR Notifications delayed

    Server OOM caused drop in PR notifications between 10:48PM ET to 11:20PM ET. PRs expecting notifications during that period have now been manually sent.

    Resolved

Jul 25, 2026

  1. LiveKitIncreased egress latency and media connection interruptions in London region

    On July 23, between 07:50 and 08:07 UTC, media servers in our London region experienced a host-level network fault, causing them to fail health checks and restart. Users connected to these servers may have experienced brief connection interruptions, and egress operations may have seen increased latency. The affected servers were removed and replaced. The region has been operating normally since.

    Resolved

  2. AmplitudeIntermittent Connectivity Issues

    Between approximately 2026-07-24 03:39–05:00 PT (10:39–12:00 UTC), some customers may have experienced intermittent connectivity issues while accessing Amplitude or sending data, including connection timeouts. This was caused by an AWS networking disruption in the us-west-2 region affecting multiple upstream AWS services. The issue originated outside of Amplitude's infrastructure and was resolved by AWS. Services: - Our SDKs queue undelivered events on-device and automatically retry sending them, so we expect minimal to no data loss from this incident. No ingested data was lost and no action is required. - Experiment/Flag evaluations failed and return 503s due to service unavailability. There is no data loss.

    Resolved

  3. SanityElevated errors serving images and assets

    Between approximately 23:16 UTC on July 24 and 00:10 UTC on July 25, some requests for images and assets served from cdn.sanity.io returned errors or loaded slowly for users in North America and Europe. Image and asset delivery has since returned to normal operation. The Content APIs (api.sanity.io, apicdn.sanity.io) and Studio editing were not affected.

    Resolved

Jul 24, 2026

  1. GitHubDisruption with actions hosted runners

    On July 22, 2026, between 19:36 UTC and 22:04 UTC, GitHub Actions experienced delayed and failed job starts on GitHub-hosted runners. The incident was caused by an unhealthy state in a backend data service responsible for provisioning hosted runners, preventing runner acquisition for a subset of workloads. During most of the incident, approximately 15% of workflow runs on hosted runners were delayed by more than 5 minutes, while roughly 1% failed to start.<br /><br />At 21:49 UTC, we restored the health of the backend data replication system, allowing provisioning to recover and the accumulated workflow backlog to drain. Service performance then returned to expected levels. We are improving provisioning-service resiliency, workload distribution, and capacity balancing to reduce the likelihood and impact of similar incidents.

    Resolved

  2. ZillizElevated errors on control plane API (July 22)

    This incident was fully resolved at 10:07 UTC on July 22, 2026. Control plane API requests have been operating normally since. Running clusters, data access, and query traffic were not affected at any point.

    Resolved

  3. BrazeAWS Networking Disruption in US-WEST-2 (Resolved)

    At approximately 7:30 AM ET, we became aware of an AWS networking outage in the US-WEST-2 region affecting network connectivity between 6:55 AM ET and 8:00 AM ET. AWS has since resolved the underlying issue. During the impact window, some customers may have experienced intermittent delays and latency in email delivery. Mail is now being delivered normally. As queue depth increased, some customers may have experienced residual delays in message delivery. These delays have been resolved as of 2:40 PM ET today. This disruption originated within AWS infrastructure and was not caused by any component of the Braze platform. For further details on the AWS incident, please refer to the AWS status page: https://health.aws.amazon.com/health/status

    Resolved

  4. AkamaiEdge Delivery Issues

    We can confirm that the issue was mitigated at 12:00 UTC on July 24, 2026 and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a700001KQ2QQCA1 or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.

    Resolved

  5. Retoolretool-email unavailable

    Some Retool Emails failed with a "Disabled for sending spam" error due to an issue with our upstream email provider. The sending domain has since been restored, and email delivery is operating normally. We've also added safeguards to prevent recurrence. We apologize for the disruption.

    Resolved

  6. CircleCIGitHub service degradation may impact customers using GitHub

    The issue impacting customers who use GitHub as their VCS while GitHub was undergoing a service degradation (https://www.githubstatus.com/incidents/yjysg0xrl67m) has now been resolved. GitHub has resolved the underlying issue and the affected functionality has returned to normal. We thank you for your patience.

    Resolved

  7. JamfJamf Trust app deactivation affecting all customers

    The issue has been resolved. The Jamf Trust app will no longer be unexpectedly deactivated on devices. Remaining Customer Impact: For Jamf Trust apps that had been previously deactivated, they will need to be reactivated. Depending on deployment configuration this may be automatic or require manual reactivation. For assistance with reactivating devices, please login to the Jamf Account portal and create a ticket (Contact Support) referencing Jamf Trust app deactivation. While the Jamf Trust app is deactivated, its protections — including Zero Trust Network Access (ZTNA) and content filtering — are not enforced. This affects devices on all platforms: iOS, macOS, Android, and Windows. We apologize for any inconvenience.

    Resolved

Older incidents