dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
1053
share rss forum feed


h5sm2

@rogers.com

[Express] Ottawa - Rogers High Latency

Is anyone in Ottawa having latency issues? I've tried online gaming lately, and have been having constant connection issues over the last couple weeks.

When I run a tracert, my 2nd hop seems to be crapping out and taking up to 700ms to respond. From what I read, this should be the Rogers CTMS right? If so, would everyone have the same issues? I'm not sure if the issue is hardware on my end, or a network issue. Here are some tracerts to google.ca

Tracing route to google.ca [173.194.77.94]
over a maximum of 30 hops:
 
  1     1 ms     2 ms    1 ms  192.168.1.1
  2   115 ms   117 ms   216 ms  7.48.64.1
  3   298 ms   223 ms    75 ms  69.63.242.13
  4    94 ms   166 ms   263 ms  XE6-1-2.gw02.ym.phub.net.cable.rogers.com [69.63
.248.153]
  5   618 ms   476 ms   232 ms  69.63.248.145
  6    73 ms    70 ms    27 ms  72.14.216.189
  7   194 ms   284 ms   291 ms  209.85.254.128
  8   222 ms   133 ms   147 ms  72.14.237.130
  9   400 ms   559 ms   605 ms  72.14.239.15
 10   100 ms   172 ms    81 ms  216.239.46.59
 11     *        *        *     Request timed out.
 12   130 ms   213 ms   173 ms  ob-in-f94.1e100.net [173.194.77.94]
 
Trace complete.
 

Tracing route to google.ca [173.194.77.94]
over a maximum of 30 hops:
 
  1     1 ms    1 ms    1 ms  192.168.1.1
  2    21 ms     8 ms     8 ms  7.48.64.1
  3   146 ms    75 ms    14 ms  69.63.242.13
  4   217 ms   287 ms   383 ms  XE6-1-2.gw02.ym.phub.net.cable.rogers.com [69.63
.248.153]
  5   206 ms   143 ms   194 ms  69.63.248.145
  6    26 ms    54 ms    26 ms  72.14.216.189
  7   259 ms   271 ms   243 ms  209.85.254.128
  8    56 ms    27 ms    30 ms  72.14.237.130
  9   359 ms   379 ms   295 ms  72.14.239.15
 10    44 ms    48 ms    41 ms  216.239.46.61
 11     *        *        *     Request timed out.
 12   105 ms    46 ms   161 ms  ob-in-f94.1e100.net [173.194.77.94]
 
Trace complete.
 

Tracing route to google.ca [173.194.77.94]
over a maximum of 30 hops:
 
  1     1 ms     2 ms    1 ms  192.168.1.1
  2   245 ms   346 ms   429 ms  7.48.64.1
  3   135 ms    81 ms   238 ms  69.63.242.13
  4   124 ms   179 ms   252 ms  XE6-1-2.gw02.ym.phub.net.cable.rogers.com [69.63
.248.153]
  5   334 ms   255 ms   177 ms  69.63.248.145
  6    77 ms    56 ms    32 ms  72.14.216.189
  7   273 ms   307 ms   416 ms  209.85.254.128
  8   309 ms   217 ms   287 ms  72.14.237.130
  9    55 ms   135 ms   192 ms  72.14.239.15
 10   513 ms   401 ms   213 ms  216.239.46.59
 11     *        *        *     Request timed out.
 12   332 ms   235 ms   118 ms  ob-in-f94.1e100.net [173.194.77.94]
 
Trace complete.
 


mozerd
Light Will Pierce The Darkness
Premium,MVM
join:2004-04-23
Nepean, ON

I'm in the Greenbank/Craig Henry Area and Yes its been all over the map this AM



mlerner
Premium
join:2000-11-25
Nepean, ON
kudos:5
reply to h5sm2

No problems here (Greenbank/Banner) though I am on a different node and CMTS. But the 2nd hop is not the CMTS, rather the local node in your area which appears to have severe latency so there's your problem.



h5sm2

@sdc-dsc.gc.ca

I'm in the Parkdale/Wellington Area. So nothing I can do but call Rogers and get them to look at what's up in my area?



Alexpandian

@rogers.com

The 2nd hope is not ur CMTS ip address, its an ip address that rogers assigns to each modem on their network that you cant access that is used to access into their customers modems, you probably have an issue with the modem it self, try doing factory reset on you modem and see if that changes anything, if it doesn't work best thing to do is to exchange the modem.



Anon1

@teksavvy.com
reply to h5sm2

The high latency could also be caused by the upstream being saturated. Anyone doing uploads at the time (dropbox etc)?



DS256
Premium
join:2003-10-25
Markham, ON
reply to h5sm2

May not be related but last week I had high latencies on the 1st and subsequent hops through Rogers internal routers before hitting the Internet last week just before that large outage. Your experience seems to imply that Rogers has an internal routing issues.


craquer

join:2012-12-16
Orleans, ON

3 edits
reply to h5sm2

Out here in Orleans it's been marginal to terrible since 16-Dec-2012. Ping times to google.ca vary from ~30ms to ~400ms, to the old "Request timed out". Traceroute over here shows similar times to yours. Time to give Bell a try?

Tracing route to www.google.ca [173.194.75.94]
over a maximum of 30 hops:

1 * * * Request timed out.
2 109 ms 91 ms 15 ms 69.63.255.213
3 * 137 ms * so-4-1-0.gw02.ym.phub.net.cable.rog
85.83.198]
4 103 ms 39 ms 99 ms 69.63.250.97
5 29 ms 156 ms 262 ms 72.14.216.14



mlerner
Premium
join:2000-11-25
Nepean, ON
kudos:5

December 16? You might want to get your cable signal checked out first especially if your connection drops in and out. Even Rogers doesn't let node issues go on that long.


craquer

join:2012-12-16
Orleans, ON

Tried, got the usual "the problem exists in your house" "reboot your PC" "reboot your modem" "ensure the cable modem is on a dedicated power outlet" etc.

Had to tell them that the neighbour also experiences poor connectivity, irregardless if our connections are wired or wireless. It was just last Friday that they finally changed their response from "the problem exists in your house" to "it's an area problem".


craquer

join:2012-12-16
Orleans, ON
reply to h5sm2

Message on the answering machine stated your problem has been resolved... looks like it might be back to normal, but there's probably not a lot of congestion at 1532hrs...


Tracing route to www.google.ca [173.194.64.94]
over a maximum of 30 hops:

1 * * * Request timed out.
2 18 ms 26 ms 12 ms 69.63.255.213
3 19 ms 21 ms 34 ms 24.156.157.177
4 20 ms 44 ms 16 ms 24.153.4.150
5 17 ms 114 ms 19 ms 72.14.216.14

Ping statistics for 173.194.64.94:
Packets: Sent = 184, Received = 184, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 39ms, Maximum = 620ms, Average = 57ms