Skip to main content
Netlify

Build Issues due to Github Outage

Degraded Lasted 56m · started · Netlify's page

Level
confirmed
Worst impact
Degraded
Components
Build Pipeline
Down Index
17of 100

What to do

  • Check whether you use Netlify Build Pipeline. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 56m it lasted.

    Anything that failed between 2026-05-11 14:31 UTC and 2026-05-11 15:27 UTC may need a replay.
  • Subscribe to Netlify's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=netlify works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Netlify 5

  1. investigating

    We are experiencing issues with our build pipeline due to degraded performance in Github

    provider

  2. identified

    The issue has been identified and posted on Github's status page.

    provider

  3. monitoring

    We are monitoring improvements.

    provider

  4. monitoring

    We are continuing to monitor for any further issues.

    provider

  5. resolved

    This incident has been resolved.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-a0b0ebf883

Is Netlify still down?

No, this incident was resolved 2026-05-11 15:27 UTC. For Netlify's live state, see https://down.guide/netlify.

How long did it last?

56m, from 2026-05-11 14:31 UTC to 2026-05-11 15:27 UTC, by the times Netlify posted.

What was affected?

Netlify named Build Pipeline.

What caused it?

Netlify hasn't published a root cause. If it does, it shows here.

Where does this come from?

Netlify's official status page, https://www.netlifystatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.