O2 gone painfully slow?

Fanatic · 8 Mar 2009 at 22:11

"Due to a Fibre Fault outside London Users May be Experiencing Slow Speeds and Increased Latency. Please Accept our apologies for the Inconvenience Caused."

From the Be status page: https://www.bethere.co.uk/networkStatusScreenForForum.do

Yamahahahahaha · 8 Mar 2009 at 22:13

Guess that explains it all.

I blame the government, rant rant rant...

pmbuzz · 8 Mar 2009 at 22:18

My connection has been all over the place for a couple of months now, slow, disconnections that sort of thing, i've been on to them a few times but it's still the same.
I found their CS to pretty good to be fair.
All seems fine at the moment though

gurusan · 8 Mar 2009 at 22:54

Normally great for me, TERRIBLE all today.

pmbuzz · 8 Mar 2009 at 22:57

LOL
Just after i made that post ^^ my router (bebox) restarted itself for the 2nd time today !!

F2kSel · 8 Mar 2009 at 23:33

My speed has been fine today, the ping is up a little but still ok.

Is this three or four weeks in a row the cable has been cut?

It always seems to be at the weekend as well.

Chronictank · 8 Mar 2009 at 23:37

Still problems at Slough
syncing at 11 but downloading at 2.5

But problem is on the be status page, will be fixed in a few more hrs apparently

Wicksta · 8 Mar 2009 at 23:52

Chronictank said:
Still problems at Slough
syncing at 11 but downloading at 2.5

But problem is on the be status page, will be fixed in a few more hrs apparently

I'm on the Burnham exchange, syncing at about 17 but downloading about 7. Pings are fine though.

Hyper · 9 Mar 2009 at 00:23

Wicksta said:
I'm on the Burnham exchange, syncing at about 17 but downloading about 7. Pings are fine though.

Wish I could say the same,

Not even getting .5mb speeds and 200ms pings here in Newcastle.

First time I have had any issues.

thecremeegg · 9 Mar 2009 at 00:47

Mines suffering too

I'm in Bristol btw

thecremeegg · 9 Mar 2009 at 01:32

Its back now!

jas07 · 9 Mar 2009 at 01:54

O'Rly?

Code:

Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:
Reply from 212.58.224.138: bytes=32 time=87ms TTL=122
Reply from 212.58.224.138: bytes=32 time=88ms TTL=122
Reply from 212.58.224.138: bytes=32 time=89ms TTL=122
Reply from 212.58.224.138: bytes=32 time=89ms TTL=122

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

Draeger · 9 Mar 2009 at 07:24

Mine back to normal now, give or take a few meg :-

Are we going to have to put up with this carry on every Sunday?.

And as far as this "A cable has been cut in xxxxxxxxx location, sorry for the hassle" nonsense I don't believe for 1 minute that the whole of the O2 UK broadband operation runs through 1 or 2 particular cables and if one of said cables goes down the whole of the country ends up with what we had last night.

Smacks of the railway networks and their "Ohh....it's the wrong type of leaves, sorry!!".

More inclined to believe it is network contention issues to blame and if they are upgrading and we have to have downtime then that is acceptable.

What I do take issues with is the lack of official info on the problems when they occur. Makes no sense to either stay silent when these issues crop up and then have us all guessing at what the root issue is.

But on the other hand I will admit that on face value - What ISP does keep you fully informed when any issues crop up?. Not many, if any at all!!!.

Dougsnake · 9 Mar 2009 at 12:32

mines improved speed wise but still pinging at 73ms and still not as fast as it was a week ago looks like my honeymoon period is gone

F2kSel · 9 Mar 2009 at 13:20

My ping still hasn't returned to normal either was 43ms to London now 53ms.

Hyper · 9 Mar 2009 at 13:27

Nearly back to normal here now,

Code:

Pinging jolt.co.uk [84.234.17.86] with 32 bytes of data:
Reply from 84.234.17.86: bytes=32 time=32ms TTL=123
Reply from 84.234.17.86: bytes=32 time=33ms TTL=123
Reply from 84.234.17.86: bytes=32 time=31ms TTL=123
Reply from 84.234.17.86: bytes=32 time=32ms TTL=123

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

That will do for me

DJMK4 · 9 Mar 2009 at 14:59

15ms pings now and 1.2MB/s downloads

What cable do you think will be cut next sunday?

Hyper · 9 Mar 2009 at 15:09

How do you get a 15ms ping on O2?

Have they turned interleaving off or something?

Dougsnake · 9 Mar 2009 at 15:40

Back to normal also now pings back to 10ms

@Hyper with be there is a gaming option to select in the control panel dont know if its same for o2 but presume so.
with it on normal my ping is around 20-24ms with it turned on 10-15ms

Hyper · 9 Mar 2009 at 15:45

Ohh I see I thought you were with O2,

O2 wont disable interleaving and there isnt a gaming option