cancel
Showing results for 
Search instead for 
Did you mean: 

Brutal latency/ping Recently

t27c
I Plan to Stick Around

I am wired, with the gigabit package and all of the sudden have gotten constant ping spikes for over the last few days. I haven't been able to play any games online because the crazy ping spikes and latency make it completely unplayable. My speeds are what they are expected to be, no issues there. I have tried hard wiring straight into the modem but alas, the issue still persists. I have tried switching cables, power cycling my devices, factory resetting my devices. The issue still persists. I have called and contacted Rogers multiple times and they say everything seems fine on their end. But still, the issue persists and is steady. resulting in me not able to use any of my gaming devices due to the brutal and constant ping spikes. It's frustrating paying over $100 a month for internet I cant use for the things I want it for. Any help or suggestions are welcomed and appreciated. Thank you

 

*** Edited Labels ***

956 REPLIES 956

Re: Brutal latency/ping Recently

super_robot
I Plan to Stick Around

@GMX 

 

You'd expect this from a 3rd party re seller at the mercy of BELL/Rogers. But for the main entity to have issues for this long and so widespread is just baffling.

 

 

Re: Brutal latency/ping Recently

super_robot
I Plan to Stick Around

Looks like it's only getting worse

 

Pinging www.google.ca [172.217.164.227] with 32 bytes of data:
Reply from 172.217.164.227: bytes=32 time=31ms TTL=55
Reply from 172.217.164.227: bytes=32 time=60ms TTL=55
Reply from 172.217.164.227: bytes=32 time=39ms TTL=55
Reply from 172.217.164.227: bytes=32 time=45ms TTL=55
Reply from 172.217.164.227: bytes=32 time=21ms TTL=55
Reply from 172.217.164.227: bytes=32 time=50ms TTL=55
Reply from 172.217.164.227: bytes=32 time=49ms TTL=55
Reply from 172.217.164.227: bytes=32 time=23ms TTL=55
Reply from 172.217.164.227: bytes=32 time=44ms TTL=55
Reply from 172.217.164.227: bytes=32 time=33ms TTL=55
Reply from 172.217.164.227: bytes=32 time=30ms TTL=55
Reply from 172.217.164.227: bytes=32 time=23ms TTL=55
Reply from 172.217.164.227: bytes=32 time=30ms TTL=55
Reply from 172.217.164.227: bytes=32 time=36ms TTL=55
Reply from 172.217.164.227: bytes=32 time=28ms TTL=55
Reply from 172.217.164.227: bytes=32 time=107ms TTL=55
Reply from 172.217.164.227: bytes=32 time=132ms TTL=55
Reply from 172.217.164.227: bytes=32 time=354ms TTL=55
Reply from 172.217.164.227: bytes=32 time=488ms TTL=55
Reply from 172.217.164.227: bytes=32 time=445ms TTL=55
Request timed out.
Reply from 172.217.164.227: bytes=32 time=138ms TTL=55
Reply from 172.217.164.227: bytes=32 time=67ms TTL=55
Reply from 172.217.164.227: bytes=32 time=29ms TTL=55
Reply from 172.217.164.227: bytes=32 time=36ms TTL=55

Ping statistics for 172.217.164.227:
Packets: Sent = 25, Received = 24, Lost = 1 (4% loss),
Approximate round trip times in milli-seconds:
Minimum = 21ms, Maximum = 488ms, Average = 97ms

Re: Brutal latency/ping Recently

Shahin6470
I Plan to Stick Around

Not sure what else to do with Rogers Internet. Hear me out on this cause this has been a 6-8 months back and forth argument with Rogers Tech Support. Someone is not understanding whats happening here. And Rogers tech support don't follow up to see if everything is fine after couple days. Maybe I can get my message across from here

 

I been having Internet issues for the past 6-8 months. I have 1 Gbps internet package for a while now. Recently upgraded to Ignite TV as well. Over the past 6-8 months, I had 3 Techs and many MANY hours of talking and chatting with Rogers Tech Support. They come in, they do a couple speed test, then they say everything is fine, Bye. 

