Atlassian Support Outage History

Atlassian Support is up right now

Atlassian Support had 12 outages in the last 2 years totaling 185h 16m of downtime — averaging 0.5 incidents per month.

There were 12 Atlassian Support outages since June 17, 2025 totaling 185h 16m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://support.status.atlassian.com

Critical April 2, 2026

Confluence documentation and knowledge base is unavailable

Detected by Pingoru
Apr 02, 2026, 01:49 AM UTC
Resolved
Apr 02, 2026, 02:39 AM UTC
Duration
50m
Affected: Support PortalTicketingKnowledge BaseCommunityAPI DocsPublic Issues TrackerTrainingBlogsCareersContent DeliverySearchDownloads AccessPreferences Center
Timeline · 3 updates
  1. investigating Apr 02, 2026, 01:49 AM UTC

    Our team is investigating an issue relating to 503 errors being displayed when attempting to load confluence.atlassian.com. We are investigating this issue with urgency and will provide an update within 1 hour.

  2. monitoring Apr 02, 2026, 02:23 AM UTC

    We are now seeing recovery across confluence.atlassian.com and ja.confluence.atlassian.com sites. We are continuing to monitor the recovery and will update when we are satisfied that this incident is fully resolved.

  3. resolved Apr 02, 2026, 02:39 AM UTC

    Our team has been able to successfully recover all services from confluence.atlassian.com and ja.confluence.atlassian.com and these sites are now performing as expected. This incident is now resolved. We apologize for any inconvenience that this issue may have caused.

Read the full incident report →

Minor December 17, 2025

Support Ticket creation is slow or partially impacted

Detected by Pingoru
Dec 17, 2025, 01:48 PM UTC
Resolved
Dec 17, 2025, 02:43 PM UTC
Duration
55m
Affected: Support PortalTicketingKnowledge BaseCommunityAPI DocsPublic Issues TrackerTrainingBlogsCareersContent DeliverySearchDownloads AccessPreferences Center
Timeline · 3 updates
  1. investigating Dec 17, 2025, 01:48 PM UTC

    Support ticket creation is slow or partially impacted for some of our customers. Support chats are being initiated but not visible to Atlassian support teams. Our team is aware and investigating the same. We will update you in next 60 mins or sooner.

  2. monitoring Dec 17, 2025, 02:15 PM UTC

    This issue resulted from a permission problem. The Atlassian team quickly identified and has fixed it. All support tickets raised during this period are being created. Our support team will process the tickets in the order they were received. For expired chat support sessions, support tickets will be created and our support team will proactively reach out. We continue to monitor the status.

  3. resolved Dec 17, 2025, 02:43 PM UTC

    Team has reconfirmed everything is working as expected. This issue is resolved.

Read the full incident report →

Minor December 5, 2025

Multiple customer sites have lost access to Support tickets

Detected by Pingoru
Dec 05, 2025, 08:08 AM UTC
Resolved
Dec 05, 2025, 12:09 PM UTC
Duration
4h
Affected: Support PortalTicketingKnowledge BaseCommunityAPI DocsPublic Issues TrackerTrainingBlogsCareersContent DeliverySearchDownloads AccessPreferences Center
Timeline · 5 updates
  1. investigating Dec 05, 2025, 08:08 AM UTC

    We are aware that access to created Ecohelp support tickets is not available for some of our customers. Our team is investigating this issue. Repeat creation of tickets is not required as the created tickets are visible to the Atlassian teams. We will provide next update in 60 minutes.

  2. investigating Dec 05, 2025, 09:23 AM UTC

    Customers encounter a permission error when accessing tickets: No Access - You do not have permission to view this request. Ticket creation works and created tickets are visible to the Atlassian teams. The Atlassian team continues investigating. The root cause remains unclear. We will provide next update in 60 minutes.

  3. investigating Dec 05, 2025, 09:56 AM UTC

    Customers encounter a permission error when accessing tickets: No Access - You do not have permission to view this request. Ticket creation works and created tickets are visible to the Atlassian teams. The Atlassian team continues investigating. The root cause remains unclear. We will provide next update in 60 minutes.

  4. investigating Dec 05, 2025, 11:06 AM UTC

    Customers continue to encounter a permission error when accessing tickets: No Access - You do not have permission to view this request. Ticket creation works and created tickets are visible to the Atlassian teams. The Atlassian team is engaged and continues investigation. However, the root cause remains unclear. We will provide next update in 3 hours or sooner.

  5. resolved Dec 05, 2025, 12:09 PM UTC

    The feature flag causing the issue has been reverted, fixing the problem. With that this incident is resolved.

