Functions recovered
Timeline · 1 update
- investigating Aug 02, 2026, 06:29 AM UTC
Functions went down
Appwrite had 29 outages in the last 2 years totaling 21h 19m of downtime — averaging 1.2 incidents per month.
There were 29 Appwrite outages since March 2, 2026 totaling 21h 19m of downtime. Each is summarised below — incident details, duration, and resolution information.
Functions went down
Messaging recovered
Databases recovered
Auth recovered
API went down
Storage went down
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.
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.
Main went down
MCP recovered
Support went down
We've observed elevated errors on Fuctions & Sites on the NYC regions. We're investigating the issue.
We've identified the issue and have observed recovery. Please reach out to support if you encounter further issues.
Support went down
Internal monitoring has alerted the team about elevated errors rates on the FRA region for a subset of projects. We're investigating the issue.
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.
We're noticing an elevated amount of errors and increase in response time from NYC region. Our team is investigating the issue.
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
We're noticing degraded performance which leads to an increase in response times from the API. The team is investigating the issue.
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’re monitoring an incident that appears to be causing increased response times.
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.
We're noticing an increase in failed requests. The engineering team is looking into it.
The team has applied a fix, the service is recovering. We'll keep monitoring.
We’re noticing an increase in login-related issues from mobile apps. This appears to be a regression caused by a failed fix attempt for an incident we resolved yesterday. All relevant engineers are investigating this with the highest priority. We apologize for the inconvenience and will share a full incident report later.
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.
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.
The issues causing runtime failure for both sites and function has been resolved.
We're investigating an issue where realtime isn't connecting or messages aren't being delivered.
Realtime appears to be running normally, but we'll continue to monitor.
We have detected an increase in errors across our edge network in some regions, and our team is actively investigating the issue.
All services are now available. Our team will continue investigating the root cause of the issue.
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.
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.