Fauna Status: How to Check If Fauna Is Down (2026)
Updated June 2026 · 5 min read · By API Status Check
Quick Answer: Check Fauna Status Now
Fauna is a serverless document-relational database with a global, multi-region architecture and a strongly-consistent transaction model. It exposes a GraphQL API and its own Fauna Query Language (FQL), making it popular with JAMstack and serverless JavaScript apps. When Fauna goes down, all database reads and writes fail — queries return errors, mutations stall, and GraphQL endpoints return 5xx responses. This guide explains how to check Fauna's status and distinguish a platform outage from a configuration or throttling issue.
Understanding Fauna's Status Page (status.fauna.com)
Fauna operates status.fauna.com — its official status page. Because Fauna databases are region-specific (Classic, US, EU), status is reported per region. A US-region incident does not affect EU or Classic databases, so check the status for your specific database region.
Fauna API (Classic)
The global multi-region API endpoint (db.fauna.com). Classic databases replicate across multiple regions for low-latency reads globally. Incidents here affect all Classic-region databases worldwide.
Fauna API (US Region)
The US-region endpoint (db.us.fauna.com). Databases created in the US region are hosted in us-east-1. US-region incidents are isolated from EU and Classic region status.
Fauna API (EU Region)
The EU-region endpoint (db.eu.fauna.com). Databases in the EU region are hosted in eu-central-1 for data residency compliance. EU incidents are independent of US and Classic status.
Fauna Dashboard
dashboard.fauna.com — the web console for browsing collections, running queries, and managing API keys. Dashboard incidents prevent browser-based management but do not affect database API access for your application.
What Fauna Status Colors Mean
⚠️ Fauna Platform Issue vs. App Issue — Know the Difference
Many "Fauna is down" reports turn out to be API key or throttling issues, not platform outages. Before assuming a platform problem:
- Verify your
FAUNA_SECRET(orFAUNA_KEY) environment variable is set and valid - Check whether you are connecting to the correct region endpoint (
db.fauna.com,db.us.fauna.com, ordb.eu.fauna.com) - Look for a 429 response — Fauna throttles databases that exceed read/write operation limits
- Confirm the target database and collection exist in the Fauna dashboard
- Test a simple query in the Fauna Shell to isolate whether the issue is code or platform
Monitor your Fauna-powered app with independent uptime monitoring
Fauna's status page shows platform health — not your specific database's health. Better Stack monitors your actual app endpoints and alerts you when they go down. Free plan available.
Try Better Stack Free →5 Ways to Check If Fauna Is Down
status.fauna.com (Official)
Fauna's official status page, with per-region status for Classic, US, and EU endpoints. Subscribe to email notifications to be alerted when incidents are posted and resolved. Always check the region that matches your database location.
Check status.fauna.com →Fauna Dashboard Query Shell
Open dashboard.fauna.com and run a simple FQL query in the Shell tab (e.g., Collection.all().first()). If the query succeeds, the API is reachable from your browser. This is a quick sanity check that bypasses your app's environment variables.
Open Fauna Dashboard →Fauna Discord
Fauna's Discord server has a #status channel where outage reports surface quickly from the developer community. The Fauna team typically acknowledges incidents in Discord early in an outage, often before the status page is updated.
Join Fauna Discord →@fauna on X
Fauna's official X account posts incident updates and maintenance announcements. Searching 'fauna down' or 'faunadb down' also surfaces developer reports from the broader community during active outages.
Follow @fauna →X / Twitter (Search)
Search 'fauna down', 'faunadb down', or 'fauna database error' on X. Developers using Fauna in Next.js, Netlify, and Vercel serverless functions tend to report issues quickly on X. The older 'FaunaDB' name still surfaces in searches.
Search X for 'fauna down' →Common Fauna Errors and What They Mean
"Unauthorized (401)"Your FAUNA_SECRET is missing, expired, or invalid. Generate a new server key in the Fauna dashboard under Security. Make sure you're using the correct secret for the target database and region."throttled (429)"Your database exceeded its read or write operation limit for the current billing period or rate window. This is not a platform outage — upgrade your Fauna plan or optimize queries to use indexes and reduce bytes read per operation."instance not unique (400)"A unique constraint violation — you tried to create a document that conflicts with an existing unique index entry. This is a data integrity error in your application, not a Fauna platform issue."stream closed unexpectedly"Fauna's streaming (change data feed) connection dropped. This can indicate a transient network issue, an idle connection timeout, or a Fauna platform incident affecting streaming. Implement reconnection logic in your streaming code."request size limit exceeded"Your FQL query or mutation payload is too large. Fauna has per-request size limits. Split large batch operations into smaller chunks or use pagination instead of fetching all documents at once."transaction aborted"A multi-document transaction was aborted due to a write conflict (optimistic concurrency control). Fauna uses MVCC — concurrent transactions modifying the same documents will cause one to abort. Retry the transaction with exponential backoff.Fauna Outage History: What the Data Shows
Fauna (originally FaunaDB) differentiates itself with Calvin-protocol global consistency, meaning all writes are globally consistent without sacrificing partition tolerance. Its serverless pricing model charges per read and write operation byte, making it popular for low-traffic apps that don't want to pay for idle compute. Incidents most commonly affect API latency rather than complete unavailability. Because Fauna is region-partitioned, regional incidents are isolated — if your database is in the EU region and there's a US-region incident, your app is unaffected.
What to Do When Fauna Is Down
If Queries Are Failing
- Check status.fauna.com for your region's status
- Verify FAUNA_SECRET is valid and targets the right region
- Test a simple query in the Fauna Dashboard Shell
- Check for 429 throttling vs. 5xx platform errors
- Search Fauna Discord #status for active reports
For Better Outage Resilience
- Cache critical read-only data at the CDN or edge layer
- Implement retry logic with exponential backoff for transient errors
- Use Fauna's Classic region for global redundancy if latency allows
- Show graceful error states rather than blank screens during outages
- Set up independent endpoint monitoring for your app
Frequently Asked Questions
Where is the official Fauna status page?
Fauna's official status page is at status.fauna.com. It shows real-time status per region (Classic, US, EU). Subscribe to email notifications to be automatically alerted when incidents are posted and resolved.
My Fauna queries are failing but the status page is green — what's wrong?
When queries fail but status is green, the issue is almost always with your API key or region endpoint. Verify your FAUNA_SECRET is valid (not expired or revoked) in the Fauna dashboard. Check that you are connecting to the correct regional endpoint — db.us.fauna.com for US-region databases, db.eu.fauna.com for EU-region databases, or db.fauna.com for Classic. Also check for 429 throttling responses, which indicate rate limiting, not a platform outage.
What is the difference between Fauna regions (Classic, US, EU)?
Fauna Classic is a multi-region deployment that replicates data globally, providing low latency from anywhere but potentially higher costs. US and EU are single-region deployments offering lower price points and data residency guarantees for compliance (GDPR for EU). Each region has its own API endpoint and independent status. When creating a database, choose the region that matches your users' geography and your compliance requirements.
Does Fauna support automatic failover during an outage?
Fauna Classic has built-in multi-region replication with automatic failover between its replica set. If one node in the Classic cluster fails, traffic is automatically routed to healthy nodes. US and EU single-region databases do not have cross-region failover — if the region has an outage, there is no automatic fallback. For critical applications requiring cross-region redundancy, Fauna Classic is the recommended option.
How do I monitor my Fauna-powered app independently?
Create a lightweight health check endpoint in your app that executes a simple Fauna read query (e.g., fetching a sentinel document) and returns HTTP 200 if successful. Monitor that endpoint with Better Stack or API Status Check Alert Pro. This catches Fauna connectivity issues, including API key expiration and throttling, that don't appear on the platform status page.
Alert Pro
14-day free trialStop checking — get alerted instantly
Next time Fauna goes down, you'll know in under 60 seconds — not when your users start complaining.
- Email alerts for Fauna + 9 more APIs
- $0 due today for trial
- Cancel anytime — $9/mo after trial