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 13:09:36 GMT |
| Latest update published (provider) | Wed, 18 Nov 2026 13:33:47 GMT |
| Seen by Spike | Wed, 18 Nov 2026 13:34: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 13:33 UTC · seen by Spike 1 min laterCoinbase said: “This incident has been resolved.”
- Revision 1 · Incident opened
Published by Coinbase 2026-11-18 13:09 UTC · seen by Spike 1 min laterCoinbase said: “We are aware that some users may be experiencing delayed sends and receives on the Injective Network. Buys, Sells, and Fiat withdrawals/deposits remain unaffected. We’re working on this issue and will provide updates as soon as possible. Your funds are safe.”