Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
freem
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Openai/68ff0983-d77c-8006-beff-1e8aa72a6d28
(section)
Add languages
Page
Discussion
English
Read
Edit
Edit source
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
Edit source
View history
General
What links here
Related changes
Special pages
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
=== Assistant: Got it — since you’ve swapped routers and even tested on a different computer, that rules out local hardware as the mai… === Got it — since you’ve swapped routers and even tested on a different computer, that rules out local hardware as the main culprit. If your ping used to be good but is now consistently worse, the problem is most likely upstream. Here’s how that usually breaks down: ===== - ISP-side issues Your line might have developed noise, or your ISP changed routing/peering agreements (which can suddenly make latency higher to certain regions). ===== * Local line degradation Old coax/DSL lines in the house or outside can cause persistent latency increases, even if your speeds seem fine. * Congestion If neighbors are on the same cable node/DSLAM and usage has gone up, your ping can suffer at all times. * Background traffic you didn’t notice Even IoT devices (smart cameras, TVs, consoles auto-updating) can quietly eat bandwidth. ===== 1. Ping/trace route test - Open Command Prompt (Windows) → run: ``<code> ping 8.8.8.8 -n 20 </code>`<code> Then also try: </code>`<code> tracert 8.8.8.8 </code>`` - This shows whether high ping starts inside your network, at the ISP gateway, or further out. ===== # Bypass the router - Connect one computer directly to the modem with Ethernet, no router. - If ping is still bad → problem is at the ISP/line level. # Check time patterns - Is latency bad all the time, or mainly evenings/weekends? - If it’s time-dependent → congestion issue on ISP’s side. # Contact ISP with evidence - Save your ping/traceroute results and provide them to support. - Tell them you’ve tested across devices, on wired, and with a new router. That rules out your hardware. ⚡ If you want, you can run that ping and tracert test and paste the results here. I can help you read where the latency spike is happening — inside your home, at your ISP, or further along the route. Want to try that?
Summary:
Please note that all contributions to freem are considered to be released under the Creative Commons Attribution-ShareAlike 4.0 (see
Freem:Copyrights
for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource.
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)