Rewindex

RewindexOutage eventsAug 23, 2022

Heroku outage, Aug 23, 2022

10 vendors posted 10 incidents between 23:00 on Aug 23 and 01:00 on Aug 24 UTC, against about 3 incidents from 3 vendors in the same hours on an ordinary week. 3 vendors named Heroku in 3 incidents (3 of them blamed it). Vendors reported a Heroku outage; Heroku’s own incident for this date is not in the archive.

Observed, not verified. A line means a vendor’s incident named another vendor, or started in the same window. It is not a proven cause.

Times are UTC; lags are from when the first vendor named Heroku.

    5. first vendor named Heroku 23:25
Named HerokuNamed another vendorDid not name anyoneEach column is 30 minutes

How it spread

Vendors that named Heroku, grouped by when they posted, and vendors that blamed one of the vendors Heroku took down. Solid lines: the vendor named the other. Dashed: same window, not named.

Swipe sideways to see the whole diagram.

Herokuown incident not archivedWithin an hour3 vendors, 3 blamed HerokuSecureframe, Bitrise, BigCommerce
Herokuown incident not archivedWithin an hour3 vendors, 3 blamed HerokuSecureframe, Bitrise,BigCommerce
Rendered on the server with pele from the Mermaid source below. Each box lists the first few vendors; every vendor is listed further down.
Mermaid source
flowchart LR
  root["Heroku<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>3 vendors, 3 blamed Heroku<br/>Secureframe, Bitrise, BigCommerce"]:::blames
  root --> h1

Vendors that named Heroku

In their own words. “Blames” means a causal phrase sits next to the name (“due to”, “upstream provider”…).

Within an hour

3 vendors

  • +0 min

    Blames Heroku

    Incident, no impact listed

    SecureframeDNS Issue with Heroku

    …DNS Issue with Heroku We have found a workaround to the hosting providers ongoing issue. Our hosting provider is having a DNS outage. More information can be found here https://status.heroku.com/incid…

  • +19 min

    Blames Heroku

    Major incident

    BitriseBitrise.io is down due to a Heroku incident

    …Bitrise.io is down due to a Heroku incident This incident has been resolved.…

  • +43 min

    Blames Heroku

    Major incident

    BigCommerceThird Party Outage Impacting Developer Portal

    …Third Party Outage Impacting Developer Portal Heroku and their upstream DNS provider have implemented a fix, and service within our developer portal is stable. Thank you for your patience.…

Same window, did not name anyone

7 incidents started during the event without naming Heroku or another vendor. Some are part of it, some are a normal day’s background (about 3 in these hours).

Show all 7

Detected automatically from 8 status pages opening incidents in the peak hour (normally at most 5). Mentions are matched by name in each incident’s title and updates, then classified as cause, location or integration; quoted text is the vendor’s. Vendors that share one status page are shown once.