Rewindex

CompaniesSentryIncidents

Sentry: GitHub related Integrations Unstable due to GitHub Incident

MinorStatus: resolvedStarted Resolved (30 min)1 updatestatus.sentry.io (opens in new tab)
Part of an outage event

GitHub outage, Apr 21, 2020 · 12 vendors, 14 incidents

Sentry’s incident blames GitHub as the cause. (hop 1, posted +31 min vs GitHub’s own post)

“…GitHub related Integrations Unstable due to GitHub Incident GitHub has reported their incident to be resolved.…”

Swipe sideways to see the whole diagram.

GitHubposted 15:45 UTCWithin an hour4 vendors, 4 blamed GitHubv0, Vercel, Travis CI, SentrySentry (this incident)posted +31 min
GitHubposted 15:45 UTCWithin an hour4 vendors, 4 blamed GitHubv0, Vercel, Travis CI, SentrySentry (this incident)posted +31 min
Sentry is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["GitHub<br/>posted 15:45 UTC"]:::root
  h1["Within an hour<br/>4 vendors, 4 blamed GitHub<br/>v0, Vercel, Travis CI, Sentry"]:::blames
  root --> h1
  me["Sentry (this incident)<br/>posted +31 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.

Timeline of updates

  1. resolved

    GitHub has reported their incident to be resolved.

From Sentry’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

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

Sentry profileRecent Sentry incidentsMarkdownJSON