Is Logseq down in the US?
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 Logseq at Nov 5, 2026, 4:30 PM UTC.
Over the last 24 hours we completed 253 checks from Ashburn and San Jose and 253 answered cleanly, 100.00% availability.
Of the 2 other regions we check Logseq from, all 2 read checks passing right now.
Email me the next time we see Logseq go down
What our Ashburn and San Jose probes measured
Last checked Nov 5, 2026, 4:30 PM UTC.
Logseq from Ashburn and San Jose over the last 30 days
Over the last 30 days, Logseq answered our Ashburn probe in 796 ms on average, and 1 check in 20 took longer than 1,157 ms.
Over the last 30 days, Logseq answered our San Jose probe in 866 ms on average, and 1 check in 20 took longer than 1,241 ms.
Ranked by average response time across the 4 cities we check Logseq from, Ashburn 2nd, San Jose 3rd; Frankfurt was fastest at 520 ms and Tokyo slowest at 1,500 ms.
From Ashburn and San Jose we ran 776 checks of Logseq in 4 days, and 775 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 248 checks.
In Ashburn local time (EST), Logseq was slowest around 2 PM, at 1,072 ms on average over the last 14 days, and quickest around 11 AM, at 535 ms.
| Day (UTC) | Checks | Availability | Average response |
|---|---|---|---|
| Thu, Nov 5 | 170 | 100.00% | 844 ms |
| Wed, Nov 4 | 254 | 100.00% | 795 ms |
| Tue, Nov 3 | 248 | 99.59% | 821 ms |
| Mon, Nov 2 | 104 | 100.00% | 887 ms |
Logseq outages measured from the US
Our Ashburn and San Jose probes measured no confirmed Logseq outage in the last 90 days.
How the other regions read right now
Of the 2 other regions we check Logseq from, all 2 read checks passing right now.
| Probe city | Right now | Last 24h |
|---|---|---|
| Frankfurt | Checks passing | 100.00% of 99 checks |
| Tokyo | Checks passing | 100.00% of 60 checks |
Other countries we check Logseq from
How we measured this
The US readings on this page come from RealUptime's own Ashburn and San Jose probes against Logseq's public endpoints. They are not user reports, and they are not Logseq's own status page.
See Logseq'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 Logseq 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 serversRun 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