o2 pings & packet loss

Have you actually read the thread? There are problems at the moment due to the fiber cut.

In regards to those sorts of sites, I've used them on and off (admittedly not prolifically) and not had any problems. Is it only recently you've had the issue?

For the last two weeks at least, Right now downloads aren't to bad it really starts at about 4pm but can continue well into the small hours.

I know about the fiber and this has nothing to do with that.

There are some posts at the O2 website.
 
Last edited:
For the last two weeks at least, Right now downloads aren't to bad it really starts at about 4pm but can continue well into the small hours.

I know about the fiber and this has nothing to do with that.

There are some posts at the O2 website.

Very odd. I wasn't aware of that.
 
I know this exact feeling, I've been having convo's with Be tech support for a while now when I first migrated to Be from BT8mb I was getting around 15-20ping which I was happy with (although with BT my ping was between 6-10 constantly). Now all of a sudden i'm getting pings of 40-50 and notified Bethere and they said this is perfectly normal??????? and well within the acceptable range.

Needless to say I have put a request to cancell my subscription and will be changeing over to Ukonline.
 
seems to be back to normal again here, average ping to bbc.co.uk is 19ms.
Download Speed: 9116 kbps (1139.5 KB/sec) Upload Speed: 1104 kbps (138 KB/sec)
 
seems to be back to normal again here, average ping to bbc.co.uk is 19ms.
Download Speed: 9116 kbps (1139.5 KB/sec) Upload Speed: 1104 kbps (138 KB/sec)

There's not much point in checking it until peak time though really. It was fine during the day for me, but awful at night.
 
and to be honest it isnt as bad over the weekend than say week nights, we will see, im still getting 100+ pings as I type this.
 
Code:
Tracing route to bbc.co.uk [212.58.224.138]
over a maximum of 30 hops:

  1    85 ms    99 ms    99 ms  192.168.1.254
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4    16 ms    16 ms    15 ms  83.245.126.93
  5    15 ms    16 ms    16 ms  212.58.238.129
  6    16 ms    15 ms    14 ms  virtual-vip.thdo.bbc.co.uk [212.58.224.138]

Code:
	Link Information
			
Uptime:	3 days, 0:52:55
DSL Type:	G.992.5 annex A
Bandwidth (Up/Down) [kbps/kbps]:	1,304 / 23,878
Data Transferred (Sent/Received) [kB/kB]:	0.00 / 0.00
Output Power (Up/Down) [dBm]:	12.0 / 18.0
Line Attenuation (Up/Down) [dB]:	4.0 / 9.0
SN Margin (Up/Down) [dB]:	8.5 / 8.0
Vendor ID (Local/Remote):	TMMB / BDCM
Loss of Framing (Local/Remote):	4 / 0
Loss of Signal (Local/Remote):	1 / 0
Loss of Power (Local/Remote):	0 / 0
Loss of Link (Remote):	0
Error Seconds (Local/Remote):	55 / 0
FEC Errors (Up/Down):	323 / 0
CRC Errors (Up/Down):	323 / 726
HEC Errors (Up/Down):	21,015 / 534

Not too great for me still.
 
Has anyone tried Rapidshare, filefactory or sendspace?

Just taken a 1:30 to download 100meg file, check out how much time the download isn't doing anything.

Each pause is about 20seconds long.

 
o2 are traffic shaping imo, as ping times and download suck, but newsgroups/giganews is perfect still, so 100% capping bandwidth and have been doing for a month now.

hah. sorry mate, but you're talking bobbins.

there is absolutely no traffic shaping or ability to traffic shape on our network.

the big outage affected 7 of our MAIN circuits, essentially our core packet links were cut so we had to shunt down our redundant links, but whereas the core links are around 10Gb each, a lot of the redundant ones are only LAGs at about 3-4Gb. Now, we are currently running very hot, capacitywise at the moment anyway, so it crippled us quite significantly and unfortunately the issue was protracted by the supplier.

6 of the 7 links were fixed by yesterday morning but the remaining Birmingham to London link was still severed, this link is a primary connect from Manchester which serves pretty much the whole north of England. It took a lot of fault finding from GC to find out where the fibre snap was as it wasn't in the location of the original breakage.

I know people are a bit ****ed at the moment and seem to think we're acting underhand but we are seriously not. We are pouring capacity hand over fist into the network but you need to understand that lead times do occur, and with our growth its sometimes a bit difficult to try and grow the network at the same time that the userbase grows.

What i can tell you is we're adding further capacity to many of the LAGs that serve our inter-regional nodes so that we can serve this capacity, but we in no way, shape or form use any traffic shaping and this is coming from someone who works on *** network, day in, day out.
 
by the way, the best thing you can do if you're getting slow throughput at peak times is to contact customer service. we actively monitor links but some we can't capture, so its really important that you report these.

i can guarantee if you report a slow throughput case to the CS, it will probably end up landing on my desk and i do investigate them thoroughly to see where the issue lies. 9/10 it is due to line errors and customers trying to throw too much bandwidth down their line than it can cope with, but they are all investigated.
 
I did phone your CS and second line who dont have a clue, and was told to call back after xmas, To be honest thats poor really poor, basicly they said tuff luck live with it or leave.

So I have got live with poor speeds and pings for 2 months. So I get a lesser service than everyone else, do I pay less... errr no.

atm ping is at 120ms to any uk server, just isnt on.
 
i sincerly doubt it, but your choice of ISP is your perogative. what do you really expect? a fibre link straight to your door? if you're on EMBURTO (Burton-on-Trent) i assume from your location, i'll check the link on monday and see if its topping out at peak time.
 
Last edited:
im not, im at swadlincote exchange

And i dont expect 1:1, all I require is a reasonable ping, not to much to ask is it?

And 100% did tell me on the phone by your second line support that I should call back after Xmas, why would I lie?
 
hah. sorry mate, but you're talking bobbins.

there is absolutely no traffic shaping or ability to traffic shape on our network.

the big outage affected 7 of our MAIN circuits, essentially our core packet links were cut so we had to shunt down our redundant links, but whereas the core links are around 10Gb each, a lot of the redundant ones are only LAGs at about 3-4Gb. Now, we are currently running very hot, capacitywise at the moment anyway, so it crippled us quite significantly and unfortunately the issue was protracted by the supplier.

6 of the 7 links were fixed by yesterday morning but the remaining Birmingham to London link was still severed, this link is a primary connect from Manchester which serves pretty much the whole north of England. It took a lot of fault finding from GC to find out where the fibre snap was as it wasn't in the location of the original breakage.

I know people are a bit ****ed at the moment and seem to think we're acting underhand but we are seriously not. We are pouring capacity hand over fist into the network but you need to understand that lead times do occur, and with our growth its sometimes a bit difficult to try and grow the network at the same time that the userbase grows.

What i can tell you is we're adding further capacity to many of the LAGs that serve our inter-regional nodes so that we can serve this capacity, but we in no way, shape or form use any traffic shaping and this is coming from someone who works on *** network, day in, day out.

that's for the decent explanation, is this still the case as im seeing about 5mbps and im located in york on a 20mbps sync.
 
Would these problems also be affecting O2 Access customers or is that a different network? I'm getting very low throughput but that is because my IP/bRAS profile is stuck at 2000kbps and O2 won't do anything until 10 days after activation. The line has been stable at 8128 kbps for over 6 days now so I know it's not going to fix itself.
 
Back
Top Bottom