Your hosting provider has a sick, sick upstream connection

[pyld]

Not that windows is good for this, but...

Their XO upstream hop in Michigan is dropping about half of all packets going in (and judging by the performance of the site right now, coming out). Page load times measured in minutes. It does appear to be transit related.

[FNG19]

Not that windows is good for this, but...

Their XO upstream hop in Michigan is dropping about half of all packets going in (and judging by the performance of the site right now, coming out). Page load times measured in minutes. It does appear to be transit related.

+1. Here's the mtr output taken at the time of this writing... and this represents an improvement over an hour ago.

                                       Packets               Pings
 Host                                Loss%   Snt   Last   Avg  Best  Wrst StDev
 6. 0.ae2.BR2.IAD8.ALTER.NET          0.0%    50   18.5  23.0  16.6  85.2  15.0
 7. ae7.edge1.washingtondc4.level3.n  0.0%    50   16.9  21.1  16.5  82.3  12.8
 8. vlan80.csw3.Washington1.Level3.n  0.0%    50   18.3  19.6  17.1  48.5   5.2
 9. ae-92-92.ebr2.Washington1.Level3  0.0%    50   20.4  18.9  17.3  33.6   2.8
10. ae-5-5.ebr2.Washington12.Level3.  0.0%    49   18.7  19.0  17.6  24.0   1.2
11. ae-6-6.ebr2.Chicago2.Level3.net   0.0%    49   36.4  36.3  34.8  51.7   2.7
12. ae-5-5.ebr2.Chicago1.Level3.net   0.0%    49   42.6  40.1  35.2  61.5   5.7
13. ae-8-8.car1.Detroit1.Level3.net   0.0%    49   41.6  63.2  40.6 202.6  47.2
14. ae-11-11.car2.Detroit1.Level3.ne  0.0%    49   39.0  63.8  38.9 229.5  53.1
15. NETWORK-INN.car2.Detroit1.Level3 28.6%    49   50.0  52.6  45.8 239.9  32.6
16. g2-0.core2.troy2.waveform.net    28.6%    49   44.9  44.6  43.5  49.8   1.1
17. www1.pafoa.net                   30.6%    49   48.2  51.5  45.5 198.6  26.0

[LifeInPa]

Yeah what's the deal? This website is taking forever to load any page or it tells me the connection has been reset. It's very frustrating.

[The_War_Wagon]

It is DEFINITELY draggin' ass tonite!

[bac0nfat]

Glad to know it wasn't just me. I have noticed this a few times in the past too.

Anyone else feel totally lost without PAFOA?

[pyld]

Just did it again. This pathping from southern butler county:

Tracing route to forum.pafoa.org [208.92.217.245]
over a maximum of 30 hops:
0 deleted
1 192.168.1.1
2 dynamic-acs-24-239-117-1.zoominternet.net [24.239.117.1]
3 dynamic-acs-24-101-13-51.zoominternet.net [24.101.13.51]
4 static-acs-24-154-0-189.zoominternet.net [24.154.0.189]
5 * 207.88.183.33.ptr.us.xo.net [207.88.183.33]
6 vb1004.rar3.washington-dc.us.xo.net [207.88.14.117]
7 ae0d0.mcr2.southfield-mi.us.xo.net [216.156.0.190]
8 ip65-46-187-10.z187-46-65.customer.algx.net [65.46.187.10]
9 g2-2.core2.troy2.waveform.net [216.29.182.174]
10 www3.pafoa.net [208.92.217.245]

