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.
Service disruption activity for Appwrite
Last 24 hoursObserved disruption signals combine available incidents, recorded reports, website checks, and emerging problem patterns. A low score does not guarantee that every feature is working.
Latest observation: 2026-11-10 15:50:00 UTC. Refreshes automatically while this page is visible.
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
Website responded successfully HTTP 200. Last checked 2026-11-10 15:27:12 UTC.
Checked address: https://appwrite.io/
DNS lookup: 6 ms · TCP connection: 7 ms · TLS handshake: 9 ms. Certificate expires 2027-01-24; trusted connection: yes.
100%
Successful website checks (24h)
22 successful / 22 measurable checks
414 ms
Median response time
474 ms
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-11-10 15:50:00 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
Static Appwrite Sites return 500 errors · resolved · 2026-11-02T14:21:00Z
Product match: components.
Read the provider’s incident report
- ·
Since 14:08 UTC, requests to static sites hosted on Appwrite Sites are failing with HTTP 500 errors in all regions. We have identified the cause and are working on a fix. Functions and server-rendered sites are not affected.
- ·
Static sites are serving normally again in all regions. A configuration change to how our servers connect to site storage caused the errors, and we have corrected it. This incident is resolved.
Slow requests in Frankfurt and for Functions and Sites · resolved · 2026-10-30T10:55:00Z
Product match: components.
Read the provider’s incident report
- ·
API requests in the Frankfurt region and the Console slowed down, and some timed out. Appwrite Functions and Sites in all regions were also slower, and some requests failed. A sudden rise in traffic exhausted capacity on an internal database proxy that these requests depend on.
- ·
We have increased the capacity of the affected database proxy, and response times are returning to normal in all regions. We're monitoring the recovery and will post an update once it is complete.
- ·
Response times and error rates are back to normal in all regions, and have stayed there since. This incident is resolved.
Realtime events not delivered in Frankfurt · resolved · 2026-10-28T15:32:00Z
Product match: components.
Read the provider’s incident report
- ·
This incident was recorded retrospectively. Realtime subscribers in the Frankfurt region stopped receiving events. Realtime connections and subscriptions still succeeded, and API requests, including the writes that produce events, completed normally.
- ·
Realtime event delivery in the Frankfurt region recovered at 15:32 UTC after we restarted the realtime servers. Events published during the incident were not delivered. We're investigating why the servers stopped delivering events and measures to prevent recurrence.
Slow storage operations in San Francisco · resolved · 2026-10-27T13:00:00Z
Product match: components.
Read the provider’s incident report
- ·
We're investigating intermittent slowness in Storage in the San Francisco region. Some file operations take several seconds longer than usual to complete. Uploads, downloads and file previews continue to succeed. We're working with our infrastructure provider and will share updates here.
- ·
Storage in the San Francisco region has been working normally since 16:00 UTC on October 26. File operations complete at their usual speed again, and we've monitored the region since to confirm the fix is holding. We're sorry for the disruption.
Degraded Appwrite Sites due to ephemeral key failures · resolved · 2026-10-25T15:46:00Z
Product match: components.
Read the provider’s incident report
- ·
We're investigating degraded performance for Appwrite Sites in all regions. Ephemeral keys are not working, so some sites cannot complete requests that depend on them. We will post an update as soon as we know more.
- ·
We have identified the cause. A proactive security hardening change we made introduced a regression that stops ephemeral keys from working. We are preparing a fix and will post an update when it is rolling out.
- ·
While we prepare the fix, you can work around the issue by switching your site from the ephemeral key to a standard API key with the scopes your site needs.
- ·
We have pushed a fix. Ephemeral keys work again, and Appwrite Sites are fully available in all regions. We're sorry for the disruption.
Some Appwrite Sites deployments return 404 Not Found · resolved · 2026-10-21T14:00:00Z
Product match: components.
Read the provider’s incident report
- ·
Since 11:16 UTC, some Appwrite Sites are showing a 404 Not Found page instead of the site. This affects new site deployments and sites being served for the first time in a region; sites that were already being served are not affected. Functions and other services are not affected. We have identified the cause and are rolling out a fix. Affected sites will recover automatically once the fix is live; no action is needed from you.
- ·
The fix is live in all regions and new site deployments are being served normally again. Sites that showed a 404 Not Found page recover on their next request. We're sorry for the disruption.
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.
Recovery tracker
No recent recovery can be established from available evidence.
1 consecutive successful checks within the last 30 minutes. These checks measure the public website; they cannot establish recovery of every feature.
Slowdown detection
No sustained slowdown has been established against the earlier baseline.
Recent median: 181 ms · Earlier median: 415 ms. 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
- is appwrite down
Query “is appwrite” · observed 2026-11-10 15:24:04 UTC · 0 newly observed problem phrases.
Query “appwrite” · observed 2026-11-10 14:52:14 UTC · 0 newly observed problem phrases.
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.
- Changes to Cloudflare Workers are not producing Event Subscription events · investigating
- Fedramp Customers have Delayed Purges · identified
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. Latest public website measurement: 2026-11-10T15:27:12.000Z.
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.
Website troubleshooting guide · Sign-in problems · API errors and timeouts
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
Latest available product-matched official incidents in the calendar’s archive. Times below use UTC. Duration is the provider’s recorded incident window, not a measurement of impact on every user.
| Incident | Started (UTC) | Recorded duration | Last collected status |
|---|---|---|---|
| Slow requests in Frankfurt and for Functions and Sites | No resolution recorded | investigating | |
| Slow storage operations in San Francisco | No resolution recorded | investigating | |
| Degraded Appwrite Sites due to ephemeral key failures | No resolution recorded | investigating | |
| Some Appwrite Sites deployments return 404 Not Found | No resolution recorded | investigating |
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-11-10T15:52:57.000Z.
How many Appwrite outage reports are there today?
The displayed rolling 24-hour window contains 0 recorded reports, from 2026-11-09T15:50:00.000Z to 2026-11-10T15:50: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-11-10T15:50:00.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. Optional browser notifications can flag status changes while the watchlist page stays open and visible; background alerts are not sent. 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.