Rewindex

CompaniesCircleCIIncidents

CircleCI: No webhooks received from GitHub

MinorStatus: resolvedStarted Resolved (2.8 h)1 updatestatus.circleci.com (opens in new tab)
Part of an outage event

GitHub outage, Jun 29, 2020 · 6 vendors, 6 incidents

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

“…No webhooks received from GitHub GitHub's incident has been resolved (https://www.githubstatus.com). We are now receiving all GitHub webhooks again.…”

Swipe sideways to see the whole diagram.

GitHubposted 09:14 UTCWithin an hour2 vendors, 2 blamed GitHubCircleCI, SnykCircleCI (this incident)posted +6 min
GitHubposted 09:14 UTCWithin an hour2 vendors, 2 blamed GitHubCircleCI, SnykCircleCI (this incident)posted +6 min
CircleCI 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 09:14 UTC"]:::root
  h1["Within an hour<br/>2 vendors, 2 blamed GitHub<br/>CircleCI, Snyk"]:::blames
  root --> h1
  me["CircleCI (this incident)<br/>posted +6 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's incident has been resolved (https://www.githubstatus.com). We are now receiving all GitHub webhooks again.

From CircleCI’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.circleci.com (opens in new tab).

CircleCI profileRecent CircleCI incidentsMarkdownJSON