Live  /  Providers  /  CEX.IO

CEX.IO

cex.ioReporting incidents

Independent assessment — SquidGrid is not affiliated with CEX.IO. Provider-published information is labeled as such; SquidGrid’s own measurements are observations of network paths, not determinations of fault.

SaaS & business software · SquidGrid tracks CEX.IO’s own status and independently measures the internet paths that reach it, so you can tell a provider-side problem from a problem on the route to it.

Public — what CEX.IO is reporting

Current & recent incidents

investigating

PTB withdrawals maintenance

2026-10-28 13:07 UTC · still open per the provider’s page — may be stale · source

investigating

VELO withdrawals maintenance

2026-09-30 12:19 UTC · still open per the provider’s page — may be stale · source

Resolved

CEX.IO Spot and Margin Trading maintenance

2026-10-27 12:13 UTC · source

Resolved

ATOM transactions maintenance

2026-09-23 16:19 UTC · source

Incident titles and states as published by the provider. Times in UTC.

Track record

SquidGrid has archived 5 incidents from CEX.IO’s own status page since 2026-09-22.

Recent incidents in the archive

Computed by SquidGrid from the incidents CEX.IO published. Their own page shows only recent history; this archive keeps every one.

Independent path health

A status page tells you what CEX.IO has published. SquidGrid independently observes the actual routes from its own worldwide fleet against their own baselines — so when a path moves off its usual range before (or without) a status post, you still see it, and you see where.

CEX.IO runs its services on other companies’ networks rather than operating its own, so path measurements roll up to its hosting providers. SquidGrid’s assessment of CEX.IO is its published incident record, archived and analyzed above and kept after the provider’s own page forgets it.

SquidGrid is not affiliated with CEX.IO.