Directus Status: How to Check If Directus Is Down (2026)
Updated June 2026 · 5 min read · By API Status Check
Quick Answer: Check Directus Status Now
Directus is an open-source headless CMS and data platform that wraps any SQL database (PostgreSQL, MySQL, MariaDB, SQLite, MS SQL) with a REST and GraphQL API, plus a no-code Data Studio for content editors. Available as Directus Cloud (managed) or self-hosted via Docker. When Directus goes down, your frontend apps can't fetch content, form submissions fail, file uploads stall, and the Data Studio becomes inaccessible to editors. This guide covers how to check status for both Cloud and self-hosted deployments.
Understanding Directus's Status Page
Directus Cloud operates status.directus.cloud — its official status page. This page covers Directus Cloud infrastructure only. Self-hosted Directus instances have their own /server/health endpoint that you should monitor independently.
Directus Cloud API
The REST and GraphQL API that powers all data reads, writes, and file operations. API incidents affect all SDK requests and direct HTTP calls to /items, /files, /users, and other endpoints.
Directus Data Studio
The web-based admin interface at your Directus Cloud URL. Data Studio incidents prevent content editors from accessing the CMS. Studio incidents can occur independently of the underlying API — the API may remain accessible while the studio UI fails.
Directus Asset Storage
File storage and asset transformation (image resizing, format conversion via the /assets endpoint). Storage incidents affect file uploads and dynamic image transformations but may not affect database content queries.
Directus Infrastructure
The underlying Cloud infrastructure (database, network, load balancers). Infrastructure incidents are the most severe — they affect all services simultaneously and are the root cause of most major outages on Directus Cloud.
What Directus Status Colors Mean
⚠️ Self-Hosted Directus: Use /server/health
The Directus Cloud status page is irrelevant for self-hosted instances. Instead:
- Call
GET /server/healthon your instance — returns per-service health status (database, cache, email, storage) - A
status: "error"with a database entry indicates your SQL database connection is broken — check yourDB_*environment variables - Run
docker logs directusfor detailed error output - Check that Redis is running if you have
CACHE_ENABLED=true— a missing Redis connection causes Directus to crash on startup - Verify the
SECRETenvironment variable is set — missing it prevents Directus from starting
Monitor your Directus instance with independent uptime monitoring
Directus's status page only covers Cloud — your self-hosted instance needs its own monitoring. Better Stack monitors your /server/health endpoint and alerts you when Directus goes down. Free plan available.
Try Better Stack Free →5 Ways to Check If Directus Is Down
status.directus.cloud (Cloud Users)
Directus Cloud's official status page. Subscribe to email notifications to be alerted when incidents are created and resolved. Note: this page only covers Directus Cloud, not self-hosted instances.
Check status.directus.cloud →/server/health Endpoint (All Users)
Both Cloud and self-hosted Directus expose GET /server/health. This endpoint returns the health of each internal service without requiring authentication. Monitor this endpoint directly for the most accurate uptime data about your specific Directus instance.
View /server/health docs →Directus Discord
Directus has an active Discord community where outage reports and workarounds surface quickly. The #support and #cloud channels are the fastest places to confirm whether an issue is platform-wide or isolated to your instance.
Join Directus Discord →@directus on X
Directus's official X account posts incident updates and Cloud maintenance announcements. Searching 'directus down' or 'directus api error' on X also surfaces community reports during active outages.
Follow @directus →GitHub Issues
For self-hosted Directus bugs that look like a platform issue (not your config), check the Directus GitHub Issues page. The community often reports version-specific bugs and breaking changes that affect self-hosted deployments before they are addressed in releases.
Check Directus GitHub Issues →Common Directus Errors and What They Mean
"FORBIDDEN (403)"The access token lacks permission for the requested operation. Check your token's role and the collection's access control settings in the Directus Data Studio under Settings → Access Policies. The Public policy controls unauthenticated access."INVALID_CREDENTIALS (401)"The authentication token is expired, revoked, or malformed. Re-authenticate to get a fresh access token. Static API tokens (created in the Data Studio) do not expire by default — if one stops working, check that it hasn't been deleted or regenerated in the admin panel."RECORD_NOT_UNIQUE (400)"A create or update operation violated a unique constraint on the collection. Check the item fields that have unique constraints in the collection schema — you're trying to create a duplicate value where uniqueness is enforced."ROUTE_NOT_FOUND (404)"The API endpoint or item does not exist. Verify the collection name is spelled correctly (Directus collection names are case-sensitive). For custom endpoints, ensure the extension is installed and the Directus server was restarted after installation."service unavailable (503)"Directus itself is running but an internal dependency (database, cache, or storage adapter) is unhealthy. Call /server/health to identify which service is failing. Common causes: database connection lost, Redis not reachable, or cloud storage credentials expired."Snapshot mismatch / schema conflict"Your Directus schema snapshot is out of sync with the database (common after failed migrations). Run 'npx directus schema snapshot ./snapshot.yaml' to export the current schema, then 'npx directus schema apply ./snapshot.yaml' to resync. This is a self-hosted administration task, not a Cloud incident.Directus Cloud Outage History: What the Data Shows
Directus has been in production since 2004 and open source since 2016, making it one of the most mature headless CMS platforms available. Directus Cloud launched as a managed offering for teams that want the flexibility of Directus without the infrastructure overhead. Because Directus wraps your existing SQL database rather than using a proprietary data store, self-hosted instances give teams full control over their data and availability. Cloud incidents are relatively infrequent and tend to resolve quickly — the Directus team maintains an active status page and Discord community for incident communication.
What to Do When Directus Is Down
If API Calls Are Failing
- Check status.directus.cloud (Cloud) or /server/health (self-hosted)
- Verify your access token is valid and has the right permissions
- Test a simple unauthenticated GET /server/ping to confirm reachability
- Check Directus Discord #cloud for active incident reports
- For self-hosted: check Docker container health and logs
For Better Outage Resilience
- Cache content responses at the CDN layer (e.g., Cloudflare) for read-heavy frontends
- Use ISR (Incremental Static Regeneration) in Next.js to serve stale content during outages
- Monitor /server/health with uptime tooling — not just the status page
- For self-hosted: configure Redis cache to reduce database load during recovery
- Keep a static fallback for critical public-facing pages
Frequently Asked Questions
Where is the official Directus status page?
Directus Cloud's official status page is at status.directus.cloud. It shows real-time per-component status for the Directus Cloud API, Data Studio, and asset storage. Subscribe to email notifications to be alerted automatically when incidents are posted and resolved.
How do I check the health of a self-hosted Directus instance?
Call GET /server/health on your Directus instance (e.g., https://cms.yourdomain.com/server/health). The endpoint is public (no authentication required) and returns a JSON response with status ('ok', 'warn', or 'error') for each internal service: database, cache (Redis, if configured), email (SMTP, if configured), and storage adapter. A 200 response with status 'ok' means all services are healthy.
What does it mean if Directus returns 503 Service Unavailable?
A 503 from Directus means the server is running but a critical internal dependency is unhealthy. The most common cause is a broken database connection — check that your SQL database (PostgreSQL, MySQL, MariaDB) is running and that the DB_HOST, DB_PORT, DB_DATABASE, DB_USER, and DB_PASSWORD environment variables are correct. If you have Redis caching enabled, also verify Redis is reachable.
Can I use Directus with Next.js and will content be affected during outages?
Yes — Directus is commonly used with Next.js as a headless CMS backend. During a Directus outage, getStaticProps/generateStaticParams calls that fetch from Directus will fail at build time, and getServerSideProps/fetch calls will fail at request time. To protect against outages, use Next.js ISR (revalidate interval) so your site serves cached content during Directus downtime, with automatic revalidation once Directus recovers.
How do I monitor my Directus-powered site uptime independently?
Monitor GET /server/health on your Directus instance with Better Stack or API Status Check Alert Pro. This endpoint catches all internal service failures and doesn't require authentication. For Cloud users, also monitor the specific API endpoints your frontend uses (e.g., /items/articles?limit=1) to detect app-specific issues that the general health check might not surface.
Alert Pro
14-day free trialStop checking — get alerted instantly
Next time Directus goes down, you'll know in under 60 seconds — not when your users start complaining.
- Email alerts for Directus + 9 more APIs
- $0 due today for trial
- Cancel anytime — $9/mo after trial