Computing statistics for 250 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 deleted
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 9ms 0/ 100 = 0% 0/ 100 = 0% dynamic-acs-24-239-117-1.zoominternet.net [24.239.117.1]
0/ 100 = 0% |
3 10ms 0/ 100 = 0% 0/ 100 = 0% dynamic-acs-24-101-13-51.zoominternet.net [24.101.13.51]
0/ 100 = 0% |
4 16ms 0/ 100 = 0% 0/ 100 = 0% static-acs-24-154-0-189.zoominternet.net [24.154.0.189]
0/ 100 = 0% |
5 32ms 0/ 100 = 0% 0/ 100 = 0% 207.88.183.33.ptr.us.xo.net [207.88.183.33]
0/ 100 = 0% |
6 27ms 0/ 100 = 0% 0/ 100 = 0% vb1004.rar3.washington-dc.us.xo.net [207.88.14.117]
0/ 100 = 0% |
7 38ms 0/ 100 = 0% 0/ 100 = 0% ae0d0.mcr2.southfield-mi.us.xo.net
[216.156.0.190]
0/ 100 = 0% |
8 35ms 0/ 100 = 0% 0/ 100 = 0% ip65-46-187-10.z187-46-65.customer.algx.net [65.46.187.10]
0/ 100 = 0% |
9 --- 100/ 100 =100% 100/ 100 =100% g2-2.core2.troy2.waveform.net [216.29.182.174]
0/ 100 = 0% |
10 37ms 0/ 100 = 0% 0/ 100 = 0% www3.pafoa.net [208.92.217.245]

Trace complete.

You have a massively broken upstrem connection at your host. Or it's getting slammed. If I had a host where I could approach them thru the level3 upstream, I suspect I'd find the same based on other posts above from last night.

[FNG19]

Pyld, here's what I'm seeing:

                                       Packets               Pings
 Host                                Loss%   Snt   Last   Avg  Best  Wrst StDev
 5. so-8-0-0-0.LCC1-RES-BB-RTR1-RE1.  0.0%    30   18.8  23.7  17.1  65.5  13.9
 6. 0.ae1.BR1.IAD8.ALTER.NET          0.0%    30   20.0  20.5  18.7  37.9   4.0
 7. te9-2-0d0.cir1.ashburn-va.us.xo.  0.0%    30   20.1  23.1  19.8  53.3   6.8
 8. vb2000d1.rar3.washington-dc.us.x  0.0%    30   22.8  23.7  21.3  35.1   2.7
 9. ae0d0.mcr2.southfield-mi.us.xo.n  0.0%    30   39.6  40.4  38.7  55.8   3.7
10. ip65-46-187-10.z187-46-65.custom  0.0%    30   38.8  35.9  34.9  38.8   0.7
11. g2-2.core2.troy2.waveform.net     0.0%    30   38.2  38.4  37.4  40.0   0.7
12. www2.pafoa.net                    0.0%    30   37.2  37.3  35.7  42.1   1.5

From where I'm sitting, the problem appears resolved. That said, it's also worth noting that my path to the forum no longer takes me through Level3. I'm well aware that routes change as network conditions evolve, but I thought it was worth pointing out. It doesn't mean that Level3 isn't still having problems. It simply means I'm not seeing those issues anymore.

Then again, Dan hasn't been on in a week, so I'm not sure if he's even aware that there is (or was) an issue.

[pyld]

From where I'm sitting, the problem appears resolved. That said, it's also worth noting that my path to the forum no longer takes me through Level3. I'm well aware that routes change as network conditions evolve, but I thought it was worth pointing out. It doesn't mean that Level3 isn't still having problems. It simply means I'm not seeing those issues anymore.

Yeah, I don't have (at home) the ability to influence routing enough to check level-3 path. I do at work, and will check if it bombs again.

I'll bet the host has someone getting DDOSed.

[LifeInPa]

Haven't had any issues so far today.

[FNG19]

Yeah, I don't have (at home) the ability to influence routing enough to check level-3 path. I do at work, and will check if it bombs again.

Oh, even from home, I have no ability to influence my routing. I was more remarking on the resiliency of modern network protocols and connectivity, and recognizing the fact that the route changed drastically from last night.

I'll bet the host has someone getting DDOSed.

Certainly possible -- good point!