BitGo logo

Is BitGo Down?

SaaSLive status, outages, and incident history

No. BitGo is up right now.

Every monitored BitGo system is operational as of November 9, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 4m agoLive · every 60s

Know the moment BitGo breaks

BitGo is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

Official BitGo status page
How we know: the official BitGo status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

BitGo Status Summary

As of 20:26 UTC on 9 November 2026, BitGo is operational. PulsAPI checked BitGo's official status page and found 63 of 63 components operational, with no active incidents. Over the last 30 days PulsAPI measured 99.98% uptime for BitGo, counting degraded performance as up. The latest incident, "Issues accessing BitGo platform", was on Nov 7, 2026 and lasted 14 min.

Cite as: PulsAPI, “BitGo status”, checked 9 November 2026, 20:26 UTC. https://www.pulsapi.com/services/bitgo

BitGo Component Status

The main BitGo systems on this page. All 63 are operational right now.

63operational
API
Operational
Digital Assets » Algorand
Operational
Digital Assets » Aptos
Operational

60 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Digital Assets » Arbitrum, Digital Assets » Atom, Digital Assets » Avalanche C-chain, Digital Assets » Avalanche P-chain, Digital Assets » Berachain, Digital Assets » Binance Coin, Digital Assets » Bitcoin, Digital Assets » Bitcoin Cash, Digital Assets » Bitcoin Gold, Digital Assets » Bitcoin SV, Digital Assets » Canton, Digital Assets » Cardano, and 48 more.

See all of them free

Component statuses may change independently during partial outages.

Recent BitGo Outages & Incidents

Incident history from the official BitGo status page, including resolution updates.

Issues accessing BitGo platformResolved Nov 7, 2026 · 14 minResolved

This incident has been resolved. --- [2026-11-06T16:29:14.043-08:00] (monitoring) A fix has been implemented and we are monitoring the results. --- [2026-11-06T16:20:28.248-08:00] (investigating) We are currently investigating this issue.

Issues processing TransactionsResolved Oct 20, 2026 · 1h 58mResolved

This incident has been resolved. --- [2026-10-20T11:28:07.609-07:00] (monitoring) A fix has been implemented and we are monitoring the results. --- [2026-10-20T10:58:29.978-07:00] (identified) We've identified the cause as a network outage at a third-party data center provider. It is affecting connectivity to a number of the blockchain nodes we operate there. --- [2026-10-20T10:50:34.320-07:00] (investigating) We’re investigating connectivity issues affecting nodes. Coins affected: TON, IOTA, PLUME, SEI, EOS, BSC, NEAR, XTZ EVM, OG, MEGAETH, KAIA, INKETH, WEMIX, HYPE, SGB, TEMPO, INJECTIVE, GETH, OSMO, ADA, ALGO, APE, ARB, ARC, ASI, ATOM, AVAXP, TRX, HOODETH, BABY, FLUENTETH, PEARL, ETH, SOL, IP, and TIA. Customers may experience intermittent issues with services that depend on these nodes (Staking, Withdrawals, Deposits, etc) while we continue to investigate.

Canton Scheduled Network Upgrade (LSU)Resolved Oct 9, 2026 · 25h 31mResolved

This incident has been resolved. --- [2026-10-09T07:55:25.838-07:00] (investigating) We are continuing to investigate this issue. --- [2026-10-09T06:13:40.984-07:00] (investigating) The Canton Foundation is performing a Logical Synchronizer Upgrade (LSU) on Canton MainNet to adopt CantonBFT. This is a network-wide update and is not specific to BitGo. This will come into effect for 24 hours, from Friday (13:00 UTC) to Saturday (13:00 UTC) What to expect: Regular transactions, such as transfers, will continue to be processed during the freeze. Nothing can be added to or removed from the network during the freeze, so Canton wallet initialisations will not go through during this window.

BitGo Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a BitGo incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history91 days observed
Aug 1199.97% average · 18 days with incidentsNov 9

Going further back: BitGo uptime by month and every recorded BitGo outage.

Live BitGo Outage Reports

Problems reported by engineers using BitGo. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No BitGo problems reported yet.

Something wrong with BitGo on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About BitGo

BitGo exposes 66 monitored components on its status page at status.bitgo.com — API, Bitcoin (V1) and BitGo Trust Trade API among them. Follow BitGo downtime, degraded performance and resolved incidents here, with uptime history alongside your other SaaS services.

Over the past 30 days, PulsAPI has measured BitGo uptime at 99.98%. Response times, incident history, and SLA tracking for BitGo are available on the PulsAPI dashboard.

BitGo Status FAQ

Is BitGo down right now?

The verdict at the top of this page comes from the latest poll of the official BitGo status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if BitGo is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until BitGo recovers.

How do I check BitGo uptime history?

PulsAPI tracks BitGo uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 99.98%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever BitGo changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect BitGo outages?

PulsAPI reads the official BitGo status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual BitGo components?

Yes. PulsAPI monitors 63 individual BitGo components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when BitGo goes down?

Yes. Create a free account and subscribe to BitGo: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with BitGo to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot BitGo problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor BitGo?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so BitGo plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track BitGo with the rest of your stack

2660+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services