Skip to main content
Atlassian Statuspage

Incorrect AWS Component Emails

Degraded Lasted 3h 30m · started · Atlassian Statuspage's page

Level
confirmed
Worst impact
Degraded
Components
External
Down Index
20of 100

What to do

  • Check whether you use Atlassian Statuspage External. 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 3h 30m it lasted.

    Anything that failed between 2022-05-16 19:00 UTC and 2022-05-16 22:31 UTC may need a replay.
  • Subscribe to Atlassian Statuspage's feed to hear about the next one first. RSS feed

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

Updates from Atlassian Statuspage 4

  1. investigating

    A number of incorrect emails were sent out saying AWS third party components will no longer receive updates. These components have not been impacted and we are investigating the root cause of the emails now.

    provider

  2. identified

    We have identified the cause of the emails and are working on a resolution now

    provider

  3. identified

    We are continuing to work on a fix for the incorrect emails. If any other emails are received about AWS components please disregard them

    provider

  4. resolved

    This incident has been resolved.

    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-4afb8f02eb

Is Atlassian Statuspage still down?

No, this incident was resolved 2022-05-16 22:31 UTC. For Atlassian Statuspage's live state, see https://down.guide/statuspage.

How long did it last?

3h 30m, from 2022-05-16 19:00 UTC to 2022-05-16 22:31 UTC, by the times Atlassian Statuspage posted.

What was affected?

Atlassian Statuspage named External.

What caused it?

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

Where does this come from?

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