1013
Try Again Later
Sent by: ServerRetryable
1013 Try Again Later is sent when the server is temporarily unable to accept new connections due to overload or temporary unavailability. Clients should wait and retry. This is the WebSocket equivalent of HTTP 503 Service Unavailable – the server is alive but cannot handle more connections right now.
Description
1013 signals temporary capacity constraints. Common in rate limiting scenarios or when a server is under load but not being restarted. Clients should implement exponential backoff. Unlike 1001 (going away) or 1012 (restarting), 1013 means the server is staying up but is too busy to maintain this connection. It is appropriate for load-shedding under traffic spikes.
Common Causes
- –Server at connection capacity limit
- –Rate limiting per IP or user
- –Temporary overload condition
- –Load shedding during traffic spike
Code
1013
RFC
RFC 6455
Sent By
Server
Retry
Yes