What are Frontier Gateways busy doing?
Sniffing DNS requests, packets, then writing stats to a hard drive? We know Frontier sniffs DNS traffic.
What type of equipment is being used as the Gateway; a slow PC?
Is there extremely slow virus sniffing software running.
Some type of file maintenance activity, backups, or is somebody playing games on this Gateway?
SO THE BASIC QUESTION; Why do these Gateways have these massive delays? (With no packet loss!)
Below I've added traces to my path to the internet. A good ping or trace response from my Gateway (74.442.148.170 in Dallas, PA) is typically 24 milliseconds(ms). But frequently a ping can take 500, 1000, even 1500 ms, WITH NO PACKET LOSS. I connect using pppoe. Large delays with no packet loss cannot be blamed on the intermediate DSL/T1/Fiber network. If there were network congestion on this network, there would be packet loss, and congestion is always the reason provided by support for slow internet performance. My DSL connects, and is provisioned at, 3712 down, 443 UP. When things are good I can see 3 mbps/second.
WHEN THESE MASSIVE delays occur of course performance is terrible.
TIP: Whenever your Frontier internet (or phone) goes out, take a drive, find the Frontier truck and talk to the techs doing the work! Hint: They can re-provision your DSL in a minute! Try to talk them higher! My line could be provisioned at 6 megabit, feeding the 4 T1 lines, I couldn't convince one tech that even a pole mount DSLAM can do load balancing, I was hoping he would re-provision to 6 Megs. One other tip about pole mount DSLAMs, the replacements are now all fiber, T1 versions are no longer available! (Fiber is Faster (If you can get the provisioning))
My route to my Dallas Gateway is:
DSL 800 ft. to Pole Mount DSLAM
Four T1 lines (1.5mbps) 9000 ft. to a Landstation
Fiber from Landstation to CO.
????? from CO to Dallas, PA. and my Gateway, most likely fiber too.
Good Trace
1, 192.168.1.1, 3ms,,0
2, 74.42.148.170, 24ms,adr01.dlls.pa.frontiernet.net,0
3, 74.42.150.137, 25ms,ae3---0.car01.dlls.pa.frontiernet.net,0
4, 74.40.5.29, 29ms,ae3---0.cor01.asbn.va.frontiernet.net,0
5, 74.40.2.174, 31ms,ae0---0.cbr01.asbn.va.frontiernet.net,0
Bad Trace, typical and frequent
1, 192.168.1.1, 3ms,,0
2, 74.42.148.170, 525ms,adr01.dlls.pa.frontiernet.net,0
3, 74.42.150.137, 459ms,ae3---0.car01.dlls.pa.frontiernet.net,0
4, 74.40.5.029, 440ms,ae3---0.cor01.asbn.va.frontiernet.net,0
5, 74.40.2.174, 526ms,ae0---0.cbr01.asbn.va.frontiernet.net,0
Primary DNS 74.40.74.41
1,192.168.1.1,5ms,,0
2,74.42.148.170, 23ms,adr01.dlls.pa.frontiernet.net,0
3,74.42.150.137, 24ms,ae3---0.car01.dlls.pa.frontiernet.net,0
4,74.43.38.254, 22ms,,0
5,74.40.74.41, 22ms,dns2.anycast.frontiernet.net,0
Backup DNS 74.40.74.40
1,192.168.1.1, 5ms,,0
2,74.42.148.170, 25ms,adr01.dlls.pa.frontiernet.net,0
3,74.42.150.137, 23ms,ae3---0.car01.dlls.pa.frontiernet.net,0
4,74.40.5.29, 52ms,ae3---0.cor01.asbn.va.frontiernet.net,0
5,74.40.2.182, 54ms,ae0---0.cor02.asbn.va.frontiernet.net,0
6,74.40.2.193, 54ms,ae1---0.cor02.chcg.il.frontiernet.net,0
7,74.40.3.241, 50ms,ae0---0.cor01.chcg.il.frontiernet.net,0
8,74.40.2.146, 54ms,ae9---0.car01.ftwy.in.frontiernet.net,0
9,184.17.0.145, 50ms,static-184-17-0-145.drr01.ftwy.in....
10,74.40.74.40, 51ms,dns1.anycast.frontiernet.net,0
Using DSLReports monitoring, I've pinged my router for a long time. In quiet times the ping from VA. is 30ms, the ping from CA. is 100ms. Oddly, when things get busy, the ping time from both VA and CA goes to 400 ms on average which is on the order of the delays I see in my gateway's ping response from my side. So the same typical delay from networks on opposite sides of the Dallas Frontier Gateway (74.42.148.170). All the other intermediate points in the route don't seem to add appreciable delays. I should have written this post a couple years ago, but now the performance is truly degrading.
A link to my stats:
https://www.dslreports.com/testhistory?view=92
So how's your Frontier Gateway treating YOU?
↧
