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

As listed on BitGo’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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.

The full archive is on the BitGo status & history page.

Related: BitGo status & history. SquidGrid is not affiliated with BitGo.