Live / BitGo / Incident
BitGo: Issue processing OSMO transactions
BitGo · bitgo.comMinor incidentResolved2026-11-13 18:09 UTC
Public — what happened
Summary
BitGo said it had a minor issue affecting the processing of transactions for OSMO, the Osmosis network's token, starting at 11:09 UTC on 2026-11-13. Later that morning, at 13:37 UTC, the company reported that the Osmosis network had restarted after an earlier halt, but that normal handling on its side was still waiting on a patch from the Osmosis Foundation. BitGo marked the incident resolved at 18:09 UTC the same day.
Affected
API, Wallets
Timeline
- Started — 2026-11-13 11:09 UTC
- Investigating — 2026-11-13 11:09 UTC (2 updates)
- Resolved — 2026-11-13 18:09 UTC · 6h 59m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach BitGo against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for BitGo: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the BitGo report →
More from BitGo
Covered in The Squid’s Ink, Week 47, 2026, our weekly internet health report.