Site seems really slow today

I'm getting ping times in the 70-80 mS range.  Yours are in the the 2-3000 mS range.  Something fishy here, but I don't believe it is the server.

Howard, can you do the following, and post the result up here?  Thanks.

tracert 68.171.217.195

-Allen

I missed the molasses windows today. I will do a traceroute next time I experience a slowdown.

I missed the molasses windows today. I will do a traceroute next time I experience a slowdown.

Me too.  Currently looking good:

C:\Users\asatre>tracert 68.171.217.195

Tracing route to 195.217.171.68.securenet-server.net [68.171.217.195]
over a maximum of 30 hops:

  1     2 ms     1 ms     1 ms  192.168.60.1
  2     2 ms     1 ms     1 ms  future-208-85-42-1.pandora.com [208.85.42.1]
  3     4 ms     2 ms     2 ms  sjo-bb1-link.telia.net [62.115.46.245]
  4    54 ms    54 ms    52 ms  chi-b21-link.telia.net [213.248.80.24]
  5    59 ms    59 ms    59 ms  123net-ic-304910-chi-b21.c.telia.net [62.115.38.246]
  6    60 ms    60 ms    60 ms  138.209.171.68.securenet-server.net [68.171.209.138]
  7    60 ms    60 ms    59 ms  195.217.171.68.securenet-server.net [68.171.217.195]

Trace complete.

Had lots of timeouts last time I did a trace.

Results a bit squished

FYI, I am using a new cable modem but was having the slowdown long before replacing the old one.

That ping above the tracert was the previous one you did earlier today, right?

When you have a slowdown, can you do both a new ping and a new traceroute when reporting the results?  Thanks.

-Allen

Will do.

So I let ping run continuously for the past hour by using the -t option.  I saw ping times up to 548 mS, with the average being 94 mS.  That's not too alarming to me and does explain an extreme slowdown some of you are seeing.

-Allen

D:\>tracert 68.171.217.195

Tracing route to 195.217.171.68.securenet-server.net [68.171.217.195]
over a maximum of 30 hops:

  1     2 ms    <1 ms    <1 ms  192.168.1.1
  2     7 ms     8 ms    11 ms  astound-66-234-209-1.ca.astound.net [66.234.209.1]
  3     7 ms     6 ms     9 ms  204-195-91-33.wavecable.com [204.195.91.33]
  4     8 ms    12 ms    11 ms  76-14-93-249.sf-cable.astound.net [76.14.93.249]

  5    12 ms    10 ms    11 ms  76-14-93-242.sf-cable.astound.net [76.14.93.242]

  6    10 ms    11 ms    12 ms  cr1-200p-a-be-100.bb.spectrumnet.us [208.76.187.5]
  7    10 ms    12 ms    10 ms  te0-0-1-0.rcr12.b003070-1.sfo01.atlas.cogentco.com [38.122.64.97]
  8     9 ms    11 ms    10 ms  be2452.ccr21.sfo01.atlas.cogentco.com [154.54.28.69]
  9    46 ms    49 ms    47 ms  be2132.ccr21.mci01.atlas.cogentco.com [154.54.30.54]
 10    61 ms    57 ms    61 ms  be2156.ccr41.ord01.atlas.cogentco.com [154.54.6.86]
 11    66 ms    70 ms    66 ms  be2351.ccr21.cle04.atlas.cogentco.com [154.54.44.86]
 12    72 ms    68 ms    69 ms  be2006.rcr21.dtw04.atlas.cogentco.com [154.54.5.10]
 13    67 ms    68 ms    67 ms  38.122.60.46
 14    68 ms    67 ms    71 ms  138.209.171.68.securenet-server.net [68.171.209.138]
 15  3913 ms  2860 ms  2911 ms  195.217.171.68.securenet-server.net [68.171.217.195]

Trace complete.

D:\>time /t
01:36 PM

D:\>tracert 68.171.217.195

