Critical Outage : Confluence REST API by Atlassian - Help

:fire: :fire: :fire: :fire: :fire: :fire: :fire: :fire:
Summary: Current Critical Outage, 2 hours + and as of yet no response to tickets, messages or posts
:fire: :fire: :fire: :fire: :fire: :fire: :fire: :fire:

Hi Team Atlassian,

There is currently a critical outage with the Confluence REST API which several vendors and thousands of customers depend on. We have followed the escalation path given to vendors up to this point.

However, it seems Atlassian is not actively monitoring vendor tickets even while rolling out untested code updates that are breaking the platform? Feel free to correct me on that (I love to be wrong about such things) but it seems to be the only explanation. And when I say untested its because any basic integration test would have caught this.

I know times are crazy right now in the world. However, that’s all the more reason to either not roll out changes if you’re understaffed to test or fix things when they break.

We’ve detailed this breakage and easy steps too reproduce here public to this community
and here
https://ecosystem.atlassian.net/servicedesk/customer/portal/14/DEVHELP-4339 (not public)
and here
https://community.developer.atlassian.com/t/critical-outage-api-just-broke-all-vendor-apps-that-use-pagehierarchy-copy/36881/6 (not public)

The real question here is:

When Atlassian breaks the platform in a critical way and we have a trivial reproducer how do we escalate in a way that works? Because the current state of affairs seems that there is no working path.

@bmagro
@WarrenChen
@chparker

Thank you!
Brendan

1 Like

Cross posting response from our Dev Advocacy team:
https://community.developer.atlassian.com/t/cph-copy-page-hierarchy-rest-api-says-success-but-page-tree-is-not-at-destination/36880/4?u=warrenchen

Page does not exist :frowning:

Apologies @claudioac. It’s in a gated portion of the developer community.

Latest update from @mpaisley (Can you please provide status updates here as well?): The team are in the deployment phase now which can take a few hours, so i’ll update you in about an hour to let you know how it’s going.

1 Like

Thanks so much @WarrenChen!! The updates have been awesome from @mpaisley and @rwhitbeck and you and several others.

Looking forward to getting the scoop/debrief afterwards on what happened and a meeting to streamline the escalation path. I’m sure its not efficient for you guys to be receiving messages from me and others across 6 sites, channels and paths escalating till we got traction. That ended up being my whole day as well, which is fine. I am motivated as I’m confident you are to stem reoccurrence.

Since traction the response has been excellent! Cheers!

It appears this might now be fixed. Light testing affirms this. Thank you for you attention and efforts!!!

@WarrenChen please let me know about the debrief in my last post :arrow_heading_up: or who I should chat with.
Cheers,
Brendan

@brendan I’m glad the issue has been resolved. Thanks goes to @Andrew_Golokha @rwhitbeck @mpaisley for working with the product engineering teams on the resolution.

2 Likes

Thanks, @WarrenChen! Agreed, many thanks to @rwhitbeck, @mpaisley, and @Andrew_Golokha.

2 Likes