- Level
- confirmed
- Worst impact
- Degraded
- Components
- Asia Southeast 1
- Regions
- apac
- Down Index
- 24of 100
What to do
Check whether you use Statsig Asia Southeast 1 in apac. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 2h 40m it lasted.
Anything that failed between 2025-04-17 01:00 UTC and 2025-04-17 03:40 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
04/16/2025 20:40 PDT Mitigated: The sporadic propagation delays affecting updates to all configuration types in Southeast Asia were resolved. 04/16/2025 18:00 PDT Investigating: We detected intermittent delays in the propagation of updates to all configuration types for API requests in the Southeast Asia region.
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-138a665ba8
Is Statsig still down?
No, this incident was resolved 2025-04-17 03:40 UTC. For Statsig's live state, see https://down.guide/providers/statsig.
How long did it last?
2h 40m, from 2025-04-17 01:00 UTC to 2025-04-17 03:40 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.