- Level
- confirmed
- Worst impact
- Degraded
- Replicate says
- 2026-11-03 06:20 to 06:32 UTC (12m)
- Components
- Network, Cloud Network Interconnect (CNI), Hong Kong - (HKG)
- Regions
- apac
- Down Index
- 29of 100
What to do
Check whether you use Replicate Network, Cloud Network Interconnect (CNI), Hong Kong - (HKG) 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 12m it lasted.
Anything that failed between 2026-11-03 06:20 UTC and 2026-11-03 06:32 UTC may need a replay.Subscribe to Replicate's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=replicate works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Replicate 1
- resolved
Between 06:20-6:32 UTC customers reaching Hong Kong may have experienced an elevated number of 5xx errors or CNI timeouts due to congestion.
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-e09b33e7ba
Is Replicate still down?
No, this incident was resolved 2026-11-03 06:32 UTC. For Replicate's live state, see https://down.guide/providers/replicate.
How long did it last?
12m, from 2026-11-03 06:20 UTC to 2026-11-03 06:32 UTC, by the times Replicate posted.
What was affected?
Replicate named Network, Cloud Network Interconnect (CNI), Hong Kong - (HKG) in apac.
What caused it?
Replicate hasn't published a root cause. If it does, it shows here.
Where does this come from?
Replicate's official status page, https://www.cloudflarestatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.