Shop holiday gifts while you still can - Everyone gets our best deals on any smartphone!
Get superfast AT&T Fiber internet
jfclifton's profile

New Member

 • 

17 Messages

Friday, August 26th, 2022 1:16 AM

High Ping + Packet Loss between 8pm-11pm EST

I've had ATT fiber 1000 for about 3 years now and never had an issue until now. 

I recently moved into a new house (new build) which was serviced by ATT fiber so my service was moved over without any hiccups. Until I attempted to use it in the evening hours.

Just to be clear before all this info- My speeds have continued to be superb.

The first night (last night) I noticed it was bad when I got on. 20% packet loss pinging google.com, hitting average ping of ~80ms (during the day it is ~25ms). Then I noticed.. it got better literally as I was on the phone talking to an ATT tech. I look at the time it's 11:02pm.

So since that was strange I decided to test on the hour tonight and discovered the issues started picking up again at exactly 8pm. More timeouts and high pings.

I tried connecting to the nearest location my VPN supported and everything was normal. No timeouts and no high pings.

Before I cancel- because this isn't something I want to pay for- is there anything that can actually be done here? I feel like with reading other threads on similar issues - this could go on for months without resolution. Or just continue to go nowhere.

I am in the NE Raleigh, NC area.

Thanks for any help/suggestions!

Scholar

 • 

3.7K Messages

1 year ago

What is your real issue. Are you playing FPS games that require low latency and no lag?

Average Ping times to Google.com at ~80 ms during peek hours is an issue. It would help if you posted some traceroute comands so we could look to find where the slow ICPM Echo commands are being dropped.

However please note that Pings (ICPM Echo) commands are low priority and as discarded when routers are busy with real routing work. This is by design to prevent DDoS attacks on the routers.

If you are not seeing any issue reaching your VPN local POP it initially looks like a peering issue somewhere in the Internet.

Dave

New Member

 • 

17 Messages

1 year ago

Yes. 8-11pm is prime game hours for me. 

The ping will constantly spike in game anywhere from 60ms to 200ms during these hours. Also becomes a bigger problem when playing a particular game with a ping limit. If that ping is reached - you are dropped.

So that's the real issue.

And just seeing 150-200 ping to a Dallas server during this timeframe is disappointing. ~30 ping out of the timeframe to the same server.

I will post some traceroutes tonight during the timeframe. 

When you say "peering issue" can you explain? 

Thanks for your response.

Scholar

 • 

3.7K Messages

1 year ago

When you say "peering issue" can you explain? 

All ISPs interconnect the other ISPs a peering points where groups of ISPs share a Col-location site with high speed connections for exchange of Internet traffic.

Once traffic leaves AT&T there is almost nothing AT&T Network Operations can do about issues with show response.

That's where traceroutes come into play as most routers have names we can decode to determine which router is where the issue tends to go south had have high spikes (aka lag) in traffic.

Dave

New Member

 • 

17 Messages

1 year ago

Ok thanks, Dave.

So basically if the failure is not happening at an AT&T point - we're kind of dead in the water with a fix?

Also, is there non-default traceroute settings to use to provide you with the best info possible? I'm not familiar with what parameters I can also pass to help. Or even websites to target. I'm not sure of the game server IPs I typically hit. I'm sure there's a way to find out. I think their out of game server address is just "prod.escapefromtarkov.com". But it's happening all over anyway.

Thanks,

Jordan

New Member

 • 

17 Messages

1 year ago

Here is the traceroute running at 9pm est

Tracing route to www.google.com [2607:f8b0:4009:807::2004]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2     9 ms     1 ms     1 ms  2001:506:6000:116:76:229:56:174
  3     2 ms     2 ms     2 ms  2001:506:6000:116:76:229:56:165
  4   145 ms    93 ms    72 ms  2001:1890:f6:1443::2
  5    90 ms    89 ms    68 ms  2001:1890:c01:b1:12:255:11:2
  6    65 ms    61 ms    73 ms  2607:f8b0:82a9::1
  7    57 ms    62 ms     *     2001:4860:0:1::47ae
  8     *       73 ms     *     2001:4860:0:1099::2
  9     *       78 ms     *     2001:4860::c:4002:332d
 10   109 ms     *       82 ms  2001:4860::c:4002:6e13
 11     *        *        *     Request timed out.
 12    93 ms   143 ms   142 ms  2001:4860::1:4000:d31c
 13    92 ms   114 ms    98 ms  2001:4860:0:100e::1
 14    88 ms   109 ms   103 ms  2001:4860:0:1::191f
 15   112 ms   140 ms   115 ms  ord08s13-in-x04.1e100.net [2607:f8b0:4009:807::2004]

Trace complete.

New Member

 • 

17 Messages

1 year ago

Here is another traceroute taken at 12am est

Tracing route to www.google.com [2607:f8b0:4002:c02::93]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2     1 ms     2 ms     1 ms  2001:506:6000:116:76:229:56:174
  3     3 ms     3 ms     3 ms  2001:506:6000:116:76:229:56:165
  4    10 ms    10 ms    10 ms  2001:1890:f6:1443::2
  5    11 ms    10 ms    11 ms  2001:1890:fff:fb5:12:255:11:10
  6    11 ms    10 ms    11 ms  2607:f8b0:8040::1
  7     *        *       11 ms  2001:4860:0:1::219c
  8    12 ms     *        *     2001:4860:0:eae::2
  9    19 ms    19 ms    19 ms  2001:4860::c:4001:e747
 10    18 ms    19 ms    18 ms  2001:4860::c:4002:6e16
 11    19 ms    18 ms    19 ms  2001:4860::c:4001:588f
 12    19 ms    19 ms    19 ms  2001:4860::c:4002:8e38
 13    19 ms    19 ms    18 ms  2001:4860::cc:4000:fb6e
 14    17 ms    19 ms    18 ms  2001:4860:0:1::4e37
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24    18 ms    17 ms    17 ms  ym-in-f147.1e100.net [2607:f8b0:4002:c02::93]

Trace complete.

ACE - Guru

 • 

9.9K Messages

1 year ago

Go into the gateway at http://192.168.1.254 and click the Home Network tab and then the IPv6 link and you'll be asked for the Access Code that is on a label on the gateway.  Then change IPv6 to Off, click Save and then I'd probably reboot the router. 

See if that makes a difference.

New Member

 • 

17 Messages

1 year ago

No difference unfortunately. Thanks for info.

May just come down to switching iSPs.

The exact timeframe degraded service thing is new to me. And seems like it's an "AT&T thing". 

Community Support

 • 

225.7K Messages

1 year ago

Hey there jfclifton, let us help you fix the high ping and packet loss so that you can enjoy your games.

 

We'll be sending you a Direct Message to get started. Look for the chat icon next to the bell icon in the upper right corner of the Forums page.

 

Aminah, AT&T Community Specialist

New Member

 • 

34 Messages

1 year ago

@jfclifton 

Did they resolve this issue for you ? I am having the same issue in Dallas since Friday 9/2

Not finding what you're looking for?