Appwrite Outage History

22 incidents recorded over the last 365 days, 22 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Appwrite status98.58% uptime history

Every Recorded Appwrite Incident

Appwrite incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Nov 2, 2026Static Appwrite Sites return 500 errors64h 51mResolved
Oct 30, 2026Slow requests in Frankfurt and for Functions and Sites140h 39mResolved
Oct 28, 2026Realtime events not delivered in Frankfurt183h 52mResolved
Oct 25, 2026Slow storage operations in San Francisco254h 19mResolved
Oct 25, 2026Degraded Appwrite Sites due to ephemeral key failures255h 44mResolved
Oct 21, 2026Some Appwrite Sites deployments return 404 Not Found355h 43mResolved
Oct 3, 2026Google OAuth sign-in failures796h 41mResolved
Oct 1, 2026Delayed Realtime events and intermittent API errors in New York832h 15mResolved
Sep 25, 2026Platform maintenance2h 58mResolved
Sep 4, 2026Analytics/Usage2h 0mResolved
Sep 4, 2026Analytics/Usage2h 0mResolved
Sep 3, 2026Degraded npm Installation Performance535h 39mResolved
Sep 3, 2026Degraded npm Installation Performance1502h 59mResolved
Aug 13, 2026Incident in Singapore region1046h 45mResolved
Aug 13, 2026Incident in Singapore region2014h 5mResolved
Jul 27, 2026Increased database errors1454h 49mResolved
Jul 27, 2026Increased database errors2422h 9mResolved
Jul 22, 2026Investigating - DNS Resolution Errors Affecting Custom Domains1577h 18mResolved
Jul 22, 2026Investigating - DNS Resolution Errors Affecting Custom Domains2544h 38mResolved
Jun 17, 2026Elevated errors on Functions & Sites in NYC1807h 24mResolved
Jun 17, 2026Sites & Functions Logs3h 0mResolved
Jun 11, 2026Elevated errors on FRA region1953h 19mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Appwrite incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Appwrite Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Appwrite acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Appwrite outage in this window ran 106d, against a mean recovery of 37d 9h. If you depend on Appwrite in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.