Day worth of pings !

[Djwindas]

full days results very interesting. obviously there must be alot of spikes.

Ping statistics for ***********:
    Packets: Sent = 35267, Received = 35091, Lost = 176 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 22ms, Maximum = 1562ms, Average = 48ms
Control-C
^CTerminate batch job (Y/N)?

[Blueflame]

It had a pissy fit today, kept dropping out and pings like this. Then in an instant, perfect again.

Pinging www.bbc.net.uk [212.58.244.69] with 32 bytes of data
Reply from 212.58.244.69: bytes=32 time=36ms TTL=56
Reply from 212.58.244.69: bytes=32 time=78ms TTL=56
Reply from 212.58.244.69: bytes=32 time=148ms TTL=56
Reply from 212.58.244.69: bytes=32 time=113ms TTL=56
Reply from 212.58.244.69: bytes=32 time=173ms TTL=56
Reply from 212.58.244.69: bytes=32 time=48ms TTL=56
Reply from 212.58.244.69: bytes=32 time=25ms TTL=56
Reply from 212.58.244.69: bytes=32 time=127ms TTL=56
Reply from 212.58.244.69: bytes=32 time=17ms TTL=56
Reply from 212.58.244.69: bytes=32 time=275ms TTL=56
Reply from 212.58.244.69: bytes=32 time=36ms TTL=56
Reply from 212.58.244.69: bytes=32 time=102ms TTL=56
Reply from 212.58.244.69: bytes=32 time=110ms TTL=56
Reply from 212.58.244.69: bytes=32 time=33ms TTL=56
Reply from 212.58.244.69: bytes=32 time=130ms TTL=56
Reply from 212.58.244.69: bytes=32 time=150ms TTL=56
Reply from 212.58.244.69: bytes=32 time=100ms TTL=56
Reply from 212.58.244.69: bytes=32 time=92ms TTL=56
Reply from 212.58.244.69: bytes=32 time=34ms TTL=56
Reply from 212.58.244.69: bytes=32 time=124ms TTL=56
Reply from 212.58.244.69: bytes=32 time=69ms TTL=56
Reply from 212.58.244.69: bytes=32 time=30ms TTL=56
Reply from 212.58.244.69: bytes=32 time=44ms TTL=56
Reply from 212.58.244.69: bytes=32 time=347ms TTL=56
Reply from 212.58.244.69: bytes=32 time=107ms TTL=56
Reply from 212.58.244.69: bytes=32 time=89ms TTL=56
Reply from 212.58.244.69: bytes=32 time=29ms TTL=56
Reply from 212.58.244.69: bytes=32 time=47ms TTL=56
Reply from 212.58.244.69: bytes=32 time=67ms TTL=56
Reply from 212.58.244.69: bytes=32 time=82ms TTL=56
Reply from 212.58.244.69: bytes=32 time=28ms TTL=56
Reply from 212.58.244.69: bytes=32 time=90ms TTL=56
Reply from 212.58.244.69: bytes=32 time=57ms TTL=56
Reply from 212.58.244.69: bytes=32 time=71ms TTL=56
Reply from 212.58.244.69: bytes=32 time=77ms TTL=56
Reply from 212.58.244.69: bytes=32 time=80ms TTL=56
Reply from 212.58.244.69: bytes=32 time=58ms TTL=56
Reply from 212.58.244.69: bytes=32 time=24ms TTL=56
Reply from 212.58.244.69: bytes=32 time=68ms TTL=56
Reply from 212.58.244.69: bytes=32 time=56ms TTL=56
Reply from 212.58.244.69: bytes=32 time=128ms TTL=56
Reply from 212.58.244.69: bytes=32 time=98ms TTL=56
Reply from 212.58.244.69: bytes=32 time=49ms TTL=56

Ping statistics for 212.58.244.69:
    Packets: Sent = 43, Received = 43, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 17ms, Maximum = 347ms, Average = 87ms

[Blueflame]

Got an email later in the day explaining they were having problems.

[jamadams]

Mines a right old bag of crap tonight. Long time since it's been this bad.

[Djwindas]

ricky told me slowline doing some work. 

[richardmyers]

ricky told me slowline doing some work. 

As they always are!

[Djwindas]

yerp

[Djwindas]

Speaks for its self! 

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Phil>tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.241.131]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.11.1
  2   527 ms   612 ms   596 ms  static.quickline.co.uk [91.214.230.***]
  3   592 ms   627 ms   701 ms  202.88.80.arpa.orbital.net [80.88.202.129]
  4   783 ms   669 ms   618 ms  ge0.ln1.thn.orbital.net [80.88.216.113]
  5   665 ms   660 ms   662 ms  bbc-gw0-linx.prt0.thdoe.bbc.co.uk [195.66.224.10
3]
  6   565 ms   643 ms   700 ms  212.58.238.153
  7   610 ms   682 ms   653 ms  virtual-vip-231.thdo.bbc.co.uk [212.58.241.131]


Trace complete.

C:\Documents and Settings\Phil>

[Blueflame]

Improved a little bit, but still pretty slow, and unstable to use.

