rewindex

CompaniesNetlifyIncidents

Netlify: Build Notifications Not Arriving From GitHub

MinorStatus: resolvedStarted Resolved (0 min)1 updatewww.netlifystatus.com (opens in new tab)

Timeline of updates

  1. resolved

    Github commit notifications were not being delivered to us due to a DNS issue on their end. We worked with them to restore connectivity. In the meantime, manual deploys and “triggered deploys” via our UI worked fine, as did deploys from other Git providers.

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

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 www.netlifystatus.com (opens in new tab).

Cite this

Status incident (vendor impact label: minor) posted by Netlify, started 2017-07-11 19:35 UTC, resolved after 0 min, 1 update(s).

Title
Build Notifications Not Arriving From GitHub
Vendor
Netlify
Date
URL
https://rewindex.com/company/netlify/incidents/290sz2xqktzp

Netlify profileRecent Netlify incidentsAll outages on July 11, 2017Netlify in July 2017MarkdownJSON