Skip to main content
Opsgenie

Android users of Jira, Confluence and Opsgenie app with Compromised device check feature turned on is getting locked out of their app

Partial outage Lasted 2h 59m · started · Opsgenie's page

Level
confirmed
Worst impact
Partial outage
Components
Mobile Application
Down Index
30of 100

What to do

  • Check whether you use Opsgenie Mobile Application. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 2h 59m it lasted.

    Anything that failed between 2022-11-11 21:02 UTC and 2022-11-12 00:01 UTC may need a replay.
  • Subscribe to Opsgenie's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=opsgenie works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Opsgenie 3

  1. identified

    We are investigating reports of intermittent errors for Confluence, Jira Software, and Opsgenie Cloud customers. We will provide more details once we identify the root cause.

    provider

  2. identified

    We are investigating an issue where Android users of Jira, Confluence and Opsgenie app with the Compromised device check feature turned on is getting locked out of their app. Note that this is only affecting the Android mobile app for customers who have turned on the Compromised device check feature via admin.atlassian.com

    provider

  3. resolved

    Between 2022-11-06 and 2022-11-11, 18:45 EST, we experienced an issue where Android users of Jira, Confluence, and Opsgenie apps with the Compromised device check feature turned on is getting locked out of their apps for Confluence, Jira Software, and Opsgenie. The issue has been resolved and the service is operating normally. If a customer is locked out post-login and there is no retry option, we request that a user either clears the app data or reinstall the app.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-7376f650e0

Is Opsgenie still down?

No, this incident was resolved 2022-11-12 00:01 UTC. For Opsgenie's live state, see https://down.guide/opsgenie.

How long did it last?

2h 59m, from 2022-11-11 21:02 UTC to 2022-11-12 00:01 UTC, by the times Opsgenie posted.

What was affected?

Opsgenie named Mobile Application.

What caused it?

Opsgenie hasn't published a root cause. If it does, it shows here.

Where does this come from?

Opsgenie's official status page, https://opsgenie.status.atlassian.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.