My winbox was failing to download so I did a netstat -b with a admin command prompt.. The data was coming straight from riga to the US and it looks like a New York - London link is the slowdown:
C:\Windows\System32>tracert 159.148.147.251
Tracing route to 159.148.147.251 over a maximum of 30 hops
1 6 ms 3 ms 2 ms 10.0.54.1
2 10 ms 9 ms 10 ms 71.181.84.1
3 10 ms 9 ms 13 ms 7.l.burlvtma97w.vt.consolidated.net [64.222.213.131]
4 15 ms 73 ms 14 ms 38.104.52.78
5 * * * Request timed out.
6 13 ms 106 ms 15 ms be3255.ccr31.bos01.atlas.cogentco.com [66.28.4.29]
7 14 ms 57 ms 13 ms telia.bos01.atlas.cogentco.com [154.54.9.26]
8 16 ms 70 ms 98 ms bost-b5-link.ip.twelve99.net [62.115.140.180]
9 21 ms 18 ms 19 ms nyk-bb5-link.ip.twelve99.net [62.115.122.202]
10 150 ms 206 ms 203 ms ldn-bb1-link.ip.twelve99.net [62.115.139.245]
11 178 ms 190 ms 206 ms hbg-bb3-link.ip.twelve99.net [62.115.137.215]
12 215 ms 297 ms 208 ms war-b3-link.ip.twelve99.net [62.115.120.69]
13 220 ms 207 ms 202 ms riga-b6-link.ip.twelve99.net [62.115.139.55]
14 219 ms 214 ms 191 ms riga-b8-link.ip.twelve99.net [62.115.143.92]
15 199 ms 205 ms 203 ms riga-b4-link.ip.twelve99.net [62.115.142.89]
16 214 ms 203 ms 203 ms riga-b5-link.ip.twelve99.net [62.115.138.111]
17 211 ms 203 ms 203 ms siatet-ic-332270.ip.twelve99-cust.net [213.248.84.33]
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 176 ms 203 ms 203 ms 159.148.147.251
Trace complete.
I don't think it's quite as easy as "slow ping = crap downloads". If I get a VPN to exit at Riga, it still has to get there from the otherside of the world, so suffers ping.
Even when downloading from Western Europe I found the performance quite average, however from Latvia it is wicked fast.
I'm fairly sure the issue is in those first few hops, just trying to nail it down is pretty hard.
No, not quite. I does improve the situation a lot however.
I did some updates this morning and ho lee sheet it was running slow and a few attempts timed out.
Downloads (firmware updates, image downloads via Router or browser, etc) the last few months or so have been significantly slower than in the past. And its erratic where either the download starts fast and slows down or starts slow and speeds up. It will also sometimes fail.
Downloads used to take 5-10 secs, now ill wait over 1-2 mins for the tiny lil 12M file.
From western Europe I never saw slow or failed downloads from download.mikrotik.com in the last weeks or months. With traceroute, I see ping times climbing from ~5ms to ~40ms once reaching ip.twelve99.net (62.115.0.0/16) hops, but download speed is stable around 10MB/s
$ wget https://download.mikrotik.com/routeros/7.24.5/routeros-7.24.5-arm64.npk
Resolving download.mikrotik.com (download.mikrotik.com)... 159.148.147.251
Connecting to download.mikrotik.com (download.mikrotik.com)|159.148.147.251|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 13922637 (13M) [application/octet-stream]
Saving to: ‘routeros-7.24.5-arm64.npk’
routeros-7.24.5-arm64.npk 100%[=================================================>] 13.28M
10.8MB/s in 1.2s
The OP edited the very first post as resolved and whole thread lost it's sense - frankly it was done in other topics too - and I wonder if the original text should be restored.
Please do not do that ... if you want to close the topic, it could be done without loosing the history.
Now we have kind of a discussion about "who knows what it was about?".
I don't always agree with your moderation, but I think that what you are proposing is reasonable. Deleting an opening post after other people have put in their thoughts is anti social.
You were even more tactful than I would have been in explaining it.
It certainly isn't respectful towards others.
I agree with restoring both the title and the OP.