Why playback sometimes just refuses to start
Connection limits cause more false fault reports than anything else, because the devices consuming them are the ones nobody is thinking about.
What a connection actually is
Every plan permits a fixed number of simultaneous streams, and the limit is enforced at the server rather than in the app. When your player authenticates, the server checks how many streams are currently open against that line and refuses anything beyond the allowance.
The refusal is often silent. Some players show a generic error, some simply sit there, and some drop an existing stream instead. None of that looks like "you are out of connections", which is why it is so consistently misdiagnosed.
The devices people forget
A box left powered on in an empty room is streaming. A phone player that was backgrounded rather than closed often holds its slot for several minutes afterwards. A second television someone else in the house switched on counts in full.
Before assuming a fault, account honestly for everything that could be streaming right now. In a multi-person household the real peak is almost always higher than the one people estimate.
Sharing credentials is the other cause
The credentials are the subscription. Anyone who has them can consume your slots, from anywhere. A login shared with a friend produces exactly this symptom on an unpredictable schedule, which makes it maddening to diagnose from the inside.
If playback fails at times that correlate with nothing in your own house, that is worth considering before anything technical.
Choosing the right number
Work out the household peak before buying rather than after. A plan bought too small does not feel like a plan bought too small — it feels like a service that does not work properly, and no amount of troubleshooting will change that. Adding connections is the fix, and it is cheaper than a month of frustration.
Still stuck?
Send us your order number and the device you are using, and a real person will work through it with you.
Contact support