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…”
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.
What changed
Struck in red is what RubyGems.org removed; blue is what they added. Muted text is unchanged context.
BeforeAfter
AddedTitle#1
Before: not present
After: Elevated Errors
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2021-06-08 10:00 UTC
AddedResolved time#5
Before: not present
After: 2021-06-08 11:29 UTC
AddedAffected components#6
Before: not present
After: Application, Dependency API, Gem Downloads, Gem Index API
AddedUpdateinvestigating#7
Before: not present
After: We're experiencing an elevated level of errors and are currently looking into the issue.
AddedUpdateinvestigating#8
Before: not present
After: 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.
AddedUpdateidentified#9
Before: not present
After: Our CDN partner has identified the issue and a fix is being implemented.
AddedUpdatemonitoring#10
Before: not present
After: Our CDN provider has applied a fix and over the last few minutes we saw traffic levels and errors return to normal.