I don't understand why they don't send out an email before they start the work. They must know it's going to impact the service. Do they really think nobody will notice?

No updates on the quickline twitter either.



Pinging www.bbc.net.uk [212.58.246.93] with 32 bytes of data
Reply from 212.58.246.93: bytes=32 time=90ms TTL=55
Reply from 212.58.246.93: bytes=32 time=69ms TTL=55
Reply from 212.58.246.93: bytes=32 time=71ms TTL=55
Reply from 212.58.246.93: bytes=32 time=59ms TTL=55
Reply from 212.58.246.93: bytes=32 time=41ms TTL=55
Reply from 212.58.246.93: bytes=32 time=44ms TTL=55
Reply from 212.58.246.93: bytes=32 time=48ms TTL=55
Reply from 212.58.246.93: bytes=32 time=58ms TTL=55
Reply from 212.58.246.93: bytes=32 time=79ms TTL=55
Reply from 212.58.246.93: bytes=32 time=64ms TTL=55
Reply from 212.58.246.93: bytes=32 time=78ms TTL=55
Reply from 212.58.246.93: bytes=32 time=81ms TTL=55
Reply from 212.58.246.93: bytes=32 time=69ms TTL=55
Reply from 212.58.246.93: bytes=32 time=52ms TTL=55
Reply from 212.58.246.93: bytes=32 time=45ms TTL=55
Reply from 212.58.246.93: bytes=32 time=56ms TTL=55
Reply from 212.58.246.93: bytes=32 time=75ms TTL=55

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

[Ace247]

I don't understand why they don't send out an email before they start the work. They must know it's going to impact the service. Do they really think nobody will notice?

It would suggest to me they don't actually know BF!
Sounds more like they are reacting to unknown situations rather than anything actually planned... Reactive not proactive! 

[Djwindas]

more then likely

[Blueflame]

Subject of the email I got was 'Urgent Service Update from Quickline' and came from their sister company uniquecomms.co.uk

Said they were 'implementing some essential maintenance works and upgrades to the network over the next couple of days'.

'next couple of days' isn't very specific is it. That was 2 days ago, and pings are high, speeds are still halved and browsing laggy.

Hoping these upgrades are for real.

[Scotty]

lmao, they've been making 'upgrades' for years.. it's all bullshit, and never fixes anything.

[Blueflame]

Apparently they should be complete by the end of this afternoon. See how it looks when I get back.

[Blueflame]

Looks like this.




Pinging www.bbc.net.uk [212.58.244.67] with 32 bytes of data
Reply from 212.58.244.67: bytes=32 time=69ms TTL=55
Reply from 212.58.244.67: bytes=32 time=50ms TTL=55
Reply from 212.58.244.67: bytes=32 time=54ms TTL=55
Reply from 212.58.244.67: bytes=32 time=47ms TTL=55
Reply from 212.58.244.67: bytes=32 time=52ms TTL=55
Reply from 212.58.244.67: bytes=32 time=42ms TTL=55
Reply from 212.58.244.67: bytes=32 time=44ms TTL=55
Reply from 212.58.244.67: bytes=32 time=40ms TTL=55
Reply from 212.58.244.67: bytes=32 time=34ms TTL=55
Reply from 212.58.244.67: bytes=32 time=39ms TTL=55
Reply from 212.58.244.67: bytes=32 time=66ms TTL=55
Reply from 212.58.244.67: bytes=32 time=31ms TTL=55
Reply from 212.58.244.67: bytes=32 time=39ms TTL=55
Reply from 212.58.244.67: bytes=32 time=42ms TTL=55
Reply from 212.58.244.67: bytes=32 time=36ms TTL=55
Reply from 212.58.244.67: bytes=32 time=182ms TTL=55
Reply from 212.58.244.67: bytes=32 time=56ms TTL=55
Reply from 212.58.244.67: bytes=32 time=78ms TTL=55
Reply from 212.58.244.67: bytes=32 time=46ms TTL=55
Reply from 212.58.244.67: bytes=32 time=49ms TTL=55
Reply from 212.58.244.67: bytes=32 time=62ms TTL=55
Reply from 212.58.244.67: bytes=32 time=67ms TTL=55
Reply from 212.58.244.67: bytes=32 time=41ms TTL=55
Reply from 212.58.244.67: bytes=32 time=56ms TTL=55
Reply from 212.58.244.67: bytes=32 time=38ms TTL=55
Reply from 212.58.244.67: bytes=32 time=52ms TTL=55
Reply from 212.58.244.67: bytes=32 time=60ms TTL=55
Reply from 212.58.244.67: bytes=32 time=57ms TTL=55
Reply from 212.58.244.67: bytes=32 time=31ms TTL=55
Reply from 212.58.244.67: bytes=32 time=38ms TTL=55
Reply from 212.58.244.67: bytes=32 time=43ms TTL=55
Reply from 212.58.244.67: bytes=32 time=50ms TTL=55

Ping statistics for 212.58.244.67:
    Packets: Sent = 32, Received = 32, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 31ms, Maximum = 182ms, Average = 52ms