Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Mar 27, 2026

Mar 26, 2026

  1. InngestFunction run scheduling delays

    The incident is now resolved and the system is full operational. This was related to an issue caused by the part of the system powering the debounce feature. The internal event backlog is fully caught up and the two mitigations deployed have addressed the issue. The team is preparing a post-mortem to ensure this issue does not reoccur.

    Resolved

  2. GitHubDisruption with some GitHub services

    On March 22, 2026, between 09:05 UTC and 10:02 UTC, users may have experienced intermittent errors and increased latency when performing Git http read operations. On average, the error rate was 3.84% and peaked at 15.55% of requests to the service. The issue was caused by elevated latency in an internal authentication service within one of our regional clusters. We mitigated the issue by redirecting traffic away from the affected cluster at 09:39 UTC, after which error rates returned to normal. The incident was fully resolved at 10:02 UTC. <br /><br />We are working to scale the authentication service and reduce our time to detection and mitigation of issues like this one in the future.

    Resolved

  3. LeverLever Reporting Delays - Resolved

    This incident has been resolved. Impact Summary: Users may have experienced delays in getting up-to-date reporting data, specifically related to profile cards. Incident Duration: Started at approximately 4 am EST and resolution confirmed at 9 am EST An RCA will be provided within 7-10 business days

    Resolved

  4. ZapierIntermittent failures across tasks due to exhausted db connections for developercli

    We have successfully completed the recovery process for the intermittent task failures that occurred between March 24-26, 2026. Our team replayed all affected tasks, which have been successful with no data loss. **What Happened** Between March 24 at 11:02 AM UTC and March 26 at 2:04 PM UTC, some tasks failed for customers using Zaps that depend on our developercli service. **Resolution** We fixed the underlying issue causing this failure and completed a full replay of all impacted tasks. No action is needed on your side if affected — tasks have been automatically recovered and are now running normally. Thank you for your patience while we worked through this issue. If you do have any other questions or see any issues, please reach out to our Support team at zapier.com/app/get-help "zapier.com/app/get-help": http://zapier.com/app/get-help

    Resolved

  5. BitbucketDisrupted Bitbucket availability

    ### Summary On March 6, 2026, between 02:19 UTC and 04:00 UTC, Bitbucket Cloud experienced an incident impacting the web app, API, CLI, and Pipelines operations. This was caused by the Bitbucket application hitting a regional provisioning API rate limit with our hosting provider, preventing application workers from handling website traffic. The incident was detected within 1 minute by automated monitoring and mitigated by scaling systems down and then back up to full capacity which put Atlassian systems into a known good state. ### **IMPACT** The incident resulted in a Bitbucket Cloud services being unavailable for 1 hour and 6 minutes on March 6, 2026 between 02:19 UTC and 03:25 UTC, followed by degraded website performance until 04:00 UTC. During this time, customers were unable to access Bitbucket services including the web app, Git operations \(clone, push, pull over HTTPS and SSH\), API, and running builds in Pipelines. ### **ROOT CAUSE** The issue stemmed from a change to an internal deployment system that increased use of a platform credential service, hitting a quota with our hosting provider. This blocked Bitbucket services from deploying additional capacity because new application nodes request the credential service on startup and were rate limited. This caused degradation of Bitbucket experiences and more failed requests to Bitbucket Cloud’s website and public APIs. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** The incident response team manually scaled down Bitbucket services, then gradually scaled them back up while closely monitoring our quota. We simultaneously engaged with our hosting provider to temporarily increasing this limit to unblock bringing more Bitbucket service capacity online. We know that outages impact your productivity. While we have a number of testing and preventative processes in place, Bitbucket services lacked necessary boundaries to be resilient to upstream platform system changes. To help minimise the impact of breaking changes to our environments, we will implement additional preventative measures such as: * Improve monitoring of shared Atlassian platform resources. * Update Bitbucket application bootstrapping to prevent new capacity from failing during resource contention of shared platform services. * Reduce Bitbucket’s dependency on shared hosting provider services. * Deploy Bitbucket services across multiple regions to reduce single-region failure risk. 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

  6. BufferDegraded Performance

    The performance issues affecting Buffer have been resolved, and the app should now be operating normally. We apologise for any inconvenience caused by the slowness and thank you for your patience throughout the resolution process. If you experience any further issues, please let us know.

    Resolved

Mar 25, 2026

  1. HubSpot"HubSpot Email Reply Functionality Fails"

    Between 03:44 PM (UTC -04:00) and 04:39 PM (UTC -04:00), some customers in all affected regions experienced issues with Email replies. This was caused by a server impairment. As of 04:39 PM (UTC -04:00), our Email replies 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

Older incidents