Realtime connections giving `TIMED_OUT` errors
Last edited: October 13, 2026
If your Realtime connections in your application are giving TIMED_OUT errors, this often indicates an incompatibility between the version of realtime-js being used in your supabase-js client library package and your Node.js version. This issue happens when using versions of Node.js older than v22 with more recent versions of supabase-js.
Why This Occurs: This happens due to a fundamental change made to fix various issues. Please see more details on why this change was made and solutions to fix it: https://github.com/orgs/supabase/discussions/37869
How to Resolve This:
There are two primary options to fix this:
- Upgrade Node.js: Upgrade your Node.js version to the latest Long Term Support (LTS) release, such as Node.js v24 as of November 2025.
- Explicitly set the WebSocket transport: See the linked Github discussion above for a detailed guide on doing this.
Related topics
- Realtime error codes
- Debug Realtime with Logger and log levels
- Understanding and monitoring Realtime heartbeats
- Handling silent disconnections in backgrounded applications
- Realtime messages not arriving