Site really slow

FyreWulff

PA's timing out on me / taking really long to load.

Microsoft Windows [Version 6.1.7100]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

ping www.google.com

Pinging www.l.google.com [209.85.225.147] with 32 bytes of data:
Reply from 209.85.225.147: bytes=32 time=50ms TTL=55
Reply from 209.85.225.147: bytes=32 time=49ms TTL=55
Reply from 209.85.225.147: bytes=32 time=55ms TTL=55
Reply from 209.85.225.147: bytes=32 time=44ms TTL=55

Ping statistics for 209.85.225.147:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 44ms, Maximum = 55ms, Average = 49ms

ping www.penny-arcade.com

Pinging www.penny-arcade.com [208.81.201.34] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 208.81.201.34:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

tracert www.penny-arcade.com

Tracing route to www.penny-arcade.com [208.81.201.34]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     9 ms    16 ms    17 ms  ip68-229-166-1.om.om.cox.net [68.229.166.1]
  3     8 ms    22 ms    13 ms  68.13.8.225
  4    10 ms    11 ms    18 ms  mtc1dsrj02-xe210.0.rd.om.cox.net [68.13.14.13]
  5    24 ms    33 ms    36 ms  dalsbbrj02-ae2.0.r2.dl.cox.net [68.1.1.243]
  6    24 ms    23 ms    35 ms  te2-4.ccr02.dfw01.atlas.cogentco.com [154.54.6.61]
  7    32 ms    46 ms    32 ms  te8-4.ccr02.iah01.atlas.cogentco.com [154.54.3.178]
  8     *      117 ms    85 ms  te9-2.ccr02.lax01.atlas.cogentco.com [154.54.3.186]
  9    82 ms    80 ms    84 ms  te9-1.mpd02.lax01.atlas.cogentco.com [154.54.25.166]
 10   121 ms    86 ms    82 ms  vl3811.na31.b020604-0.lax01.atlas.cogentco.com [38.20.38.154]
 11    80 ms     *       75 ms  ge3-3-lax3-border.3jane.com [38.99.221.46]
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.

etc


edit: just in case, running it specifically on forums.penny-arcade.com :

tracert forums.penny-arcade.com

Tracing route to forums.penny-arcade.com [208.81.201.38]

1     1 ms    <1 ms    <1 ms  192.168.1.1
  2    18 ms     8 ms    17 ms  ip68-229-166-1.om.om.cox.net [68.229.166.1]
  3     7 ms    18 ms    13 ms  68.13.8.225
  4    11 ms    29 ms     8 ms  mtc1dsrj02-xe210.0.rd.om.cox.net [68.13.14.13]
  5    24 ms    26 ms    31 ms  dalsbbrj02-ae2.0.r2.dl.cox.net [68.1.1.243]
  6    29 ms    28 ms    25 ms  te9-1.ccr02.dfw01.atlas.cogentco.com [66.28.4.133]
  7    42 ms    71 ms    27 ms  te2-2.ccr01.iah01.atlas.cogentco.com [154.54.25.218]
  8    81 ms    92 ms    93 ms  te9-2.ccr01.lax01.atlas.cogentco.com [154.54.0.237]
  9    89 ms    83 ms    79 ms  te7-1.mpd02.lax01.atlas.cogentco.com [154.54.3.78]
 10    88 ms    76 ms    76 ms  vl3811.na31.b020604-0.lax01.atlas.cogentco.com [38.20.38.154]
 11    77 ms    79 ms    87 ms  ge3-3-lax3-border.3jane.com [38.99.221.46]
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.

ASimPerson

The site is plenty responsive for me. I got the same ping/tracerotue responses, which likely indicates that ICMP is being filtered at their gateway (i.e., the last hop before it starts timing out).

FYI, I have Comcast in the SF Bay Area. It's likely a problem with your ISP or one of their upstream providers (your average ping more than doubles on the way from Houston to LA, for instance).

FyreWulff

Still extremely slow here.

Takes about 10-15 seconds to load pages, every other site on the internet is still super fast.

I have to reload about every 5 pages because I'll only get half the page.

ASimPerson

FYI, as reported in H/A, there was a fiber cut in Arizona that affected Cox traffic to/from the West Coast today.

http://forums.penny-arcade.com/showthread.php?t=111505

FyreWulff

Interesting, but I'm in Nebraska, and it was only affecting PA. It could have contributed, though.

I'll be posting again if it starts effin' up during peak hours again.

ASimPerson

Well, indeed, but from your traceroute it appears that at the time your packets were getting routed to LA (where PA's servers are apparently located) via Dallas and Houston. Your ping was doubling between Houston and LA, and Arizona is sort of "on the way" so it makes sense.

Chances are they either fixed it by now or they're routing around it. If you run traceroute again, it'll be the same route if it's the former and different if it's latter.

Älphämönkëy

Our servers are indeed in LA

Our cogent peering always seems to be the culprit, though I'm going to bet that the severed connection in AZ caused your latency problems either directly through rerouting, or indirectly through a bunch of unexpected traffic getting rerouted.

I've come to the realization that BGP is closer to a religion than a software protocol.

ASimPerson

alphamonkey wrote: »

I've come to the realization that BGP is closer to a religion than a software protocol.

Yeah, pretty much.