a month ago
Production WebSocket incident: 2026-07-19 nearly all day issues have been observed
Edge currently observed: jfk1 / railway-hikari
Deployment: #139 / bf43f117b
Multiple independent Colyseus clients received 1006 without Close frames.
The process remained healthy and resource usage was low.
Protocol ping: every 15 s; application traffic: approximately every 1 s.
Some reserved-seat reconnects completed in 0 ms; replacement sockets then
closed before Colyseus JOIN finalization with "reconnection denied".
Please confirm whether Hikari/TCP proxy recycling or connection resets occurred
for this service and edge during that UTC window.
2 Replies
a month ago
This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.
Status changed to Open Railway • about 1 month ago
a month ago
Oui
a month ago
main-KHTIN2VG.js:87 [2026-07-19T11:26:34.984Z] Error: Connection disconnected with error 'Error: WebSocket closed with status code: 1006 (no reason given).'.
main-KHTIN2VG.js:87 [2026-07-19T11:26:51.020Z] Error: Connection disconnected with error 'Error: WebSocket closed with status code: 1006 (no reason given).'.
main-KHTIN2VG.js:87 [2026-07-19T11:27:07.031Z] Error: Connection disconnected with error 'Error: WebSocket closed with status code: 1006 (no reason given).'.
main-KHTIN2VG.js:87 [2026-07-19T11:27:23.505Z] Error: Connection disconnected with error 'Error: WebSocket closed with status code: 1006 (no reason given).'.
main-KHTIN2VG.js:87 [2026-07-19T11:27:55.027Z] Error: Connection disconnected with error 'Error: WebSocket closed with status code: 1006 (no reason given).'.