Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Dec 6, 2025

Dec 5, 2025

  1. BitbucketBitbucket availability degraded

    ## Summary On November 11, 2025, between 16:25 and 19:13 UTC, Atlassian customers were unable to access Bitbucket Cloud services. Customers experienced a period of 1 hour and 16 minutes where performance was degraded and a period of 1 hour and 32 minutes where the Bitbucket Cloud website, APIs, and Git hosting were unavailable. The event was triggered by a code change that unintentionally impacted how we evaluate feature flags, impacting all customers. The incident was detected within 5 minutes by automated monitoring systems and mitigated by scaling multiple services and deploying a fix which put Atlassian systems into a known good state. The total time to full resolution was about 2 hours and 48 minutes. ### **IMPACT** The overall impact was between November 11, 2025, 16:25 UTC and November 11, 2025, 19:13 UTC on Bitbucket Cloud. Between 16:25 UTC and 16:50 UTC, users were seeing degraded experiences with both Git services and pull request experiences within the Bitbucket Cloud site. Starting at 16:50 UTC, users were unable to access Bitbucket Cloud and associated services entirely. ### **ROOT CAUSE** During a routine deployment, a code change had a negative impact on a component used for feature flag evaluation. To mitigate this issue the Bitbucket engineering team manually scaled up Git services. This inadvertently resulted in hitting a regional limit with our hosting provider, causing new Git service instances to fail. This ultimately led to degradation of multiple dependent services and an increased number of failed requests via Bitbucket Cloud’s website and public APIs. ### **ACTIONS TAKEN** Our team immediately began investigating the issue and testing various mitigations, including scaling the impacted services, in an effort to reduce the effects of the change. However, these efforts were unsuccessful due to an unexpected scaling limit imposed by our underlying hosting platform. Attempts to roll back the code change were also unsuccessful, as the platform’s scaling limit prevented new infrastructure from being provisioned during the rollback process. In particular, any attempts to provision new infrastructure caused a high volume of calls to occur in a short period, leading to failures, retries, and a feedback loop that worsened the situation. To address this, the team scaled down certain services to reduce load on the platform, which allowed for the successful deployment of a fix and restoration of service. Once the fix was in place, healthy services were scaled back up to meet customer demand. ### **REMEDIATION AND NEXT STEPS** We recognize the significant impact outages have on our customers’ productivity. Despite our robust testing and preventative measures, this particular issue related to feature flag evaluation was not detected in other environments and only became apparent under high load conditions that had not previously occurred. The incident has provided valuable information about our hosting platform’s scaling limits, and we are actively applying these learnings to enhance our resilience and response times. To help prevent similar incidents in the future, we have taken the following actions: * Enhanced the resiliency of the affected feature gate component to to prevent future changes from resulting in widespread service impact. * Updated application logic to prevent services from hitting these platform scaling limits. * Implemented additional safeguards to detect and handle platform-imposed limits proactively during deployment and rollback scenarios. We apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform’s performance and availability. Thanks, Atlassian Customer Support

    Resolved

  2. monday.comConnectivity Issues across accounts and devices

    On December 5th, starting around 03:50am EST, our customers experienced connectivity issues to the platform across all of our servers. In total, customers experienced 19 minutes of downtime on the AUS server, 48 minutes on the US server and 64 minutes on the EU server. **What caused it:** This incident was caused by a major outage at our third-party cloud service provider, Cloudflare. This outage led to widespread disruptions across many platforms, including [monday.com](http://monday.com/). **How we responded:** Our engineering teams acted immediately to stabilize the platform as soon as the issue was detected at 3:48am EST. As Cloudflare began to recover, we restored platform functionality in stages to ensure stability. By 4:11am EST, access to accounts in the AUS server was fully restored. By 4:40am EST, full access was restored to accounts on our US server. By 4:55am EST, the platform was fully operational across all servers. We continued to monitor the situation closely, and declared the incident resolved at 5:17 am EST. We kept customers informed through regular updates on our Status Page regularly until the incident was fully resolved. We sincerely apologize for any disruption this may have caused today. Thank you for your patience and understanding. Your engineering team at [monday.com](http://monday.com/)

    Resolved

  3. KlaviyoCloudflare incident disrupting Klaviyo

    Between 3:48am (US Eastern) and 4:10am (US Eastern) Cloudflare experienced an outage which affected Klaviyo. During this time, users were unable to access Klaviyo.com and all Klaviyo APIs. During this window, a number of services were affected. Subscription events and click tracking events were lost. Outbound campaign message sending was not affected. Klaviyo is now fully operational and this incident has been resolved. https://www.cloudflarestatus.com/incidents/k9ppxftx8bs5

    Resolved

  4. UdemySite is degraded

    The Cloudflare-related impact has been resolved. All systems are functioning as expected, and the incident is now cleared.

    Resolved

  5. Webflow[RESOLVED] Reports Of Issues Accessing Hosted Sites, Webflow.com, SSL Certificate Provisioning, and Form Submissions

    Following continued monitoring and confirmation from our upstream provider, we’ve verified that performance across all impacted services has returned to normal. This incident is now resolved. Services were affected between 08:48 and 09:11 UTC. We appreciate your patience and understanding while we worked with our upstream provider to resolve this issue.

    Resolved

  6. HubSpotHubSpot is currently unavailable for all customers.

    Between 04:55 PM (UTC +08:00) and 05:20 PM (UTC +08:00), all customers in all regions experienced issues with all impaired tools. This was caused by a Cloudflare outage. As of 05:20 PM (UTC +08:00), our all impaired tools are working properly and the incident has been fully resolved. HubSpot conducts a thorough review after each incident to understand the cause and prevent it from happening again. Learn more about HubSpot's commitment to reliability at www.HubSpot.com/reliability. The information on this page reflects our understanding of the incident and impact at the time of the update.

    Resolved

Dec 4, 2025

  1. KeeperEU data center login errors - Resolved

    On December 2, our **EU region** experienced an unexpected outage during planned infrastructure updates. The issue began at **1:24 PM PT** and service was fully restored by **4:10 PM PT**. **What Happened** During an update to our server configuration, a region-specific configuration error caused the EU environment to begin throwing API errors. Although the underlying issue was identified quickly, each corrective change required a full autoscaling group rollout \(up to 30 minutes per cycle\) which extended the total recovery time. **Resolution** Our engineering team implemented the necessary fixes and restored service. We have also updated our infrastructure-as-code to ensure this issue cannot recur in future deployments. We apologize for the disruption and appreciate your patience while we resolved the incident.

    Resolved

  2. SanitySecurity vulnerability identified with React Server Components

    We have completed dependency updates per guidance from Vercel and the React team. Sanity studio deployments are not affected and require no action. If your Studio is deployed using Next.js, please follow the recommended steps outlined here: https://vercel.com/changelog/cve-2025-55182#resolution.

    Resolved

  3. NeonIssues with logging in to the Neon console

    Between 14:33 UTC and 15:29 UTC December 04, 2025, customers may have experienced difficulty logging in to the Neon console. Database access and operations remained unaffected. The issue has been fully resolved. All affected components are operating normally again.

    Resolved

Older incidents