CompaniesRubyGems.orgIncidents
RubyGems.org: Elevated DNS Errors
Cloudflare outage, Jul 17, 2020 · 24 vendors, 24 incidents
RubyGems.org’s incident started in the same window without naming Cloudflare (timing only, not evidence of a link). (timing only, posted +21 min vs the first vendor naming Cloudflare)
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["Cloudflare<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>6 vendors, 6 blamed Cloudflare<br/>Sigma Computing, WorkOS, Doppler, Linode (Akamai) +2"]:::blames
root --> h1
h4["1 to 4 hours later<br/>1 vendor, 1 blamed Cloudflare<br/>Hotjar"]:::blames
root --> h4
me["RubyGems.org (this incident)<br/>posted +21 min"]:::me
root -.->|"same window"| meFull 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 APIUpstream Provider: DNSimple Name ServersApplicationGem DownloadsGem Index API
Timeline of updates
- investigating
We're experiencing an elevated level of DNS errors and are currently looking into the issue.
- monitoring
DNS seems to be resolving again. We continue to monitor the situation.
- monitoring
We are continuing to monitor for any further issues.
- resolved
This incident has been resolved.
Changes Rewindex caught on this incident
- Jul 17, 2020Major incident: Elevated DNS Errors
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.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
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