Appwrite Outage History

Functions recovered

We've identified the issue and have observed recovery. Please reach out to support if you encounter further issues.

Databases recovered

All services are fully available for all customers. Our team will share an incident report in the the next few days with actions items we will take to prevent such incidents happening again. Thank you for you support and patience.

Storage recovered

Our upstream cloud infrastructure vendor has confirmed that the issue has been resolved. From our side, we can confirm that all affected services are now fully operational and available again. We will continue working closely with the vendor to complete a full investigation into the incident, better understand the root cause, and identify additional measures that can help prevent similar issues in the future. We appreciate everyone’s patience while this incident was being addressed.

Our engineering team identified an issue with the components responsible for downsizing cluster capacity in our FRA edge location. This issue prevented new runtimes from being created, but did not affect existing workloads. We have disabled the affected component, and runtime creation success rates are now back to 100% in this location. Service should be stable now. We’re starting a follow-up investigation to identify the root cause and address it properly. Once ready, we’ll share the incident details in our public GitHub repo: https://github.com/appwrite/incidents

Console recovered

Main recovered

We have applied manual patches to resolve the current issue and are implementing additional patches to ensure system stability. We will continue investigating a long-term solution under the updated configuration to ensure auto-scaling operates as expected. All services are now fully functional.

We have updated the service configuration, and the impact appears to be positive. Error rates have returned to normal levels, and services are now fully available with normal response times. We will continue to monitor the system and investigate the root cause.

The team has applied a fix, the service is recovering. We'll keep monitoring.

We have confirmed the issue is now resolved with multiple customers. If anyone is still facing issues we'd recommend to create a new user session. We will share a full incident report once our internal investigation will complete.

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

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

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

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.

Services have restored. Thanks for your patience

Services are available again.

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

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