Last updated: November 10, 2026

Is Logseq down? User reports show no current problems with Logseq

Logseq is a free, open-source knowledge app that stores your notes as local Markdown files in a graph of linked blocks. Its paid Sync service moves graphs between devices, and many users add Git backups.

Report a problem

Report a problem !

Select which issue applies

Jump to comments

Logseq problems reported in the last 24 hours

Learn about our methodology

Most reported problems

All quiet. No issues reported in the last 24 hours.

Your feedback

How would you rate Logseq over the past 3 months?

/* v1.5.0: locations + reports-map side by side (Downdetector-style). */

Most reported locations

Where Logseq reports are coming from in the last 24 hours.

No problem locations to show yet. Logseq looks fine right now. Locations appear here as soon as users submit reports.

Reports map

📍 View Map

Nothing on the map right now. Logseq looks fine.

Latest Logseq user reports

No reports yet — be the first to report a problem above.

Logseq outage history

Our latest check and the live report status for Logseq.

✓ Our latest check (8 November 2026, 4:00 AM PKT): logseq.com answered normally in 79 ms.

Good news. Logseq has no reported problems right now. If it is not working for you, report it above and your report will appear here.

Logseq uptime and reports

Live report counts and the day by day record for the last 30 days.

0
Last hour
0
Last 24 hours
0
Last 30 days

User reports received in each period.

Last 30 days, day by day: 11 October 2026 to 9 November 2026

Green: up. Red: outage. Amber: some checks failed. Grey: no record yet.

The daily record builds from today as our checks run. Grey days have no saved record yet. A red day marks a confirmed outage.

Get Logseq down alerts

Leave your email and we will tell you when Logseq is having problems, and when it is back up. No spam.

Logseq on social media

An early signal from outside our site, watched in rotation.

0
Last hour
0
Last 24 hours

Posts on Bluesky saying Logseq is down. Checked 8 November 2026, 1:51 PM PKT.

Quiet right now. Nobody on Bluesky is saying Logseq is down.

Is Logseq Down Right Now?

No, Logseq itself is not down. The app is local-first, so your graph opens from your own device even with no network.

Trouble starts when a graph folder meets a sync service. Logseq Sync, iCloud, and Dropbox can fight over the same files and damage them. Check the Logseq status above, then find your fault below.

Is Logseq Down for Me or Everyone?

Open your graph folder and look at the files directly. If the Markdown files hold your text, your data exists and the app or sync layer is at fault.

Ask, is Logseq down for me or for everyone? Logseq Sync faults hit many users together, while a folder clash on your machine hurts only your own graph. A real Logseq outage hits the Sync service itself.

Why Did Logseq Sync Overwrite Your Notes?

Users have watched Sync replace fresh local edits with older cloud copies. In one report, turning Sync back on changed about 200 files across a graph.

Editing before a sync fully lands invites the same loss. Let every device finish syncing before you write, and keep a Git backup of the folder.

Why Does Your Graph Look Empty?

A nested graph is the sneaky cause. If a new graph was created inside an old graph folder, Logseq opens the wrong level and your pages seem gone.

The files still sit in the inner folders. Unlink the graph, move the folders to their own clean folder, and link that folder as the graph.

Why Is a Cloud Folder a Risky Home for Your Graph?

iCloud and Dropbox also rewrite files when they sync. Two writers on one folder can swap in old copies and quietly undo your newest work.

Running Logseq Sync on top of a cloud folder doubles the risk. The safest setup is a plain local folder, with Sync or Git as the only mover.

Common Logseq Problems and Fixes

These fixes cover the faults that scare Logseq users most.

Pages Keep Refreshing While You Scroll

Very long pages can trigger constant refreshes, mostly with some plugins active. Test with plugins off, and split giant pages into linked smaller pages.

Notes Vanished After a Sync

Look in the logseq/bak folder inside your graph right away. Logseq keeps backup copies there, and many lost pages return from that folder intact.

Sync Fails Between Phone and Computer

Both devices must use the same graph and the same sync account. Check the graph name on each device, and keep the iOS graph inside the Logseq folder.

Files With Odd Characters Will Not Sync

Names with special characters can block older builds from syncing. Update Logseq, and rename pages that use symbols in their titles.

The Mobile App Feels Painfully Slow

The phone apps are lighter than the desktop build. Keep daily work on desktop for big graphs, and let the phone finish syncing before you edit.

Having a problem with Logseq?

Comments are public and help others understand the issue.

Subscribe
Notify of
guest
0 Comments
Oldest
Newest Most Voted

Frequently Asked Questions

Why did Logseq Sync overwrite my local notes?

Sync can push an older cloud copy over fresh local edits, mostly when you edit before sync finishes. Keep a Git backup, and let every device finish syncing before you write.

Why does my Logseq graph look empty?

You may have a nested graph, where a new graph sits inside the old folder. Unlink the graph, move its folders somewhere clean, and link that folder again.

How do I recover lost notes in Logseq?

Check the logseq/bak folder inside your graph folder first, since Logseq keeps backup copies there. Page history inside the app can also restore older versions of a page.

Why is Logseq Sync not working between my phone and computer?

Both devices need the same graph, the same account, and a finished sync. On iOS the graph must live in the Logseq folder, or sync cannot reach it.

Is it safe to keep my Logseq graph in iCloud or Dropbox?

It is risky. Cloud folders rewrite files on their own schedule and can clash with Logseq, which has caused data loss. Use a local folder and one sync method instead.

Why do pages keep refreshing while I scroll in Logseq?

Very long pages and some plugins trigger repeated refreshes. Turn plugins off to test, and split huge pages into smaller linked pages to calm the view.