Skip to content

Outage tracker / Ledger / In the US

Is Ledger down in the US?

Vendor lists an old incident, not shown as liveWhat Ledger reports

Ledger still lists an incident opened on 2026-10-27 with no update since 2026-10-27; we do not show it as live.

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

Ledger'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 Ledger at Nov 6, 2026, 5:07 PM UTC.

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

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

Email me when Ledger 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 Ledger'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 passing107 checks in 24h, 100.00%

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

Ledger from Ashburn and San Jose over the last 30 days

Over the last 30 days, Ledger answered our San Jose probe in 2,459 ms on average, and 1 check in 20 took longer than 4,698 ms.

Over the last 30 days, Ledger answered our Ashburn probe in 2,641 ms on average, and 1 check in 20 took longer than 4,819 ms.

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

From Ashburn and San Jose we ran 1,015 checks of Ledger in 5 days, and 1,015 answered cleanly: 100.00% availability.

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

In Ashburn local time (EST), Ledger was slowest around 4 PM, at 3,349 ms on average over the last 14 days, and quickest around 3 AM, at 1,638 ms.

Day (UTC)ChecksAvailabilityAverage response
Fri, Nov 6173100.00%2,409 ms
Thu, Nov 5247100.00%2,490 ms
Wed, Nov 4247100.00%2,284 ms
Tue, Nov 3245100.00%2,529 ms
Mon, Nov 2103100.00%3,749 ms

Ledger outages measured from the US

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

How the other regions read right now

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

Probe cityRight nowLast 24h
FrankfurtChecks passing100.00% of 96 checks
TokyoChecks passing100.00% of 57 checks

Other countries we check Ledger from

How we measured this

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

See Ledger'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 Ledger 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