F5F Stay Refreshed Power Users Networks Can I check if my AT&T Fiber BGW210-700 router is broken?

Can I check if my AT&T Fiber BGW210-700 router is broken?

Can I check if my AT&T Fiber BGW210-700 router is broken?

X
xXSuperNovaXx
Posting Freak
811
10-02-2026, 07:42 PM
#1
I use AT&T fiber 1 gbps speed through a 2 year-old BGW210-700. This sends data to ports in different rooms of my house. From one port, I run a Cat6 cable to my gaming PC. About two weeks ago, terrible lag started between the client and server of an online game I play. It happens on every server I connect to. After downloading WinMTR, I checked www.google.com and got 0% loss until it reached Sent/Received, which was around 100%. Then it just got worse and worse, hitting about 60% loss while my speed still shows ~950 Mbps. It feels like information is getting lost. I'm sorry if this sounds technical; I don't know what else to try. I hope someone can suggest another tool to see if the BGW210-700 is actually broken, so I can ask my ISP to replace it.
X
xXSuperNovaXx
10-02-2026, 07:42 PM #1

I use AT&T fiber 1 gbps speed through a 2 year-old BGW210-700. This sends data to ports in different rooms of my house. From one port, I run a Cat6 cable to my gaming PC. About two weeks ago, terrible lag started between the client and server of an online game I play. It happens on every server I connect to. After downloading WinMTR, I checked www.google.com and got 0% loss until it reached Sent/Received, which was around 100%. Then it just got worse and worse, hitting about 60% loss while my speed still shows ~950 Mbps. It feels like information is getting lost. I'm sorry if this sounds technical; I don't know what else to try. I hope someone can suggest another tool to see if the BGW210-700 is actually broken, so I can ask my ISP to replace it.

N
nehatchick1
Junior Member
28
10-07-2026, 09:03 AM
#2
winmtr isn't a great tool because you have to understand exactly what it's checking. It's basically an automated way to run tests, but it's easy to see problems that aren't actually real ones. The most important thing is routers in your path can be set to ignore ping or trace traffic and give those requests lower priority if they are busy moving other data. This helps stop using ping as a denial-of-service attack against internet routers. You should do this manually. Start by making sure the standard leave a constant ping run to 8.8.8.8. If you don't see any loss or huge spikes in latency here, then you probably have something completely different going on that isn't really a network problem. But if you do see an issue at this point, then you can try pinging the router's IP address and pinging your first ISP router. Usually, these are hop 2 in a trace test. You could try other nodes, but it is much harder to fix them because they might not be on your network. If the issue is at hop 2 in the trace test, the ISP should also be able to test it. It's unlikely the problem is the router itself, but it could be. If that one looks like a newer router, it has tons of info about how the fiber connection is doing.
N
nehatchick1
10-07-2026, 09:03 AM #2

winmtr isn't a great tool because you have to understand exactly what it's checking. It's basically an automated way to run tests, but it's easy to see problems that aren't actually real ones. The most important thing is routers in your path can be set to ignore ping or trace traffic and give those requests lower priority if they are busy moving other data. This helps stop using ping as a denial-of-service attack against internet routers. You should do this manually. Start by making sure the standard leave a constant ping run to 8.8.8.8. If you don't see any loss or huge spikes in latency here, then you probably have something completely different going on that isn't really a network problem. But if you do see an issue at this point, then you can try pinging the router's IP address and pinging your first ISP router. Usually, these are hop 2 in a trace test. You could try other nodes, but it is much harder to fix them because they might not be on your network. If the issue is at hop 2 in the trace test, the ISP should also be able to test it. It's unlikely the problem is the router itself, but it could be. If that one looks like a newer router, it has tons of info about how the fiber connection is doing.