View Evidence Brief What changed, who says so and when, and what was known at each revision.
Four clocks
| Began (provider) | Wed, 18 Nov 2026 02:43:27 GMT |
| Latest update published (provider) | Wed, 18 Nov 2026 04:23:22 GMT |
| Seen by Spike | Wed, 18 Nov 2026 04:23:25 GMT |
| Delivered | Per customer, in each Spike Pro workspace's delivery receipts. |
What the provider states
| Claim | Value | Evidence |
|---|---|---|
| service status | resolved | Direct: Coinbase status page · source ↗ |
| Cause | Coinbase has not stated a cause in a structured field. Read the provider's updates. | |
| Customer impact | Depends on what you run. Spike Pro matches this incident to the services a workspace lists. | |
Revisions, newest first
- Revision 2 · Resolved
Published by Coinbase 2026-11-18 04:23 UTC · seen by Spike 0 min laterCoinbase said: “This incident has been resolved.”
- Revision 1 · First recorded by Spike
Published by Coinbase 2026-11-18 02:43 UTC · seen by Spike 54 min later (first read of this status page)Coinbase said: “We are aware that some users may be experiencing delayed sends and receives for ALEO. Buys, Sells, and Fiat withdrawals/deposits are not affected. We are investigating this issue and will provide an update shortly. Rest assured, your funds are safe.”