Investigating - DNS Resolution Errors Affecting Custom Domains

What to do

• Check whether you use Appwrite Cloud DNS ns1.appwrite.zone, DNS ns2.appwrite.zone. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 38m it lasted.

  Anything that failed between 2026-07-22 06:21 UTC and 2026-07-22 06:59 UTC may need a replay.

• Subscribe to Appwrite Cloud's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=appwrite works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Appwrite Cloud 2

1. updateJul 22, 2026, 6:21 AM UTC

   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.

   provider

2. updateJul 22, 2026, 6:59 AM UTC

   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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.