I don't have consistent internet connection. Simple as that. I live in a house that has A LOT of devices connected to the network. I have a Switch board that has wired connections running to all the rooms throughout the house that is connected to the Rogers modem. But this isn't a switch board program, cause I tried connecting my laptop directly to the Rogers modem, and same result. Running a 4 sec ping test is not enough. I ran a Ping test for 1-2 hours just TODAY, and here is the result

Ping statistics for 172.217.164.228: Packets: Sent = 4313, Received = 4189, Lost = 124 (2% loss), Approximate round trip times in milli-seconds: Minimum = 5ms, Maximum = 339ms, Average = 21ms

124 times that my internet got disconnected. And Ping reaching 339?? How can I prove to Rogers Tech Support that? I can't use VPN, I cant use Video Conferencing, and I cant play video games. Please someone help me before I lose my mind.

Re: Brutal latency/ping Recently

@Shahin6470  ok, I'll bite.....  First question, can you explain how the switch board is wired?   Maybe post a photo so I understand what it looks like?  

 

Using a direct connection to the modem via ethernet from the laptop, can you run a ping test to the Cable Modem Termination System (CMTS).  To do that run a trace to anywhere, google for example:

 

tracert -4 www.google.ca

 

If your modem is running in Gateway mode or the modem is in Bridge mode with a router behind it, the first hop IP address is the modem or router, depending on your equipment installation.  The second hop IP address is the CMTS.  Ping the CMTS IP address using the following command:

 

Ping -n 3600 xxx.xxx.xxx.xxx       where xxx.xxx.xxx.xxx is that second hop IP address

 

That will run a ping test for an hour.  What we're looking for are any timeouts which would indicate a cable or connector issue.  The path for the ping is:

 

1.  from the pc/laptop to the modem via ethernet: then

2.  to the external demarcation point outside of the home via RG-6 cable; then

3.  to the local tap that connects you and your immediate neighbours to the network via RG-6 cable: then

4.  to the neighbourhood node via hardline cable; then

5.  to the CMTS via fibre from the neighbourhood node.

 

Usually if there is a disconnect issue, the problem is with the external cable run from the external demarcation point to the local tap, but, you can end up with problems at the local tap or enroute to the neighbourhood node. So, the ping test would hopefully indicate whether or not there was a disconnect issue in that section of the path from the modem to the neighbourhood node which is all copper cable.  Potentially there could be an issue enroute to the CMTS from the neighbourhood node but that's a fibre run and any faults would affect all of your neighbourhood, so Rogers would certainly be seeing a lot of complaints if that was the case.  

 

When that ping test is done, copy the command box results and paste then into a text editor like notepad.  To do that right click on the top title line of the Command Box.  Select Edit ... Select All.  Then right click again on the top title bar and select Edit .... Copy.  Then paste that into a text editor.  At that point copy just the bottom results portion and paste that into a post.  The question of course is whether or not there is an external cable and/or connector issue that doesn't show up in the modems signal levels.  

 

Ok, lets start with that and see where it goes, so, looking for a "switch board" explanation and photo please, and ping test results from a ping test to the CMTS. 

 

Edit:  Additional food for thought.  I know that you've had techs to your home, but, if you have the time and patience can you post the signal levels from the modem.   To to that please follow the instructions from @mozerd  and myself in the following thread to copy the signal levels and paste them into a post.

 

https://www.dslreports.com/forum/r32715001-Rogers-BlueCurve-Gateway-Issues

 

It never hurts to have a look at the signal levels to see whats up, if anything.

 



Re: Brutal latency/ping Recently

super_robot
I Plan to Stick Around

@Shahin6470 

 

Rogers' cable network has been running poorly for some time and COVID19 and everyone at home just magnified these issues.

 

Assuming I read correctly and that you ran your tests directly connected to them modem...

 

Your situation is the same as people all across the province.. high latency/packet loss/crippled upload speed. The situation is the same for Rogers cable resellers (tekksavy etc.). 

 

 

Just stop wasting your time troubleshooting, there's nothing that can be fixed on your end. It's 100000% on Rogers' end and what they do from here is entirely up to them. Switch to BELL if it is available in your area.

 

The issue is massive and widespread. Only people that game or are tech savy will notice and see the issue. Your average user that watches Netflix won't notice or care. 

Re: Brutal latency/ping Recently

