Why streams buffer in the evening, and how to actually fix it

Speed is almost never the problem

The first thing people do when a stream stutters is run a speed test, see a healthy number, and get more confused. That is because a speed test measures the best case: one big download, from a nearby server, for a few seconds. Streaming is a very different job. It needs a modest amount of data delivered without interruption, continuously, for hours.

A connection that peaks at 200 Mbps but drops packets every thirty seconds will buffer constantly. A steady 20 Mbps line will not. Consistency beats headline speed every time, which is why the fix usually has nothing to do with upgrading your package.

It is worth understanding what buffering physically is, because it makes the rest of this page obvious. Your player keeps a small reserve of video in memory and plays from that reserve while topping it up from the network. When data arrives more slowly than it is being consumed, the reserve empties and playback stops until enough has arrived to start again. Every buffering event is that reserve running dry. The question is never "is my connection fast enough" in the abstract; it is "does my connection ever stop delivering for long enough to empty the buffer".

Start with the wireless link

Wi-Fi is the single most common cause we see, and it is worth ruling out before touching anything else. The 2.4 GHz band in particular is crowded: your neighbours, your microwave, your baby monitor and half the Bluetooth devices in the house all share it.

If your device supports 5 GHz, use it. If your streaming box has an Ethernet port, use that instead and the problem often disappears entirely. Where running a cable is impractical, a pair of powerline adapters is usually a bigger improvement than any router upgrade.

Most streaming sticks have no Ethernet port but will accept an adapter; on a Fire TV Stick, Amazon's own Ethernet adapter replaces the power lead and adds a network socket for a modest sum. In our support experience it is the single highest-value change available to anyone with a main television that buffers, and it is a five-minute job.

The quickest way to prove Wi-Fi is your culprit takes no equipment at all. Play a channel that normally stutters, then play the same channel on a phone using mobile data rather than your home network. If mobile data is clean and the television is not, nothing is wrong with your subscription or your provider; the problem is between your router and your television.

Router placement, bands and channels

If wiring the television is genuinely impossible, the next best thing is to give the wireless link the easiest job you can.

• Move the router, not the television. Routers work best high up, in the open, roughly central to the house. In a cupboard under the stairs, behind a television, or on the floor beside a radiator, they lose a great deal of their range before they have started.
• Count the walls, and notice what they are made of. Each solid wall costs signal. Foil-backed insulation, metal studwork, mirrors and anything containing water, including a large fish tank, are much worse than plasterboard.
• Use 5 GHz for anything that matters. It is faster and far less congested; it simply carries less well through walls. If your router publishes both bands under one name, the streaming device may cling stubbornly to the weaker 2.4 GHz signal. Splitting the bands into two network names in the router settings and connecting the television explicitly to the 5 GHz one is a permanent fix for a common problem.
• Change the wireless channel if you live somewhere dense. In a block of flats, twenty routers may be shouting over one another. Most routers will pick a quieter channel automatically if you reboot them; some need to be told.
• Reboot the router occasionally. Consumer routers develop problems over months of uptime in the same way that streaming sticks do.

Then look at the device itself

Cheap streaming sticks run hot and have very little memory. After a few weeks of uptime, an inexpensive Fire Stick will start stuttering on content it handled fine when new, simply because it has run out of headroom.

Unplug it at the wall for ten seconds, clear the player app cache, and remove apps you never open. This sounds trivial, and it resolves a genuinely large share of the reports we get.

Heat deserves a mention of its own, because it produces a distinctive symptom: fine for the first twenty minutes, then progressively worse. A stick tucked into the recess behind a wall-mounted television has no airflow at all, and it will throttle its own processor to protect itself. A short HDMI extension lead that lets the stick hang free in the air behind the set costs very little and solves the problem completely.

Storage matters too. Streaming devices slow down markedly when they are nearly full, and an IPTV player that has been caching a large channel list and programme guide for months can be occupying a surprising amount of it. On a Fire TV device, Settings, Applications, Manage Installed Applications shows the size of each app and offers Clear cache, which removes the cached list and guide without touching your login. That is always worth trying before anything more drastic.

If a Fire Stick is your main screen, the performance and error sections of the complete Fire Stick setup guide go through the device-side fixes in more detail, including which settings to switch off and what each on-screen error actually means.

Check whether your provider is throttling you

Some internet providers deliberately slow sustained video traffic during peak hours. The signature is distinctive: everything is perfect at two in the afternoon and unwatchable at nine in the evening, while speed tests stay fine throughout because they are short.

