Rewindex

CompaniesOpsgenieIncidents

Opsgenie: Increased API errors for Configuration REST API's

MinorStatus: resolvedStarted Resolved (1.3 h)1 updateopsgenie.status.atlassian.com (opens in new tab)
Part of an outage event

AWS outage, Mar 9, 2022 · 12 vendors, 12 incidents

Opsgenie’s incident started in the same window without naming AWS (timing only, not evidence of a link). (timing only, posted +23 min vs the first vendor naming AWS)

Swipe sideways to see the whole diagram.

same windowAWSown incident not archivedWithin an hour2 vendors, 2 blamed AWSCourier, Unbounce1 to 4 hours later1 vendor, 1 blamed AWSXeroOpsgenie (this incident)posted +23 min
same windowAWSown incident not archivedWithin an hour2 vendors, 2 blamed AWSCourier, Unbounce1 to 4 hours later1 vendor, 1 blamed AWSXeroOpsgenie (this incident)posted +23 min
Opsgenie is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["AWS<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>2 vendors, 2 blamed AWS<br/>Courier, Unbounce"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>1 vendor, 1 blamed AWS<br/>Xero"]:::blames
  root --> h4
  me["Opsgenie (this incident)<br/>posted +23 min"]:::me
  root -.->|"same window"| me

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Timeline of updates

  1. resolved

    Our engineers have been closely monitoring the platform and are declaring this incident resolved. Thank you for your patience.

From Opsgenie’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

Impact, status and times are the vendor’s own, as last archived. View on opsgenie.status.atlassian.com (opens in new tab).

Opsgenie profileRecent Opsgenie incidentsMarkdownJSON