Getting the following error
Hello,
We apologize for the length of this ongoing incident and for not being more proactive in our communication with you. We understand how mission-critical our products are for you and want to make sure we are relaying the most accurate information possible.
While we really want to get in front of you live to answer your questions, we are prioritizing getting customers up and running first and foremost. We will host an AMA (Ask Me Anything) after we get all of our customers fully restored.
In the meantime, please add your questions here and we will respond as quickly and transparently as we can. Some questions may not be answered until we do an official PIR, but we will let you know that and answer as much as we can now.
Our Chief Technology Officer Sri Viswanath has posted a blog about this incident with more background and details, and our team is working around the clock to move through the various stages for restoration.
We are working 24/7 to restore your service. Thank you to those who have been sharing all the information you know from your support requests. Thank you for being open, honest, and caring for your fellow Community members. This speaks a lot about what makes Community a special place.
Lastly, if you're unsure if a support request was raised on your behalf, please let me know, and I will personally check. My team and I went through all Community posts related to this incident to ensure everyone's site had a support request.
Regards,
Stephen Sifers | Product Lead, Community
Hello, We're sorry you've been impacted by this incident. We have sent email communications to all affected customers which provide further details of the incident as well as a link for live status updates. Reach out to us at https://support.atlassian.com/contact if you have any questions or concerns.
Additionally, we’re checking and validating anyone who has posted in Community to report their site has been impacted and we are creating a support request on their behalf. If you’re unsure if an issue has been created for your site we suggest reaching out to your site admins or technical contacts.
Regards,
Stephen Sifers | Product Lead, Community
Seems to be something general going on, lots of posts popping up with users that have the same.
I've already escalated it to see if can get more info
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
https://jira-service-management.status.atlassian.com/incidents/0bcftpvmjkpt
The issue is up and you can subscribe to any status updates!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Any inside information? This is causing considerable issues and no update from JIRA
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Come on Atlassian.. your last update was nearly 2 hours ago, and yet that update said: " We will provide more details within the next hour".
Not good enough !
Zendesk or ServiceNow anyone ??
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
We apologize for the length of this ongoing incident and for not being more proactive in our communication with you. We understand how mission-critical our products are for you and want to make sure we are relaying the most accurate information possible.
While we really want to get in front of you live to answer your questions, we are prioritizing getting customers up and running first and foremost. We will host an AMA (Ask Me Anything) after we get all of our customers fully restored.
In the meantime, please add your questions here and we will respond as quickly and transparently as we can. Some questions may not be answered until we do an official PIR, but we will let you know that and answer as much as we can now.
Our Chief Technology Officer Sri Viswanath has posted a blog about this incident with more background and details, and our team is working around the clock to move through the various stages for restoration.
We are working 24/7 to restore your service. Thank you to those who have been sharing all the information you know from your support requests. Thank you for being open, honest, and caring for your fellow Community members. This speaks a lot about what makes Community a special place.
Lastly, if you're unsure if a support request was raised on your behalf, please let me know, and I will personally check. My team and I went through all Community posts related to this incident to ensure everyone's site had a support request.
Regards,
Stephen Sifers | Product Lead, Community
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Unable to contact support - Cannot even find our URL: Sorry, we can't find this Cloud URL.
See instructions below on how to find your URL.
NONE!!!!!!! No Instructions!!!!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I can see an Atlassian Support ticket was raised on behalf of our Community Support Engineer. Please check your email inbox or spam folder for the ticket under JST or PCS key.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Our sites are also down
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
7 Days have passed since Tuesday morning (April 5th PDT), we have a enterprise License, seems that SLA has been breached. hope fully this incident will be resolved Soon. ref ticket JST-749469
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I would go with it has been obliterated rather than just breached....
I hope there is a serious amount of compensation as we are being told it could be another 2 weeks for full restoration of service.
That is unless we have moved away by that stage - too much pressure from C-Suite as this is a totally unacceptable situation for a Cloud Provider.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.