What is Anti-Freeze Packet FEC Technology?
Protocol Definition & Architecture: Best Practices 2026
Technical Definition
Anti-Freeze describes a bundle of transport techniques that prevent visible stalls: Forward Error Correction parity packets, dual-source ingest with automatic failover, BBR congestion control on origin servers, and a 5,000 ms client jitter buffer.
How It Operates Under the Hood
FEC (RFC 6363) adds one XOR parity packet per ten MPEG-TS packets so a single loss in each block is reconstructed locally. Dual ingest monitors continuity-counter errors and switches sources within one GOP. BBR keeps TCP throughput high under random loss, and the client buffer absorbs the remaining jitter.
2026 Best Practices
In 2026 the recommended baseline for Anti-Freeze Packet FEC Technology is HEVC Main 10 delivery with LL-HLS, DNS over HTTPS on every device, WireGuard tunnels in throttled regions, and 5,000 ms player buffers. Resellers should bundle these recommendations into their customer setup guide.
Protocol Engineering Specifications
| Stream Engineering Metric | Reference Specification | Governing Standard |
|---|---|---|
| FEC ratio | 1:10 XOR parity |
RFC 6363 |
| Failover time | < 2 s (one GOP) |
Dual ingest |
| Client buffer | 5,000 ms |
Player setting |
| Transport Container | MPEG-TS (188 bytes: 4 B header + 184 B payload, 0x47 sync) |
ISO/IEC 13818-1 |
| Manifest Specification | Extended M3U8 playlist / LL-HLS 0.5 s parts |
IETF RFC 8216 |
| Decoder Pipeline | Hardware MediaCodec HEVC Main 10 (ExoPlayer / Media3) |
Android Media3 |
Client buffer time is the allocated buffer memory converted to bits, divided by the stream bitrate. Drag the sliders to see how much protection a given allocation gives against ISP shaping bursts:
A 15 MB allocation on an 18.5 Mbps 4K feed yields 6.49 seconds of reserve, enough to absorb a 2-4 second ISP shaping burst without a visible freeze.
Packet-Loss & Throttling Mitigation
Forward Error Correction (FEC)
Edge ingest nodes add XOR / Reed-Solomon parity packets (RFC 6363 FECFRAME) at a 1:10 ratio. A client can reconstruct a single lost 188-byte transport packet inside each 10-packet block without any retransmission round-trip, which is why peak-hour UDP loss of 0.5% produces zero visible artifacts.
TCP BBR Congestion Control
Origin and edge servers run Linux with net.ipv4.tcp_congestion_control=bbr. Unlike CUBIC, BBR models bottleneck bandwidth and round-trip propagation time instead of treating random loss as congestion, so an HLS session on a lossy Wi-Fi link keeps its 18.5 Mbps throughput rather than collapsing to half.
DNS over HTTPS via 1.1.1.1
Set the player device or router resolver to https://cloudflare-dns.com/dns-query (RFC 8484). ISP resolvers that return NXDOMAIN or poisoned A records for streaming hostnames are bypassed, and resolution latency typically drops below 15 ms.
Jitter Buffer & Dual-Ingest Failover
Players should hold 5,000 ms of media (TiviMate "Large" buffer). Upstream, every channel is ingested from two independent sources; a continuity-counter error rate above 0.1% on the primary flips the mux to the backup within one GOP (2 seconds).
Anti-Freeze Packet FEC Technology FAQ
What is Anti-Freeze Packet FEC Technology in simple terms?
Anti-Freeze describes a bundle of transport techniques that prevent visible stalls: Forward Error Correction parity packets, dual-source ingest with automatic failover, BBR congestion control on origin servers, and a 5,000 ms client jitter buffer.
Does Anti-Freeze stop ISP throttling?
No; it masks random loss and jitter. Deliberate shaping requires a WireGuard tunnel or DNS over HTTPS.
WireGuard vs OpenVPN: which VPN protocol is better for 4K IPTV?
WireGuard. It runs in the Linux kernel, uses a 4,000-line codebase with ChaCha20-Poly1305 encryption, and adds roughly 1-3 ms of latency with 5-8% throughput overhead, so an 18.5 Mbps 4K stream passes untouched. OpenVPN in TCP mode suffers from TCP-over-TCP meltdown during packet loss and typically costs 20-35% throughput; use OpenVPN only in UDP mode with tls-crypt on networks that block UDP port 51820.
How do I know if my ISP is throttling IPTV streams, and how do I stop it?
Run a speed test on the same device while a stream buffers. If raw throughput is above 25 Mbps but the player reports a bitrate below 8 Mbps, your ISP is applying traffic shaping to the stream flow, usually triggered by deep packet inspection of the TLS SNI or by sustained UDP/TCP flows to known hosting ASNs. Stop it by routing the player through a WireGuard tunnel (which hides destination and SNI inside ChaCha20-Poly1305 encryption), switching DNS to 1.1.1.1 over HTTPS, and keeping a 5,000 ms player buffer so short shaping bursts never reach the decoder.
What buffer size should I set in TiviMate, Smarters, or XCIPTV for 4K sports?
Set the largest option (5,000 ms in TiviMate, "Large" in Smarters). Buffer time in seconds equals buffer bytes multiplied by 8, divided by the stream bitrate in Mbps: a 15 MB allocation on an 18.5 Mbps 4K feed yields 6.5 seconds of protection, which covers typical ISP shaping bursts of 2-4 seconds without a visible freeze.
How are reseller credits priced and how is the margin calculated?
Credits are bought in tiers: $3.00 each at 50 credits, $2.20 at 100, $1.80 at 250, and $1.40 at 500+. One credit creates a 1-month line that retails for $10-$15. At the Pro tier (100 credits for $220) sold at $12/month, gross revenue is $1,200 and net profit is $980, a 445% return on the credit purchase.
Do providers offer a free trial and how long does activation take?
Every network in this directory issues 24-hour trial lines from the reseller panel. Activation is instant: the panel writes the line to the Xtream database and the player can authenticate within 10 seconds. Trial lines are usually limited to 1 connection and exclude PPV bouquets.
Every external citation on this page points to a primary source: telecommunications RFCs, ITU-T and ISO codec standards, manufacturer and developer documentation, national regulators, or official sports governing bodies. No commercial IPTV competitor is cited.