Brev - Notice history

https://app.brev.io - Operational

100.0% uptime
Mar 2026 · 100.0%Apr · 100.0%May · 100.0%
Mar 2026
Apr 2026
May 2026

Notice history

View current status

May 2026

Users experiencing issues accessing multiple Atlassian products
ResolvedMajor outage6 minutes
  • UpdateUTC

    Summary

    On May 14, 2026, between 04:30 and 05:26 UTC, Atlassian customers experienced widespread service disruption across multiple Atlassian Cloud products. The issue was caused by a race condition in our internal deployment orchestration platform during a routine rollback operation of a core identity service in the us-east region. This race condition resulted in insufficient capacity for the identity service in the affected region which started returning errors to dependent products. The incident was detected within a minute by automated monitoring systems and mitigated in 56 minutes.

    IMPACT

    During the incident, customers attempting to access Atlassian Cloud products in the us-east region experienced authentication and permission failures and were unable to access services. Customers also experienced errors when accessing the support portal until Atlassian fell back to an alternate support method. This was caused by a core identity service in the us-east region becoming unavailable. Affected products included Atlassian Administration, Atlassian Analytics, Bitbucket, Compass, Confluence, Jira, Jira Product Discovery, Jira Service Management and Trello. Some users outside us-east may have been affected in certain scenarios.

    ROOT CAUSE

    The incident was caused by a race condition in our internal deployment orchestration platform during a routine rollback operation of a core identity service in the us-east region. This race condition resulted in insufficient capacity for the identity service in the affected region which started returning errors to dependent products.

    REMEDIAL ACTIONS PLAN & NEXT STEPS

    We know that outages impact your productivity. Atlassian is prioritizing the following actions to help prevent similar incidents in future:

    • Refine deployment orchestration safeguards

      • Harden our deployment platform to prevent similar race conditions or resulting capacity loss during a rollback operation.
      • Streamline mitigation steps when a service becomes unavailable in a region.
    • Reduce cross-region impact

      • Improve regional isolation and fallback handling so an issue affecting a single region is less likely to impact customers or product functionality in other regions.

    We recognise how critical reliable access to Atlassian products is for our customers' productivity, and we apologize to customers who were impacted by this incident.

    Thanks,

    Atlassian

  • ResolvedUTC

    All products and services impacted by this incident should now be fully recovered, and this incident is resolved.

  • UpdateUTC

    We are approaching full system recovery at this time, and are performing final confirmations that services are restored.

  • UpdateUTC

    We are now able to see recovery for all impacted products, and users should be able to access their products as expected.

    Our team is continuing to monitor all products and services to ensure there is no further impact, and we will provide further update when this has been validated and the incident is closed.

  • MonitoringUTC

    Our team has implemented a mitigation for this issue and we are now seeing recovery across Atlassian products.
    We will continue to monitor this issue for any ongoing concerns, and provide further updates here within an hour as we are able to confirm a full recovery has taken place.

  • UpdateUTC

    Our team has identified the root cause of this issue and is now actively working on mitigating the issue with accessing Atlassian products.

    At this time, Atlassian customers should also be able to once again raise support requests with our team.

    We will provide further update within an hour as we are able to progress mitigating this issue.

  • UpdateUTC

    It is likely if you are experiencing any issues relating to logging in or accessing Atlassian products at this time it is likely due to this ongoing incident.

    We are continuing to receive reports about expanded product impact resulting from this incident.

    While our team continues to investigate the issue with urgency, we will continue to provide further updates here with additional information.

    We will provide further update within one hour, or sooner as further information becomes available.

  • IdentifiedUTC

    Further confirmations of impacted products have now been added to the incident.

    Our team is investigating the issue with urgency and we will provide further update as soon as it becomes available.

  • UpdateUTC

    We are aware that the current issues with accessing Atlassian products are impacting additional products. We have now expanded the impact of the incident to cover the known impacted products at this time.
    We will provide further update within one hour or sooner as information is available.

  • InvestigatingUTC

    We are investigating an issue with multiple Atlassian products that is impacting a large number of Confluence and Jira Cloud customers. We are continuing to investigate and will add further details about additional impact as our investigation continues.
    We will provide more details within the next hour or sooner if further information becomes available

