Check out AT&T's Valentine's Day Gift Guide for ideas & deals on the new Samsung Galaxy S23!
Need help with your equipment?
ph4teR's profile

Contributor

 • 

3 Messages

Sunday, August 30th, 2015 2:32 AM

Intermittent Slow Speeds West Palm Beach

Have been experiencing really slow speeds through the day and night intermittenly for the past couple weeks. Opened a service call, but they did not show today. Have been troubleshooting my network, but bypassed evertyhing and reset modem to the factory defaults, with a pc directly connected still experiences slow speeds to the internet. Started continually pinging sites, my home router, and the modem gateway. Only the gateway and websites will respond with high ping times, while staying under 1ms for my home router. Think there is an issue with an upstream devices, just watched this happen within a matter of 12 minutes of me sitting here.

 

Slow_Internet.png

 

Latency.png

 

108.83.248.3 seems to be overloaded and dropped out, or reset itself then the connection works fine and get full speeds. This happened 5 minutes after everything was slow.

 

Latency_Fixed.png

 

Fast_Internet.png

 

We now have fast internet again! 12 minutes later you can see that device come back.

 

Latency_Fixed2.png

 

108.83.248.3 pops back into the picture and speeds are still fast until it stops working again.

 

Hopefully someone can take a look at this and stabilize the connection

 

Thanks,

chris

5 Attachments

Contributor

 • 

3 Messages

7 years ago

I am getting the same. Im in fresno. for the last 3 weeks i have been having periodic slow downs as well.  I'm interested to find out whats going on as no one from AT&T can figure it out.

Contributor

 • 

3 Messages

7 years ago

Yea its pretty bad, just now....Prevents you from doing just about anything!

 

Reply from 8.8.8.8: bytes=32 time=23ms TTL=52
Reply from 8.8.8.8: bytes=32 time=23ms TTL=52
Reply from 8.8.8.8: bytes=32 time=24ms TTL=52
Reply from 8.8.8.8: bytes=32 time=24ms TTL=52
Reply from 8.8.8.8: bytes=32 time=23ms TTL=52
Reply from 8.8.8.8: bytes=32 time=23ms TTL=52
Reply from 8.8.8.8: bytes=32 time=23ms TTL=52
Reply from 8.8.8.8: bytes=32 time=23ms TTL=52
Reply from 8.8.8.8: bytes=32 time=24ms TTL=52
Reply from 8.8.8.8: bytes=32 time=24ms TTL=52
Reply from 8.8.8.8: bytes=32 time=24ms TTL=52
Reply from 8.8.8.8: bytes=32 time=190ms TTL=52
Reply from 8.8.8.8: bytes=32 time=220ms TTL=52
Reply from 8.8.8.8: bytes=32 time=245ms TTL=52
Reply from 8.8.8.8: bytes=32 time=270ms TTL=52
Reply from 8.8.8.8: bytes=32 time=296ms TTL=52
Reply from 8.8.8.8: bytes=32 time=318ms TTL=52
Reply from 8.8.8.8: bytes=32 time=379ms TTL=52
Reply from 8.8.8.8: bytes=32 time=371ms TTL=52
Reply from 8.8.8.8: bytes=32 time=391ms TTL=52
Reply from 8.8.8.8: bytes=32 time=419ms TTL=52
Reply from 8.8.8.8: bytes=32 time=448ms TTL=52
Reply from 8.8.8.8: bytes=32 time=470ms TTL=52
Reply from 8.8.8.8: bytes=32 time=502ms TTL=52
Reply from 8.8.8.8: bytes=32 time=458ms TTL=52
Reply from 8.8.8.8: bytes=32 time=486ms TTL=52
Reply from 8.8.8.8: bytes=32 time=507ms TTL=52
Reply from 8.8.8.8: bytes=32 time=598ms TTL=52
Reply from 8.8.8.8: bytes=32 time=576ms TTL=52
Reply from 8.8.8.8: bytes=32 time=616ms TTL=52
Reply from 8.8.8.8: bytes=32 time=629ms TTL=52
Reply from 8.8.8.8: bytes=32 time=641ms TTL=52
Reply from 8.8.8.8: bytes=32 time=670ms TTL=52
Reply from 8.8.8.8: bytes=32 time=697ms TTL=52
Reply from 8.8.8.8: bytes=32 time=716ms TTL=52
Reply from 8.8.8.8: bytes=32 time=752ms TTL=52
Reply from 8.8.8.8: bytes=32 time=770ms TTL=52
Reply from 8.8.8.8: bytes=32 time=787ms TTL=52
Reply from 8.8.8.8: bytes=32 time=844ms TTL=52
Reply from 8.8.8.8: bytes=32 time=853ms TTL=52
Reply from 8.8.8.8: bytes=32 time=878ms TTL=52
Reply from 8.8.8.8: bytes=32 time=902ms TTL=52
Reply from 8.8.8.8: bytes=32 time=932ms TTL=52
Reply from 8.8.8.8: bytes=32 time=960ms TTL=52
Reply from 8.8.8.8: bytes=32 time=730ms TTL=52
Reply from 8.8.8.8: bytes=32 time=830ms TTL=52
Reply from 8.8.8.8: bytes=32 time=987ms TTL=52
Reply from 8.8.8.8: bytes=32 time=992ms TTL=52
Reply from 8.8.8.8: bytes=32 time=979ms TTL=52
Reply from 8.8.8.8: bytes=32 time=1008ms TTL=52
Reply from 8.8.8.8: bytes=32 time=1019ms TTL=52
Reply from 8.8.8.8: bytes=32 time=1050ms TTL=52
Reply from 8.8.8.8: bytes=32 time=1060ms TTL=52
Reply from 8.8.8.8: bytes=32 time=1085ms TTL=52
Reply from 8.8.8.8: bytes=32 time=1115ms TTL=52
Reply from 8.8.8.8: bytes=32 time=1164ms TTL=52
Reply from 8.8.8.8: bytes=32 time=1192ms TTL=52
Reply from 8.8.8.8: bytes=32 time=1232ms TTL=52
Reply from 8.8.8.8: bytes=32 time=1262ms TTL=52
Reply from 8.8.8.8: bytes=32 time=1282ms TTL=52
Reply from 8.8.8.8: bytes=32 time=1311ms TTL=52

