Rate this page:
Incidents are disruptive for you, your team, and your users. Staying updated is critical.
While we strive to reduce incident rate and severity, we also want to share how and where you can get updates.
Here you can find:
Stay updated on how we’re improving Ecosystem & Marketplace Platform Stability & Reliability.
If you meet the eligibility requirements (one paid-via-Atlassian app and a private domain), apply for Partner Portal access. In the Partner resources section, select Access the Partner Portal.
If your issue requires an emergency response from Atlassian, it may be classified as an incident.
This could be due to:
If your issue does not require an emergency response but is urgent or important in nature do not use an incident ticket to report it.
Using incident tickets does not escalate an issue. It will get de-prioritized during the incident triage process.
Instead, select the relevant support type at Developer and Marketplace support. In the ticket submission form, select the issue's severity from low to critical.
We categorize the severity level of an issue when we identify one, or you report one at Developer and Marketplace support.
The severity level influences how and when we share incident communications.
There are three severity (Sev) categories:
To learn about severity levels, check out Incident severity definitions.
You can check major Ecosystem incidents (Sev 1 and 2) updates on Atlassian developer status page.
Major incidents have a dedicated major incident manager (MIM).
MIMs address the issue and share communications. Detail and frequency will depend on the level of impact.
For major incidents, MIMs:
Check the developer status page for incident updates affecting developers.
This status page is updated whenever a major incident is:
You can also check the Atlassian status page for major product incidents. Depending on the impact, these incidents can affect both partners and other Atlassian customers.
Subscribe to a status page to stay updated via:
Select whether you’d like updates on specific components, products, or the entire page.
Atlassian ecosystem incidents classified as minor (Sev 3) vary greatly in impact.
Unlike major incidents, minor ones don't have a major incident manager (MIM).
These incidents are a high priority during the normal, local working hours for the Atlassian team addressing the issue.
While the developer status page is the best place to first check for minor incident updates, it depends on the overall impact. Public updates may not be shared so Atlassian teams can focus on resolving the issue as soon as possible.
Check if an existing public incident ticket matches your issue.
If you see one, leave a comment to let us know you’re experiencing the same issue.
By commenting on an existing, public ticket, you can help raise the severity level of the issue. The number of reports can result in a higher severity level assigned.
Submit a ticket at Developer and Marketplace support:
For updates, check the:
If an incident is escalated elsewhere, you'll be redirected to these sources so it can be officially reported and monitored by our team.
Channels such as Slack and the Developer Community are great resources to discuss incidents. Providing feedback in these forums helps us learn and improve so we can reduce the impact of incidents for you and your customers.
Rate this page: