Peak time latency spikes

[#1]

Some of you will be aware that we've been seeing some latency spikes and performance problems for a couple of hours in the evening over the past week. These issues are centered around those customers that are connected on the gateways that start with PCL, you can see which gateway you're connected to here: http://usertools.plus.net/@gateway
We've been working with our hardware vendors to diagnose and resolve this problem and have been gathering data over recent days to help get to the bottom of the issue and resolve it once and for all.
If you do experience a spike in your latency, or start to see sluggish browsing or streaming problems and are connected to a PCL gateway then we'd suggest logging in to your router, disconnect and reconnecting until you are on a gateway that doesn't start with PCL.

[#2]

Hi guys,
Quick update for you.  We'll be running a debug session tonight to gather a bit more information.  It will affect customers on PCL-AG01 and PCL-AG02 but shouldn't be apparent for more than 30 minutes.  Symptoms of this will be the latency spikes and slower than normal speeds you've been seeing over the last week.  
If you are affected, feel free to disconnect and reconnect to connect to a different gateway.

[#3]

Thanks guys 

[#4]

ive just had pings of 300 again and had to jump gatewys. Im on ptw-ag04 now and pings have gone back to normal ill see how this goes.

[#5]

I am on ptw-ag01 my ping 160ms+ where it is normally 30ms. I am going to try to reconnect the router.

[#6]

Yep.  We've got the problem again tonight.  Disconnect and reconnect to try and get off the affected gateways.

[#7]

Quote from: Oxslow

I am on ptw-ag01 my ping 160ms+ where it is normally 30ms. I am going to try to reconnect the router.

Exactly the same for me, I upgraded from Unlimited from Value fibre and dropped the Pro Add on so, I hope its not because of that.

[#8]

No, not to do with that.  It's a general issue.   

[#9]

ok thanks Kelly.
yes pings around 150 at the mo, normally its 30

[#10]

Ouch, just done a few cmd prompt pings
Pinging ntp.plus.net [212.159.6.10] with 32 bytes of data:
Reply from 212.159.6.10: bytes=32 time=141ms TTL=246
Reply from 212.159.6.10: bytes=32 time=155ms TTL=246
Reply from 212.159.6.10: bytes=32 time=154ms TTL=246
Reply from 212.159.6.10: bytes=32 time=157ms TTL=246
Ping statistics for 212.159.6.10:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 141ms, Maximum = 157ms, Average = 151ms
Normally circa 39/40mS on pcl-ag04 (20CN).

[#11]

I just logged into router as recommended by someone on this forums, disconnected, then reconnect, lower ping now.

[#12]

Kelly I know you are working on PCL-AG01 and PCL-AG02 this evening, but Chris did mention PCL as a whole (I'm currently on PCL-AG07 [21CN]), and the ping graphs have looked very similar over the last 2 nights
Monday:

Tuesday:

[#13]

On pcl-ag07 (21CN), outgoing pings are normal
Ping statistics for 212.159.6.9:
    Packets: Sent = 25, Received = 25, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 29ms, Maximum = 34ms, Average = 30ms
but the ping monitor (incoming) shows minimum 30ms, average around 35ms, peak 60ms, very similar to MsDizzie.

[#14]

I believe those small lifts you are seeing are due to more general business because of the iOS update release and because we are lighting some more bandwidth next week.

[#15]

Seems pretty much back to normal here at the moment, pcl-ag04 20CN
Pinging ntp.plus.net [212.159.6.10] with 32 bytes of data:
Reply from 212.159.6.10: bytes=32 time=39ms TTL=246
Reply from 212.159.6.10: bytes=32 time=40ms TTL=246
Reply from 212.159.6.10: bytes=32 time=38ms TTL=246
Reply from 212.159.6.10: bytes=32 time=38ms TTL=246
Ping statistics for 212.159.6.10:
   Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
   Minimum = 38ms, Maximum = 40ms, Average = 38ms