Rewindex

CompaniesAptibleIncidents

Aptible: Host Provisioning Delays in us-east-1

No impact listedStatus: resolvedStarted Resolved (4.6 h)4 updatesstspg.io (opens in new tab)
Part of an outage event

AWS outage, Sep 28, 2023 · 23 vendors, 24 incidents

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

“…Host Provisioning Delays in us-east-1 This incident has been resolved. AWS continues to work on recovering this issue in a single availability zone in the us-east-1 region. Running apps and databases…”

Swipe sideways to see the whole diagram.

AWSown incident not archivedWithin an hour3 vendors, 1 blamed AWSAbly, Temporal Cloud, Keeper1 to 4 hours later4 vendors, 3 blamed AWSDremio, Firebolt, CockroachDB, Elastic CloudLater3 vendors, 1 blamed AWSAptible, Temporal Cloud, ConfluentAptible (this incident)posted +4 h 41 min
AWSown incident not archivedWithin an hour3 vendors, 1 blamed AWSAbly, Temporal Cloud, Keeper1 to 4 hours later4 vendors, 3 blamed AWSDremio, Firebolt, CockroachDB,Elastic CloudLater3 vendors, 1 blamed AWSAptible, Temporal Cloud,ConfluentAptible (this incident)posted +4 h 41 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/>3 vendors, 1 blamed AWS<br/>Ably, Temporal Cloud, Keeper"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>4 vendors, 3 blamed AWS<br/>Dremio, Firebolt, CockroachDB, Elastic Cloud"]:::blames
  root --> h4
  later["Later<br/>3 vendors, 1 blamed AWS<br/>Aptible, Temporal Cloud, Confluent"]:::blames
  root --> later
  me["Aptible (this incident)<br/>posted +4 h 41 min"]:::me
  later --- 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. investigating

    AWS is experiencing an issue preventing the timely deployment of new hosts in a single availability zone in the us-east-1 region. As a result, some app and database restart, scale, and deployment operations that result in a new host being provisioned may fail and roll back. Running apps and databases are not impacted by this failure.

  2. identified

    AWS continues to work on recovering this issue in a single availability zone in the us-east-1 region. Running apps and databases continue not to be impacted by this failure.

  3. monitoring

    We are again seeing successful deployment of new hosts in the affected single availability zone in the us-east-1 region. We will continue to monitor for an additional period before resolving the incident.

  4. resolved

    This incident has been resolved.

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

Aptible profileRecent Aptible incidentsMarkdownJSON