Skip to content

Outage tracker / Semaphore CI / In the US

Is Semaphore CI down in the US?

Vendor reports no incidentWhat Semaphore CI reports

Semaphore CI reports no incident on its status page.

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

Semaphore CI'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 Semaphore CI at Nov 5, 2026, 5:21 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 Semaphore CI from, all 2 read checks passing right now.

Email me when Semaphore CI 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 Semaphore CI'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, 5:21 PM UTC.

Semaphore CI from Ashburn and San Jose over the last 30 days

Over the last 30 days, Semaphore CI answered our Ashburn probe in 913 ms on average, and 1 check in 20 took longer than 1,377 ms.

Over the last 30 days, Semaphore CI answered our San Jose probe in 1,305 ms on average, and 1 check in 20 took longer than 1,794 ms.

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

From Ashburn and San Jose we ran 783 checks of Semaphore CI in 4 days, and 783 answered cleanly: 100.00% availability.

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

In Ashburn local time (EST), Semaphore CI was slowest around 12 AM, at 1,381 ms on average over the last 14 days, and quickest around 4 AM, at 605 ms.

Day (UTC)ChecksAvailabilityAverage response
Thu, Nov 5182100.00%1,056 ms
Wed, Nov 4251100.00%983 ms
Tue, Nov 3246100.00%1,113 ms
Mon, Nov 2104100.00%1,308 ms

Semaphore CI outages measured from the US

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

How the other regions read right now

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

Probe cityRight nowLast 24h
FrankfurtChecks passing100.00% of 99 checks
TokyoChecks passing100.00% of 61 checks

Other countries we check Semaphore CI from

How we measured this

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

See Semaphore CI'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 Semaphore CI 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