Tracing route to 195.217.171.68.securenet-server.net [68.171.217.195]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    10 ms    10 ms    10 ms  astound-66-234-209-1.ca.astound.net [66.234.209.1]
  3     7 ms     6 ms     8 ms  204-195-91-33.wavecable.com [204.195.91.33]
  4     8 ms     9 ms    10 ms  76-14-93-249.sf-cable.astound.net [76.14.93.249]

  5     8 ms    17 ms    10 ms  76-14-93-242.sf-cable.astound.net [76.14.93.242]

  6    11 ms    10 ms    12 ms  cr1-200p-a-be-100.bb.spectrumnet.us [208.76.187.5]
  7    12 ms    12 ms    11 ms  te0-0-1-0.rcr12.b003070-1.sfo01.atlas.cogentco.com [38.122.64.97]
  8    17 ms    11 ms    11 ms  be2452.ccr21.sfo01.atlas.cogentco.com [154.54.28.69]
  9    49 ms    50 ms    50 ms  be2132.ccr21.mci01.atlas.cogentco.com [154.54.30.54]
 10    59 ms    61 ms    62 ms  be2156.ccr41.ord01.atlas.cogentco.com [154.54.6.86]
 11    70 ms    69 ms    67 ms  be2351.ccr21.cle04.atlas.cogentco.com [154.54.44.86]
 12    69 ms    69 ms    70 ms  be2006.rcr21.dtw04.atlas.cogentco.com [154.54.5.10]
 13    67 ms    72 ms    67 ms  38.122.60.46
 14    70 ms    66 ms    98 ms  138.209.171.68.securenet-server.net [68.171.209.138]
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *     3781 ms  2862 ms  195.217.171.68.securenet-server.net [68.171.217.195]

Trace complete.

D:\>time /t
01:41 PM

Took 11 seconds to load this page after clicking reply:

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

C:\Users\asatre>tracert 68.171.217.195

Tracing route to 195.217.171.68.securenet-server.net [68.171.217.195]
over a maximum of 30 hops:

  1     2 ms     2 ms     2 ms  172.23.12.1
  2     3 ms     3 ms     3 ms  vlan-103.br2.sv1.corp.equinix.com [216.221.228.3
]
  3     2 ms     3 ms     2 ms  vlan-103.br1.sv1.corp.equinix.com [216.221.228.2
]
  4    55 ms    55 ms    55 ms  f2-0-2849.br1.ch3.equinix.net [64.191.206.186]
  5     *        *        *     Request timed out.
  6    62 ms    62 ms    67 ms  i123.edge2.chicago2.level3.net [4.35.98.106]
  7    62 ms    61 ms    63 ms  138.209.171.68.securenet-server.net [68.171.209.
138]
  8  2869 ms  2911 ms  2807 ms  195.217.171.68.securenet-server.net [68.171.217.
195]

Trace complete.

C:\Users\asatre>ping 68.171.217.195

Pinging 68.171.217.195 with 32 bytes of data:
Reply from 68.171.217.195: bytes=32 time=1358ms TTL=54
Reply from 68.171.217.195: bytes=32 time=1556ms TTL=54
Reply from 68.171.217.195: bytes=32 time=1767ms TTL=54
Reply from 68.171.217.195: bytes=32 time=1871ms TTL=54

Ping statistics for 68.171.217.195:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1358ms, Maximum = 1871ms, Average = 1638ms

C:\Users\asatre>

That was 1 min ago.

Pinged one more time, quite a difference!

C:\Users\asatre>ping 68.171.217.195

Pinging 68.171.217.195 with 32 bytes of data:
Reply from 68.171.217.195: bytes=32 time=63ms TTL=54
Reply from 68.171.217.195: bytes=32 time=66ms TTL=54
Reply from 68.171.217.195: bytes=32 time=63ms TTL=54
Reply from 68.171.217.195: bytes=32 time=63ms TTL=54

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

Oh, but i'm on a different network than yesterday, so not a great comparison on my previous trace.

Nice.  This gives me something I can file with my datacenter.   

I'm currently seeing ping time as high as 1086 ms with an average of 146, not nearly as bad as you guys, but definitely shows something is slowing down at this time of the day.

-Allen

Question for you slow users ... did the window of slowdown change any after this weekends time change?

-Allen

Seems to be around the same local time, regardless of daylight savings.

D:\>date /t
Wed 03/11/2015

D:\>ping 68.171.217.195

Pinging 68.171.217.195 with 32 bytes of data:

