dslreports logo
 
    All Forums Hot Topics Gallery
spc

spacer

Search Topic:
uniqs
9
share rss forum feed

neilb

join:2012-10-07
Toronto, ON
reply to MaynardKrebs

Re: Bloor phub - Terrible connection

I'm in Toronto and getting similar problems. I'm unable to download any sizeable files. I'm running a variety of mac, linux boxes, windows, boxes. All have the same issues.

My Rogers.com connection is relatively okay but I can't get any downloads from sites such as easynews. The network has been much worse than usual for around a week. I'm using the CISCO modem and a separate wireless bridge.

$ traceroute rogers.comtraceroute to rogers.com (207.245.252.27), 30 hops max, 40 byte packets
1 * * *
2 24.156.150.165 (24.156.150.165) 11.024 ms 12.599 ms 11.814 ms
3 so-4-0-0.gw02.wlfdle.phub.net.cable.rogers.com (66.185.82.97) 12.991 ms 11.325 ms 11.793 ms
4 pos-0-0-0.gw02.abcgy.phub.net.cable.rogers.com (24.153.7.118) 49.906 ms 9.336 ms 12.501 ms
5 ge10-1.gwy2-tor.bb.allstream.net (216.191.65.129) 9.958 ms 11.868 ms ge10-0.gwy2-tor.bb.allstream.net (216.191.65.121) 11.428 ms
6 10ge4-11.hcap9-tor.bb.allstream.net (199.212.169.202) 10.142 ms 11.989 ms 12.176 ms
7 66-46-129-178.dedicated.allstream.net (66.46.129.178) 12.822 ms 17.632 ms 11.828 ms
8 * * *
9 * * *
10 * * *
11 * *

etc

$ traceroute downloads.easynews.com
traceroute to downloads.easynews.com (66.152.109.61), 30 hops max, 40 byte packets
1 * * *
2 69.63.243.97 (69.63.243.97) 10.602 ms 11.758 ms 7.845 ms
3 69.63.250.21 (69.63.250.21) 10.288 ms 12.386 ms 10.979 ms
4 66.185.83.62 (66.185.83.62) 25.882 ms 25.842 ms 28.119 ms
5 te1-5.mpd01.iad01.atlas.cogentco.com (154.54.12.89) 29.833 ms 29.970 ms 29.435 ms
6 te0-0-0-6.ccr21.iad02.atlas.cogentco.com (154.54.31.221) 30.009 ms 28.778 ms 29.837 ms
7 te0-3-0-5.ccr21.dca01.atlas.cogentco.com (154.54.2.49) 29.896 ms te0-1-0-5.ccr21.dca01.atlas.cogentco.com (154.54.26.129) 29.854 ms te0-3-0-1.ccr21.dca01.atlas.cogentco.com (154.54.30.121) 29.185 ms
8 te0-1-0-5.mpd22.dca01.atlas.cogentco.com (154.54.26.121) 30.483 ms te0-7-0-2.ccr21.jfk02.atlas.cogentco.com (154.54.25.237) 31.294 ms te0-0-0-2.ccr21.jfk02.atlas.cogentco.com (66.28.4.125) 29.773 ms
9 te0-6-0-12.mpd22.jfk02.atlas.cogentco.com (154.54.25.149) 30.582 ms 29.707 ms te0-7-0-12.mpd22.jfk02.atlas.cogentco.com (154.54.7.1) 29.502 ms
10 te3-3.ccr01.jfk01.atlas.cogentco.com (154.54.1.210) 28.757 ms 29.082 ms te9-8.ccr01.jfk01.atlas.cogentco.com (154.54.40.29) 29.364 ms
11 te8-2.ccr01.alb02.atlas.cogentco.com (154.54.43.5) 32.091 ms te7-2.ccr01.alb02.atlas.cogentco.com (154.54.42.141) 33.536 ms te8-2.ccr01.alb02.atlas.cogentco.com (154.54.43.5) 33.076 ms
12 38.104.52.10 (38.104.52.10) 33.975 ms 33.806 ms 38.802 ms
13 vl107.es1b.alb1.tvc-ip.com (66.109.38.33) 32.718 ms 32.495 ms 32.075 ms
14 ge-1-1.es1.alb9.tvc-ip.com (66.109.38.182) 31.682 ms 33.020 ms 31.852 ms
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 *


jmck
formerly 'shaded'

join:2010-10-02
Ottawa, ON
those two network are simply blocking/dropping ICMP/UDP responses for some dumb and prehistoric reason. it would be like installing a moate around your house today to prevent someone from breaking in.


Tenebre81

@rogers.com
There is no problem with any of your modems, splitters, etc. As of a few weeks ago, Rogers internet service has just been wonky. Naturally, they will NEVER admit this to you. EVER. They will try and stall you and take you through the usual troubleshooting routines ('power cycle' the modem, get a new modem, etc etc). Anything to avoid the real issue:

Rogers internet just STINKS currently.