Why do Polygon WebSocket disconnects happen?

Feb 14, 2022
Updated: Jan 17, 2023

WebSocket disconnects can happen for various reasons. One common reason is when market data is not being consumed fast enough. Our server-side buffer can fill, resulting in delayed and killed connections. To prevent this, it is best to read packets off the network immediately and put them into a queue. A separate thread can then parse the messages and process them. Additionally, using multi-threaded languages like GoLang or C# can be more efficient for streaming large amounts of data than single-threaded languages like Python. You can check the buffer limit in the connections tab in your dashboard.

If you need additional assistance, please reach out to support@polygon.io.


Was this helpful?
Help us improve
contact

Still have questions?

Get in touch with our team

contact
cta icon
Newsletter

Newsletter Sign Up

Submit your email below and get notified via our email newsletter
cta image
cta icon
Public Slack

Join us on Slack

Submit your email below for an invite to the Polygon.io slack community
cta image
cta icon
Public GitHub

Find us on GitHub

Join an active community of developers contributing to polygon.io
Find us on GitHub
cta image
All data provided on Polygon is provided for informational purposes only, and is not intended for trading or investing purposes. Polygon provides all information as is. You must not redistribute information displayed on or provided by Polygon. Stock prices displayed in the ticker are from a subset of exchanges, this price does not represent the real-time price from the SIP.

© Polygon.io, Inc