Visitor

 • 

5 Messages

Sunday, May 24th, 2026 10:55 PM

Why can't call Comcast or submit tracert to prove NOC issue at the head end?

COD/BF6 latency has been hurting big time. Its bad, so we have to have a senior tech come and show the real issue is not on my end. 

Your wasting a roll out, 

  1    <1 ms    <1 ms    <1 ms  2601:183:4105:fb50:c650:9cff:fefb:2ccf

  2    13 ms    13 ms    14 ms  2001:558:1000:58::2

  3    14 ms    12 ms    15 ms  po-308-387-rur101.branford.ct.hartford.comcast.net [2001:558:202:ff26::1]

  4    14 ms    25 ms    16 ms  po-2-rur102.branford.ct.hartford.comcast.net [2001:558:200:8159::2]

  5    12 ms    16 ms    14 ms  po-100-xar02.branford.ct.hartford.comcast.net [2001:558:200:97f::1]

  6    19 ms    20 ms    18 ms  2001:558:200:2030::1

  7     *        *        *     Request timed out.

  8    22 ms    22 ms    21 ms  2001:559:e000::3b2

  9    21 ms    22 ms    21 ms  ae2.r01.stem01.bos01.fab.netarch.akamai.com [2600:1401:f000:302::1]

 10    22 ms    14 ms    20 ms  ae1.r03.spine01.bos01.fab.netarch.akamai.com [2600:1401:f000:801::]

 11    22 ms    22 ms    19 ms  ae3.r01.leaf01.bos01.fab.netarch.akamai.com [2600:1401:f000:802::1]

 12    23 ms    22 ms    39 ms  ae1.r19.tor01.bos01.fab.netarch.akamai.com [2600:1401:f000:1a13::1]

 13    20 ms    21 ms    22 ms  g2600-1401-d000-0582-0000-0000-0000-1127.deploy.static.akamaitechnologies.com [2600:1401:d000:582::1127]

 

Trace complete.

 

C:\>tracert microsoft.com

 

Tracing route to microsoft.com [2603:1061:14:47::1]

over a maximum of 30 hops:

 

  1     1 ms     1 ms     1 ms  2601:183:4105:fb50:c650:9cff:fefb:2ccf

  2    14 ms    17 ms    14 ms  2001:558:1000:58::2

  3    16 ms    13 ms    13 ms  po-308-387-rur101.branford.ct.hartford.comcast.net [2001:558:202:ff26::1]

  4    17 ms    13 ms    25 ms  po-2-rur102.branford.ct.hartford.comcast.net [2001:558:200:8159::2]

  5    14 ms    25 ms    18 ms  po-100-xar02.branford.ct.hartford.comcast.net [2001:558:200:97f::1]

  6    17 ms    15 ms    18 ms  2001:558:200:2030::1

  7     *        *        *     Request timed out.

  8     *        *        *     Request timed out.

  9     *        *        *     Request timed out.

 10    35 ms    31 ms    36 ms  2603:1060:0:12::f12a

 11    98 ms    37 ms    34 ms  2a01:111:201:f200::e8d

 12    34 ms     *       34 ms  2603:1060:0:10::f441

Oldest First
Selected Oldest First

Official Employee

 • 

4.2K Messages

1 hour ago

 

user_c2dc3c This is a great question! I know it can be really frustrating to have multiple technicians out for an issue, however any repair requests or maintenance tickets that may be needed would require a technician on site to submit them. We can only do so much via remote troubleshooting, when that fails our technicians are our eyes on the ground so to speak and can check signals and determine next steps based on their findings. 

Do you already have a technician scheduled to come out? 

 

forum icon

New to the Community?

Start Here