#RealTime API down and connections are not show in cloud console
20 messages · Page 1 of 1 (latest)
Console connections are disabled temporarily
when will the issue be fixed?
The console stats should not affect the realtime API...
I am not able to get response through subscribe even though I was able to get the response yesterday from the same code
Appwrite Realtime functionality down across all SDKs
We are experiencing a critical outage with Appwrite's Realtime features affecting all SDKs. The situation is as follows:
- Realtime functionality is completely unstable and non-functional.
- This is impacting our real-world product running in production.
- For the past 5 days, all Realtime database events have failed to trigger.
- The system has stopped working entirely in the cloud environment.
- We have not updated any code during this period, ruling out changes on our end as the cause.
Additional details:
- The issue appears to be widespread, potentially affecting Appwrite's entire cloud infrastructure.
- Our application heavily relies on Realtime updates for core functionalities.
- We've attempted troubleshooting but found no local causes for the failure.
- The persistent nature of this issue over multiple days is causing severe disruption to our service.
This outage is significantly impacting our operations and user experience.
this issue is being tracked.
I understand the frustration, but sometimes it's impossible to prevent an unknown issue 😬
Appwrite realtime was working fine since a long time ago so I think I could say it's a stable feature
how is it now?
Great!!!

If you face some issues again, don't hesitate to create a new post so the team investigates and works to solve the issue asap 
I'm really interested in what is actually causing this issue. From my own personal testing realtime can get unstable the more realtime connection are concurrently running. I simulated several thousand connections and it is really random when it crashes. Sometimes it is stable at 2k sometimes at 8k or more. Even if I cap the connections at 2k after some time realtime crashes. Then realtime stops working. No events are sent or no new connections can be made.
As soon as this appears in the logs it's game over
Fatal error: Uncaught Swoole\Error: Socket#34 has already been bound to another coroutine
Is there a github issue for this?
i was referring to team's internal tracking. idk if there's a public issue on the repo though.
In self-hosting?
In selfhosted
Hmm it would be great to create an issue on GitHub for this. Anyways if I'm not wrong 1.6 comes with improvements on Swoole coroutines so maybe this will be fixed with other similar issues
Yeah I'm excited but are you sure it's coming in 1.6?