Before you change a single setting, figure out how wide the fault is. One channel freezing while the rest of the guide plays fine points at that channel's source feed, not your setup. A whole category going dark at once, like every group under one heading, points at a server-side fault on that feed group. Every channel failing at the same time, across apps, points at your line, your player, or your session. This one check decides whether the next twenty minutes are worth spending, so do it first, every time.

1. 1One channel down = source problem
2. 2One group down = server-side to that group
3. 3Everything down = line, player, or session

A live stream is not one continuous file. It arrives as a series of short segments, roughly 6 seconds each, stitched together in real time. When a channel freezes, switch to a different channel, then switch straight back. If the original channel plays clean again, the session stalled and recovered on its own, which means your bandwidth was never the cause. If it freezes again in the same spot, the fault sits upstream of you. This is the cheapest test you have and it separates two causes that look identical on screen.

Every plan allows a set number of simultaneous connections, 1 to 5 depending on the plan. If you set up the same account on a second device or a second app, and the first one is still logged in and playing, the newer connection can throw an error on every channel even though nothing about your playlist changed. This looks like a broken setup, but it is a slot conflict. Log out of any other device or app using the account, wait a minute, then reconnect on the device you want to use.

Player apps get updated on their own schedule, and a fresh version can regress a setting that was working the day before, especially buffer size or how the app handles a large channel list. If the problem started right after your app updated itself, that timing is the clue, not your internet. Clear the app's cache, reset buffer and playback settings to default, and reload the channel list. If the app also feels sluggish or slow to switch channels generally, a very long visible channel list, upward of about 18,000 entries held in memory, is a known way these apps destabilize, and hiding unused groups fixes that.

Some stalling is capacity on the provider's side, not your router or your device, and no local setting reaches it. That is a real answer, not a way to dodge the question, and it is also why a provider's published uptime figure matters more than any single troubleshooting tip. IP4KTV runs at 99.99% uptime, which works out to roughly 53 minutes of downtime a year. If you have run the scope test, the switch-back test, and checked your connection slot and still get the same fault, the honest next step is contacting support, not repeating the same restart.