Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Jul 4, 2025

Jul 3, 2025

  1. KlaviyoDuplicate Flow Sends

    The team continues to work through the appropriate adjustments to billing as a result of these duplicate sends. We expect to follow up with impacted customers early next week with more information once this work has been completed.

    Resolved

  2. Cockroach LabsCluster operations impaired

    We have corrected a misconfiguration which was preventing cluster operations from succeeding. We are monitoring the success of cluster operations already in progress and new operations.

    Resolved

  3. IdeogramOutage

    This incident has been resolved.

    Resolved

Jul 2, 2025

  1. UdemySite is degraded

    We have resolved the stability issue on our site, and performance is back to normal. We appreciate your patience.

    Resolved

Jul 1, 2025

  1. IdeogramOutage

    This incident has been resolved.

    Resolved

Jun 30, 2025

Jun 29, 2025

Jun 28, 2025

  1. Voyage AIIncreased authentication errors

    We observed a spike in mistaken 401 errors starting at 4:50 PM PDT, peaking at 90% from 5:13–5:17 PM PDT. A brief 1.5% 500 error rate occurred at 5:50 PM PDT. The issue was due to the work identity binding missing from a manual operation. The issue has been resolved and system is stable now.

    Resolved

Jun 27, 2025

  1. AsanaElevated application and API/Mobile errors

    **Incident**: A configuration change unintentionally blocked internal network access between application components. This change was identified as the cause of downtime and reverted.  **Impact**: The Asana App and API were unavailable for 24 minutes. App and API traffic recovered over the next 5 minutes, and Automations & Background Actions recovered over 10 minutes.  **Moving forward**: We have completed a redesign of our core application architecture to better protect our services from disruption by segmentation into independent sections, or "cells." We are considering ways we can leverage this architecture to roll out configuration changes like the one which triggered this incident more gradually and carefully across our systems to ensure safety & stability. Our metric considers a weighted average of uptime experienced by users at each data center. The number of minutes of downtime shown reflects this weighted average.

    Resolved

  2. BitbucketIntermittent issues affecting Bitbucket cloud

    ### **SUMMARY** On June 13, 2025, between 08:58 UTC and 09:34 UTC, a subset of Bitbucket website and API users experienced an error page when attempting to load the website or make API requests. This was caused by high resource usage on a core Bitbucket service’s database, leading to an increase in query response times. A reoccurrence of the issue impacted website reliability again between 12:24 UTC and 14:02 UTC. The incident was detected within 6 minutes by monitoring and was fully mitigated by running scaling database capacity, running database maintenance operations, and removing a faulty read replica, which put Atlassian systems into a known good state. The total time to resolution was about 36 minutes for the first occurrence and one hour and 38 minutes for the second occurrence. ### **IMPACT** The total window during which we saw the impact was June 13, 2025, between 08:58 UTC and 14:02 UTC. The incident caused service disruption to customers trying to access the [Bitbucket.org](http://bitbucket.org/) website and APIs. Customers may have seen a “something went wrong” error page when trying to access the website or APIs. Git operations over SSH and HTTPS were not impacted. ### **ROOT CAUSE** The issue originated from a problem with query plan execution time on read replica instances. This led to increased query latency, spikes in CPU usage, and ultimately resulted in longer request times. As a result, the influx of incoming requests to Bitbucket led to a saturation of connections. This resulted in Bitbucket web requests returning slowly or showing an error page. ### **REMEDIAL ACTION PLAN & NEXT STEPS** We fully understand that outages impact your productivity. While we have a number of testing and preventative processes in place, this specific issue wasn’t identified with existing coverage. We are prioritizing the following improvement actions designed to avoid repeating this type of incident: * Continue to improve database resiliency and read replica routing for Bitbucket Cloud’s dependencies * Improve database monitoring and failover speed to reduce time to recovery * Run database maintenance tasks and improve process to discover and upgrade all databases to well known versions We apologize to customers whose services were impacted during this incident; we are taking steps to improve the platform’s performance and availability. Thanks, Atlassian Customer Support

    Resolved

Jun 26, 2025

Older incidents