The quickest way to test this is to run a VPN for one evening. If the stutter vanishes, your provider was shaping the traffic, and a VPN is the practical long-term answer.

A few notes on doing that test properly, because a badly run one tells you nothing. Use the VPN on the streaming device itself rather than on a different device. Pick a server geographically close to you, since a distant one introduces its own delay and muddies the result. Test at the hour when the problem is at its worst, not at lunchtime. And judge it over at least half an hour; a clean five minutes proves very little.

Most customers never need a VPN. But when throttling is the cause, nothing else you do will help, which is why this test is worth running early rather than after a fortnight of changing other things.

Peak-hour congestion is not quite the same thing

Throttling is deliberate. Congestion is not, and they look identical from your sofa.

Many home connections share capacity with neighbouring properties somewhere upstream. When everyone in the area is streaming at once, the shared segment fills up and your effective throughput falls even though your provider is doing nothing intentional. The symptom is the same evening-only stutter.

You can usually tell the two apart with the VPN test, because a VPN routes around traffic shaping but cannot route around a full pipe. If the VPN fixes it, it was shaping. If the VPN changes nothing and the evening is still bad while the afternoon is perfect, it is congestion, and your options are to talk to your provider about it or to reduce what you are asking of the line at peak times, whether fewer simultaneous streams or the SD variant of a channel during the busiest hour.

Player settings that make a measurable difference

Two settings inside your IPTV player are worth knowing about, and the rest mostly are not.

Buffer size. Most players let you choose how much video to hold in reserve before playback starts. A larger buffer absorbs brief interruptions that would otherwise stop the picture; the cost is a longer pause when you change channel. If your connection is mostly good with occasional hiccups, increasing the buffer is exactly the right tool and often makes the problem disappear from your point of view entirely. If your connection cannot sustain the stream at all, a bigger buffer only delays the inevitable.

Hardware decoding. Players usually offer hardware, hardware-plus and software decoding. Hardware decoding hands the work to the chip designed for it and is what you want on almost every device; on older boxes it is frequently the difference between smooth playback and stutter. The exception is a single channel showing a green or garbled picture, which points to a codec that device's hardware decoder handles badly; switch that one channel to software decoding rather than changing the setting globally.

If a channel plays but has no sound, look for the audio decoder or audio track option instead. Some sources use audio formats that particular devices dislike, and switching decoder normally clears it.

Rule out the individual channel

If one channel stutters and the other two thousand are perfect, the problem is that channel, not your setup. Sources vary in quality, and occasionally one is having a rough night at its own end.

Try the same channel from a different group, or its HD and SD variants. When you tell support "channel X buffers but everything else is fine", that is precise enough for us to fix the source directly rather than sending you through generic troubleshooting.

Rule out the device slot problem

There is one cause of stopping and stuttering that has nothing to do with your network at all: each simultaneous stream needs its own device slot. If your drop-outs track who else is at home rather than the time of day, that is almost certainly your answer, and adding a second device without breaking the first one explains how slots work and how many a household genuinely needs.

A short checklist

Work through it in this order and you will find the cause quickly: switch to Ethernet or 5 GHz; reboot the streaming device at the wall; clear the player cache; check whether anyone else is using the same login at the same time; test the same login on a phone using mobile data; increase the player's buffer size; try a VPN for one evening; note whether it is one channel or all of them.

That last step matters more than any of the others. "All channels, every evening, on every device" and "one channel, sometimes, on the Fire Stick only" are completely different problems, and knowing which one you have saves everybody a great deal of time.

It is also worth checking your figures against what internet speed you actually need before concluding your connection is adequate, particularly if more than one screen is running at once, because the requirement is per simultaneous stream rather than per household.

When to contact support, and what to send

Contact us once you have tried the wired-or-5 GHz test and the reboot, and still have a problem. There is nothing to be gained from a week of trial and error, and in our support experience most buffering reports resolve in a couple of messages provided we are given something to work with.

Send these five things and you will get a diagnosis rather than a questionnaire:

• Your order number, so we can look at the line itself.
• The device, including whether it is on Ethernet, 5 GHz or 2.4 GHz.
• One channel or all of them, and one device or all of them. This single distinction narrows the problem more than everything else combined.
• When it happens: all day, or only in the evening, and roughly which hours.
• What you have already tried, so we do not ask you to do it again.

The contact page and the WhatsApp button on any page reach the same support team, and you will get a person rather than a ticket number. While you wait for a reply, the help page covers several of the questions that tend to arrive alongside buffering.