Last updated: November 10, 2026
Is CouchDB down? User reports indicate possible problems with CouchDB
Apache CouchDB is a document database that stores JSON and syncs by replication between servers and devices. It is known for offline-first apps and its HTTP API.
Report a problem !
Select which issue applies
CouchDB problems reported in the last 24 hours
Most reported problems
All quiet. No issues reported in the last 24 hours.
Your feedback
How would you rate CouchDB over the past 3 months?
Most reported locations
Where CouchDB reports are coming from in the last 24 hours.
No problem locations to show yet. CouchDB looks fine right now. Locations appear here as soon as users submit reports.
Latest CouchDB user reports
No reports yet — be the first to report a problem above.
CouchDB outage history
Our latest check and the live report status for CouchDB.
✓ Our latest check (8 November 2026, 3:30 AM PKT): couchdb.apache.org answered normally in 143 ms.
Good news. CouchDB has no reported problems right now. If it is not working for you, report it above and your report will appear here.
CouchDB uptime and reports
Live report counts and the day by day record for the 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 CouchDB down alerts
Leave your email and we will tell you when CouchDB is having problems, and when it is back up. No spam.
CouchDB on social media
An early signal from outside our site, watched in rotation.
Posts on Bluesky saying CouchDB is down. Checked 8 November 2026, 1:07 PM PKT.
Quiet right now. Nobody on Bluesky is saying CouchDB is down.
Guides that can fix it
Step by step fixes for the problems people report most.
→ Is My Internet Down? How to Tell in Minutes
→ How to Restart Your Router the Right Way
→ How to Change Your DNS Servers
Is CouchDB Down Right Now?
No. CouchDB is not down as a public service, because Apache CouchDB runs on your own servers. When it seems down, the cause is your instance: the service, the config, or the storage under it.
This page tracks the CouchDB status problems administrators hit most. Use it to sort out whether you face a start failure, a replication stall, an access problem, or a CouchDB outage inside your own setup.
Is CouchDB Down for Me or Everyone?
Start with the simplest test. Open the root URL on port 5984 and look for the welcome JSON. If that answers, the server lives and your problem sits in a database, a view, or permissions.
If nothing answers, check the process and its logs before touching config. Disk-full errors and bad config edits after an upgrade explain most dead instances.
Why Won’t CouchDB Start or Open Fauxton?
Config edits are the classic cause. One bad line in the ini files and the service refuses to start. The log names the file and the offending setting, so read it before changing anything else.
Fauxton, the admin interface, lives under the /_utils path. A server can run fine while Fauxton 404s, if the path is wrong or a proxy strips it. Test the root JSON to separate the two problems.
Why Is Replication Stuck or Failing?
Replication needs working network paths and valid credentials on both ends. An expired password inside the replicator document loops forever. The replicator status shows the error while documents stop moving.
Design documents and large attachments slow things further. A single huge document can stall a stream that otherwise looks healthy. Watch the progress counters to find where it sticks.
Why Do I Get ‘Name or Password Is Incorrect’?
CouchDB 3.x ended the old admin party. A fresh install needs a server admin created before it serves requests. Old guides that assume open access now land on a login wall.
Forgotten admin passwords are common too. Admin accounts live in the config file as hashed entries. Editing that section and restarting is the supported way back in.
Why Is My Database So Slow or So Big?
Every edit creates a new revision, and old revisions take space until compaction. A busy database grows fast between compactions. The file on disk reflects history, not just current data.
Views build indexes on first use. A changed design document triggers a full rebuild, and queries crawl while it runs. Large databases feel frozen during that first index pass.
Common CouchDB Problems and Fixes
Fauxton login loops back
Clear cookies for the server address and sign in again. Confirm the account is a server admin in the config. Mixed http and https setups break the session cookie often.
Replication keeps retrying
Open the replicator document and update the credentials inside it. Then check that the target server is reachable and its disk is not full.
View index never finishes
Give it time on a large database, and watch progress in the tasks list. Avoid editing the design document again, since each edit restarts the build from zero.
Database file keeps growing
Run compaction on the database and its views. Then set a revision limit that suits your app, so old edit history stops piling up forever.
Conflict documents everywhere
Conflicts come from editing the same document on two replicas at once. Pick a winner in your app logic, save it, and delete the losing revisions.
Having a problem with CouchDB?
Comments are public and help others understand the issue.
Frequently Asked Questions
What is the default port for CouchDB?
CouchDB listens on port 5984 by default. The admin interface, Fauxton, sits under the /_utils path on that same port.
How do I reset a CouchDB admin password?
Edit the admins section of the local config file and put a plain password there. Restart CouchDB, and it hashes the new password on startup.
Why does CouchDB keep so many document revisions?
Revisions let replication resolve conflicts safely. Old revisions hold space until compaction. You can lower the revision limit per database if history grows too fast.
What is the difference between CouchDB views and Mango queries?
Views are prebuilt indexes written in JavaScript that you define ahead of time. Mango is a JSON query language that finds documents without a custom index for every query.
Why is my replication showing an error state?
The status names the cause, usually bad credentials, an unreachable target, or a full disk. Fix that cause, and the replicator retries on its own.
Does CouchDB work offline and sync later?
Yes. That is its core design. Apps store data locally and replicate when a connection returns, with conflicts resolved during sync.