Visitor
•
4 Messages
Routing Issue
I am trying to connect my computer to a server for work and after performing a Trace Routing, it appears that there is an issue with po-2-xar01.killngwrth81.ct.hartford.comcast.net [96.108.68.45] and/or po-2-xar02.killngwrth81.ct.hartford.comcast.net [96.108.68.46].
This issue is preventing me from reaching the server that I need to reach.
How do I go about reporting this issue so it can be fixed?
user_xjb39u
Visitor
•
4 Messages
2 hours ago
Here is the tracing route I ran:
Tracing route to 20.83.132.169 over a maximum of 30 hops
1 3 ms 3 ms 5 ms Docsis-Gateway.hsd1.ct.comcast.net [10.1.10.1]
2 14 ms 14 ms 13 ms 100.92.51.187
3 13 ms 14 ms 14 ms po-57-rur202.killngwrth81.ct.hartford.comcast.net [96.108.102.217]
4 13 ms 21 ms 15 ms po-200-xar02.killngwrth81.ct.hartford.comcast.net [162.151.188.213]
5 * 346 ms 364 ms po-2-xar01.killngwrth81.ct.hartford.comcast.net [96.108.68.45]
6 350 ms 361 ms 355 ms po-2-xar02.killngwrth81.ct.hartford.comcast.net [96.108.68.46]
7 368 ms * * po-2-xar01.killngwrth81.ct.hartford.comcast.net [96.108.68.45]
8 355 ms 347 ms * po-2-xar02.killngwrth81.ct.hartford.comcast.net [96.108.68.46]
9 * 341 ms 358 ms po-2-xar01.killngwrth81.ct.hartford.comcast.net [96.108.68.45]
10 344 ms 383 ms * po-2-xar02.killngwrth81.ct.hartford.comcast.net [96.108.68.46]
11 334 ms 384 ms 372 ms po-2-xar01.killngwrth81.ct.hartford.comcast.net [96.108.68.45]
12 * 369 ms * po-2-xar02.killngwrth81.ct.hartford.comcast.net [96.108.68.46]
13 350 ms 357 ms 359 ms po-2-xar01.killngwrth81.ct.hartford.comcast.net [96.108.68.45]
14 373 ms 359 ms 357 ms po-2-xar02.killngwrth81.ct.hartford.comcast.net [96.108.68.46]
15 * 375 ms 358 ms po-2-xar01.killngwrth81.ct.hartford.comcast.net [96.108.68.45]
16 * 356 ms 361 ms po-2-xar02.killngwrth81.ct.hartford.comcast.net [96.108.68.46]
17 339 ms 343 ms 344 ms po-2-xar01.killngwrth81.ct.hartford.comcast.net [96.108.68.45]
18 * 374 ms 367 ms po-2-xar02.killngwrth81.ct.hartford.comcast.net [96.108.68.46]
19 373 ms * 377 ms po-2-xar01.killngwrth81.ct.hartford.comcast.net [96.108.68.45]
20 * 358 ms 346 ms po-2-xar02.killngwrth81.ct.hartford.comcast.net [96.108.68.46]
21 * * * Request timed out.
22 * * 374 ms po-2-xar02.killngwrth81.ct.hartford.comcast.net [96.108.68.46]
23 350 ms 344 ms 360 ms po-2-xar01.killngwrth81.ct.hartford.comcast.net [96.108.68.45]
24 * * * Request timed out.
25 * 351 ms 358 ms po-2-xar01.killngwrth81.ct.hartford.comcast.net [96.108.68.45]
26 * 353 ms * po-2-xar02.killngwrth81.ct.hartford.comcast.net [96.108.68.46]
27 * 349 ms 359 ms po-2-xar01.killngwrth81.ct.hartford.comcast.net [96.108.68.45]
28 * * * Request timed out.
29 352 ms 367 ms 357 ms po-2-xar01.killngwrth81.ct.hartford.comcast.net [96.108.68.45]
30 * 349 ms * po-2-xar02.killngwrth81.ct.hartford.comcast.net [96.108.68.46]
Trace complete.
0
0
EG
Expert
•
115.4K Messages
1 hour ago
Wow. Haven't seen one like that in a long while. That's quite a routing loop going on there between .45 and .46. The reps here will need to escalate this right to the NOC / network engineers if they can. Good luck !
1
0
EG
Expert
•
115.4K Messages
36 minutes ago
Nope, sorry. I'm not an employee. Seems that the NOC / engineering is on another planet somewhere, as are many things Comcast....... I escalated this to the corporate employees here. That's all I can do.
(edited)
0