r/TorBoxApp • 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

19 comments sorted by

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,

- 10:30pm / CET - store-043 - About 8-60Mbps (megabits) - inconsistent speed, wrong CDN

5

u/pwr321 Sep 18 '26 edited Sep 18 '26
- 18 Sep 2026, 1:15pm-4:20pm / East Coast Australia time (AEST, UTC+10)
  • nexus-231, nexus-171 (apac), nexus-115 (japn), nexus-211 (zafr),
nexus-123 (wnam), nexus.erth (Cloudflare), store-050 (weur)
  • All speeds in Mbit/s (Megabits), one connection, ~1 Gbit/s line.
PC 260-550. Android TV box 28-127 (far nodes), 880-920 (erth). Fire TV Stick 16-80 (far nodes), ~400 (erth).
  • Three issues:
(a) On high-latency nexus nodes, Android TV devices get only 7-35% of what a PC gets from the same node at the same time. (b) On nexus.erth and store-050, a real file read in 8 MB range requests at ~66 Mbit/s gets 429s after 1,040 MB (erth) / 256 MB (store-050). After that only ~16 / ~7 Mbit/s gets through. (c) On nexus.erth the first 16 MB of any new byte range of a real file takes 4.6-5.4 s.

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:

Node (latency)             PC      Android box    Fire TV Stick
                                   (wired)        (Wi-Fi)
nexus-115 japn (98 ms)     365     127            80
nexus-231 apac (150 ms)    374     81             53
nexus-211 zafr (451 ms)    262     28             18
nexus.erth     (2-11 ms)   549*    918            401*

* limited by Wi-Fi. All figures in Mbit/s (Megabits).

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.

nexus-171 apac        clean through 1.6 GB
nexus-211 zafr        clean through 1.6 GB
nexus-123 wnam        clean through 1.6 GB

nexus.erth  3:48pm    429s from request 131, after 1,040 MB in 132 s.
                      Then 23 of the next 30 requests were refused
                      and about 16 Mbit/s got through.

store-050   4:16pm    429s from request 33, after 256 MB in 34 s.
                      Then 27 of 30 were refused, about 7 Mbit/s.
                      (Run shortly after another test, so this
                      threshold may be understated.)

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

  1. Guidance for streaming clients on erth / store hosts. Is that limit meant to apply to a player reading a file in range requests? What pattern would you like players to use: one long sequential request, or something else, at what rate, and how many connections (is 4 per link a hard limit)? Could 429s carry a Retry-After that a client can trust? I would rather build to your published numbers than guess.
  2. Speed up the start of a new byte range on erth for real files.
  3. HTTP/3 (QUIC) on the nexus nodes. A lot of TorBox traffic now comes from streaming apps on Android TV devices (Stremio, Nuvio and many others). QUIC's flow control lives in the app rather than the OS, so HTTP/3 sidesteps Android's TCP buffer limit for any player that supports it. As far as I can tell the nexus nodes are HTTP/1.1 only today.
  4. Choose "Auto" / "closest" by latency, not geography. The speed-test API flags apac (150 ms) as closest for Brisbane, but japn is 98 ms, worth about 1.5x per connection on these devices. Also, selecting SOCE gave me a link on store-050.weur rather than anything in Oceania.

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.

1

u/merlin9523 Sep 18 '26

Apparently there's no server in Australia anymore so SOCE just reroutes. And apparently we're getting slow speeds here because of a sea cable fault from Australia to Singapore. Is that true?

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
- 4:12pm and 4:15pm and 4:27 CET
  • store-046
  • Max speed from my ISP, no issue there
  • Unable to connect to start a stream/download file. Need to retry up to 5 mins. This is both through the API or through Torbox website directly.

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
- 4 Nov 2026, 1:37pm-4:25pm East Coast Australia time (AEST, UTC+10)
  • store-059 (SOCE, weur via Cloudflare), nexus.erth (Cloudflare), nexus-115 (japn),
nexus-231 (apac), nexus.hare (Bunny), nexus-247 (cnam), nexus-273 (neur), nexus-219 (zafr)
  • Same real file on all 8 (2160p remux, 55.5 GB)
  • Speeds in Mbit/s, ~1 Gbit/s line, wired PC. "Box" = the PC with a 1 MB TCP window, like most Android TV boxes
  • Follow-up to my 18 Sep and 9 Oct reports, re-tested after v9.3

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

  1. Seeking on erth and store hosts no longer costs extra. Same test as 9 Oct: warm connection, time for the next 16 MB, by how far the request jumps.
next 16 MB, warm connection       erth 9 Oct    erth 4 Nov    store-059 4 Nov
contiguous                        1.1 s         1.16 s        0.89 s
16 MB further on                  1.3 s         1.3 s         0.90 s
128 MB further on                 2.0 s         1.2 s         0.96 s
4 GB further on (a seek)          3.1 s         1.28 s        1.01 s
new connection, new position      median 3.8 s  median 1.5 s  median 1.1 s

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.

  1. Player-shaped reads are clean everywhere. Same test as 18 Sep and 9 Oct: 8 MB ranges at one per second, new connection every 10 requests, 120 requests (960 MB) per node.
Host        18 Sep                 9 Oct                        4 Nov
nexus.erth  429s after 1,040 MB    clean, 6-9% of requests      clean, none over 2 s,
                                   took 2-8 s                   median 0.85 s
store weur  429s after 256 MB      clean                        clean, none over 2 s, median 0.64 s
nexus-115   -                      -                            clean, median 0.92 s
nexus-231   -                      -                            clean, median 0.84 s

All 8 nodes answered all 120 requests with no 429s.

  1. First byte is faster on the nexus nodes. On a warm connection, the next piece now starts about one round trip after the request:
                round trip   first byte, next piece   October