Read the full incident report →

Minor November 6, 2025

Atlassian Community is experiencing the slowness on Forums

Detected by Pingoru
Nov 06, 2025, 07:36 PM UTC
Resolved
Nov 10, 2025, 04:17 AM UTC
Duration
3d 8h
Affected: Support PortalTicketingKnowledge BaseCommunityAPI DocsPublic Issues TrackerTrainingBlogsCareersContent DeliverySearchDownloads AccessPreferences Center
Timeline · 4 updates
  1. investigating Nov 06, 2025, 07:36 PM UTC

    Marketplace Community is experiencing slow load times and degraded performance on the Forums. We are actively investigating and hope to have a resolution as soon as possible.

  2. investigating Nov 06, 2025, 07:50 PM UTC

    Atlassian Community is experiencing slow load times and degraded performance on the Forums. We are actively investigating and hope to have a resolution as soon as possible.

  3. monitoring Nov 07, 2025, 02:10 PM UTC

    The incident has been fixed and continue to stay under monitoring.

  4. resolved Nov 10, 2025, 04:17 AM UTC

    The issue has been resolved and there is no performance related slowness on Atlassian Community Forums now.

Read the full incident report →

Notice October 20, 2025

Atlassian Cloud Services impacted

Detected by Pingoru
Oct 20, 2025, 07:56 AM UTC
Resolved
Oct 21, 2025, 05:24 AM UTC
Duration
21h 28m
Affected: Support PortalTicketingKnowledge BaseCommunityAPI DocsPublic Issues TrackerTrainingBlogsCareersContent DeliverySearchDownloads AccessPreferences Center
Timeline · 24 updates

Read the full incident report →

Minor October 8, 2025

Loom Users on Chrome Extension Encountering Video Saving Delays

Detected by Pingoru
Oct 08, 2025, 10:20 PM UTC
Resolved
Oct 09, 2025, 08:00 PM UTC
Duration
21h 39m
Affected: Content Delivery
Timeline · 2 updates
  1. identified Oct 08, 2025, 10:20 PM UTC

    We have identified an issue starting at 17:00 UTC on Monday, October 6th, 2025 affecting all Loom users who record videos with the Chrome Extension, causing unexpected delays when saving videos. If the browser is closed before the video is playable, the recording may be lost. To address this, we have developed an updated version of the extension, which is currently under review by Google. We anticipate the fix to be published by 20:00 UTC on October 15th, 2025, or sooner. In the meantime, users will see an in-browser message if their video has not yet been saved, advising them not to close the browser session. We will provide an update again when the fix is available.

  2. resolved Oct 09, 2025, 08:00 PM UTC

    We have resolved the incident. A new version of the Loom chrome extension has been approved and published to the Chrome Extension store. Update to the latest version(v5.5.142) of the extension.

Read the full incident report →

Minor June 17, 2025

Report of Customers not being able to view their Support requests on support.atlassian.com

Detected by Pingoru
Jun 17, 2025, 08:10 AM UTC
Resolved
Jun 17, 2025, 08:32 AM UTC
Duration
21m
Affected: Support Portal
Timeline · 3 updates
  1. investigating Jun 17, 2025, 08:10 AM UTC

    We are investigating the issue

  2. identified Jun 17, 2025, 08:12 AM UTC

    The issue has been identified and a fix is being implemented.

  3. resolved Jun 17, 2025, 08:32 AM UTC

    This incident has been resolved.

Read the full incident report →