Skip to content

Outage tracker / Logseq / In Japan

Is Logseq down in Japan?

Checks passingin Japan, measured from Tokyo

Our Tokyo probe last checked Logseq at Nov 5, 2026, 4:35 PM UTC and read checks passing.

Over the last 24 hours we completed 61 checks from Tokyo and 61 answered cleanly, 100.00% availability.

Of the 3 other regions we check Logseq from, all 3 read checks passing right now.

Email me the next time we see Logseq go down

One email when our checks of Logseq fail from two or more distant regions, and one when they pass, after you confirm the address. No account, no card.

This is our own reading from outside. It is not Logseq's official status.

What our Tokyo probe measured

TokyoChecks passing61 checks in 24h, 100.00%

Last checked Nov 5, 2026, 4:35 PM UTC.

Logseq from Tokyo over the last 30 days

Over the last 30 days, Logseq answered our Tokyo probe in 1,496 ms on average, and 1 check in 20 took longer than 2,304 ms.

Ranked by average response time across the 4 cities we check Logseq from, Tokyo 4th; Frankfurt was fastest at 519 ms and Tokyo slowest at 1,496 ms.

From Tokyo we ran 190 checks of Logseq in 4 days, and 190 answered cleanly: 100.00% availability.

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

In Tokyo local time (GMT+9), Logseq was slowest around 11 PM, at 2,212 ms on average over the last 14 days, and quickest around 9 PM, at 1,082 ms.

Day (UTC)ChecksAvailabilityAverage response
Thu, Nov 543100.00%1,381 ms
Wed, Nov 459100.00%1,618 ms
Tue, Nov 360100.00%1,495 ms
Mon, Nov 228100.00%1,423 ms

Logseq outages measured from Japan

Our Tokyo probe measured no confirmed Logseq outage in the last 90 days.

How the other regions read right now

Of the 3 other regions we check Logseq from, all 3 read checks passing right now.

Probe cityRight nowLast 24h
AshburnChecks passing100.00% of 142 checks
San JoseChecks passing100.00% of 111 checks
FrankfurtChecks passing100.00% of 99 checks

Other countries we check Logseq from

How we measured this

Japan readings on this page come from RealUptime's own Tokyo probe 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.

Japan 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 Tokyo

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