Reviews:
 ·Primus Telecommu..
| reply to Suzie
Re: [speed/latency] Massive network slowdown every morning after said by Suzie :Every single night after 2am my computer slows down to a complete crawl. I'm in NE Maine. Anyone else experiencing this? Fairpoint has been fairly good for several months. No more red lights. But this is very maddening.
You might want to check if Windows Automatic Update is scheduled to run at that time. (I believe 2am is the default time.) |
|
| The automatic update runs at 3pm. My Avast update asks me first. I work at night and this seriously impedes that. I wonder when they will update the lines? |
|
 tschmidtPremium,MVM
join:2000-11-12
Milford, NH
kudos:8
·G4 Communications
·Fairpoint Commun..
 ·Hollis Hosting
| The time frame is strange. Normally one assumes problems like this are due to congestion due to heavy usage, Unlikely at 2AM.
There was a problem last week that affected service regionally but that has been corrected.
»www.nashuatelegraph.com/news/sta···sed.html
said by suzee :The automatic update runs at 3pm.
Since you have eliminated that as the cause the next step is to see if it is due to a problem with the physical circuit or congestion within the FairPoint network.
ADSL Circuit
To check the circuit log into your modem and record line stats: sync speed, tx/rx power, attenuation and margin. Do this in both good times and bad. Readings should not change much, perhaps 1 or 2 DB of margin and sync speed should remain constant.
Congestion
Assume circuit is OK do a traceroute (tracert in Windows) to stable sites like this one. Do that in good and bad times. Latency should gradually increase with hop count and distance. The DSLReports data center is in NY so that is a good site to test from Maine. Sudden unexplained jump in latency typically means congestion at that hop or the previous one.
First hop latency depends on speed and interleave probably around 40-50ms.
Typical choke point is the first hop, this is where the ADSL ATM circuit is handed off the the ISP edge router. This is typically not at the local central office but at some regional data center. Back-haul congestion due to lack of capacity is the culprit.
The other common problem is peering, this is where the ISP hands off their traffic to a transits provider. You can usually tell because the router names will change. If you are not sure post the results.
FairPoint has had a lot of problems in Maine but my understanding is they have long since been corrected.
/tom |
|
| Most "core" routers prioritize traffic..ICMP is the bottom rung, if it gets busy it would drop this before impacting 'real' network traffic.
Still ICMP, but pathping »en.wikipedia.org/wiki/PathPing might provide a little more information then the 'snap shot' of trace route (or if on *nix box mtr), as traceroute is that one time you trace..pathping is constant.
pathping 8.8.8.8 (google dns server) and let that run during your lags. if it's on network (fairpoint) call and talk (but I hope to the lords of networking they use some sort of monitoring program and already know)..if it's off their network not much they can do. |
|
| totally agree |
|
