AT&T Holiday Deals & Gifts - Don't miss these holiday deals on the latest devices!
Get superfast AT&T Fiber internet
rickcuri's profile

New Member

 • 

4 Messages

Mon, Aug 1, 2022 8:26 PM

Routing Issues

After many years w/o any issues, since last week my internet service has been lagging when accessing specific sites and after checking the routing, I can see there are some hops with high latency and packet loss:

Target Name: www.facebook.com
         IP: 31.13.65.36
  Date/Time: 8/1/2022 3:49:15 PM - 8/1/2022 3:59:15 PM

Hop  Sent  PL%   Min      Max     Avg  Host Name / [IP]

...

  3   239  100     0        0       0   [-]
  4   239    0  0.72    11.20    2.37  76.239.207.130 [76.239.207.130]
  5   239   15  5.72  1487.93  456.06  12.242.113.37 [12.242.113.37]
  6   239    7  5.01  1547.71  458.02  12.125.59.42 [12.125.59.42]
  7   239    0  3.40     9.49    4.02  po103.psw02.atl3.tfbnw.net [31.13.25.249]
  8    12    0  6.01     6.66    6.19  173.252.67.57 [173.252.67.57]
  9   239    0  3.53   212.85    5.41  www.facebook.com [31.13.65.36]

I contacted support but it appears they can't understand what I'm trying to explain and this must be escalated to the right team.

JefferMC

ACE - Expert

 • 

30.3K Messages

4 months ago

High rates of no TTL ICMP error messages on intermediate hops from a traceroute is not really packet loss (even if the traceroute tool mislabels it as such).  High latency on intermediate hops is really only interesting if it carries on to subsequent hops.

I'm not saying you're not having performance symptoms, but I am saying that (other than the single 212.85 ms response from FB which is just one little data point in an ocean), your traceroute isn't showing any evidence of a problem.

New Member

 • 

4 Messages

4 months ago

@JefferMC Thank you for your comments.

This datapoint is just an example, the same issue is happening to different destinations.

Also, packet loss is happening but not showing on this summary.

Intermediate hops also belong to ATT.

JefferMC

ACE - Expert

 • 

30.3K Messages

4 months ago

This bears repeating:

High rates of no TTL ICMP error messages on intermediate hops from a traceroute is not really packet loss

AT&T routers may not send TTL exceeded messages for every packet they could.  Calling a lack of response "packet loss" is simply not accurate (I don't care that the tool labels it "PL%", it's not).   When they do respond, it will take longer than they would to merely pass traffic.  


There are other online tools that will give a more complete picture.

If the issue is intermittent, what would be more useful would be traceroutes when there is, and when there isn't an issue, to compare the difference between them (i.e. where does the latency increase between the two?  Does the route change between the two?)

New Member

 • 

4 Messages

4 months ago

I'm pretty familiar with the tools and I'm using the same tool used to when I was working in a data center years ago. Packet loss is there. My findings are not base on simple traceroute.

(edited)

JefferMC

ACE - Expert

 • 

30.3K Messages

4 months ago

Oh.  Well.  Then I guess you don't need my help.

New Member

 • 

4 Messages

4 months ago

Thank you anyways and I see you've been of great help on this forum @JefferMC

 Probably I just could call my former boss and ask him to help me contacting AT&T's right team about this issue :).

Not finding what you're looking for?
New to AT&T Community?
New to the AT&T Community? Start by visiting the Community How-To.
New to the AT&T Community?
Visit the Community How-To.