Skip to content

Outage tracker / Breeze ChMS / In the US

Is Breeze ChMS down in the US?

Vendor reports no incidentWhat Breeze ChMS reports

Breeze ChMS reports no incident on its status page.

As of the last successful poll, 2026-11-05 17:54 UTC.

Breeze ChMS'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 Breeze ChMS at Nov 5, 2026, 6:00 PM UTC.

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

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

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

What our Ashburn and San Jose probes measured

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

Last checked Nov 5, 2026, 6:00 PM UTC.

Breeze ChMS from Ashburn and San Jose over the last 30 days

Over the last 30 days, Breeze ChMS answered our Ashburn probe in 1,041 ms on average, and 1 check in 20 took longer than 1,642 ms.

Over the last 30 days, Breeze ChMS answered our San Jose probe in 1,456 ms on average, and 1 check in 20 took longer than 2,018 ms.

Ranked by average response time across the 4 cities we check Breeze ChMS from, Ashburn 2nd, San Jose 4th; Frankfurt was fastest at 989 ms and San Jose slowest at 1,456 ms.

From Ashburn and San Jose we ran 784 checks of Breeze ChMS in 4 days, and 784 answered cleanly: 100.00% availability.

Every one of those days was clean: not one failed check.

In Ashburn local time (EST), Breeze ChMS was slowest around 7 AM, at 1,658 ms on average over the last 14 days, and quickest around 1 PM, at 785 ms.

Day (UTC)ChecksAvailabilityAverage response
Thu, Nov 5185100.00%1,217 ms
Wed, Nov 4251100.00%1,109 ms
Tue, Nov 3245100.00%1,295 ms
Mon, Nov 2103100.00%1,324 ms

Breeze ChMS outages measured from the US

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

How the other regions read right now

Of the 2 other regions we check Breeze ChMS 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 Breeze ChMS from

How we measured this

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

See Breeze ChMS'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 Breeze ChMS 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