Well, not that I'm going to argue with what you're saying, but, a ping test to the CMTS should rule out or indicate whether a local cable problem existed.  Beyond that, with no evident local cable issues, then yes, I agree with the comments on the network situation.  However, as usual, one has to do some amount of troubleshooting before making the leap to say, its all the networks fault. 



Re: Brutal latency/ping Recently

Shahin6470
I Plan to Stick Around

doing the CMTS test right now. Will let you know in a hour

Re: Brutal latency/ping Recently

Shahin6470
I Plan to Stick Around

Oh man. I thought that was only my house. Nothing is worst than 2-3 am internet outage. I been getting it over the past couple weeks. 

Re: Brutal latency/ping Recently

-G-
Resident Expert
Resident Expert

@Shahin6470 wrote:

Ping statistics for 172.217.164.228: Packets: Sent = 4313, Received = 4189, Lost = 124 (2% loss), Approximate round trip times in milli-seconds: Minimum = 5ms, Maximum = 339ms, Average = 21ms


I don't find those numbers surprising these days.  I have seen it better and I have seen it worse.  If you can replicate those numbers with your computer directly connected to the Rogers gateway, then that is not great.

 

124 times that my internet got disconnected. And Ping reaching 339?? How can I prove to Rogers Tech Support that?


That "124" is packet loss, not your Internet disconnecting.  Packet loss can happen due to load, or even if have QoS enabled on a network device and some network traffic gets dropped intentionally.

 

With network latency being all over the map, that's the topic at the heart of the thread.  When too much traffic gets backed up at the local node, that too can result in packet loss.

 

Pinging an Internet host repeatedly will give you an indication of general network health along a particular path, and any network devices on that path can contribute to latency and packet loss.

 

Pinging your local modem/gateway should produce consistently low latency and no packet loss.  If you see problems with this test, you have local (LAN/WiFi) problems that you need to address before reporting "network problems" to Rogers.

 

If you have no local issues, pinging your CMTS router (ideally while simultaneously performing other ping tests) will show whether the local node is causing latency and/or packet loss.

 

Not sure what else to do with Rogers Internet. Hear me out on this cause this has been a 6-8 months back and forth argument with Rogers Tech Support. Someone is not understanding whats happening here. And Rogers tech support don't follow up to see if everything is fine after couple days. Maybe I can get my message across from here

 

How can I prove to Rogers Tech Support that? I can't use VPN, I cant use Video Conferencing, and I cant play video games. Please someone help me before I lose my mind.


I can't really say what could have started happening 6-8 months ago for you.  Most of the people here started seeing a degradation in their Internet service starting at the beginning of this year.

 

I ran a short ping test while I was typing this with the following results:

 

--- 172.217.164.228 ping statistics ---
600 packets transmitted, 600 received, 0% packet loss, time 599827ms
rtt min/avg/max/mdev = 8.619/14.891/59.903/6.693 ms

 

I don't see the the same extremes that you do, but I also did not perform this test at a peak time of day.  Regardless, the RTTs are not consistent... and the pings to my CMTS router show much higher latency, which is also indicative that it is under load and likely causing the jitter that we are seeing.

 

--- CMTS Router ping statistics ---
600 packets transmitted, 600 received, 0% packet loss, time 599807ms
rtt min/avg/max/mdev = 5.596/37.410/194.882/27.102 ms

 

Right now, these network conditions are not breaking Ignite TV but they are a royal pain for gamers and for anybody working from home using a remote desktop.

 

I don't know what to say or what we can expect them to say but Rogers is in a pickle.  If they confirm that network conditions are less than ideal, customers will demand compensation and that will cost them money, and possibly customers, and upset their shareholders.  If Rogers dispatches tech after tech for problems that are beyond their ability to fix, it will cost them money and irritate their customers as well.  They need to implement a fix, now, and that too could cost significant money, especially if it delays other projects.  Right now, they are not saying anything... and some customers are at their breaking point.  Hopefully this will get fixed soon.

Re: Brutal latency/ping Recently

Marando
I Plan to Stick Around

@-G-  Agreed!

Re: Brutal latency/ping Recently

Shahin6470
I Plan to Stick Around

Bridge Mode: Disable

tracert -4 www.google.com

