Skip to content

Outage tracker

Mercury: incident history

The last 24 hours in detail, Mercury's declared incident record, and our regional check results beside it.

← Back to Mercury's check readings

We started checking Mercury on August 22, 2026, which is 63 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.

Email me when Mercury reports an incident on its status page, and again when it reports it resolved.

One email when it is reported and one when it is resolved, after you confirm the address. No account, no card.

This is Mercury's own statement from its status page, with our regional reading beside it.

The last 24 hours

What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Mercury's own status page declared. Below it, any public chatter we saw about Mercury and the extra probe it triggered.

The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Mercury's own status page declared. Three records side by side; none of them changes another.

Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about Mercury in the last 24 hours, which is not evidence that nothing is wrong.
Mercury's status pageNo incident declared in the last 24 hours.

Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Mercury's own declaration, shown as they made it.

Third-party chatter, labeled

Public posts from the last hour that mention Mercury next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.

  • Bluesky posts1 in the last hour (prior day averaged 0.3/hour)

Checks passing by region

Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.

RegionChecks passingProbes recorded
US-East99.90%2910
US-West99.93%2911
Europe99.90%2908
Asia-Pacific99.93%2884
US-Central100.00%1206
Canada100.00%1206
UK100.00%1206
Southeast Asia99.92%1203
Australia99.92%1203
South America99.67%1205

Their declared record

Mercury's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.

Failed Investments Wire Transfers Out for Some CustomersMinor incident
Oct 7, 2026, 10:14 PM UTC to Oct 14, 2026, 3:42 PM UTC (6d 17h)resolved
their latest update (Oct 16, 2026, 4:13 PM UTC): This incident has been resolved. Investments transfers are fully restored and operating normally. No further action is needed. Thank you for your patience.
Issues Revealing Card Details on Web and MobileMinor incident
Oct 2, 2026, 4:11 PM UTC to Oct 2, 2026, 5:29 PM UTC (1h 18m)resolved
their latest update (Oct 2, 2026, 5:29 PM UTC): This incident has been resolved. Card detail revealing is fully restored and operating normally. No further action is needed. Thank you for your patience.
Account Actions Experiencing DelaysMinor incident
Sep 2, 2026, 12:02 AM UTC to Sep 2, 2026, 2:07 AM UTC (2h 5m)resolved
their latest update (Sep 2, 2026, 2:07 AM UTC): This incident has been resolved. Impacted account functions are fully restored and operating normally. No further action is needed. Thank you for your patience.
Intermittent Inbound & Outbound Call DisruptionMinor incident
Sep 1, 2026, 5:57 PM UTC to Sep 1, 2026, 6:36 PM UTC (38 min)resolved
their latest update (Sep 1, 2026, 6:36 PM UTC): This incident has been resolved. Phone calls with our Support team are fully restored and operating normally. No further action is needed. Thank you for your patience.

These entries are Mercury's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.

Mercury's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.

Full detail on what a probe does and does not prove is in the methodology page.