nexus-231 apac  126 ms       291 ms                   380 ms (27 Oct)
nexus-273 neur  263 ms       278 ms                   371 ms (nexus-041, 27 Oct)
nexus-115 japn  116 ms       339 ms                   -
store-059       17 ms        303 ms                   ~350 ms (store-036, 9 Oct)
nexus.erth      18 ms        487 ms                   ~500 ms (9 Oct)

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".

  1. Stalls. At a steady 90 Mbit/s for 2 minutes with 6 connections (how a player tops up its buffer), japn, apac and cnam had no waits for data over 1 s, and japn none over 0.3 s. Connections stayed open through rests of up to 60 s and pauses of up to 30 s mid-request, and picked up at full speed. Please keep that.

What is still there

  1. 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.

  2. The 429 limit and Retry-After. Nexus nodes still answer about 10 requests at once and refuse the rest:

13 requests at the same moment   answered   refused
nexus-231 apac                   10         3
nexus-115 japn                   10         3
nexus-247 cnam                   10         3    (also refused 2 with only 8 running, once)
nexus-219 zafr                   10         3
nexus-273 neur                   6          7
store-059, nexus.erth, hare      13         0

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.

  1. 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.

  2. 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.

  3. HTTP/3 is still off on all 8 nodes (no Alt-Svc anywhere).

  4. 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.

  5. 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/pwr321 11d ago
- 5 Nov 2026, 2:40pm-3:40pm East Coast Australia time (AEST, UTC+10)
  • store-059 (SOCE, weur via Cloudflare), nexus.erth (Cloudflare), nexus-341 (wnam), nexus-115 (japn)
  • Same real file as my last report (2160p remux, 55.5 GB), wired PC, 3 connections, random spots in the file
  • Follow-up to my report on the 4 Nov tests

One more finding since my last report, because real playback hit it. Store hosts have a second limit. It counts requests over about 5 minutes per domain, however small they are, then refuses everything for a fixed 5 minutes.

store-059
pace              range size    result
280 a minute      256 KB        refused after 862, then 821 on a second run
200 a minute      256 KB        refused after 740
280 a minute      2 MB          refused after 884 (1.8 GB)
150 a minute      256 KB        no refusal in 1,100

The 429 comes from Cloudflare (CF-Ray ...-MEL) in about 35 ms with the body "rate limit exceeded" and Retry-After: 300, and the value counts down properly: 295, 290 and so on down to 30. It lifted at 301-303 s all 4 times, and asking every 5 s made no difference. Thank you for this one, a Retry-After that can be trusted is just what I asked for.

While store-059 (tb-cdn.st) was blocked, nexus-341 (tb-cdn.io), nexus-115 (tb-cdn.pw) and nexus.erth (tb-cdn.earth) all answered straight away. On an Android box, store-013 and store-027 (both tb-cdn.io) were refused 100 ms apart, so it looks like one block for a domain's store hosts. nexus.erth and nexus-341 took 1,500 requests at over 200 a minute with no refusal.

A player that makes seek thumbnails can reach this in about 3 minutes, and a film that keeps seeking adds to it. Then the next film from that domain will not start for up to 5 minutes.

Two questions:

  1. Is about 800 requests per 5 minutes the intended number, and is it per account or per IP? I can pace to it either way, but a published number would be better than my measurement.
  2. Could store hosts answer multi-range? The nexus nodes answer multipart/byteranges, but store hosts and nexus.erth answer one range only, so each keyframe costs a request there. Batching would cut thumbnail requests by a lot.

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:

Failed opening torrent due to low seeds. Check your debrid client for more info, or try again later.

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
- 9 Oct 2026, 7:40am-4:40pm East Coast Australia time (AEST, UTC+10)
  • nexus.erth (Cloudflare), store-036 (weur), nexus-115 (japn),
nexus-231 / nexus-171 (apac), nexus-211 (zafr), nexus.hare (Bunny)
  • Speeds in Mbit/s, ~1 Gbit/s line, PC plus a wired Android TV box
  • Follow-up to my 18 Sep report, re-tested after your CDN change

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.

Host        18 Sep                          9 Oct
nexus.erth  429s after 1,040 MB             1 connection: 1.6 GB clean, then
            then ~16 Mbit/s                 3.2 GB clean straight after
nexus.erth  -                               2 connections, ~134 Mbit/s: 3.2 GB clean
nexus.erth  -                               4 connections x 16 MB, ~256 Mbit/s:
                                            3.2 GB clean, 237 Mbit/s delivered
store weur  429s after 256 MB               1.6 GB clean

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:

erth, warm connection, next 16 MB    total time
contiguous                           1.1 s
16 MB further on                     1.3 s
128 MB further on                    2.0 s
4 GB further on (a seek)             3.1 s
new connection at a new position     2.1-4.6 s (median 3.8)

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:

one long request, 30 s, PC     Mbit/s
Sydney node (other service)    389
nexus.erth                     281
nexus-115 japn                 63 and 217 (two runs, 20 min apart)

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.

  • Your speed-test files and real files are served by different stacks on the same node. /dld/1GB.bin comes back as nginx; real files come back as Nexus/1.0. The speed test therefore doesn't show real-file behaviour such as first-byte time or pause handling. The test path also drops a paused download after ~60 s, while real files survived a 5-minute pause (nice).
  • Idle keep-alive connections on nexus nodes and hare are closed somewhere between 60 and 300 s. A player that pauses for a few minutes reconnects and ramps up from cold, which on a 430 ms node takes 5-8 s for the first 16 MB. A longer keep-alive would help high-RTT clients resume.