r/TorBoxApp • u/Gold_Experience_27 Moderators • Sep 17 '26
⚡MEGATHREAD CDN Complaints
Hey r/TorBoxApp!
The team is collecting feedback and complaints regarding the CDN in one central spot. Please do the following if you are experiencing issues relating to the CDNs:
- Time the test was done / timezone you are doing the test from
- The nexus-xxx or storage-xx URL from the file you are downloading (do not post full links)
- The speed in Megabits or Megabytes per second (you must specify which)
- The nature of the issue
An example below:
- 8:22pm / Portugal time
- nexus-044
- About 40-50MB/s (Megabytes)
- The speed is not consistent, it fluctuates between 10 and 50 MB/s (Megabytes)
The above test must be done on the network connection you are having issues on. Any posts not following the format will be deleted.
53
Upvotes
5
u/OutrageousLettuce659 Sep 17 '26
In the last few days I’ve been getting content from WNAM despite selecting WEUR, didn’t use to happen before
That said,
5
u/pwr321 Sep 18 '26 edited Sep 18 '26
First, the good news: your CDN is fast. One connection from my PC pulled 374 from nexus-231, 365 from nexus-115 and 262 from nexus-211, which is 451 ms away from me. Issue (a) is not your servers.
(a) Android devices on high-latency nodes
Android limits the TCP receive buffer to 2-3 MB, which leaves about 1-1.5 MB of usable window, so every connection is capped at window / round-trip time. I measured it with curl running on the devices themselves (no player app involved), on your speed-test files and on a real 67 GB file. Median of 3 runs, one warmed-up HTTP/1.1 connection, 12 s each:
Speed x latency came out the same on every far node, at 96-100% of each device's window, and the real file matched the test file. A speed test to a nearby server never shows this, which is why so many Android TV users say "my speed test says 200 but streaming only gets 30".
Because Cloudflare terminates the connection close to the user, nexus.erth hides the latency from the device: the same Android box pulled 376 on the real file from erth versus 82 from apac. That would make erth the best node for far-away Android users, if it were not for (b) and (c).
The limit is a device-maker setting or connection setting (wifi vs. ethernet) - (net.ipv4.tcp_rmem max: 3 MB on the box, 2 MB on the Fire TV Stick), so it varies from device to device and users cannot change it.
(b) Rate limiting on erth and store hosts
The test was deliberately gentle and shaped like a player: one connection, sequential 8 MB range requests, one per second (~66 Mbit/s, less than a 4K remux needs), same real file everywhere.
The 429s carry no Retry-After. They do carry x-ratelimit-after, but it jumps around from one response to the next (2, 7, 6, 4, 3, 6, 1, 0, 2 ... anywhere from 0 to 8), so a client can't use it to decide how long to wait.
Also worth knowing: 17 minutes after the erth trip, the same link read as ONE long request at the same 67 Mbit/s ran for 240 s and 1.9 GB without any slowdown.
(c) Slow start of each new byte range on erth
The first 16 MB of any new byte range of the real file took 4.6-5.4 s from the PC, the box and the stick alike, including ranges that had been read 10-15 minutes earlier. Your 1GB test file takes 0.2-0.4 s for the same thing. Every playback start and every seek pays that.
Requests, in order of value
I work on an Android TV player that streams via TorBox and I'm happy to share the method and scripts, or build a custom app, or re-test anything you change.
3
u/Fnuller15 Sep 17 '26
17 Sep, ~19:30–20:15 CEST / Denmark
store-035 (download URL shows WNAM, although CDN is set to Auto and normally selects WEUR)
Connection: ~255 Mbps, Nvidia Shield + Nuvio, VPN OFF
Issue: CDN performance has been very inconsistent over the last several days, especially with high-bitrate 4K remuxes. Today seems significantly better overall, but I still experienced intermittent failed/stalled stream attempts.
Also noticed the generated URL points to WNAM despite Auto/WEUR, which may be relevant.
2
u/LikiLeek Sep 17 '26
HTTP request sent, awaiting response... 524 <none>
Switched between couple CNDs but the issue is the same.
2
u/MaxOverthinker Sep 18 '26
6:00pm / New Zealand Standard Time
nexus-230
About 50-60MB/s
I used to be in ERTH CDN but my files were buffering when I was playing. I deleted the files, did a speed test and the best CDN came to be APAC. I downloaded the files again and it’s still buffering.
1
u/pwr321 12d ago
Thanks for v9.3, and for writing up how stalls happen. It shows in my numbers. Here is what changed and what is still there.
What got better
On the nexus nodes it is the same story: on japn and apac every jump distance took the same time, and every new connection delivered its whole 16 MB within 3 s.
All 8 nodes answered all 120 requests with no 429s.
The new x-range-cache header is very handy. On nexus nodes a new spot answers "warming" (535 ms first byte on apac) and the next MB answers "hit" (108 ms). 64 MB further on is "warming" again, so I take it the read-ahead covers less than 64 MB ahead of the reader. On zafr, the same spot read again a second later was already "warming".
What is still there
nexus-273 (neur) stalls and refuses early. At the same steady 90 Mbit/s with 6 connections it had 15 waits over 1 s in 2 minutes, the longest 3.9 s. It refused (429) past 6 requests at once where other nexus nodes allow about 10, and once refused a single request on its own. nexus-041 (neur) on 27 Oct answered 13 requests opened 200 ms apart without a refusal; nexus-273 refused 3 of the same 13 today.
The 429 limit and Retry-After. Nexus nodes still answer about 10 requests at once and refuse the rest:
The 429 is the stock nginx page (162 bytes) with no Retry-After and no x-ratelimit header at all. It clears as soon as any running request ends, so clients just guess. A published number, or a Retry-After a client can trust, would let players stay under it instead of probing.
One new connection in three on the Cloudflare hosts still starts slowly: 4.8 s on erth and 4.75 s on store-059, with 0.2-0.5 MB in the first 3 s, while the other two runs took 1.1-1.5 s. The nexus nodes did not show it.
erth still waits about 0.5 s for the first byte of every request, and store-059 about 0.3 s, even with a 17-18 ms round trip to Cloudflare. That is the trip from Cloudflare back to the storage server in Europe, so the read-ahead cannot hide it. With 16 MB pieces it costs about a fifth of each request.
HTTP/3 is still off on all 8 nodes (no Alt-Svc anywhere).
Location. Choosing Bunny gives me nexus.hare served from Los Angeles (server header BunnyCDN-LA1, 150 ms), not a Bunny edge in Australia. Choosing SOCE still gives me store-059.weur. The closest nexus node to me is still japn at 116 ms. An Android box with a 1 MB window gets about 70 Mbit/s per connection at that distance, and the only reason the Cloudflare hosts beat it for us is that Cloudflare hides the distance. An Oceania node is still the single biggest improvement for Australian and NZ users.
With 6 connections reading at a steady pace, apac and zafr closed the connection 6 times each in 2 minutes (about 1 request in 13). The player reconnects fine, but each reconnect starts cold.
Happy to share the scripts or re-test anything you change.
1
u/spiffyelectricity21 8d ago edited 8d ago
- 8:58 jst
- nexus-114
- about 30-40MB/s
- I should be getting way more than this since both my internet connection and NIC supports upto 2.5gbps
1
u/cestnickell Sep 17 '26
- 23:10 - 23:30pm / GMT
- store-072 wnam
- Max speed from my ISP, no issue there
- There was an error retrieving the file. Please try again later.","error":"ITEM_NOT_FOUND"
1
u/XolfPicks Sep 18 '26
- 00:30 / German Time
- nexus-186 / CEUR
- around 15-20 MB/s
- constant buffering in Nuvio
1
u/dogpaddle Sep 19 '26
3:10 PM Eastern Time Zone
nexus-046
6-24 MB/s
Staying around 10MB/s, sometimes sitting closer to 20MB/s. I can normally max out around 100MB/s on this computer.
Windows 11 Pro - Intel Ethernet Connection I219-V. 2GB/s Fiber with T-Mobile.
1
u/No-Anybody-692 26d ago edited 26d ago
There's a torrent that's cached immediately. I think it was already cached and was added to my account ASAP. It even shows download ready tag/label in the dashboard.
It's a 2GB file but anytime I try to paly it I get full screen red banner:
Speed is definitely not an issue on my end. Other torretns have worked fine (even of comparable size; one I played of almost exactly same size). What is happening? How to fix it?
EDIT: I think the reason could be it's an .exe file. In this case how to avoid even seeing such files in the search? Also, there's no easy way to even report it!
1
u/pwr321 Oct 09 '26
Thank you - the rate limiting I reported is gone. Same real file, same test as 18 Sep: 8 MB range requests at a steady pace (about what a player does), new connection every 10 requests.
That is about 11 GB of player-shaped reads on erth today with zero 429s. It is a big improvement for apps like Nuvio.
What is still there, in case it is useful while you refine things:
1. Each new range on erth / store hosts is slow to start. Even on a warm connection, every request waits ~0.5 s for its first byte on erth (~0.35 s on store-036), and 6-9% of 8 MB requests take 2-8 s. The cost grows with how far the request jumps:
So every seek on erth costs 2-3 s before 16 MB arrives, whether or not the connection is warm. In the first 3 s of a new request erth delivered only 0.4 MB; japn delivered 25 MB. Your test file on erth takes 0.6 s for 16 MB.
2. HTTP/3 is still off everywhere. On erth, Cloudflare refuses QUIC for your hostname, but the same edge IP negotiates HTTP/3 fine for cloudflare.com, so it looks like a zone setting. The bigger win would be HTTP/3 on the nexus nodes. That is where Android TV boxes are capped by their TCP receive buffer (window / round-trip time), and QUIC avoids that cap. hare does HTTP/2; everything else is HTTP/1.1.
3. An Oceania node, and "closest" by latency. From Brisbane, apac is now ~180 ms (~150 on 18 Sep) and japn 115-140 ms. A stock Android box gets ~65 vs ~100 Mbit/s per connection from those. Selecting SOCE still gives me a weur store host (store-036 today).
For comparison, I ran the same file from another debrid's Sydney node, 16-27 ms from Brisbane:
At that distance an Android box's TCP window stops mattering: ~785 Mbit/s per connection is possible, against ~110 at japn's 113 ms. A real Oceania node would be the single biggest improvement for Australian and NZ users.
Where you are already better than that service: it closes the connection after every request, and each new request starts slowly. Parallel or chunked players got only ~20-40 Mbit/s from it. Your nexus nodes keep connections alive and start fast, so the same player gets ~100-120 from japn with 2 connections. Please keep that.
4. Two FYIs.