Skip to content

Outage tracker / Mezmo / In the US

Is Mezmo down in the US?

Vendor reports no incidentWhat Mezmo reports

Mezmo reports no incident on its status page.

As of the last successful poll, 2026-11-05 21:23 UTC.

Mezmo's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingin the US, measured from Ashburn and San Jose

All 2 of our probes in the US, in Ashburn and San Jose, read checks passing when they last checked Mezmo at Nov 5, 2026, 9:33 PM UTC.

Over the last 24 hours we completed 252 checks from Ashburn and San Jose and 252 answered cleanly, 100.00% availability.

Of the 2 other regions we check Mezmo from, all 2 read checks passing right now.

Email me when Mezmo 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 Mezmo's own statement from its status page, with our regional reading beside it.

What our Ashburn and San Jose probes measured

AshburnChecks passing142 checks in 24h, 100.00%
San JoseChecks passing110 checks in 24h, 100.00%

Last checked Nov 5, 2026, 9:33 PM UTC.

Mezmo from Ashburn and San Jose over the last 30 days

Over the last 30 days, Mezmo answered our Ashburn probe in 1,045 ms on average, and 1 check in 20 took longer than 1,442 ms.

Over the last 30 days, Mezmo answered our San Jose probe in 1,399 ms on average, and 1 check in 20 took longer than 1,995 ms.

Ranked by average response time across the 4 cities we check Mezmo from, Ashburn 2nd, San Jose 3rd; Frankfurt was fastest at 503 ms and Tokyo slowest at 1,582 ms.

From Ashburn and San Jose we ran 830 checks of Mezmo in 4 days, and 829 answered cleanly: 99.87% availability.

1 of the 4 days had at least one failed check. The weakest was Nov 3 (UTC), at 99.59% across 247 checks.

In Ashburn local time (EST), Mezmo was slowest around 12 PM, at 1,471 ms on average over the last 14 days, and quickest around 10 AM, at 694 ms.

Day (UTC)ChecksAvailabilityAverage response
Thu, Nov 5225100.00%1,166 ms
Wed, Nov 4254100.00%1,098 ms
Tue, Nov 324799.59%1,263 ms
Mon, Nov 2104100.00%1,367 ms

Mezmo outages measured from the US

Our Ashburn and San Jose probes measured no confirmed Mezmo outage in the last 90 days.

How the other regions read right now

Of the 2 other regions we check Mezmo from, all 2 read checks passing right now.

Probe cityRight nowLast 24h
FrankfurtChecks passing100.00% of 97 checks
TokyoChecks passing100.00% of 60 checks

Other countries we check Mezmo from

How we measured this

The US readings on this page come from RealUptime's own Ashburn and San Jose probes against Mezmo's public endpoints. They are not user reports, and they are not Mezmo's own status page.

See Mezmo's full check readings, the 90-day history by region, or the outage tracker methodology.

The US readings here are taken from that country and show the time of the last one, but Mezmo has not yet accumulated enough continuous history for us to publish this page to search engines.

Check your own site from Ashburn

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

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter