Appwrite Outage History

Appwrite is up right now

Appwrite had 35 outages in the last 2 years totaling 23h 41m of downtime — averaging 1.4 incidents per month.

There were 35 Appwrite outages since February 25, 2026 totaling 23h 41m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.appwrite.io

Minor April 2, 2026

Increased Runtime Failures

Detected by Pingoru
Apr 02, 2026, 06:34 AM UTC
Resolved
Apr 02, 2026, 06:53 AM UTC
Duration
19m
Affected: Cloud services - TOR (Functions)Cloud services - TOR (Sites)
Timeline · 2 updates
  1. investigating Apr 02, 2026, 06:34 AM UTC

    We are currently observing an increase in runtime failures across the platform. Core services, including functions and sites, remain operational and available. Our team is actively investigating the issue and working towards mitigation.

  2. resolved Apr 02, 2026, 06:53 AM UTC

    The issues causing runtime failure for both sites and function has been resolved.

Read the full incident report →

Minor March 31, 2026

Realtime instability

Detected by Pingoru
Mar 31, 2026, 03:42 PM UTC
Resolved
Mar 31, 2026, 04:53 PM UTC
Duration
1h 11m
Affected: Cloud services - TOR (API)
Timeline · 2 updates
  1. investigating Mar 31, 2026, 03:42 PM UTC

    We're investigating an issue where realtime isn't connecting or messages aren't being delivered.

  2. resolved Mar 31, 2026, 04:53 PM UTC

    Realtime appears to be running normally, but we'll continue to monitor.

Read the full incident report →

Minor March 28, 2026

Elevated errors for Functio...

Detected by Pingoru
Mar 28, 2026, 08:40 PM UTC
Resolved
Mar 28, 2026, 09:25 PM UTC
Duration
45m
Affected: Cloud services - TOR (Functions)Cloud services - TOR (Sites)
Timeline · 2 updates
  1. investigating Mar 28, 2026, 08:40 PM UTC

    We have detected an increase in errors across our edge network in some regions, and our team is actively investigating the issue.

  2. resolved Mar 28, 2026, 09:25 PM UTC

    All services are now available. Our team will continue investigating the root cause of the issue.

Read the full incident report →

Minor March 26, 2026

Degraded email delivery

Detected by Pingoru
Mar 26, 2026, 11:38 PM UTC
Resolved
Mar 27, 2026, 08:07 AM UTC
Duration
8h 29m
Affected: Cloud services - TOR (Auth)
Timeline · 2 updates
  1. investigating Mar 26, 2026, 11:38 PM UTC

    We are working with our vendor to resolve email delivery issues. For the time being, it would be best to use a custom SMTP server if you can.

  2. resolved Mar 27, 2026, 08:07 AM UTC

    We have migrated to a fallback provider, and service is now fully restored. We will continue to monitor the situation closely and work with our vendors to help prevent similar incidents in the future.

Read the full incident report →

Minor March 20, 2026

Instability with FRA sites ...

Detected by Pingoru
Mar 20, 2026, 07:48 PM UTC
Resolved
Mar 20, 2026, 09:05 PM UTC
Duration
1h 17m
Affected: Cloud services - TOR (Functions)Cloud services - TOR (Sites)
Timeline · 2 updates
  1. investigating Mar 20, 2026, 07:48 PM UTC

    We're investigating issues with FRA sites and functions

  2. resolved Mar 20, 2026, 09:05 PM UTC

    Services have restored. Thanks for your patience

Read the full incident report →

Major March 20, 2026

SYD is down

Detected by Pingoru
Mar 20, 2026, 05:34 PM UTC
Resolved
Mar 20, 2026, 05:50 PM UTC
Duration
16m
Affected: Cloud services - TOR (API)Cloud services - TOR (Auth)Cloud services - TOR (Databases)Cloud services - TOR (Storage)
Timeline · 2 updates
  1. investigating Mar 20, 2026, 05:34 PM UTC

    We're investigating an issue with SYD.

  2. resolved Mar 20, 2026, 05:50 PM UTC

    Services are available again.

Read the full incident report →

Minor March 17, 2026

Increase in errors on FRA r...

Detected by Pingoru
Mar 17, 2026, 03:57 PM UTC
Resolved
Mar 17, 2026, 11:45 PM UTC
Duration
7h 48m
Affected: Cloud services - TOR (API)Cloud services - TOR (Auth)Cloud services - TOR (Databases)Cloud services - TOR (Storage)
Timeline · 2 updates
  1. investigating Mar 17, 2026, 03:57 PM UTC

    Our team is aware of degraded performance in FRA region, and are investigating the problem.

  2. resolved Mar 17, 2026, 11:45 PM UTC

    Realtime should be functioning again. Thank you for your patience.

Read the full incident report →

Minor March 2, 2026

Degraded API Performance Im...

Detected by Pingoru
Mar 02, 2026, 10:46 AM UTC
Resolved
Mar 02, 2026, 12:30 PM UTC
Duration
1h 44m
Affected: Cloud services - TOR (API)
Timeline · 2 updates
  1. investigating Mar 02, 2026, 10:46 AM UTC

    We are experiencing degraded API performance affecting a subset of projects. The team is actively working on resolving the issue.

  2. resolved Mar 02, 2026, 12:30 PM UTC

    We expect API error rates to return to normal. The system is being actively monitored, and any new issues will be investigated immediately.

Read the full incident report →

Minor February 27, 2026

Elevated number of errors o...

Detected by Pingoru
Feb 27, 2026, 02:34 PM UTC
Resolved
Feb 27, 2026, 04:07 PM UTC
Duration
1h 33m
Affected: Cloud services - TOR (API)
Timeline · 2 updates
  1. investigating Feb 27, 2026, 02:34 PM UTC

    We're noticing an increase in API errors. Our team is investigating

  2. resolved Feb 27, 2026, 04:07 PM UTC

    Our engineering team has identified the root cause of the incident and is implementing a series of remediation measures to prevent recurrence. All services are fully operational and performing within normal parameters.

Read the full incident report →

Minor February 25, 2026

DB Issue Impacting App Laun...

Detected by Pingoru
Feb 25, 2026, 08:38 AM UTC
Resolved
Feb 25, 2026, 08:57 AM UTC
Duration
19m
Affected: Cloud services - TOR (Databases)
Timeline · 2 updates
  1. investigating Feb 25, 2026, 08:38 AM UTC

    We are currently aware of an issue where some users are experiencing difficulties with the application not opening as expected. Our team is actively investigating. Please be assured that this incident is being treated with the highest priority, and we are working diligently to resolve it as quickly as possible.

  2. resolved Feb 25, 2026, 08:57 AM UTC

    The issue has been identified and resolved. We will be publishing a detailed incident report outlining our findings and the corrective actions we are implementing to help ensure this does not happen again.

Read the full incident report →