Reporting a bad tracert

Participant

Reporting a bad tracert

Buffering content was the warning, bad tracerts are the confimation: Service is poor tonight.

 

I'll feel better if I can just post some of the results. I won't get my hopes up that anything will be done since it would be simple to provide an email address so that users could alert to poor service conditions directly to entities that administer. such vut no such facility is provided. This forum is replete with a set of conditions that only South Park could appreciate. Any bystander could see where the resources are being sent.

 

 

Tracing route to espn.com [199.181.132.250]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 7 ms 7 ms 32.216.223.254
3 11 ms 11 ms 8 ms 12.83.32.65
4 35 ms 35 ms 36 ms gar13.cgcil.ip.att.net [12.122.132.121]
5 * * * Request timed out.
6 83 ms 83 ms 83 ms vl-3508-ve-122.ebr1.Chicago2.Level3.net [4.69.15
8.142]
7 83 ms 82 ms 83 ms ae-3-3.ebr2.Denver1.Level3.net [4.69.132.61]
8 82 ms 91 ms 83 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.151.181]

9 84 ms 83 ms 82 ms ae-1-6.bar2.LasVegas1.Level3.net [4.69.148.1]
10 82 ms 82 ms 82 ms ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125]

11 83 ms 83 ms 83 ms ae-5-5.car1.LasVegas1.Level3.net [4.69.148.129]

12 83 ms 83 ms 83 ms WALT-DISNEY.car1.LasVegas1.Level3.net [4.71.176.
82]
13 * * * Request timed out.
14 * * * Request timed out.
15 84 ms 84 ms 84 ms ugv2.abc.go.com [199.181.132.250]

Trace complete.

 

Tracing route to www.gtm.nytimes.com [170.149.172.130]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 7 ms 7 ms 32.216.223.254
3 10 ms 7 ms 8 ms 12.83.32.225
4 36 ms 35 ms 36 ms gar13.cgcil.ip.att.net [12.122.132.121]
5 * * * Request timed out.
6 83 ms 91 ms 84 ms vl-3505-ve-119.ebr1.Chicago2.Level3.net [4.69.158.130]
7 87 ms 84 ms 82 ms ae-3-3.ebr2.Denver1.Level3.net [4.69.132.61]
8 84 ms 87 ms 87 ms ae-2-2.ebr2.Seattle1.Level3.net [4.69.132.53]
9 86 ms 175 ms 83 ms ae-2-52.edge2.Seattle1.Level3.net [4.69.147.168]
10 88 ms 86 ms 83 ms NEW-YORK-TI.edge2.Seattle1.Level3.net [4.53.158.42]
11 84 ms 89 ms 91 ms 170.149.172.130

Trace complete.

 

And how about att.com

 

Tracing route to e2318.dscb.akamaiedge.net [23.3.57.145]
over a maximum of 30 hops:

1 1 ms <1 ms 1 ms 192.168.1.1
2 7 ms 7 ms 7 ms 32.216.223.254
3 9 ms 11 ms 7 ms 12.83.32.225
4 35 ms 35 ms 36 ms gar2.clboh.ip.att.net [12.122.132.197]
5 64 ms 61 ms 59 ms 192.205.32.194
6 * 64 ms 64 ms ae-6.r21.chcgil09.us.bb.gin.ntt.net [129.250.2.26]
7 103 ms 86 ms 87 ms ae-3.r21.dllstx09.us.bb.gin.ntt.net [129.250.2.200]
8 83 ms * 87 ms ae-0.r20.dllstx09.us.bb.gin.ntt.net [129.250.2.58]
9 139 ms 105 ms 110 ms ae-2.r21.miamfl02.us.bb.gin.ntt.net [129.250.3.175]
10 115 ms 116 ms 109 ms ae-2.r04.miamfl02.us.bb.gin.ntt.net [129.250.4.251]
11 114 ms 102 ms 108 ms a23-3-57-145.deploy.static.akamaitechnologies.com [23.3.57.145]

Trace complete.

 

Nothing. Works tonight.

 

hand

 

 

 

Message 1 of 2 (387 Views)
Community Manager

Re: Reporting a bad tracert

Hello, Notmuchofahandle!

 

Thanks for posting. We would be happy to look into these results with you, so please click here to send us a private message.

 

In your message, please provide your name, phone number, email address, and the best time to reach you. You can expect a reply within two business days, so keep an eye on the little blue envelope icon in the top right corner of your screen.

 

In the meantime, feel free to message me with any other questions or concerns.

 

-Mariana

Employee Contributor*
*I am an AT&T employee and the postings on this site are my own and don't necessarily represent AT&T's position, strategies or opinions.
Message 2 of 2 (348 Views)