Rewindex

CompaniesRubyGems.orgIncidents

RubyGems.org: Elevated Errors

MajorStatus: resolvedStarted Resolved (1.5 h)5 updatesstspg.io (opens in new tab)
Part of an outage event

Fastly outage, Jun 8, 2021 · 27 vendors, 27 incidents

RubyGems.org’s incident blames Fastly as the cause. (hop 1, posted +0 min vs the first vendor naming Fastly)

“…levels and errors return to normal. The elevated 503 and 502 errors seem to be because of Fastly's ongoing incident. We are following along at https://status.fastly.com/incidents/vpk0ssybt3bj. This in…”

Swipe sideways to see the whole diagram.

Fastlyown incident not archivedWithin an hour2 vendors, 2 blamed FastlyRubyGems.org, BrazeRubyGems.org (this incident)posted +0 min
Fastlyown incident not archivedWithin an hour2 vendors, 2 blamed FastlyRubyGems.org, BrazeRubyGems.org (this incident)posted +0 min
RubyGems.org is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["Fastly<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>2 vendors, 2 blamed Fastly<br/>RubyGems.org, Braze"]:::blames
  root --> h1
  me["RubyGems.org (this incident)<br/>posted +0 min"]:::me
  h1 --- 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.

Affected components: Dependency APIApplicationGem DownloadsGem Index API

Timeline of updates

  1. investigating

    We're experiencing an elevated level of errors and are currently looking into the issue.

  2. investigating

    The elevated 503 and 502 errors seem to be because of Fastly's ongoing incident. We are following along at https://status.fastly.com/incidents/vpk0ssybt3bj.

  3. identified

    Our CDN partner has identified the issue and a fix is being implemented.

  4. monitoring

    Our CDN provider has applied a fix and over the last few minutes we saw traffic levels and errors return to normal.

  5. resolved

    This incident has been resolved.

Changes Rewindex caught on this incident

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

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

RubyGems.org profileRecent RubyGems.org incidentsMarkdownJSON