The New Developer Statuspage

Reading Time: 2 minutes

Atlassian’s Ecosystem team understands that its developer community and third-party vendors are huge partners in everything it does. As part of this relationship, the developer community and vendors depend on Atlassian’s platform, APIs, and storefront capabilities to build their own businesses. When Atlassian encounters incidents, not only is it impacted, but so are these crucial partners.

Incidents happen. They’re an undeniable part of the software industry. However, when these incidents do occur, the least one can do is communicate with their developers about what’s going on.

What’s new

The Ecosystem team has launched its new developer Statuspage! This page centralizes everything developers need to know about: API health, documentation availability, Marketplace uptime, and so forth. Many of Atlassian’s developers are also vendors on our Marketplace, and as a result this Statuspage combines everything that both developers and vendors might be interested in; it is a single Statuspage for all developer-related domains and functionality.

What about end users?

End users need not worry about all of the intricacies of Atlassian’s developer ecosystem. They don’t need to know about the availability of Atlassian’s Maven repository or Marketplace’s sales APIs. However, end users do care about things such as whether or not they’re able to discover and purchase apps, and if there are known issues with the APIs backing their installed apps.

Atlassian’s main Statuspage continues to be the source of truth for end users to monitor the health of all things Atlassian. Now included on this page are the developer-related components which matter most to end-users. You can direct your customers to this page if they want to know more about an Atlassian incident impacting your apps.

Don’t worry about the the two Statuspages getting out of sync with each other; the developer Statuspage exposes shared components to Atlassian’s main Statuspage, guaranteeing that both will always reflect the same component health to both developers and end users.

These shared components are accessible for use on your own Statuspage, too. To add them to your page, go to the components view in your Statuspage management console, click “Third-Party Components”, and select “Atlassian Developer”.

Final thoughts

Got feedback? Want to see something else added to our Statuspage? Let us know.

Want a Statuspage for your own team? Give it a shot! If you sell paid Cloud apps on the Marketplace, you even qualify for a free account.