Live  /  BitGo  /  Incident

BitGo: Delay in processing INJECTIVE transactions

BitGo · bitgo.comMajor incidentResolved2026-10-07 12:48 UTC
Public — what happened

Summary

BitGo reported a major incident on October 7, 2026, in which transactions on the Injective network were being processed with delays, starting at 09:23 UTC. A few minutes later, the company said the problem originated upstream and was outside its control, adding that the Injective Foundation had acknowledged it and planned to release upgrade instructions. BitGo marked the incident as resolved at 12:48 the same day.

Affected

API, Wallets, Injective

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 42, 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.