- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Asia Southeast 1
- Regions
- apac
What to do
Check whether you use Statsig Asia Southeast 1 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 1h 3m it lasted.
Anything that failed between 2026-03-18 01:50 UTC and 2026-03-18 02:53 UTC may need a replay.Subscribe to Statsig's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=statsig works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Statsig 2
- investigating
We are seeing degraded success rate in our southeast asia region for client SDK initialization starting at around 6:50PM. The team has identified the root cause and is working on recovering the region now. Update: 7:51PM PST -- The team expects full recovery within a few minutes. Update: 7:57PM PST -- Systems are fully recovered as of 7:53 PM PST.
provider
- resolved
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-76056ad9f6
Is Statsig still down?
No, this incident was resolved 2026-03-18 02:53 UTC. For Statsig's live state, see https://down.guide/statsig.
How long did it last?
1h 3m, from 2026-03-18 01:50 UTC to 2026-03-18 02:53 UTC, by the times Statsig posted.
What was affected?
Statsig named Asia Southeast 1 in apac.
What caused it?
Statsig hasn't published a root cause. If it does, it shows here.
Where does this come from?
Statsig's official status page, https://status.statsig.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.