Tracing route to www.google.com [172.217.1.4]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  -
  2    30 ms    13 ms    30 ms  -
  3    29 ms    21 ms    42 ms  -
  4    17 ms    21 ms    12 ms  -
  5    16 ms    20 ms    12 ms  -
  6    19 ms    19 ms    21 ms  -
  7    72 ms   104 ms    24 ms  -
  8    18 ms    18 ms    17 ms  -
  9    15 ms    17 ms    13 ms  -

 

Results for my CMTS:

Ping statistics for -:
    Packets: Sent = 3600, Received = 3496, Lost = 104 (2% loss),
Approximate round trip times in milli-seconds:
    Minimum = 5ms, Maximum = 602ms, Average = 25ms

 I understand that people are in a much worse condition then I am, but stuff I do are sensitive. Even that 1 sec of being disconnected makes everything crash. 

IndexLock StatusFrequencySNRPower LevelModulation
Downstream
Channel Bonding Value
23
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
24
25
26
27
28
29
30
31
32
33
 
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
693 MHz
279 MHz
849 MHz
855 MHz
861 MHz
579 MHz
585 MHz
591 MHz
597 MHz
603 MHz
609 MHz
615 MHz
621 MHz
633 MHz
639 MHz
645 MHz
651 MHz
657 MHz
663 MHz
669 MHz
675 MHz
681 MHz
687 MHz
699 MHz
705 MHz
711 MHz
717 MHz
723 MHz
825 MHz
831 MHz
837 MHz
843 MHz
350 MHz
275600000
37.8 dB
42.2 dB
40.7 dB
40.4 dB
40.3 dB
42.9 dB
42.8 dB
42.4 dB
42.5 dB
42.2 dB
41.9 dB
41.7 dB
41.6 dB
40.8 dB
40.6 dB
40.4 dB
40.1 dB
39.7 dB
39.1 dB
38.8 dB
36.8 dB
37.9 dB
37.7 dB
37.9 dB
38.3 dB
38.4 dB
38.6 dB
39.1 dB
41.3 dB
41.1 dB
41.1 dB
41.0 dB
0.0 dB
NA
-10.7 dBmV
-2.6 dBmV
-4.9 dBmV
-5.1 dBmV
-5.5 dBmV
-4.0 dBmV
-4.3 dBmV
-4.7 dBmV
-4.6 dBmV
-5.0 dBmV
-5.6 dBmV
-5.9 dBmV
-6.2 dBmV
-7.2 dBmV
-7.5 dBmV
-7.7 dBmV
-8.1 dBmV
-8.6 dBmV
-9.2 dBmV
-9.7 dBmV
-10.2 dBmV
-10.7 dBmV
-10.5 dBmV
-10.4 dBmV
-9.8 dBmV
-9.7 dBmV
-9.3 dBmV
-8.7 dBmV
-4.3 dBmV
-4.3 dBmV
-4.4 dBmV
-4.4 dBmV
-2.5 dBmV
NA
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
OFDM
OFDM
IndexLock StatusFrequencySymbol RatePower LevelModulationChannel Type
Upstream
Channel Bonding Value
1
2
3
4
Locked
Locked
Locked
Locked
22 MHz
25 MHz
30 MHz
36 MHz
2560
2560
5120
5120
41.3 dBmV
41.8 dBmV
42.3 dBmV
42.3 dBmV
QAM
QAM
QAM
QAM
TDMA_AND_ATDMA
TDMA_AND_ATDMA
ATDMA
ATDMA

Re: Brutal latency/ping Recently

super_robot
I Plan to Stick Around

@-G- 

 

"I don't know what to say or what we can expect them to say but Rogers is in a pickle.  If they confirm that network conditions are less than ideal, customers will demand compensation and that will cost them money, and possibly customers, and upset their shareholders.  If Rogers dispatches tech after tech for problems that are beyond their ability to fix, it will cost them money and irritate their customers as well.  They need to implement a fix, now, and that too could cost significant money, especially if it delays other projects.  Right now, they are not saying anything... and some customers are at their breaking point.  Hopefully this will get fixed soon."

 

 

 

You nailed it.

 

What I find most mind boggling is that it's happening with Rogers... one of the two main ISP. 

 

I'd expect these delays, lack of information or ability to fix things if I was dealing with a reseller... It's really concerning.

