dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
223
share rss forum feed


outlaw2000

join:2000-12-18
Guelph, ON

Man wtf is going on with rogers now??

The past few days I've noticed some real bs regarding speeds and pings. After the cap im lucky to get 1meg/180 which we all have to take up the ass but this goes beyond that. Every game server was like 2000ms and my speed test showed 100/100 roughly. I know some other rogers peeps were getting some really bad pings. Its funny how just rogers peeps were effected by the prob mostly ,yet rogers says its not their problem.



skillton

join:2000-09-14
Scarborough, ON

lots of probs @ teleglobe... or rogers routing... alot of the routing after teleglobe is being done thru sprint and the conenction between sprint and teleglobe is very overloaded



rAfChOw
Premium
join:2001-03-19
Toronto, ON
reply to outlaw2000

Let's make it simple: Rogers is ignoring their customers by not caring what they think because they have many sources of income and they also have a cable monopoly. Greed has overcome once again.



mau108
Mau
Premium
join:2001-10-07
Thornhill, ON
Reviews:
·TekSavvy Cable
reply to outlaw2000

No sprint here

over a maximum of 30 hops:

1 32 ms 42 ms 60 ms mcr2.mtth.phub.net.cable.rogers.com [24.100.
]
2 61 ms 79 ms 41 ms gw01.mtth.phub.net.cable.rogers.com [24.112.
33]
3 52 ms 30 ms 35 ms gw01.mtun.phub.net.cable.rogers.com [66.185.
34]
4 118 ms 34 ms 33 ms gw01.esna.phub.net.cable.rogers.com [66.185.
42]
5 186 ms 37 ms 35 ms gw02.mtnk.phub.net.cable.rogers.com [66.185.
89]
6 125 ms 150 ms 36 ms gw01.mtnk.phub.net.cable.rogers.com [66.185.
69]
7 202 ms 36 ms 34 ms gw02.wlfdle.phub.net.cable.rogers.com [66.18
.145]
8 39 ms 29 ms 39 ms 66.198.40.5
9 338 ms 34 ms 34 ms if-3-0.core1.Chicago3.teleglobe.net [63.243.
2]
10 174 ms 125 ms 74 ms POS5-0.BR5.CHI2.ALTER.NET [204.255.169.17]
11 206 ms 72 ms 73 ms 0.so-6-0-0.XL1.CHI2.ALTER.NET [152.63.68.198
12 70 ms 66 ms 70 ms 0.so-1-0-0.TL1.CHI2.ALTER.NET [152.63.67.105
13 85 ms 68 ms 94 ms 0.so-7-0-0.TL1.NYC9.ALTER.NET [152.63.146.54
14 57 ms 60 ms 72 ms 0.so-3-0-0.XL1.NYC1.ALTER.NET [152.63.27.29]
15 152 ms 74 ms 71 ms 0.so-0-0-0.XR1.NYC1.ALTER.NET [152.63.19.85]
16 395 ms 43 ms 70 ms 507.ATM6-0.GW7.NYC1.ALTER.NET [152.63.25.81]
17 99 ms 69 ms 81 ms nac-nyc-gw1.customer.alter.net [157.130.9.14
18 221 ms 77 ms 173 ms www.dslreports.com [209.123.109.175]
--
...:::M.A.U.1.0.8:::...



Exit
Premium,ExMod 2002
join:2001-04-10
Canada
reply to outlaw2000

When I talked to one of the techs yesterday about the ping problem at sprintlink he said they knew about it but were doing nothing to fix it. He said Rogers was hoping they would fix it themselves or that the problem would somehow just go away. Figure that one out.

Steve
--
18.98Ghz of Cancer killing power commin at yah.



sbrook
Premium,Mod
join:2001-12-14
Ottawa
kudos:13

More to the point, apart from complain to teleglobe there's not a lot they can do anyway.



paddler64

join:2002-05-07
Nirvana
reply to Exit

said by mrspec3:
When I talked to one of the techs yesterday about the ping problem at sprintlink he said they knew about it but were doing nothing to fix it. He said Rogers was hoping they would fix it themselves or that the problem would somehow just go away. Figure that one out.

Ahhh The Ostrich Method of troubleshooting


skillton

join:2000-09-14
Scarborough, ON

reply to outlaw2000

Tracing route to dslreports.com [209.123.109.175]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms skillton.mshome.net [192.168.0.1]
2 8 ms 9 ms 9 ms 10.55.56.1
3 8 ms 9 ms 7 ms gw01.mtag.phub.net.cable.rogers.com [66.185.89.9
]
4 9 ms 10 ms 8 ms gw01.ym.phub.net.cable.rogers.com [66.185.81.162
]
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 22 ms 22 ms 23 ms 66.198.40.1
11 24 ms 24 ms 21 ms if-3-0.core1.Chicago3.teleglobe.net [63.243.177.
2]
12 48 ms 47 ms 48 ms 204.255.169.17
13 48 ms 47 ms 47 ms 0.so-6-0-0.XL1.CHI2.ALTER.NET [152.63.68.198]
14 49 ms 47 ms 47 ms 0.so-2-0-0.TL1.CHI2.ALTER.NET [152.63.67.125]
15 44 ms 45 ms 46 ms 0.so-2-3-0.TL1.NYC8.ALTER.NET [146.188.163.170]

16 44 ms 47 ms 45 ms 0.so-3-0-0.XL1.NYC1.ALTER.NET [152.63.27.29]
17 45 ms 46 ms 45 ms 0.so-0-0-0.XR1.NYC1.ALTER.NET [152.63.19.85]
18 46 ms 46 ms 45 ms 507.ATM7-0.GW7.NYC1.ALTER.NET [152.63.25.73]
19 47 ms 46 ms 47 ms nac-nyc-gw1.customer.alter.net [157.130.9.142]
20 50 ms 47 ms 48 ms www.dslreports.com [209.123.109.175]
fixed now
[text was edited by author 2002-07-03 18:02:17]



outlaw2000

join:2000-12-18
Guelph, ON

Well looks like its still screwed here..not as much packetloss right now but its 1am. Can somebody look at this test »/quality/nil/800484



skillton

join:2000-09-14
Scarborough, ON
reply to outlaw2000

the line quality test is pretty good...