- Level
- confirmed
- Worst impact
- Degraded
- Components
- API
- Regions
- eu
- Down Index
- 28of 100
What to do
Check whether you use Appwrite Cloud API in eu. 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 25m it lasted.
Anything that failed between 2026-10-28 15:07 UTC and 2026-10-28 15:32 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
- update
This incident was recorded retrospectively. Realtime subscribers in the Frankfurt region stopped receiving events. Realtime connections and subscriptions still succeeded, and API requests, including the writes that produce events, completed normally.
provider
- update
Realtime event delivery in the Frankfurt region recovered at 15:32 UTC after we restarted the realtime servers. Events published during the incident were not delivered. We're investigating why the servers stopped delivering events and measures to prevent recurrence.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-f1ee49bad2
Is Appwrite Cloud still down?
No, this incident was resolved 2026-10-28 15:32 UTC. For Appwrite Cloud's live state, see https://down.guide/appwrite.
How long did it last?
25m, from 2026-10-28 15:07 UTC to 2026-10-28 15:32 UTC, by the times Appwrite Cloud posted.
What was affected?
Appwrite Cloud named API in eu.
What caused it?
Appwrite Cloud hasn't published a root cause. If it does, it shows here.
Where does this come from?
Appwrite Cloud's official status page, https://appwrite.online, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.