Corrections

When we find a factual error in a guide, we fix it and record it here. Each entry states what the guidance previously said, so you can tell whether you read the earlier version.

Entries are never removed. If you think something on this site is wrong, please tell us. Open problems we have not yet resolved are listed on our known issues page.

  1. Factual error

    VPN guidance contradicted two other guides on this site

    What was wrong
    Our buffering guide recommended trying a VPN to improve streaming, while our VPN guides stated that VPNs add a hop, reduce throughput and commonly cause buffering. A reader following both received opposite instructions.
    What it says now
    A VPN is presented as a diagnostic test for ISP throttling, not a fix. The guide states that a VPN usually reduces throughput and often makes buffering worse, and instructs the reader to turn it off again if playback does not improve at peak.
    Pages changed
    How to Fix IPTV Buffering
  2. Factual error

    DNS was listed as a cause of mid-stream buffering

    What was wrong
    DNS resolution delays were listed among the causes of buffering. DNS is resolved once when a stream starts and cached thereafter, so it cannot cause a stream to stall during playback.
    What it says now
    DNS is described as affecting channel switching and start-up time, explicitly not mid-stream buffering. The advice itself was accurate but filed under the wrong symptom.
    Pages changed
    How to Fix IPTV Buffering
  3. Factual error

    5 GHz Wi-Fi was recommended unconditionally

    What was wrong
    Guides recommended 5 GHz on the basis that the device supported it. 5 GHz is less congested than 2.4 GHz but penetrates walls significantly worse, so for a device several rooms from the router this advice could make playback worse.
    What it says now
    5 GHz is recommended when the streaming device is in the same room as the router or already has a strong signal, with 2.4 GHz advised through walls or at distance, and an instruction to switch back if playback worsens.
    Pages changed
    How to Fix IPTV Buffering · IPTV Router Settings · IPTV Ethernet vs Wi-Fi · Best Device for IPTV UK · Best Internet Speed for IPTV UK · Best IPTV Apps UK · IPTV Buffering on Android TV · Best IPTV for Firestick
  4. Factual error

    The benefit of Ethernet was attributed to the wrong property

    What was wrong
    Ethernet was described as helping because of lower latency. Buffering is caused by a player's buffer draining, which is a throughput and jitter problem rather than a baseline latency one.
    What it says now
    Ethernet is described as giving steadier throughput and lower jitter, and as the clearest available test — a problem that persists on a wired connection is not caused by Wi-Fi.
    Pages changed
    How to Fix IPTV Buffering · IPTV Ethernet vs Wi-Fi
  5. Factual error

    Bandwidth figures omitted that they were per stream

    What was wrong
    Speed requirements were given as flat figures. A household running several streams at once would read '25 Mbps for 4K' and conclude a 30 Mbps line was sufficient.
    What it says now
    Figures are stated per stream, with an instruction to multiply by the number of simultaneous streams and allow headroom for other traffic.
    Pages changed
    How to Fix IPTV Buffering · IPTV Buffering on Firestick · How to Watch IPTV · Best IPTV for Firestick · IPTV Buffering Test · IPTV Internet Requirements · IPTV Not Working · IPTV Poor Picture Quality · IPTV Streaming Guide · IPTV Speed Test
  6. Factual error

    The effect of app cache on buffering was overstated

    What was wrong
    A FAQ answer opened with a flat 'Yes' to whether cache and storage affect buffering, asserting a confirmed causal link we had not established.
    What it says now
    The answer states that cache and storage affect the app rather than network delivery, that clearing them is quick to try, and that neither will change buffering caused by the connection.
    Pages changed
    How to Fix IPTV Buffering
  7. Factual error

    Escalation guidance attributed a constant fault to the wrong cause

    What was wrong
    Buffering that persisted on Ethernet, across devices, at all times of day was attributed to the provider. Provider-side congestion characteristically varies with load, so a fault that does not vary points elsewhere.
    What it says now
    A time-invariant fault is attributed to the line, router or ISP path, and a fault confined to peak hours is attributed to ISP or provider congestion. The two patterns are now separated.
    Pages changed
    How to Fix IPTV Buffering
  8. Internal inconsistency

    Power-cycle duration differed between guides

    What was wrong
    One guide instructed unplugging for 10–15 seconds while another specified 30 seconds for the same action.
    What it says now
    30 seconds is used consistently.
    Pages changed
    IPTV Not Working on Firestick
  9. Internal inconsistency

    Free-storage guidance gave different figures

    What was wrong
    Guides advised keeping '1–2 GB' free in one place and '500MB–1GB' in another for the same recommendation.
    What it says now
    The Firestick guide states at least 1 GB. The wider inconsistency across other guides is still open — see our known issues.
    Pages changed
    IPTV Not Working on Firestick
  10. Unactionable guidance

    A guide advised moving a device that cannot be moved

    What was wrong
    The guide advised placing the Firestick closer to the router. A Firestick plugs directly into the TV's HDMI port and cannot be repositioned independently of the television.
    What it says now
    The guide notes that the Firestick cannot be moved independently, and advises moving the router or using a USB Ethernet adapter instead.
    Pages changed
    IPTV Not Working on Firestick
  11. Unactionable guidance

    Guides advised testing at a different time without saying which

    What was wrong
    Several guides referred to 'peak evening hours' without stating a window, leaving the instruction to test at a different time unexecutable, even though another guide on this site already published the figure.
    What it says now
    Peak hours are stated as typically 7–11 pm in the UK, with an instruction to compare the same channel inside and outside that window.
    Pages changed
    How to Fix IPTV Buffering · IPTV Buffering on Wi-Fi · IPTV Keeps Freezing · IPTV Buffering Test · Why IPTV Buffering Happens UK
  12. Link integrity

    Internal links pointed at URLs that redirect

    What was wrong
    118 internal links across the site pointed at older URLs that redirect to their current location. One guide linked to a URL that redirected back to the same guide.
    What it says now
    All internal links point directly at their final destination. The self-referential link was removed.
    Pages changed
    Site-wide — 37 files

All 12 corrections above were made during a single review of the troubleshooting corpus. They are dated to that review rather than spread across earlier dates.