mibrnsurg

Expert

 • 

20.4K Messages

7 years ago

@ph4teR  108.83.248.3 is your connection to the VRAD, lightspeed (Uverse code name)west palm beach, fl on sbcglobal.net.  Something is happening on the line from your home to the VRAD causing these high latency figures.

 

Click the ATT Uverse Care link in my signature below, send the PM, explain your high latency on line to VRAD situation.

Include your name, account #, email address and a good phone # (land or cell) and time to contact you on.

Check the blue PM envelope, upper right on every page, for their reply. Good luck 😉

 

Chris
__________________________________________________________

Please NO SD stretch-o-vision or 480 SD HD Channels
Need Help? PM ATT Uverse Care (all service problems)
ATT Customer Care(billing and all other problems)
Your Results May Vary, In My Humble Opinion
I Call It Like I See It, Simply a U-verse user, nothing more

mibrnsurg

Expert

 • 

20.4K Messages

7 years ago

@finger123   If you happen to have a 510/589 Arris/Moto RG, IPv6 causes disconnects, rebooting and browsing problems.

Disable IPv6 in the RG's Gui. http://192.168.1.254/

Good luck 😉

 

Chris
__________________________________________________________

Please NO SD stretch-o-vision or 480 SD HD Channels
Need Help? PM ATT Uverse Care (all service problems)
ATT Customer Care(billing and all other problems)
Your Results May Vary, In My Humble Opinion
I Call It Like I See It, Simply a U-verse user, nothing more

Contributor

 • 

3 Messages

7 years ago

The issues are that I have high latency. My ping times are in the high 800's to 1000's when speeds are slow. Normally it's supposed to be in the 10's.

JefferMC

ACE - Expert

 • 

30.9K Messages

7 years ago


@finger123 wrote:
The issues are that I have high latency. My ping times are in the high 800's to 1000's when speeds are slow. Normally it's supposed to be in the 10's.


@finger123, high pings all the time, or just at times?

How remote is the system you're pinging?

Do you saturate your upload bandwith (online backup, especially Google Drive from smartphones; P2P file sharing, etc)?

 

To set your expectation, with the interleaved configuration VDSL2, your PINGs will start at around 20 ms for the first hop after your Residential Gateway.

 

Contributor

 • 

3 Messages

7 years ago

My problems are at certain times only and can last for up to hours. I am fiber to the premises. My ping times are typically I. The low 10's when normal.

JefferMC

ACE - Expert

 • 

30.9K Messages

7 years ago


@ph4teR wrote:

Yea its pretty bad, just now....Prevents you from doing just about anything!

 

