| [speed/latency] Massive network slowdown every morning after 2am 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. |
|
| Re: [speed/latency] Massive network slowdown every morning after 2AM? It's probably their maintenance period.. my ISPs maintenance window is between 2AM and 8AM. |
|
| reply to Suzie
I am located in SouthEast Vermont and have been experiencing slowdown on my 3Mb DSL connection after 5PM for the last 3 months. Typically, speed is reduced to under 1Mb with a 500ms latency. Fairpoint IT has confirmed the evening network congestion (through a help ticket) but stated nothing can be done to correct the problem until the system is upgraded. So much for the "non line sharing" sales pitch. Also, customer service will not reduce my monthly charge stating connection speeds are not guaranteed! No other options for now. |
|
| All the lines into the local POP are dedicated to each end user. The POP to the central office is where sharing begins...
At night time your neighbors are home and although the last leg to you is not shared the area is backed up from the POP to CO, or perhaps it's even more widespread and the CO to the network handoff... |
|
|
|
Reviews:
 ·Primus Telecommu..
| reply to Suzie
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 |
|
Reviews:
 ·Verizon Wireless..
·Great Works Inte..
1 edit | reply to Suzie
I live in Belfast Maine and Im experiencing the same massivie lag spike in the evening from about 3pm to midnight. It's every day just like clock work my ping goes from 50ms in the morning then bam! 200+ all night...it's so frigging irritating. Ive called tech support numerous times emailed them also many times. They've sent tech guys to my house to test at the NID when im gone of course and during the day when everything is fine. I try to tell them it's fine during the day but when i get home from work and want to use the freaking internet its slow as hell..buffers videos every 10 seconds. They dont care they just make excuses say everything is fine must all be in my head..but theyre the only game in town. I dont have hi-speed internet i have whats probably more equal to hi-speed dial up..im serious. Not a happy camper. |
|
| I hope my cut and past shows up.
I had this trace running overnight to see if there was a widespread issue on congestion/network slowdown:
eys: Help Display mode Restart statistics Order of fields quit
Packets Pings
Host Loss% Snt Drop Last Avg Best Wrst StDev Javg
1. 192.168.91.1 0.2% 29288 56 6.1 1.7 1.0 251.6 17.3 10.9
2. 216.227.0.132 1.5% 29288 449 85.5 115.7 34.9 2586. 142.3 43.6
3. 216.227.0.49 1.5% 29288 445 62.4 112.8 35.0 2410. 144.3 44.6
4. 216.227.0.5 1.6% 29288 457 144.7 113.2 35.0 2550. 147.7 44.9
5. 71.161.104.61 1.5% 29288 451 206.2 121.4 38.9 2544. 152.4 50.0
6. 64.222.213.33 1.6% 29288 464 63.3 121.7 38.8 2694. 151.6 48.6
7. 64.222.213.136 1.6% 29287 464 63.9 118.1 38.6 2493. 152.9 46.6
my local network droped 56 pings (.2%), and Fairpoint first hop dropped 449 (1.5%). Not perfect, but not too bad..this was the overnight when ISP's like to do maintenance..I'm not overly concerned with the 1.5% packet loss (in the overnight).
Hope this helps clear any issues. |
|
Reviews:
·Verizon Wireless..
·Great Works Inte..
| reply to Suzie
Here is my proof of what i posted above, it's 11am right now i didn't have to work today. Here is my ping using tracert during the day when im usually not home its pretty decent i can live with it but when im home after 3pm it will go way up to around 200ms and stay there all night till around midnight. Of course this is when everyone else is home also and wants to use the internet too. It must be traffic congestion..i dont know what else it could be? So much for dsl having an independant line compared to cable. Ill show the spike later tonight in another post.
Tracing route to google.com [74.125.226.193]
over a maximum of 30 hops:
1 3 ms 3 ms 1 ms
2 47 ms 47 ms 46 ms d-ptld-bng1-64-222-214-1.ngn.east.myfairpoint.ne
t [64.222.214.1]
3 47 ms 46 ms 48 ms pool-64-222-213-27.port.east.myfairpoint.net [64
.222.213.27]
4 49 ms 48 ms 48 ms pool-64-222-213-136.port.east.myfairpoint.net [6
4.222.213.136]
5 51 ms 51 ms 51 ms xe-3-2-0.mpr4.bos2.us.above.net [208.184.223.233
]
6 49 ms 51 ms 51 ms xe-0-0-0.mpr3.bos2.us.above.net [64.125.25.61]
7 58 ms 57 ms 111 ms xe-5-3-0.cr1.lga5.us.above.net [64.125.24.110]
8 58 ms 57 ms 83 ms xe-1-0-0.cr2.lga5.us.above.net [64.125.29.46]
9 57 ms 56 ms 57 ms xe-0-0-1.er4.lga5.us.above.net [64.125.24.169]
10 58 ms 64 ms 57 ms 72.14.212.130
11 57 ms 57 ms 57 ms 209.85.248.178
12 58 ms 57 ms 57 ms 72.14.239.250
13 56 ms 132 ms 58 ms lga15s28-in-f1.1e100.net [74.125.226.193]
Trace complete. |
|
| can you try with pathping....trace route is not the best as it's a snapshot.
from command prompt:
pathping 64.22.213.136
anything after this point is not under Fairpoints control.
to help out I have started to pathping (MTR) 64.222.214.1 (the edge of FP and your equipment.)
Host Loss% Snt Last Avg Best Wrst StDev
1. 192.168.91.1 0.0% 57 1.4 4.5 1.1 57.2 9.0
2. 216.227.0.132 0.0% 57 51.6 53.2 36.0 119.3 17.9
3. 216.227.0.49 0.0% 57 53.8 50.9 36.3 101.2 14.5
4. 216.227.0.5 0.0% 57 53.7 53.1 36.1 103.9 17.0
5. 71.161.104.61 0.0% 57 55.6 56.1 39.4 176.8 20.6
6. 64.222.213.25 0.0% 57 59.9 55.8 39.6 105.2 14.9
7. 64.222.214.1 0.0% 56 48.1 51.1 39.0 78.9 9.4 |
|
Reviews:
·Verizon Wireless..
·Great Works Inte..
| reply to Suzie
It's 7pm heres the ping spike shown using tracert and pathping below. It's not quite 200ms tonight must be a good night only 150ms....
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Jeremy>tracert google.com
Tracing route to google.com [74.125.226.193]
over a maximum of 30 hops:
1 3 ms 3 ms 3 ms
2 129 ms 131 ms 128 ms d-ptld-bng1-64-222-214-1.ngn.east.myfairpoint.ne
t [64.222.214.1]
3 127 ms 127 ms 134 ms pool-64-222-213-27.port.east.myfairpoint.net [64
.222.213.27]
4 142 ms 141 ms 142 ms pool-64-222-213-136.port.east.myfairpoint.net [6
4.222.213.136]
5 139 ms 137 ms 133 ms xe-3-2-0.mpr4.bos2.us.above.net [208.184.223.233
]
6 128 ms 132 ms 138 ms xe-1-0-0.mpr3.bos2.us.above.net [64.125.25.65]
7 140 ms 136 ms 149 ms xe-5-3-0.cr1.lga5.us.above.net [64.125.24.110]
8 124 ms 128 ms 122 ms xe-1-0-0.cr2.lga5.us.above.net [64.125.29.46]
9 123 ms 141 ms 143 ms xe-0-0-1.er4.lga5.us.above.net [64.125.24.169]
10 127 ms 125 ms 120 ms 72.14.212.130
11 147 ms 145 ms 147 ms 209.85.248.178
12 247 ms 268 ms 144 ms 72.14.239.250
13 130 ms 129 ms 129 ms lga15s28-in-f1.1e100.net [74.125.226.193]
Trace complete.
C:\Users\Jeremy>pathping 64.22.213.136
Tracing route to network-136.rmexp-iedsl.netexpress.net [64.22.213.136]
over a maximum of 30 hops:
0 Jeremy-PC
1 My router
2 d-ptld-bng1-64-222-214-1.ngn.east.myfairpoint.net [64.222.214.1]
3 pool-64-222-213-19.port.east.myfairpoint.net [64.222.213.19]
4 pool-64-222-213-134.port.east.myfairpoint.net [64.222.213.134]
5 xe-3-2-0.mpr4.bos2.us.above.net [208.184.223.233]
6 xe-1-0-0.mpr3.bos2.us.above.net [64.125.25.65]
7 xe-3-3-0.cr1.lga5.us.above.net [64.125.25.42]
8 xe-1-0-1.er1.lga5.us.above.net [64.125.26.162]
9 above-qwest.lga5.us.above.net [64.125.13.246]
10 dvn-edge-04.inet.qwest.net [205.171.164.70]
11 205.168.6.94
12 * * *
Computing statistics for 275 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Jeremy-PC
0/ 100 = 0% |
1 4ms 0/ 100 = 0% 0/ 100 = 0%
0/ 100 = 0% |
2 140ms 0/ 100 = 0% 0/ 100 = 0% d-ptld-bng1-64-222-214-1.ngn.east.
myfairpoint.net [64.222.214.1]
0/ 100 = 0% |
3 142ms 0/ 100 = 0% 0/ 100 = 0% pool-64-222-213-19.port.east.myfai
rpoint.net [64.222.213.19]
0/ 100 = 0% |
4 140ms 0/ 100 = 0% 0/ 100 = 0% pool-64-222-213-134.port.east.myfa
irpoint.net [64.222.213.134]
0/ 100 = 0% |
5 146ms 0/ 100 = 0% 0/ 100 = 0% xe-3-2-0.mpr4.bos2.us.above.net [2
08.184.223.233]
0/ 100 = 0% |
6 151ms 0/ 100 = 0% 0/ 100 = 0% xe-1-0-0.mpr3.bos2.us.above.net [6
4.125.25.65]
0/ 100 = 0% |
7 153ms 0/ 100 = 0% 0/ 100 = 0% xe-3-3-0.cr1.lga5.us.above.net [64
.125.25.42]
0/ 100 = 0% |
8 153ms 0/ 100 = 0% 0/ 100 = 0% xe-1-0-1.er1.lga5.us.above.net [64
.125.26.162]
0/ 100 = 0% |
9 152ms 0/ 100 = 0% 0/ 100 = 0% above-qwest.lga5.us.above.net [64.
125.13.246]
0/ 100 = 0% |
10 --- 100/ 100 =100% 100/ 100 =100% dvn-edge-04.inet.qwest.net [205.17
1.164.70]
0/ 100 = 0% |
11 187ms 0/ 100 = 0% 0/ 100 = 0% 205.168.6.94
Trace complete.
C:\Users\Jeremy> |
|
| going from the other way:
Host Drop Rcv Avg Gmean Jttr Javg Jmax Jint
1. 192.168.91.1 5 2745 1.3 1.2 0.0 2.0 114. 22.2
2. 216.227.0.132 9 2740 44.6 42.8 6.0 8.2 262. 69.4
3. 216.227.0.49 2 2747 44.3 42.6 11.3 7.6 169. 75.4
4. 216.227.0.5 2 2747 43.9 42.4 0.0 6.7 164. 65.1
5. 71.161.104.61 4 2745 52.1 48.6 1.3 13.4 338. 123.
6. 64.222.213.25 7 2742 50.4 47.6 2.6 10.8 252. 64.0
7. 64.222.214.1 9 2740 47.9 46.2 4.1 7.2 161. 66.0
looks like it's from you to 64.222.214.1
line issue modem issue or your router issue.... sorry bud I would call and get another tech out, be polite,and firm and ask for a supervisor in the call center...be even headed...ask for this to be resolved explain how long you have been having degraded service. |
|
Reviews:
·Verizon Wireless..
·Great Works Inte..
| reply to Suzie
Well its not my router/modem because i have 4 of them, ive tried all of them. Thats what they thought it was too thats why they keep sending me new ones. It's not the wiring in my house because my house is only 6 years old. If they keep sending tech guys out during the day theyre just gonna keep seeing good readings because the problem starts every night. I feel like im talking to a brick wall when i have to repeat myself to them over and over like a broken record. Theres clearly a problem at the second hop theyve got too many people on the switch/router or whatevers there..im no expert, because its creating a problem/congestion once everyone gets out of work and wants to be on the internet at the same time. I'll try again tomorrow to call them i dont know what good its gonna do though. I hate sounding like a whiner but its annoying me pretty bad i dont know what else to do. |
|
tschmidtPremium,MVM
join:2000-11-12
Milford, NH
kudos:8 Reviews:
·G4 Communications
·Fairpoint Commun..
·Hollis Hosting
1 edit | said by Jeremy1976:Well its not my router/modem because i have 4 of them, ive tried all of them.
The high latency is showing up at the FairPoint edge router, the 2nd hop in your traceroute. So the congestion is between the DSLAM in the central office and that. Unfortunately the details are hidden because traffic is carried over ATM.
/tom |
|
| I forgot completely about the ATM bit..thanks! |
|
Reviews:
·Verizon Wireless..
·Great Works Inte..
| reply to Suzie
Home again today..rained out. Here we go, another typical day. Oh btw what is the ATM? What is with the 100% packet loss at hop 10 on qwest? that cant be helping the situation.
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Jeremy>pathping 64.22.213.136
Tracing route to network-136.rmexp-iedsl.netexpress.net [64.22.213.136]
over a maximum of 30 hops:
0 Jeremy-PC
1 CISCO96618
2 d-ptld-bng1-64-222-214-1.ngn.east.myfairpoint.net [64.222.214.1]
3 pool-64-222-213-19.port.east.myfairpoint.net [64.222.213.19]
4 pool-64-222-213-134.port.east.myfairpoint.net [64.222.213.134]
5 xe-3-2-0.mpr4.bos2.us.above.net [208.184.223.233]
6 xe-1-0-0.mpr3.bos2.us.above.net [64.125.25.65]
7 xe-3-3-0.cr1.lga5.us.above.net [64.125.25.42]
8 xe-0-0-1.er1.lga5.us.above.net [64.125.27.61]
9 above-qwest.lga5.us.above.net [64.125.13.246]
10 dvn-edge-04.inet.qwest.net [205.171.164.70]
11 205.168.6.94
12 * * *
Computing statistics for 275 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Jeremy-PC
0/ 100 = 0% |
1 4ms 0/ 100 = 0% 0/ 100 = 0% CISCO96618
0/ 100 = 0% |
2 54ms 0/ 100 = 0% 0/ 100 = 0% d-ptld-bng1-64-222-214-1.ngn.east.
myfairpoint.net [64.222.214.1]
0/ 100 = 0% |
3 53ms 0/ 100 = 0% 0/ 100 = 0% pool-64-222-213-19.port.east.myfai
rpoint.net [64.222.213.19]
0/ 100 = 0% |
4 49ms 0/ 100 = 0% 0/ 100 = 0% pool-64-222-213-134.port.east.myfa
irpoint.net [64.222.213.134]
0/ 100 = 0% |
5 56ms 0/ 100 = 0% 0/ 100 = 0% xe-3-2-0.mpr4.bos2.us.above.net [2
08.184.223.233]
0/ 100 = 0% |
6 60ms 0/ 100 = 0% 0/ 100 = 0% xe-1-0-0.mpr3.bos2.us.above.net [6
4.125.25.65]
0/ 100 = 0% |
7 66ms 0/ 100 = 0% 0/ 100 = 0% xe-3-3-0.cr1.lga5.us.above.net [64
.125.25.42]
0/ 100 = 0% |
8 62ms 0/ 100 = 0% 0/ 100 = 0% xe-0-0-1.er1.lga5.us.above.net [64
.125.27.61]
0/ 100 = 0% |
9 65ms 0/ 100 = 0% 0/ 100 = 0% above-qwest.lga5.us.above.net [64.
125.13.246]
0/ 100 = 0% |
10 --- 100/ 100 =100% 100/ 100 =100% dvn-edge-04.inet.qwest.net [205.17
1.164.70]
0/ 100 = 0% |
11 93ms 0/ 100 = 0% 0/ 100 = 0% 205.168.6.94
Trace complete.
C:\Users\Jeremy>tracert 64.22.213.136
Tracing route to network-136.rmexp-iedsl.netexpress.net [64.22.213.136]
over a maximum of 30 hops
1 3 ms 3 ms 3 ms CISCO96618
2 47 ms 47 ms 47 ms d-ptld-bng1-64-222-214-1.ngn.east.myfairpoint.ne
t [64.222.214.1]
3 47 ms 47 ms 47 ms pool-64-222-213-19.port.east.myfairpoint.net [64
.222.213.19]
4 48 ms 47 ms 47 ms pool-64-222-213-134.port.east.myfairpoint.net [6
4.222.213.134]
5 51 ms 50 ms 51 ms xe-3-2-0.mpr4.bos2.us.above.net [208.184.223.233
]
6 52 ms 99 ms 51 ms xe-1-0-0.mpr3.bos2.us.above.net [64.125.25.65]
7 57 ms 57 ms 60 ms xe-3-3-0.cr1.lga5.us.above.net [64.125.25.42]
8 59 ms 57 ms 67 ms xe-0-0-1.er1.lga5.us.above.net [64.125.27.61]
9 57 ms 56 ms 57 ms above-qwest.lga5.us.above.net [64.125.13.246]
10 80 ms 80 ms 80 ms dvn-edge-04.inet.qwest.net [205.171.164.70]
11 85 ms 86 ms 91 ms 205.168.6.94
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete. |
|
| the loss at quest could be that the router is not acknowledging ICMP (the protocol that trace/ping)requests...could be meaningless we don't know.
ATM is how the information is sent across FairPoints network »en.wikipedia.org/wiki/Asynchrono···fer_Mode
the only part of the trace that Fairpoint has direct control over, hops 2 - 4. the first is your home network the other is the peering point to above net. |
|