Re: Brutal latency/ping Recently

chemical1
I Plan to Stick Around

This is pathetic.  Fix the problem.  Call in and just get the run around, everything is fine here, checked your neighborhood no issues modem fine signals good bla bla.  I am online gaming and the admin is questioning me why my ping is jumping around like mad.  I say Canadian internet.

 

FIX THIS !

Re: Brutal latency/ping Recently

herrshaun
I Plan to Stick Around

So refresh my memory. If we do a traceroute to say, google.com, note the hops, ping them all individually and they're all giving back high pings, is this indicative of a problem further up the chain, or closer to us?

Re: Brutal latency/ping Recently

super_robot
I Plan to Stick Around

Anyone else seeing tighter average latency?

 

I feel like the low's aren't as low but overall the ping times are more grouped up.

 

My lowest to google is no longer 10ms but rather 30ms but my highs are no longer 100ms+ but ~50ms.

 

Minimum = 29ms, Maximum = 52ms, Average = 35ms

 

 

Almost as if some speed was traded for consistency. 

Re: Brutal latency/ping Recently

t27c
I Plan to Stick Around
For the last week it’s been pretty good for me. I have the odd ping at 60ms but for the most part it’s low and steady. Could just use a little more consistency although I will definitely take it considering my internet has been unplayable for the past 5 months with awful ping times. Now it’s at least playable and not rage inducing

Re: Brutal latency/ping Recently

super_robot
I Plan to Stick Around

andddddddddddd we're back with the high latency and packet loss

 

 

Packets: Sent = 214, Received = 213, Lost = 1 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 168ms, Average = 56ms

 

 

Reply from 172.217.7.195: bytes=32 time=46ms TTL=51
Reply from 172.217.7.195: bytes=32 time=43ms TTL=51
Reply from 172.217.7.195: bytes=32 time=36ms TTL=51
Reply from 172.217.7.195: bytes=32 time=102ms TTL=51
Reply from 172.217.7.195: bytes=32 time=42ms TTL=51
Reply from 172.217.7.195: bytes=32 time=120ms TTL=51
Reply from 172.217.7.195: bytes=32 time=116ms TTL=51
Reply from 172.217.7.195: bytes=32 time=38ms TTL=51
Reply from 172.217.7.195: bytes=32 time=49ms TTL=51
Reply from 172.217.7.195: bytes=32 time=72ms TTL=51

 

Make your pick for which hop will be troublesome...

 

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

1 * * * Request timed out.
2 27 ms 38 ms 29 ms ***.***.***.***
3 35 ms 87 ms 22 ms 8082-dgw02.etob.rmgt.net.rogers.com [67.231.220.37]
4 57 ms 15 ms 163 ms 0-15-0-6-cgw01.bloor.rmgt.net.rogers.com [209.148.232.141]
5 93 ms 38 ms 17 ms 209.148.235.30

 

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

1 * * * Request timed out.
2 72 ms 24 ms 28 ms ***.***.***.***
3 17 ms 25 ms 22 ms 8082-dgw02.etob.rmgt.net.rogers.com [67.231.220.37]
4 14 ms 17 ms 13 ms 0-15-0-6-cgw01.bloor.rmgt.net.rogers.com [209.148.232.141]
5 93 ms 18 ms 16 ms 209.148.235.30

 

 

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

1 1 ms 1 ms <1 ms INTEL_CE_LINUX [192.168.0.1]
2 108 ms 25 ms 17 ms ***.***.***.***
3 24 ms 22 ms 15 ms 8082-dgw02.etob.rmgt.net.rogers.com [67.231.220.37]
4 24 ms 16 ms 14 ms 0-15-0-6-cgw01.bloor.rmgt.net.rogers.com [209.148.232.141]
5 19 ms 23 ms 14 ms 209.148.235.30

Re: Brutal latency/ping Recently

AngryChicken
I Plan to Stick Around
I've put in a ticket with Rogers for here in Osgoode (rural Ottawa south). Since people have started working from home and learning from home en masse, we've had serious issues during the daytime hours. I'm a network consulting engineer for a large telecom equipment company and I cant afford to be offline right now. As a result, I have just had a second internet connection installed as a backup. It's DSL, so it's relatively slow, but it gets there. The timing was perfect as just last night we suffered an 8 hour total outage of all cable borne services in a large part of the Ottawa area. Maybe they were doing planned maintenance on the neighbourhood nodes? Here's hoping! 😉

