Appwrite Status: How to Check If Appwrite Is Down (2026)
Updated June 2026 · 5 min read · By API Status Check
Quick Answer: Check Appwrite Status Now
Appwrite is an open-source backend-as-a-service (BaaS) platform offering authentication, databases, file storage, serverless functions, and real-time messaging — often described as a self-hostable Firebase alternative. It's available as Appwrite Cloud (managed) or as a Docker-based self-hosted deployment. When Appwrite Cloud goes down, authentication flows fail, database queries return errors, file uploads stall, and function executions time out. This guide covers how to check Appwrite's status for both Cloud and self-hosted deployments.
Understanding Appwrite's Status Page
Appwrite Cloud operates status.appwrite.online — its official status page. Appwrite Cloud runs on managed infrastructure with multiple service components that can fail independently. Note that this page covers Appwrite Cloud only — self-hosted instances have no central status page.
Appwrite API
The core REST/GraphQL API that powers all Appwrite SDK requests. This includes the /v1/account, /v1/databases, /v1/storage, and /v1/functions endpoints. API incidents affect all operations across all services.
Appwrite Auth
Authentication and session management — email/password login, OAuth providers (Google, GitHub, Apple, etc.), magic links, and JWT validation. Auth incidents block user sign-ins and session refreshes without affecting existing sessions.
Appwrite Databases
The document database storing your collections and documents. Database incidents affect all CRUD operations. Appwrite uses MariaDB internally with automatic backups on Cloud plans.
Appwrite Storage & Functions
File storage (upload, download, preview transforms) and serverless Functions (execution). These services have separate health states — a Functions runtime incident may not affect Storage, and vice versa.
What Appwrite Status Colors Mean
⚠️ Self-Hosted vs. Cloud — Different Debugging Paths
Self-hosted Appwrite users need to debug their own infrastructure, not check the Cloud status page:
- Hit
GET /v1/healthon your instance to get a full service health report - Run
docker psto check that all Appwrite containers are running (appwrite, appwrite-worker-*, mariadb, redis, influxdb) - Run
docker logs appwritefor API error output - Check disk space — Appwrite crashes silently when the volume is full
- Verify your
_APP_ENVand_APP_OPENSSL_KEY_V1environment variables are set correctly in your.envfile
Monitor your Appwrite-powered app with independent uptime monitoring
Appwrite's status page shows Cloud platform health — not your specific project's health. Better Stack monitors your actual app endpoints and alerts you instantly. Free plan available.
Try Better Stack Free →5 Ways to Check If Appwrite Is Down
status.appwrite.online (Official)
Appwrite Cloud's official status page with per-component status for API, Auth, Databases, Storage, and Functions. Subscribe to email notifications to be alerted when incidents are created and resolved.
Check status.appwrite.online →/v1/health Endpoint
For Cloud users: hit https://cloud.appwrite.io/v1/health to get a health response from the Appwrite API. For self-hosted users: call the /v1/health endpoint on your own instance. A healthy response returns HTTP 200 with status information for each internal service.
Check Appwrite Cloud health →Appwrite Discord
Appwrite has one of the largest open-source BaaS communities on Discord. The #support and #announcements channels surface outage reports quickly. The Appwrite team is responsive and often posts incident updates in Discord before the status page is updated.
Join Appwrite Discord →@appwrite on X
Appwrite's official X account posts incident updates and Cloud maintenance announcements. Searching 'appwrite down' or 'appwrite cloud error' also surfaces community reports during active outages.
Follow @appwrite →X / Twitter (Search)
Search 'appwrite down', 'appwrite cloud down', or 'appwrite auth failing' on X. Developers using Appwrite for mobile apps (Flutter, React Native) and web apps (Next.js, SvelteKit) report issues quickly on X.
Search X for 'appwrite down' →Common Appwrite Errors and What They Mean
"AppwriteException: user_unauthorized (401)"The user session has expired or the API key is invalid. For user sessions, call account.createEmailPasswordSession() to re-authenticate. For server-side requests, verify your API key in the Appwrite console has the correct scopes for the operation."AppwriteException: general_server_error (500)"An internal server error on Appwrite Cloud or your self-hosted instance. Check status.appwrite.online for ongoing incidents. For self-hosted: check Docker logs with 'docker logs appwrite' for the specific error. This is a platform-level error, not a client code issue."AppwriteException: document_not_found (404)"The document ID you are querying does not exist in the collection. Verify the document ID is correct and that it was created in the correct database and collection. This is a data error, not a platform outage."AppwriteException: storage_file_not_found (404)"The file ID does not exist in the storage bucket, or the bucket ID is incorrect. Verify the file was uploaded successfully and that you are using the correct bucket ID for the targeted storage bucket."AppwriteException: function_execution_failed (500)"Your Appwrite Function threw an uncaught exception during execution. Check the function execution logs in the Appwrite console — each execution has detailed output, including stdout, stderr, and the return value. This is almost always a code error in your function, not a platform issue."AppwriteException: rate_limit_exceeded (429)"You have exceeded Appwrite Cloud's request rate limits. Free and Starter plan users have lower rate limits. Implement request queuing or upgrade your Appwrite Cloud plan. For self-hosted instances, adjust rate limiting settings in your Appwrite environment variables.Appwrite Cloud Outage History: What the Data Shows
Appwrite launched Appwrite Cloud in 2023, transitioning from a purely self-hosted tool to a managed platform. Its open-source heritage means the underlying code is publicly auditable, and the large developer community (60K+ GitHub stars) contributes to rapid issue identification. Appwrite Cloud incidents most commonly affect Functions (cold start timeouts, runtime crashes) and Auth (OAuth provider integration issues). The team is active on Discord during incidents and typically resolves Cloud issues faster than many comparable platforms due to the community pressure of being open source.
What to Do When Appwrite Is Down
If Appwrite Cloud Is Failing
- Check status.appwrite.online for active incidents
- Hit /v1/health to confirm API reachability
- Check the Appwrite Discord #announcements channel
- Verify your API key scopes haven't been restricted
- Check project-specific limits in the Appwrite console
For Better Outage Resilience
- Cache authentication state client-side for graceful degradation
- Implement error boundaries around Appwrite-dependent UI
- Use optimistic UI patterns for write operations
- Consider self-hosted Appwrite for critical production apps requiring SLA control
- Set up independent health check monitoring for your app endpoints
Frequently Asked Questions
Where is the official Appwrite status page?
Appwrite Cloud's official status page is at status.appwrite.online. It shows real-time per-component status for the API, Auth, Databases, Storage, and Functions. Subscribe to email notifications to be automatically alerted during incidents.
How do I check the health of a self-hosted Appwrite instance?
Call GET /v1/health on your Appwrite instance (e.g., https://appwrite.yourdomain.com/v1/health). The response includes health status for each internal service: the database (MariaDB), cache (Redis), time sync, queue workers, and storage. A 200 response means the API is reachable; the JSON body shows which services are healthy or unhealthy. You can also run 'docker ps' to check that all required containers are running.
Why does Appwrite auth work but database queries fail?
Appwrite services can fail independently. Auth uses a different internal path than database queries. If auth is working but database queries fail, check: (1) your database and collection IDs are correct, (2) the user has permission to read/write the collection (check permissions in the Appwrite console), (3) the Appwrite Databases service specifically shows as operational on the status page, and (4) you haven't hit the per-collection document limit on your plan.
Is Appwrite Cloud reliable enough for production apps?
Appwrite Cloud has improved significantly since its 2023 launch. For most apps, Cloud is reliable enough for production. For apps requiring strict SLA guarantees (99.9%+), consider self-hosting Appwrite on a managed Kubernetes cluster where you control the infrastructure. Self-hosting gives you control over scaling, backup frequency, and incident response time at the cost of operational overhead.
How do I monitor my Appwrite-powered app uptime independently?
Create a lightweight health check API route in your app that calls a simple Appwrite read operation (e.g., list a document from a health-check collection) and returns HTTP 200 if successful. Monitor that endpoint with Better Stack or API Status Check Alert Pro. This detects Appwrite connectivity issues, including rate limit hits and auth token expiration, that don't surface on the platform status page.
Alert Pro
14-day free trialStop checking — get alerted instantly
Next time Appwrite goes down, you'll know in under 60 seconds — not when your users start complaining.
- Email alerts for Appwrite + 9 more APIs
- $0 due today for trial
- Cancel anytime — $9/mo after trial