Ok, there's obviously an issue pinging Rogers DNS from your location, but, looks like other targets beyond the CMTS might be ok, depending on the path to those targets.
Can you switch to your game to see what comes up? Are you able to measure packet loss and latency ingame?
@t27c @Visuria where are both of you located?
Can both of you run a trace to the Rogers primary DNS and post the trace:
tracert 64.71.255.204
@Visuria to post the trace results, right click on the top title bar of the command prompt and select Edit .... Select All. Then right click again and select Edit .... Copy. You can then paste that into something like Notepad and copy the trace results on its own, or paste that into a new post and trim off the details that aren't required before posting the results.
@Visuria can you run a ping test to Rogers DNS as well. In this case, I'm looking for packet loss. To run this, using the same command box, type in:
ping -n 600 64.71.255.204
That will run a 10 min ping test. I'd prefer a longer test, but for now, if you're seeing the same amount of packet loss, it will show up in a short test. I'm interested in the final packet loss %.
@RogersAndy are you able to have a look at this? @t27c is seeing packet loss and unstable latency when gaming. Ping tests to the CMTS don't show any losses. Ping test to the Rogers Primary IPV4 DNS 64.71.255.204 show losses in the order of 20 to 25%, which isn't good. Ping tests to google's and OpenDNS don't show any packet loss, so the loss appears to solely within Rogers network. The question from this is, where do the paths to the DNS and the gaming server overlap, to the point that @t27c sees packet loss and unstable latency?
@Visuria is seeing similar issues although both are not co-located off of the same CMTS. The traces to the DNS marry up at hop #5 and are the same from there to the end IP address at 64.71.255.204
Fwiw, pinging the same DNS IP address from ottawa does not show any packet loss.
Your routing is the same, and the route times aren't great. Someone has to look at the CMTS which is at 99.255.58.1
As a comparison, here's the trace from Ottawa:
Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms RT-AC86U
2 18 ms 15 ms 45 ms 174.112.15x.x
3 9 ms 22 ms 8 ms 67.231.221.73
4 13 ms 12 ms 15 ms 209.148.236.161
5 18 ms 15 ms 15 ms 69.63.248.70
6 17 ms 12 ms 15 ms 209.148.227.169
7 * * * Request timed out.
8 12 ms 12 ms 18 ms dns.cp.net.rogers.com [64.71.255.204]
Trace complete.
There's one high time on hop two and hop seven times out in my case but, the overall numbers are normal.
Looks like @RogersAndy may have checked out for the night. He should see the references tomorrow if he's in. Failing that, both of you need to talk to a Tier II tech, specifically regarding the loading at your respective CMTS. The Tier I tech that you will chat with first will give you some static about the request, to which my response would be, "Can you fix a CMTS loading problem? If yes, lets chat, if not, pass me onto a Tier II tech", as in don't waste your time.
@t27c your signal levels are fine, and there doesn't appear to be any packet loss to the CMTS, so the question is, what's up at the CMTS and beyond. Your observation that this has come and gone over the holidays is interesting. That would have occurred when people are home, gaming, streaming, etc, etc, so this looks more like a load issue.
I'd put your modem back into Bridge mode and reconnect the 86U. It won't make any difference whether the modem is in Gateway mode or Bridge mode, the problem is at the CMTS and beyond. For troubleshooting purposes, Rogers staff prefers the modem in Gateway mode, with no router in the mix, so, its up to you as to when to reconnect the router.
If you do chat with a Tier II tech regarding the performance of the CMTS, and beyond please let us know how the conversation went.
There's no reason for you to be paying for a tech visit. You can try to chat with a Tier II tech, or wait for tomorrow or the weekend to chat with @RogersAndy thru the forum. Sending out a tech is useless as the problem doesn't appear to be on your side of the CMTS. The Tier I techs won't normally pass you onto Tier II or to their supervisor unless you ask for that to happen. In any event, the staff members that you want to chat with are further up the command chain.
-
201238 views
-
156 Likes
-
-
