Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,559,019
Community Members
 
Community Events
184
Community Groups

Status stuck at "Degraded performance" even after all the incidents are resolved

The statuspage status is not changed to "All Systems Operational" even after all the incidents are resolved. This happened twice in the last 30 days. 

Had to manually update the status of the affected component to resolve this.

Is this a bug or have we misconfigured something?

1 answer

0 votes
Eugenio Onofre
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Sep 12, 2022

Hello @Rajdeep Siddhapura
Welcome to the Atlassian Community!

There may be a couple reasons why it happens:

  • Incidents are resolved and the checkbox to mark components as operational are not marked
  • Components status are updated manually with no relationship with ongoing incidents.

I would strongly suggest, in case the issue happens again, to look into the Incident Resolution status update and make sure the checkbox is checked and also check if any components were manually updated without being linked to an incident.

Regards,
Eugenio

Hi @Eugenio Onofre, thank you for the reply.

We don't create or resolve incidents manually. Neither do we change the component status manually. We have PagerDuty integration which takes care of the creation and resolution of incidents. It also takes care of updating component status.

When the incident gets resolved, the component gets marked as operational with it. This works as expected >99% of the time. It has been working as expected for >2.5 years. We faced this issue for the first time in the last 30 days. 

Could there be an issue with PagerDuty app on Statuspage?

Eugenio Onofre
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Sep 14, 2022

Hi Rajdeep,

Thanks for the details provided.
It could be an issue in between PagerDuty and Statuspage.

I would recommend creating a support ticket at support.atlassian.com so the Technical Support Team can better investigate it.

Regards,
Eugenio

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events