Rewindex

CompaniesAptibleIncidents

Aptible: AWS Availability (3rd party)

No impact listedStatus: resolvedStarted Resolved (1.2 h)1 updatestatus.aptible.com (opens in new tab)
Part of an outage event

AWS outage, Jun 13, 2023 · 56 vendors, 56 incidents

Aptible’s incident blames AWS as the cause. (hop 1, posted +1 h 21 min vs the first vendor naming AWS)

“…AWS Availability (3rd party) This incident has been resolved.…”

Swipe sideways to see the whole diagram.

AWSown incident not archivedWithin an hour13 vendors, 13 blamed AWSPipedream, Wiz, Temporal Cloud +101 to 4 hours later7 vendors, 6 blamed AWSCockroachDB, Vanta, Asana +4Aptible (this incident)posted +1 h 21 min
AWSown incident not archivedWithin an hour13 vendors, 13 blamed AWSPipedream, Wiz, TemporalCloud +101 to 4 hours later7 vendors, 6 blamed AWSCockroachDB, Vanta, Asana +4Aptible (this incident)posted +1 h 21 min
Aptible 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/>13 vendors, 13 blamed AWS<br/>Pipedream, Wiz, Temporal Cloud +10"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>7 vendors, 6 blamed AWS<br/>CockroachDB, Vanta, Asana +4"]:::blames
  root --> h4
  me["Aptible (this incident)<br/>posted +1 h 21 min"]:::me
  h4 --- 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

    This incident has been resolved.

From Aptible’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 status.aptible.com (opens in new tab).

Aptible profileRecent Aptible incidentsMarkdownJSON