Reply from 68.171.217.195: bytes=32 time=3879ms TTL=51
Reply from 68.171.217.195: bytes=32 time=3324ms TTL=51
Reply from 68.171.217.195: bytes=32 time=2710ms TTL=51
Reply from 68.171.217.195: bytes=32 time=3789ms TTL=51

Ping statistics for 68.171.217.195:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 2710ms, Maximum = 3879ms, Average = 3425ms

D:\>time /t
01:28 PM

D:\>tracert 68.171.217.195

Tracing route to 195.217.171.68.securenet-server.net [68.171.217.195]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    11 ms     8 ms     8 ms  astound-66-234-209-1.ca.astound.net [66.234.209.1]
  3    10 ms     7 ms     8 ms  204-195-91-33.wavecable.com [204.195.91.33]
  4    12 ms    11 ms     8 ms  76-14-93-249.sf-cable.astound.net [76.14.93.249]
  5    11 ms     8 ms    11 ms  76-14-93-242.sf-cable.astound.net [76.14.93.242]
  6     9 ms    11 ms    11 ms  cr1-200p-a-be-100.bb.spectrumnet.us [208.76.187.5]
  7    11 ms    12 ms    11 ms  te0-0-1-0.rcr12.b003070-1.sfo01.atlas.cogentco.com [38.122.64.97]
  8    12 ms    10 ms    12 ms  be2452.ccr21.sfo01.atlas.cogentco.com [154.54.28.69]
  9    54 ms    47 ms    49 ms  be2132.ccr21.mci01.atlas.cogentco.com [154.54.30.54]
 10    62 ms    60 ms    60 ms  be2156.ccr41.ord01.atlas.cogentco.com [154.54.6.86]
 11    69 ms    67 ms    68 ms  be2351.ccr21.cle04.atlas.cogentco.com [154.54.44.86]
 12    69 ms    67 ms    68 ms  be2006.rcr21.dtw04.atlas.cogentco.com [154.54.5.10]
 13    67 ms    70 ms    69 ms  38.122.60.46
 14    69 ms    68 ms    69 ms  138.209.171.68.securenet-server.net [68.171.209.138]
 15  3102 ms  3225 ms  2960 ms  195.217.171.68.securenet-server.net [68.171.217.195]

Trace complete.

D:\>time /t
01:31 PM

D:\>tracert 68.171.217.195

Tracing route to 195.217.171.68.securenet-server.net [68.171.217.195]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    10 ms     7 ms     8 ms  astound-66-234-209-1.ca.astound.net [66.234.209.1]
  3     8 ms     8 ms     7 ms  204-195-91-33.wavecable.com [204.195.91.33]
  4     9 ms    17 ms    10 ms  76-14-93-249.sf-cable.astound.net [76.14.93.249]
  5     9 ms    10 ms    17 ms  76-14-93-242.sf-cable.astound.net [76.14.93.242]
  6    10 ms    11 ms     8 ms  cr1-200p-a-be-100.bb.spectrumnet.us [208.76.187.5]
  7    10 ms    12 ms    12 ms  te0-0-1-0.rcr12.b003070-1.sfo01.atlas.cogentco.com [38.122.64.97]
  8    11 ms    11 ms    13 ms  be2452.ccr21.sfo01.atlas.cogentco.com [154.54.28.69]
  9    46 ms    48 ms    48 ms  be2132.ccr21.mci01.atlas.cogentco.com [154.54.30.54]
 10    61 ms    59 ms    60 ms  be2156.ccr41.ord01.atlas.cogentco.com [154.54.6.86]
 11    69 ms    68 ms    68 ms  be2351.ccr21.cle04.atlas.cogentco.com [154.54.44.86]
 12    69 ms    69 ms    70 ms  be2006.rcr21.dtw04.atlas.cogentco.com [154.54.5.10]
 13    69 ms    67 ms    68 ms  38.122.60.46
 14    70 ms    68 ms    67 ms  138.209.171.68.securenet-server.net [68.171.209.138]
 15  3151 ms  3170 ms  3174 ms  195.217.171.68.securenet-server.net [68.171.217.195]

Trace complete.

D:\>time /t
01:46 PM

Thanks guys.  I have what I need and filed a ticket with the datacenter.  We'll see what they come up with.

-Allen