Rewindex

RewindexOutage eventsMar 16, 2020

Heroku outage, Mar 16, 2020

8 vendors posted 9 incidents between 16:00 and 21:00 UTC, against about 4 incidents from 4 vendors in the same hours on an ordinary week. 4 vendors named Heroku in 5 incidents (4 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.

    11. first vendor named Heroku 16:24
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 hour4 vendors, 4 blamed HerokuRevenueCat, Substack, Bitrise, crates.io1 to 4 hours later1 vendor, 1 blamed HerokuRevenueCat
Herokuown incident not archivedWithin an hour4 vendors, 4 blamed HerokuRevenueCat, Substack, Bitrise,crates.io1 to 4 hours later1 vendor, 1 blamed HerokuRevenueCat
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/>4 vendors, 4 blamed Heroku<br/>RevenueCat, Substack, Bitrise, crates.io"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>1 vendor, 1 blamed Heroku<br/>RevenueCat"]:::blames
  root --> h4

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

4 vendors

  • +0 min

    Blames Heroku

    Major incident

    RevenueCatDowntime across dashboard and APIs

    …Downtime across dashboard and APIs Heroku have resolved their issue. We will continue to monitor throughout today but everything is operational on our end.…

  • +1 min

    Blames Heroku

    Major incident

    SubstackUnable to load webpages

    …Unable to load webpages Heroku, one of our infrastructure providers, had a short outage with their routers this morning. Read here for more details: https://status.heroku.com/incidents/1973…

  • +2 min

    Blames Heroku

    Critical incident

    BitriseMajor website outage

    …Major website outage Heroku incident was closed. Website should be back to normal.…

  • +30 min

    Blames Heroku

    Major incident

    crates.ioIncreased errors while connecting to crates.io

    …crates.io. We're continuing to monitor the situation, and you can follow the progress on Heroku's status page: https://status.heroku.com/incidents/1973 This incident has been resolved.…

1 to 4 hours later

1 vendor

  • +3 h 40 min

    Blames Heroku

    Minor incident

    RevenueCatDegraded performace across dashboard and APIs

    …Degraded performace across dashboard and APIs Heroku has moved this issue to resolved, so we are too. They don't seem to have a root cause ye but we don't believe there is anything to do on our end. W…

Same window, did not name anyone

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

Show all 4

Detected automatically from 8 status pages opening incidents in the peak hour (normally at most 3). 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.