Atlassian Support incident

Atlassian Support is slow / not loading pages. Customers may be impacted when creating tickets.

Major Resolved View vendor source →

Atlassian Support experienced a major incident on April 13, 2023 affecting Support Portal and Ticketing, lasting 8h 3m. The incident has been resolved; the full update timeline is below.

Started
Apr 13, 2023, 02:58 PM UTC
Resolved
Apr 13, 2023, 11:01 PM UTC
Duration
8h 3m
Detected by Pingoru
Apr 13, 2023, 02:58 PM UTC

Affected components

Support PortalTicketing

Update timeline

  1. investigating Apr 13, 2023, 02:58 PM UTC

    We are currently investigating an issue with Atlassian Support and correlated services. Some customers may experience slowness or errors during ticket creation.

  2. investigating Apr 13, 2023, 03:24 PM UTC

    We are continuing to investigate this issue.

  3. investigating Apr 13, 2023, 04:59 PM UTC

    We are still investigating this issue. During this time you might not be able to open a support ticket. If you need help, please navigate to https://confluence.atlassian.com/support/contact-support-temporary-channel-950800787.html

  4. investigating Apr 13, 2023, 07:20 PM UTC

    We are still investigating the issue with Atlassian Support. If you are unable to open a support ticket during this time please use the page https://confluence.atlassian.com/support/contact-support-temporary-channel-950800787.html

  5. investigating Apr 13, 2023, 10:45 PM UTC

    Between 2:30 PM UTC to 10:00 PM UTC, we experienced intermittent performance issues for http://support.atlassian.com. The issue has now been resolved and the service is operating normally. Once we complete our internal incident review process, we will publish a more detailed postmortem of what went wrong, along with steps we're taking to prevent this from happening again in the future.

  6. resolved Apr 13, 2023, 11:01 PM UTC

    Between 2:30 PM UTC to 10:00 PM UTC, we experienced intermittent performance issues for http://support.atlassian.com. The issue has now been resolved and the service is operating normally. Once we complete our internal incident review process, we will publish a more detailed postmortem of what went wrong, along with steps we're taking to prevent this from happening again in the future.