Nhost: Singapore Region Connectivity Issues

What to do

Check whether you use Nhost Asia Pacific (Singapore) 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 0m it lasted.
Anything that failed between 2026-03-10 15:00 UTC and 2026-03-10 15:00 UTC may need a replay.
Subscribe to Nhost's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=nhost works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

resolvedMar 10, 2026, 3:00 PM UTC
Type: Incident Duration: 2 hours and 8 minutes Affected Components: Asia Pacific (Singapore) Mar 10, 17:08:06 GMT+0 - Resolved - This incident has been resolved. Mar 10, 16:50:32 GMT+0 - Monitoring - We implemented a fix and are currently monitoring. All services in the region should be operational again. Mar 10, 15:00:13 GMT+0 - Identified - We are currently investigating connectivity issues affecting services deployed in our Singapore region. Users may experience intermittent failures when accessing projects hosted in this region. Other regions are operating normally. Our team is working to restore full service as quickly as possible.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

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

Is Nhost still down?

No, this incident was resolved 2026-03-10 15:00 UTC. For Nhost's live state, see https://down.guide/nhost.

How long did it last?

0m, from 2026-03-10 15:00 UTC to 2026-03-10 15:00 UTC, by the times Nhost posted.

What was affected?

Nhost named Asia Pacific (Singapore) in apac.

What caused it?

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

Where does this come from?

Nhost's official status page, https://status.nhost.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.