Apr 2026

Some automation and workflow actions are delayed
Resolved4 hours 12 minutes
  • ResolvedUTC

    Between 08:57 AM EST and 3:34 PM EST some customers in North America experienced issues with workflow and automation delays. This was caused by an issue processing a small subset of actions causing a backlog in the processing. As of 3:34 PM EST, our systems are working properly and the incident has been fully resolved. We are continuing to monitor for further impact.

    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.

  • UpdateUTC

    We've addressed the issue that caused workflows and automation to be delayed in North America since 09:22 AM EST. We're monitoring performance closely to ensure the tools recover properly. Some email workflow actions continue to be delayed up to 6 hours.

    The information on this page reflects our understanding of the incident and impact at the time of the update.

  • MonitoringUTC

    We've addressed the issue that caused workflow execution delays in North America since 08:57 AM EST. We're monitoring performance closely to ensure the tools recover properly.

    The information on this page reflects our understanding of the incident and impact at the time of the update.

Users experiencing issues with login across Atlassian products
ResolvedDegraded performance2 hours 47 minutes
  • Summary

    On April 13, 2026, between 05:49 and 06:29 UTC, customers experienced failures when attempting to log in, sign up, reset passwords, and complete multi-factor authentication flows across Atlassian cloud products. Approximately 90% of authentication requests failed during the peak impact window, affecting users in the US East and EU regions. The incident was mitigated within 40 minutes through manual intervention, and full service was restored by 06:29 UTC.

    IMPACT

    • Duration: ~40 minutes (05:49–06:29 UTC, April 13, 2026)
    • Affected regions: US East and EU (authentication infrastructure serves EU traffic from US East, with traffic primarily from EU at this time of day).
    • Affected products: All Atlassian cloud products requiring authentication, including Jira, Confluence, Jira Service Management, and Trello.
    • Customer experience: Users attempting to log in, sign up, reset passwords, or complete MFA flows received errors. Users already logged in with active sessions were unaffected.

    ROOT CAUSE

    This incident had several contributing factors that combined to produce a failure that the system could not recover from without manual intervention.

    The primary cause was a recently enabled change that caused our authentication infrastructure to retry requests to a downstream identity service when those requests were slow to respond. This retry behaviour was rolled out to 100% of traffic earlier the same day. Under normal conditions this would be benign, but it meant that any slowness in the downstream service was amplified. Since multiple upstream services were also independently retrying their own failed requests, the amplification compounded further into a retry storm.

    The trigger was a burst of legitimate user traffic. A pattern of many parallel link preview requests for a single user caused a concentrated load spike on a downstream identity service, pushing its response times above the retry threshold. On its own, this kind of spike had occurred many times before and always recovered. With the retry amplification now in effect, the spike instead created a runaway feedback loop: slow responses caused retries, retries increased load, increased load caused slower responses, preventing recovery.

    The incident was mitigated by manually scaling up the downstream identity service to provide sufficient capacity to absorb the amplified load. Once scaled, the service recovered immediately, bringing authentication error rates to zero within one minute.

    REMEDIAL ACTIONS PLAN & NEXT STEPS

    We are taking the following actions designed to prevent recurrence and improve our resilience:

    1. Immediate: The retry-on-timeout change has been disabled.
    2. Load shedding and self-healing: We are adding load shedding capabilities to our authentication services so that they can automatically shed excess load and self-recover during traffic spikes, without requiring action before automatic scaling starts.
    3. Reducing request fan-out: We are reviewing patterns where a single user action can generate many parallel downstream requests, and will introduce methods where possible to reduce the amplification potential.

    We apologize to customers whose services were interrupted by this incident and we are taking immediate steps to improve the platform’s reliability.

    Thanks,

    Atlassian Customer Support

    UTC

Previous

Mar 2026 to May 2026

Next