down
Is Appwrite down?
Check Appwrite availability, incident history, downtime reports, and website performance.
https://appwrite.io ↗Mapped components are operational in the latest status update; individual experiences can vary.
Estimated down reports for Appwrite
Last 24 hoursNot enough activity data is available for this service yet.
No user-submitted outage reports in the last 24 hours.
Appwrite outage history
2025–2026Daily history over the past 12 months. Select a day for its evidence.
Select a square for daily details. Scroll sideways to explore earlier months.
How to read this calendar
Dates use New York time (America/New_York). Green means no issues observed with sufficient monitoring coverage; it does not guarantee uninterrupted uptime. Pink includes official incidents, repeated website failures, or corroborated user reports. Gray days are unknown. Activity estimates alone do not turn a day pink. Today’s result can change.
Appwrite website uptime and response time
Current website availability is unknown. No website checks available yet.
Unknown
Successful website checks (24h)
0 successful / 0 measurable checks
Unknown
Median response time
Unknown
95th percentile response time
0 failed checks; 0 restricted checks. Restricted checks are excluded from the success rate. Lines connect recorded samples across gaps; availability between checks is unknown. Response time measures receipt of HTTP headers, not full page load. Checks run from one US monitoring server and do not verify sign-in, API, or app features. These sampled results are separate from down reports and estimated activity.
Evidence behind the status
Provider reports operational. Mapped components are operational in the latest status update; individual experiences can vary.
Website checks and estimated activity have independent update times. Refer to each section for its latest observation.
These measurements describe different things. A reachable homepage can coexist with login or API failures. Missing evidence stays unknown.
Official component status
Appwrite official status · fetched 2026-10-20 22:03:51 UTC
42 mapped components · 0 reporting problems
| Component | Provider status |
|---|---|
| Website | operational |
| Console | operational |
| MCP | operational |
| DNS ns1.appwrite.zone | operational |
| DNS ns2.appwrite.zone | operational |
| Network | operational |
| API | operational |
| Auth | operational |
| Databases | operational |
| Functions | operational |
| Sites | operational |
| Storage | operational |
| API | operational |
| Auth | operational |
| Databases | operational |
| Functions | operational |
| Sites | operational |
| Storage | operational |
| API | operational |
| Auth | operational |
| Databases | operational |
| Functions | operational |
| Sites | operational |
| Storage | operational |
| API | operational |
| Auth | operational |
| Databases | operational |
| Functions | operational |
| Sites | operational |
| Storage | operational |
| API | operational |
| Auth | operational |
| Databases | operational |
| Functions | operational |
| Sites | operational |
| Storage | operational |
| API | operational |
| Auth | operational |
| Databases | operational |
| Functions | operational |
| Sites | operational |
| Storage | operational |
Official incident timeline
Google OAuth sign-in failures · resolved · 2026-10-03T07:56:00Z
Product match: components.
Read the provider’s incident report
- ·
This incident was recorded retrospectively. Some users could not sign in with Google OAuth2. Other sign-in methods continued to work.
- ·
We identified the issue and are applying a fix.
- ·
The fix is in place and Google sign-in works again.
Delayed Realtime events and intermittent API errors in New York · resolved · 2026-10-01T14:45:16Z
Product match: components.
Read the provider’s incident report
- ·
This incident was recorded retrospectively. Realtime event delivery was delayed in the New York region. A small number of API requests, including authentication and database transaction requests, returned server errors. Most API requests continued to receive successful responses.
- ·
Realtime publishing recovered and the associated API errors stopped. We are investigating the event publishing stall and measures to prevent recurrence.
Degraded npm Installation Performance · resolved · 2026-09-04T12:32:00Z
Product match: components.
Read the provider’s incident report
- ·
We are currently observing degraded performance from the npm audit service due to an ongoing npmjs incident: https://status.npmjs.org/incidents/l4f53bbr9200 As a result, users deploying Functions and Sites that use npm may experience significantly increased dependency installation and build times. As a temporary workaround, npm users can disable audit checks using the `--no-audit` flag. Alternatively, switching to Bun or pnpm can avoid the affected npm audit service. We are monitoring the si
- ·
We have implemented a mitigation that disables npm audit requests by default during Functions and Sites builds. This prevents npm installations from waiting on the currently degraded npm audit service and should restore normal dependency installation and build times.
Incident in Singapore region · resolved · 2026-08-13T09:01:00Z
Product match: components.
Read the provider’s incident report
- ·
We are investigating reports of downtime in Singapore region
- ·
We have rolled back an infrastructure change that caused the incident.
Increased database errors · resolved · 2026-07-27T09:10:00Z
Product match: components.
Read the provider’s incident report
- ·
We’ve noticed an increased rate of database errors affecting a small number of projects in the FRA region. We’re investigating the issue.
- ·
We’ve identified the issue and resolved it fully. Services have returned to normal, and our team will continue the investigation to prevent root cause in the future.
Investigating - DNS Resolution Errors Affecting Custom Domains · resolved · 2026-07-22T06:59:00Z
Product match: components.
Read the provider’s incident report
- ·
We have detected an increase in DNS resolution errors affecting custom domains. Our team is actively investigating the issue and working to identify the root cause. During this time, some requests to custom domains may fail to resolve or experience intermittent connectivity issues. We will provide another update as soon as we have more information. Thank you for your patience.
- ·
We have identified the root cause of the DNS resolution errors affecting custom domains and have deployed a patch that restores service. Custom domains are now operating normally. Our team will continue to monitor the platform closely while we work on a permanent fix to fully address the underlying issue and prevent it from recurring. Thank you for your patience while we resolved this incident.
Recovery tracker
No recent recovery can be established from available evidence.
0 consecutive successful checks within the last 30 minutes. These checks measure the public website; they cannot establish recovery of every feature.
Slowdown detection
More successful checks are needed to establish a response-time baseline.
Recent median: unknown · Earlier median: unknown. Flags require at least 3 recent and 5 earlier checks, more than twice the baseline, and at least 500 ms extra latency. Slowness alone does not identify server load as the cause.
Emerging down-report signals
No recent emerging problem patterns are available for this service.
Emerging problem patterns can persist after an incident and do not measure report counts or prove an outage.
Is it down in your region?
Run one public website check from a community probe. Results describe that probe, not every user in a country.
Results are reused for 15 minutes. Shared free allowance: up to 60 tests per hour. A successful website check does not verify authenticated app or API functions.
Infrastructure incident context
Check whether broader platform incidents coincide with the problem you are seeing. These providers are context, not verified dependencies of Appwrite.
No active incidents recorded.
About Appwrite status on Iszdown
Check Appwrite availability, incident history, downtime reports, and website performance.
This page combines the available Appwrite report activity, official product status, public website measurements, and daily history. Each measurement has its own observation time. A search spike alone does not confirm downtime, and a reachable website does not establish that sign-in or every product feature works.
42 product-matched official components are listed above. No public website measurement is available in the current window.
Visit the official Appwrite website · Official provider status · How it works
What to check when Appwrite is not working
These are troubleshooting suggestions, not a list of currently reported problems.
Appwrite will not open
Compare your usual browser or app with a private browser window, then try another network if available. Save unsent work first. A difference between networks can help separate a local connection problem from a wider disruption.
Appwrite is slow or only one feature fails
Record the affected action, exact error, and time. Compare the website response measurements with any official component incidents; loading a homepage does not test every feature.
Include the time, affected feature, and error message when contacting official support. Keep passwords, payment information, session cookies, and access tokens private.
Recent Appwrite outage history
No product-matched official incidents have been archived for this service in the displayed history. This does not establish that it has never had an outage. See the daily calendar for other available evidence.
Frequently asked questions about Appwrite
Is Appwrite down right now?
Provider reports operational. Mapped components are operational in the latest status update; individual experiences can vary. This page was assembled at 2026-10-20T22:16:37.000Z.
How many Appwrite outage reports are there today?
The displayed rolling 24-hour window contains 0 recorded reports, from 2026-10-19T22:10:00.000Z to 2026-10-20T22:10:00.000Z. This is not a calendar-day total or a count of affected people. Estimated activity is shown separately as an estimate.
Why does Appwrite show operational when it is not working for me?
An official operational status can coexist with a local network issue, account problem, or feature-specific incident. Compare the mapped components, recent incident updates, and regional diagnostic on this page. Automated website checks test public access, not your signed-in session or every Appwrite feature.
When was Appwrite status last updated?
The latest status observation was 2026-10-20T22:03:51.000Z. Only matched product components and incidents are shown. The assessment is recent.
Has Appwrite had outages before?
The daily calendar links available incident evidence and retains daily monitoring summaries. Pink marks service issues, green requires sufficient observations with no issues observed, and gray means insufficient coverage. The collected history is incomplete and is not a lifetime outage count or a guarantee of uninterrupted uptime.
How do I follow Appwrite or report a problem?
Use “Watch this service” to save Appwrite in this browser’s watchlist, then return to compare its status with other saved services. The watchlist does not send notifications. Use the problem-report button for an outage report; contact the provider through its official website for account, billing, or private support issues. Iszdown is independent and cannot resolve provider support tickets.
Related services to Appwrite
Check a related product separately; its status can differ from Appwrite.