Skip to main content
Netlify

Increased errors on High Performance Edge in Mumbai region

Degraded Lasted 33m · started · Netlify's page

Level
confirmed
Worst impact
Degraded
Components
High-Performance Edge Network
Regions
apac

What to do

  • Check whether you use Netlify High-Performance Edge Network in apac. 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 33m it lasted.

    Anything that failed between 2026-03-12 03:43 UTC and 2026-03-12 04:17 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 2

  1. investigating

    We're investigating an increase in errors on the High Performance Edge Network in Mumbai (BOM) region since 3 AM UTC.

    provider

  2. 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-93ed8373f7

Is Netlify still down?

No, this incident was resolved 2026-03-12 04:17 UTC. For Netlify's live state, see https://down.guide/netlify.

How long did it last?

33m, from 2026-03-12 03:43 UTC to 2026-03-12 04:17 UTC, by the times Netlify posted.

What was affected?

Netlify named High-Performance Edge Network in apac.

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.