Skip to content

Outage tracker / Mercury

Is Mercury down?

I'm having a problem

Operationalchecked 2 minutes ago

We reached Mercury from all 10 regions we check.

Functional endpoints verified

Last outage: 30 min on Aug 31, 2026 (API, from US-East).

our independent probeslive · checked Sep 5, 2026, 2:06 AM UTC
US-East186 msOperational
US-West226 msOperational
Europe156 msOperational
Asia-Pacific838 msOperational
US-Central260 msOperational
Canada341 msOperational
UK228 msOperational
Southeast Asia690 msOperational
Australia1122 msOperational
South America549 msOperational
their status pagetheir claim, not our reading

Mercury publishes no status feed we can read, so the only independent reading here is ours on the left.

Mercury response time, by region

US-East
341msp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 653ms2026-08-23 UTC: p95 812ms2026-08-24 UTC: p95 861ms2026-08-25 UTC: p95 909ms2026-08-26 UTC: p95 1.2s2026-08-27 UTC: p95 1.4s2026-08-28 UTC: p95 352ms2026-08-29 UTC: p95 843ms2026-08-30 UTC: p95 1.2s2026-08-31 UTC: p95 1.0s2026-09-01 UTC: p95 836ms2026-09-02 UTC: p95 556ms2026-09-03 UTC: p95 510ms2026-09-04 UTC: p95 571ms2026-09-05 UTC: p95 341ms
Aug 7Aug 21Sep 5
US-West
421msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 238ms2026-08-23 UTC: p95 435ms2026-08-24 UTC: p95 366ms2026-08-25 UTC: p95 803ms2026-08-26 UTC: p95 420ms2026-08-27 UTC: p95 644ms2026-08-28 UTC: p95 461ms2026-08-29 UTC: p95 451ms2026-08-30 UTC: p95 787ms2026-08-31 UTC: p95 728ms2026-09-01 UTC: p95 783ms2026-09-02 UTC: p95 628ms2026-09-03 UTC: p95 437ms2026-09-04 UTC: p95 528ms2026-09-05 UTC: p95 421ms
Aug 7Aug 21Sep 5
Europe
541msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 173ms2026-08-23 UTC: p95 476ms2026-08-24 UTC: p95 565ms2026-08-25 UTC: p95 495ms2026-08-26 UTC: p95 363ms2026-08-27 UTC: p95 471ms2026-08-28 UTC: p95 567ms2026-08-29 UTC: p95 616ms2026-08-30 UTC: p95 681ms2026-08-31 UTC: p95 632ms2026-09-01 UTC: p95 634ms2026-09-02 UTC: p95 689ms2026-09-03 UTC: p95 720ms2026-09-04 UTC: p95 629ms2026-09-05 UTC: p95 541ms
Aug 7Aug 21Sep 5
Asia-Pacific
857msp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 779ms2026-08-23 UTC: p95 1.3s2026-08-24 UTC: p95 1.3s2026-08-25 UTC: p95 1.4s2026-08-26 UTC: p95 1.4s2026-08-27 UTC: p95 1.4s2026-08-28 UTC: p95 1.3s2026-08-29 UTC: p95 1.2s2026-08-30 UTC: p95 1.2s2026-08-31 UTC: p95 1.2s2026-09-01 UTC: p95 1.4s2026-09-02 UTC: p95 1.2s2026-09-03 UTC: p95 1.6s2026-09-04 UTC: p95 1.2s2026-09-05 UTC: p95 857ms
Aug 7Aug 21Sep 5
US-Central
255msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 585ms2026-09-04 UTC: p95 406ms2026-09-05 UTC: p95 255ms
Aug 7Aug 21Sep 5
Canada
333msp95 · latest
500ms250ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 363ms2026-09-04 UTC: p95 376ms2026-09-05 UTC: p95 333ms
Aug 7Aug 21Sep 5
UK
583msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 713ms2026-09-04 UTC: p95 503ms2026-09-05 UTC: p95 583ms
Aug 7Aug 21Sep 5
Southeast Asia
1.4sp95 · latest
2.5s1.3s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 2.4s2026-09-04 UTC: p95 1.7s2026-09-05 UTC: p95 1.4s
Aug 7Aug 21Sep 5
Australia
1.1sp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.8s2026-09-04 UTC: p95 1.4s2026-09-05 UTC: p95 1.1s
Aug 7Aug 21Sep 5
South America
1.3sp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.2s2026-09-04 UTC: p95 1.2s2026-09-05 UTC: p95 1.3s
Aug 7Aug 21Sep 5

Is it Mercury, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Mercury -- it cannot diagnose Mercury's own systems.

What we measured, function by function

Mercury answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • APIprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 186msstatus code: 401checked: Sep 5, 2026, 2:04 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Mercury normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 226msstatus code: 401checked: Sep 5, 2026, 2:04 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Mercury normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 260msstatus code: 401checked: Sep 5, 2026, 2:02 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Mercury normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 341msstatus code: 401checked: Sep 5, 2026, 2:03 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Mercury normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 549msstatus code: 401checked: Sep 5, 2026, 2:06 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Mercury normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 156msstatus code: 401checked: Sep 5, 2026, 2:04 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Mercury normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 228msstatus code: 401checked: Sep 5, 2026, 1:38 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Mercury normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 838msstatus code: 401checked: Sep 5, 2026, 1:54 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Mercury normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 690msstatus code: 401checked: Sep 5, 2026, 1:12 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Mercury normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 1122msstatus code: 401checked: Sep 5, 2026, 2:03 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Mercury normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Mercury, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Mercury yet, which is not evidence that nothing is wrong.

Recent outages

Partial outage, under our ~30m probe resolutionmeasured by our probes · US-East2026-08-31
Partial outage, under our ~30m probe resolutionmeasured by our probes · Europe2026-08-30

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Mercury since August 22, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Mercury covering any window you pick, with our measurements and Mercury's own claim at the time, side by side.

Full availability history for Mercury: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Tell me when this goes down

Get told when we measure this

We will tell you when our probes stop reaching Mercury, and again when they can reach it again. That is our own measurement from ten regions, not Mercury's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

Put this badge in your README

Mercury uptime measured by RealUptimeLive, from this page's own readings.
[![Mercury uptime measured by RealUptime](https://realuptime.io/outages/mercury/badge.svg?days=30)](https://realuptime.io/outages/mercury)
<a href="https://realuptime.io/outages/mercury"><img src="https://realuptime.io/outages/mercury/badge.svg?days=30" alt="Mercury uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Mercury's SLA implies, from our measurement

At or above your target

We measured none of downtime for Mercury over the 338h 8m since we started watching it on 2026-08-22, which is 100% uptime by our reading. A 99.9% target allows 20 minutes over that period.

By our measurement there is no shortfall to claim for this period.

Separately, we measured 59 minutes where only one of our regions was affected. It is excluded above because most SLAs would not credit it, and it is the kind of outage a single-vantage monitor never sees at all.

This is computed from our own probe measurements, not from Mercury's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional: live API
https://api.mercury.com/api/v1/accounts
secondary
https://mercury.com/
RealUptime is not affiliated with Mercury; the name identifies what we measured, and nothing here speaks for Mercury's own team. We send a single web request to Mercury from 10 regions on our own schedule and time the response. We do not see inside Mercury's systems, do not use an account or real transaction, and are not the same signal Mercury's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Mercury is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.