Packet loss issue between ATT HOP AND NTT SACRAMENTO DATACENTER

WE RUN TRACEROUTE AND FOUND THAT THERE IS SOME ISSUE BETWEEN ATT AAND ZAYO NETWORK, LIGHTSPEED NETWORK HOP.

There is no issue unless your target IP has a 10x or higher response time vs routes along your trace route path. Post a screenshot of your trace and we look at it. Using a trace route command just sends junk traffic to each router that responds. The packets are ICMP Echo requests that are a very low priority with a modified TTL to elicit a response.

Dave

see the hop no 8

We have comcast, TATA, Sify, PLDT, spectrum and from all the ISP, everything is working fine except ATT and when i traceroute, the same hop is coming with drops

No issues on Hop 8 just like there is no issues on Hop 4 or 5 that ignore 100% of the junk ICMP Echo packets. Why do you think the issue is on Hop 8? It is just the first Hop after leaving the AT&T Core network.

Always start at the bottom of the list and work up. Note your target 65.160.227.90 has better response than a couple of nodes above it.

Dave

Hi @Manohark, 

We completely understand your concern and would like to help. Let's get the assistance you require.

The Community Forums are a public support option where other users, and AT&T, will try and assist with high level support needs. This means we won’t be able to look into account specific concerns. To get the help you need for your unique issue, please review our Contact Us page [www.att.com/support/contact-us/], and choose the best option to reach out to us. You can call, chat, or reach out via social media, and we can review your specific issue and provide you support. If you feel your issue isn’t account specific, and can be answered generally, please let us know, and we’ll be happy to help.

Thank you for contacting AT&T Community Forums,

Tess, AT&T Community Specialist.

see the reverse tracert.8 No hop having drop issue and it is from ATT. I am just trying to convay that the path is not good. If you check the path and change it. Because there are 15 office we have and all are having issue over ATT

Hi,

I already tried to contact ATT support but they are saying that they can check the IP only assigned to my office Router/modem. Also this is not account specific. 15 office are affected and all are having hop. I already discussed with NTT as well for the same from their end they can change the path for outgoing not incoming.  

Something wrong with the peering between ATT and next provider i think. 

No issues on Hop 8 just like there is no issues on Hop 4 or 5...

I don't necessarily agree with that.  Hop 8 is the first hop with substantially increased latency that begins at that point (without an obvious geographical explanation) and % loss that continues throughout the remaining responding hops.  Yes, 4 and 5 are not a problem at all, because hops 6 and 7 return low latency and near 100% return beyond 4 & 5.  There's nothing beyond hop 8 showing a return to "normalcy."

So, there may be an issue with the peer "zayo."  AT&T may or may not be aware of it.  Zayo may or may not be aware of it.  Zayo may be working through a problem they thought they'd have fixed by now.  

see the reverse tracert.8 No hop having drop issue and it is from ATT. I am just trying to convay that the path is not good.

This is not a reverse trace to your original IP of 162.237.20.1 but a trace from 96.46.146.249 (NTT Data Center) to 172.127.157.41. This trace also does not show any issues.

What is your original problem it is not showing in either of your traces?

Dave

my original problem was getting drop while ping NTT datacenter IPs, I tried to ping aleast 10 different IP and almost 25% drops were there. I just checked after jeffferMC comment and now i am not getting drops and also the path has been changed from yesterday report

Also 96.46.146.249 is hop IP.