Anyone notice the speeds from Europe are just horrible at night? i decided to do a speedtest at around noon and a speedtest now at 9pm.
The below link is at i3d, a dutch gaming host company. and before you whine that I should be downloading from a closer source, that's not the point... »mirror.i3d.net/pub/debia ··· -hybrid/
At around noon it almost maxes my 28mbit. Right now the test is going at 35KB/sec which is just sad. I'm in an apartment building and my neighbor who has rogers cable get's almost 3mb/sec doing this same test.
Will this ever be fixed? the speeds have gradually got worse and worse...
Tracing route to mirror.i3d.net [213.163.76.200]
over a maximum of 30 hops:
1 11 ms 11 ms 10 ms 7.2.120.1
2 10 ms 19 ms 11 ms 24.156.151.97
3 13 ms 15 ms 12 ms 69.63.249.185
4 28 ms 25 ms 26 ms 24.156.147.250
5 25 ms 26 ms 25 ms xe-2-0-0.er1.lga5.us.above.net [64.124.128.193]
6 25 ms 24 ms 45 ms xe-5-1-0.cr1.lga5.us.above.net [64.125.30.205]
7 25 ms 41 ms 26 ms xe-1-0-0.cr2.lga5.us.above.net [64.125.29.46]
8 25 ms 25 ms 25 ms xe-0-0-1.er4.lga5.us.above.net [64.125.24.169]
9 29 ms 27 ms 30 ms L3-Zayo.lga5.us.above.net [64.125.13.30]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 111 ms 101 ms 99 ms interactive.edge4.London1.Level3.net [212.113.8.
46]
16 104 ms 102 ms 101 ms 40ge-1-1.br3.smartdc.i3d.net [188.122.95.85]
17 102 ms 100 ms 99 ms mirror.i3d.net [213.163.76.200]
Trace complete.
This is without VPN or anything like that, just direct from rogers. Teksavvy has bad transit, that's all I can say.
here are some results, it should be noted that the return path and the path being used to send the data from a download could be different:
my server in Montreal off OVH:
justin@kif:~$ traceroute mirror.i3d.net
traceroute to mirror.i3d.net (213.163.76.200), 30 hops max, 60 byte packets
1 * * *
2 bhs-g1-6k.qc.ca (198.27.73.13) 0.547 ms * *
3 * * *
4 * * *
5 ams-1-6k.nl.eu (213.251.128.6) 82.376 ms * *
6 20ge.ams-ix.i3d.net (195.69.144.162) 82.357 ms 82.389 ms 83.046 ms
7 30ge.cr1.smartdc.i3d.net (109.200.218.86) 83.622 ms 83.203 ms 83.097 ms
8 30ge-1-2.br2.smartdc.i3d.net (188.122.95.84) 95.006 ms 40ge-1-1.br3.smartdc.i3d.net (188.122.95.85) 100.884 ms 87.543 ms
9 mirror.i3d.net (213.163.76.200) 83.999 ms 84.008 ms 83.836 ms
justin@kif:~$ wget http://mirror.i3d.net/pub/debian-cd/6.0.7-live/i386/iso-hybrid/debian-live-6.0.7-i386-standard.iso
--2013-04-03 22:40:21-- http://mirror.i3d.net/pub/debian-cd/6.0.7-live/i386/iso-hybrid/debian-live-6.0.7-i386-standard.iso
Resolving mirror.i3d.net (mirror.i3d.net)... 2a00:1630:1:13d::13d, 213.163.76.200
Connecting to mirror.i3d.net (mirror.i3d.net)|2a00:1630:1:13d::13d|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 295698432 (282M) [application/octet-stream]
Saving to: `debian-live-6.0.7-i386-standard.iso'
100%[================================================================================== >] 295,698,432 8.66M/s in 38s
2013-04-03 22:40:59 (7.34 MB/s) - `debian-live-6.0.7-i386-standard.iso' saved [295698432/295698432]
my server in NYC off HE.net:
justin@waffle:~$ traceroute mirror.i3d.net
traceroute to mirror.i3d.net (213.163.76.200), 30 hops max, 60 byte packets
1 nyc.rt2.cyberwarp.net (209.51.166.121) 0.574 ms 0.624 ms 0.750 ms
2 v103.core1.nyc1.he.net (216.66.30.217) 3.552 ms 3.606 ms 3.656 ms
3 10gigabitethernet5-3.core1.nyc4.he.net (72.52.92.49) 10.069 ms 10.067 ms 10.056 ms
4 10gigabitethernet1-2.core1.lon1.he.net (72.52.92.242) 75.688 ms 75.684 ms 75.813 ms
5 10ge.linx.i3d.net (195.66.225.146) 76.491 ms 76.869 ms 76.468 ms
6 40ge-1-2.br3.smartdc.i3d.net (188.122.95.93) 76.819 ms 30ge-1-1.br2.smartdc.i3d.net (188.122.95.92) 76.463 ms 40ge-1-2.br3.smartdc.i3d.net (188.122.95.93) 78.798 ms
7 mirror.i3d.net (213.163.76.200) 77.404 ms 77.400 ms 77.593 ms
justin@waffle:~$ wget http://mirror.i3d.net/pub/debian-cd/6.0.7-live/i386/iso-hybrid/debian-live-6.0.7-i386-standard.iso
--2013-04-03 22:42:57-- http://mirror.i3d.net/pub/debian-cd/6.0.7-live/i386/iso-hybrid/debian-live-6.0.7-i386-standard.iso
Resolving mirror.i3d.net... 213.163.76.200, 2a00:1630:1:13d::13d
Connecting to mirror.i3d.net|213.163.76.200|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 295698432 (282M) [application/octet-stream]
Saving to: `debian-live-6.0.7-i386-standard.iso'
100%[================================================================================== >] 295,698,432 9.67M/s in 30s
2013-04-03 22:43:27 (9.38 MB/s) - `debian-live-6.0.7-i386-standard.iso' saved [295698432/295698432]
FINISHED --2013-04-03 22:43:27--
Downloaded: 1 files, 282M in 30s (9.38 MB/s)
from my home DSL with Start.ca: (messy traceroute thanks to Cogent)
traceroute mirror.i3d.net
traceroute to mirror.i3d.net (213.163.76.200), 64 hops max, 52 byte packets
1 dd-wrt (192.168.1.1) 0.404 ms 0.165 ms 0.181 ms
2 192.168.2.1 (192.168.2.1) 1.016 ms 0.677 ms 0.705 ms
3 64.140.112.15 (64.140.112.15) 15.145 ms 15.186 ms 14.949 ms
4 * * *
5 204.101.4.193 (204.101.4.193) 92.884 ms 14.719 ms 14.538 ms
6 bx6-chicago23_pos0-3-0-0.net.bell.ca (64.230.186.202) 35.915 ms
bx6-chicago23_pos0-2-0-0.net.bell.ca (64.230.186.198) 33.872 ms 32.415 ms
7 te4-1.ccr01.ord09.atlas.cogentco.com (154.54.11.29) 105.041 ms * *
8 te3-5.mag02.ord01.atlas.cogentco.com (154.54.29.193) 33.318 ms
te3-5.mag01.ord01.atlas.cogentco.com (154.54.29.189) 32.873 ms
te3-5.mag02.ord01.atlas.cogentco.com (154.54.29.193) 32.838 ms
9 te0-5-0-3.ccr21.ord01.atlas.cogentco.com (154.54.45.193) 33.236 ms 32.650 ms
te0-5-0-7.mpd22.ord01.atlas.cogentco.com (154.54.81.229) 33.050 ms
10 te0-2-0-5.ccr21.bos01.atlas.cogentco.com (154.54.43.198) 45.308 ms
te0-3-0-3.mpd21.yyz02.atlas.cogentco.com (154.54.42.10) 32.811 ms
te0-7-0-13.ccr21.yyz02.atlas.cogentco.com (154.54.28.2) 32.980 ms
11 te0-4-0-5.ccr21.ymq02.atlas.cogentco.com (154.54.43.218) 41.544 ms
te0-3-0-3.ccr22.ymq02.atlas.cogentco.com (154.54.25.30) 40.343 ms
te0-4-0-3.ccr22.lpl01.atlas.cogentco.com (154.54.44.190) 109.763 ms
12 te0-3-0-6.ccr21.lpl01.atlas.cogentco.com (154.54.6.142) 110.764 ms
te0-6-0-4.mpd21.ams03.atlas.cogentco.com (154.54.38.49) 118.333 ms
te0-5-0-4.ccr21.lpl01.atlas.cogentco.com (154.54.87.61) 110.744 ms
13 te0-6-0-2.mpd22.ams03.atlas.cogentco.com (130.117.49.66) 120.320 ms
te2-1.ccr01.rtm01.atlas.cogentco.com (130.117.48.234) 121.092 ms
te4-2.ccr01.rtm01.atlas.cogentco.com (154.54.63.122) 120.513 ms
14 te4-2.ccr01.rtm01.atlas.cogentco.com (154.54.63.122) 122.264 ms
te2-1.ccr01.rtm03.atlas.cogentco.com (154.54.62.130) 119.910 ms
te3-8.ccr01.rtm01.atlas.cogentco.com (154.54.63.114) 122.825 ms
15 149.14.14.10 (149.14.14.10) 118.114 ms
te2-1.ccr01.rtm03.atlas.cogentco.com (154.54.62.130) 121.805 ms
te2-2.ccr01.rtm03.atlas.cogentco.com (154.54.62.134) 122.559 ms
16 30ge-1-2.br2.smartdc.i3d.net (188.122.95.84) 126.986 ms
149.14.14.18 (149.14.14.18) 120.817 ms
149.6.110.2 (149.6.110.2) 120.687 ms
17 40ge-1-2.br3.smartdc.i3d.net (188.122.95.93) 126.378 ms
mirror.i3d.net (213.163.76.200) 119.742 ms
40ge-1-1.br3.smartdc.i3d.net (188.122.95.85) 120.467 ms
wget http://mirror.i3d.net/pub/debian-cd/6.0.7-live/i386/iso-hybrid/debian-live-6.0.7-i386-standard.iso
--2013-04-03 22:45:06-- http://mirror.i3d.net/pub/debian-cd/6.0.7-live/i386/iso-hybrid/debian-live-6.0.7-i386-standard.iso
Resolving mirror.i3d.net... 213.163.76.200, 2a00:1630:1:13d::13d
Connecting to mirror.i3d.net|213.163.76.200|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 295698432 (282M) [application/octet-stream]
Saving to: ‘debian-live-6.0.7-i386-standard.iso’
100%[================================================================================== >] 295,698,432 2.45MB/s in 2m 16s
2013-04-03 22:47:22 (2.08 MB/s) - ‘debian-live-6.0.7-i386-standard.iso’ saved [295698432/295698432]
FINISHED --2013-04-03 22:47:22--
Total wall clock time: 2m 16s
Downloaded: 1 files, 282M in 2m 16s (2.08 MB/s)
yes shaded, thank you for understanding what I was trying to say. I was hoping there would be some way TSI would improve this. Using TSI to stream european language tv shows is almost mpossible.
yes shaded, thank you for understanding what I was trying to say. I was hoping there would be some way TSI would improve this. Using TSI to stream european language tv shows is almost mpossible.
when I was with TSI i had a lot of issues with watching streams even from the US with twitch.tv.
Yeah, there are no excuses for having crappy transit, funny there are no comments from Teksavvy or Teksavvy fanboys...lol
If this was on rogers you'd see a fury of people dissing rogers like there is no tomorrow on the rogers forum. Goes to show Teksavvy still has a good reputation as an ISP but it can only get bad if issues like this continue.
I will be making an exit shortly also. I only use 50gigs a month at most and I pay for unlimited based on principal for a few years now. It's just a waste of money now and pretty frustrating and silly to use my neighbors wifi (who uses a competitor) to actually download something faster.
Well, 'nuff said, really, no? It was horrible on McNicoll before migration. Any better now?
quote:yes, please try from: 5pm - 11pm
Okay. I can hit 5.3 MB/s after migration from the former McNicoll POI right now, provided I'm downloading enough files. But the best I can get is 2.2MB/s on a single file.
Seems fine to me. But really, I should be testing around 9:30 p.m.
I had an open ticket from February until the migration in April on the McNicoll POI for horribly sucky congestion from approximately 9:30 p.m. until 11 p.m. EST (sometimes started much earlier though).
After migration to aggregated, I'm not noticing much of anything that's bugging me.
The original problem has to be POI congestion. raphaeld was on McNicoll too.
It will be interesting to see what happens after every POI migrates. I certainly hope congestion does not return.
it's not a server limit, i linked earlier in the thread a single download coming down at 95Mbit/sec. multiple connections at once is a good way to get through congestion.
well regardless, it seems to be quite a bit faster than previously mentioned (1-3Mbit/sec)?
I'm getting 2.3 MB/s right now with a single connection to a single file. And the OP was on the same POI that I was on, so chances are the situation has improved for the OP since the migration.
But I wouldn't expect to experience congestion at this time of night, locally, anyway.
Nexicom at 12:41 a.m. (on 45/4):
Local Toronto Speedtest results are usually poorest between 9:30 p.m. and 11 p.m. for me. I often get better results from St. Catharines and Oakville speedtest servers during those times.
traceroute to mirror.i3d.net (213.163.76.200), 30 hops max, 38 byte packets 1 10.124.158.129 (10.124.158.129) 9.560 ms 9.599 ms 10.585 ms 2 24.156.135.73 (24.156.135.73) 19.307 ms 111.546 ms 17.473 ms 3 69.63.248.201 (69.63.248.201) 18.230 ms 19.573 ms 22.893 ms 4 69.196.136.36 (69.196.136.36) 16.499 ms 18.198 ms 2120.ae1.bdr04.tor.packetflow.ca (69.196.136.68) 13.641 ms 5 10gigabitethernet1-2.core2.tor1.he.net (209.51.191.173) 20.014 ms 17.912 ms 13.238 ms 6 10gigabitethernet10-3.core1.nyc4.he.net (184.105.223.173) 23.675 ms 31.944 ms 26.025 ms 7 10gigabitethernet1-2.core1.lon1.he.net (72.52.92.242) 94.662 ms 101.177 ms 102.338 ms 8 10ge.linx.i3d.net (195.66.225.146) 102.334 ms 109.218 ms 101.820 ms 9 30ge-1-1.br2.smartdc.i3d.net (188.122.95.92) 449.932 ms 40ge-1-2.br3.smartdc.i3d.net (188.122.95.93) 112.676 ms 115.233 ms 10 mirror.i3d.net (213.163.76.200) 99.933 ms 98.967 ms 99.928 ms