Reply from 8.8.8.8: bytes=32 time=23ms TTL=52
... 9 similar lines...
Reply from 8.8.8.8: bytes=32 time=24ms TTL=52
Reply from 8.8.8.8: bytes=32 time=190ms TTL=52
Reply from 8.8.8.8: bytes=32 time=220ms TTL=52
Reply from 8.8.8.8: bytes=32 time=245ms TTL=52
Reply from 8.8.8.8: bytes=32 time=270ms TTL=52
Reply from 8.8.8.8: bytes=32 time=296ms TTL=52
Reply from 8.8.8.8: bytes=32 time=318ms TTL=52
Reply from 8.8.8.8: bytes=32 time=379ms TTL=52
Reply from 8.8.8.8: bytes=32 time=371ms TTL=52
Reply from 8.8.8.8: bytes=32 time=391ms TTL=52
Reply from 8.8.8.8: bytes=32 time=419ms TTL=52
Reply from 8.8.8.8: bytes=32 time=448ms TTL=52
Reply from 8.8.8.8: bytes=32 time=470ms TTL=52
Reply from 8.8.8.8: bytes=32 time=502ms TTL=52
Reply from 8.8.8.8: bytes=32 time=458ms TTL=52
Reply from 8.8.8.8: bytes=32 time=486ms TTL=52
Reply from 8.8.8.8: bytes=32 time=507ms TTL=52
Reply from 8.8.8.8: bytes=32 time=598ms TTL=52
Reply from 8.8.8.8: bytes=32 time=576ms TTL=52
Reply from 8.8.8.8: bytes=32 time=616ms TTL=52
Reply from 8.8.8.8: bytes=32 time=629ms TTL=52
Reply from 8.8.8.8: bytes=32 time=641ms TTL=52
Reply from 8.8.8.8: bytes=32 time=670ms TTL=52
Reply from 8.8.8.8: bytes=32 time=697ms TTL=52
Reply from 8.8.8.8: bytes=32 time=716ms TTL=52
Reply from 8.8.8.8: bytes=32 time=752ms TTL=52
Reply from 8.8.8.8: bytes=32 time=770ms TTL=52
Reply from 8.8.8.8: bytes=32 time=787ms TTL=52
Reply from 8.8.8.8: bytes=32 time=844ms TTL=52
Reply from 8.8.8.8: bytes=32 time=853ms TTL=52
Reply from 8.8.8.8: bytes=32 time=878ms TTL=52
Reply from 8.8.8.8: bytes=32 time=902ms TTL=52
Reply from 8.8.8.8: bytes=32 time=932ms TTL=52
Reply from 8.8.8.8: bytes=32 time=960ms TTL=52
Reply from 8.8.8.8: bytes=32 time=730ms TTL=52
Reply from 8.8.8.8: bytes=32 time=830ms TTL=52
Reply from 8.8.8.8: bytes=32 time=987ms TTL=52
Reply from 8.8.8.8: bytes=32 time=992ms TTL=52
Reply from 8.8.8.8: bytes=32 time=979ms TTL=52
Reply from 8.8.8.8: bytes=32 time=1008ms TTL=52
Reply from 8.8.8.8: bytes=32 time=1019ms TTL=52
Reply from 8.8.8.8: bytes=32 time=1050ms TTL=52
Reply from 8.8.8.8: bytes=32 time=1060ms TTL=52
Reply from 8.8.8.8: bytes=32 time=1085ms TTL=52
Reply from 8.8.8.8: bytes=32 time=1115ms TTL=52
Reply from 8.8.8.8: bytes=32 time=1164ms TTL=52
Reply from 8.8.8.8: bytes=32 time=1192ms TTL=52
Reply from 8.8.8.8: bytes=32 time=1232ms TTL=52
Reply from 8.8.8.8: bytes=32 time=1262ms TTL=52
Reply from 8.8.8.8: bytes=32 time=1282ms TTL=52
Reply from 8.8.8.8: bytes=32 time=1311ms TTL=52


It's strange that your numbers progressively rise like that.  One thing I always ask about latency (especially when it comes and goes) is: "Are you saturating your upstream bandwidth?"  If so, it causes high latency and poor download experience.  Potential sources of upstream traffic: Online backup (Android phones like to backup pictures to Google Drive, etc.; but PCs do too); Video sharing; P2P file sharing, Malware, etc.

 

JefferMC

ACE - Expert

 • 

30.9K Messages

7 years ago


@finger123 wrote:
My problems are at certain times only and can last for up to hours. I am fiber to the premises. My ping times are typically I. The low 10's when normal.


Ah, yes, FTTP will take out VDSL2 and interleaving.  It also makes it a challenge to fill up your upstream bandwidth.  Have you tried using TRACERT with or without PING to see at what hop the pings start climing?

 

Contributor

 • 

3 Messages

7 years ago

I just tested this theory out, and it was spot on. My iPhone automatically uploads pictures and videos to iCloud. I had the ping running which was averaging about 25ms, took some pictures, and immediately saw the response times start spiking up. Watched them climb to 500ms+ consistently, then turned off my phone. The ping times dropped back to 25ms!

 

Thank you! I will have to add some QoS in there to prevent this from affecting browsing and watching tv!

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.