Re: Brutal latency/ping Recently

@AngryChicken  Some users in Ottawa have reported that Rogers has been digging in their neighbourhoods laying conduit and fibre.  I'm in the northeast GTA and contractors (Link-On) started doing similar work in my neighbourhood as well... and then all activity suddenly ground to a halt just before they got to my home, so I never got the chance to ask what specific upgrades had been planned.  Clearly Rogers is actively working on making some significant upgrades to their network but all that I have seen so far is a degradation in network performance... and all this started happening way before the COVID-19 shutdown.

Re: Brutal latency/ping Recently

super_robot
I Plan to Stick Around

@-G- 

 

I agree with you. I've personally experienced high latency for a long time. I believe the COVID19 situation magnified all of the issues and threw Rogers a massive curveball.

 

Their response?

 

None.

 

So realistically who knows what is happening and if anything is being done.

 

 

They still feel no shame to waste your time if you call in for support. I find it mind boggling that they haven't made an announcement or public acknowledgement of some sort. They are wasting their own resources deploying techs where they have no way of realistically fixing the issue and wasting the customers time. 

 

I hope that everyone fills out a complaint with CCTS and gets free internet... maybe things will start to get fixed then...

Re: Brutal latency/ping Recently

had 2 timeouts
Ping statistics for 64.71.255.204:
Packets: Sent = 3600, Received = 3598, Lost = 2 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 74ms, Average = 10ms

pinging the CMTS

Ping statistics for 99.x.x.x:
Packets: Sent = 1000, Received = 1000, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 5ms, Maximum = 105ms, Average = 13ms

doing a tracert to a game i ply nhl2000 getting lots of high pings latley so i ran a test and this is what i got

Tracing route to easo.ea.com [159.153.64.173]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms hitronhub.home [192.168.0.1]
2 31 ms 25 ms 9 ms 99.xxx.xxx.x
3 13 ms 11 ms 8 ms 8078-dgw02.ym.rmgt.net.rogers.com [66.185.89.101]
4 10 ms 15 ms 12 ms 3033-cgw01.bloor.rmgt.net.rogers.com [209.148.232.77]
5 9 ms 12 ms 9 ms 209.148.235.210
6 11 ms 9 ms 9 ms zayo.ip4.torontointernetxchange.net [206.108.35.76]
7 * * * Request timed out.
8 * * * Request timed out.
9 30 ms 30 ms 27 ms ae22.er2.iad10.us.zip.zayo.com [64.125.29.121]
10 30 ms 28 ms 34 ms 64.125.199.190.t00673-02.above.net [64.125.199.190]
11 30 ms 36 ms 33 ms 159.153.92.98
12 37 ms 31 ms 27 ms 159.153.92.94
13 30 ms 31 ms 27 ms dragonage.gos.ea.com [159.153.64.173]

Tracing route to easo.ea.com [159.153.64.173]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms hitronhub.home [192.168.0.1]
2 9 ms 17 ms 8 ms 99.xxx.xxx.x
3 14 ms 9 ms 11 ms 8078-dgw02.ym.rmgt.net.rogers.com [66.185.89.101]
4 8 ms 14 ms 31 ms 3033-cgw01.bloor.rmgt.net.rogers.com [209.148.232.77]
5 10 ms 9 ms 9 ms 209.148.235.210
6 24 ms 10 ms 11 ms zayo.ip4.torontointernetxchange.net [206.108.35.76]
7 * 39 ms 34 ms ae21.cs1.lga5.us.zip.zayo.com [64.125.26.138]
8 * * * Request timed out.
9 31 ms 31 ms 28 ms ae22.er2.iad10.us.zip.zayo.com [64.125.29.121]
10 28 ms 29 ms 29 ms 64.125.199.190.t00673-02.above.net [64.125.199.190]
11 31 ms 27 ms 29 ms 159.153.92.98
12 30 ms 32 ms 40 ms 159.153.92.94
13 44 ms 28 ms 29 ms dragonage.gos.ea.com [159.153.64.173]