PulseWatch manages 5 data types including abuse signals. Helps you organize, track, and share your work in 1 place for teams and solo users.

How does PulseWatch know if BitGo is down?

PulseWatch evaluates user reports and replay-approved automated evidence for BitGo. Canonical source identity prevents duplicate pipelines from being counted as independent corroboration.

How many people have reported BitGo issues today?

As of Oct 2, 2026 11:37 UTC, 0 users had reported issues with BitGo in the previous 24 hours.

How can I report a BitGo outage?

Click the "Report an issue" button on this page to submit an outage report. Reports are evaluated with moderation, baseline, and corroboration controls before they can support an incident.

Other

Is BitGo down right now?

NormalOfficial status last polled Oct 2, 2026 11:32 UTCbitgo.com Official status page

Are you on the BitGo team and see something inaccurate? Report it to us. We respond within one business day.

Is BitGo down right now?

No. BitGo has a current operational conclusion. Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).

Status as of Oct 2, 2026 11:37 UTC

Normal

BitGo is operating normally

As of Oct 2, 2026 11:37 UTC

No elevated reports in the last 15 minutes. Baseline 5 reports/hour.

Reports 24h

Last incident

Sep 23, 2026 16:02 UTC

Trend

0/15m

Baseline

5/hr

Observed health

Unknown

No samples qualify for a combined success and latency score.

Evidence strength

No current issue evidence

No current corroborated or observed finding.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for BitGo.

Incident days

No recorded incident

25h 15m

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical

Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.

Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for BitGo. Hover a day for detail.

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

Days with incidents

2 incidents

Busiest day

25h 15m

Recorded duration

Report volume

0 reports in last 24H

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

BitGo outage on September 23 55-minute disruption

Sep 23, 03:06 PM → Sep 23, 04:02 PM · 55 minutes · medium

A partial outage affecting BitGo was detected through automated monitoring signals, including the vendor's status page. The disruption began at 2026-09-23T15:06:58.379Z and was resolved at 2026-09-23T16:02:52.210Z, lasting 55 minutes.

Peak reports

in 15 min

Total reports

during outage

Duration

55 minutes

until recovery

Impact

This medium-severity incident resulted in a 55-minute disruption to BitGo services. Automated signals indicated a partial outage during this period. No user-reported data was collected for this incident, and therefore no specific user-visible impact, affected regions, or issue types could be determined from user reports.

Outage timeline

Sep 23, 03:06 PM
PulseWatch detected the incident from automated vendor and probe signals (medium severity)
Sep 23, 03:06 PM
Status updated: possible issue
Sep 23, 04:02 PM
Signals cleared — incident resolved

Official updates

Sep 23, 03:06 PM
BitGo status page acknowledged the incident.
View official source

Reliability

Detected by PulseWatch

30-day uptime

96.5%

90-day uptime

98.3%

Calculated from BitGo's detected incidents. Lower than the vendor's own reported SLA? That's the whole point — we measure what users actually experience.

Other other services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

Be the first to post a report.

Incident timeline

Scrub through detection, peak, status updates, and resolution.

Full history →

ResolvedMedium

BitGo: the vendor reports a partial outage on its own status page. Single origin, not independently confirmed. Users who watch BitGo or have an alert rule on it can be alerted, labelled vendor-reported.

9/23/2026, 3:06:58 PM · 55 min

03:06 PM04:02 PM

Detection9/23/2026, 3:06:58 PM · 8d ago

Detected — medium severity

ResolvedHigh

BitGo: the vendor reports a critical-impact incident on its own status page. Single origin, not independently confirmed. Users who watch BitGo or have an alert rule on it can be alerted, labelled vendor-reported.

9/22/2026, 1:06:41 PM · 1d 0h

01:06 PM01:26 PM

Detection9/22/2026, 1:06:41 PM · 9d ago

Detected — high severity

ResolvedMedium