50M : Think Broadband Ping Monitor Results (POST YOURS)

[roughbeast]

S*d*ing typical!! I did the pre-hump channel data. No peri-hump data. No hump tonight! ( Double entendre intended. )

[qasdfdsaq]

Originally Posted by Chrysalis

qas that packetloss I have seen on just about every BT graph posted in public, it appeared on my own graphs within a week of the policy change.

Its also on gateway graphs, eg. its on your gateway graph and its on my gateway graph which rules out local connection issues.

This seems to be down to some snap routing decisions over BT's LINX public peering. It appears to only affect traffic going over LINX' secondary public peering network, which incidentally, is where traffic from BT to TBB's ping monitor goes.

I couldn't find any other traffic that was affected, all privately peered routes were fine, all LINX primary links were fine, but everything over secondary was showing ~0.8% packet loss.

At about 5:15pm, the issues disappeared and everything went back to normal - I first noticed the problem when the throughput for the blu-ray I was streaming plumetted from 5MB/sec to 0.4MB/sec, and now that's jumped back up to full speed again too (actually it's peaking at 8MB/sec but the movie itself only averages around 5). That was transiting over LINX secondary the whole time, routing hasn't changed.

I'm not quite sure why BT is pushing so much traffic over the LINX secondary LAN, after all, they have ten times more capacity on primary than secondary. Whether it's BT's own routing to blame or like VM's issues a few months ago, due to an external network sending excess traffic the wrong way, I don't know. The issue seems to have disappeared abruptly for tonight so I can no longer trace where it is coming from.

[Sephiroth]

Yeah - I can back that up. 17:15 and the packet loss (at the time - not always there) stopped.

[img]Download Failed (1)[/img]

[Dash: CF noob]

Someones busy tonight --------

[Dash: CF noob]

levels getting poor

Down
55 322750000 Hz QAM256 6.0dBmV 38.6dB 317511 0
49 290750000 Hz QAM256 6.9dBmV 39.1dB 193094 0
50 298750000 Hz QAM256 6.3dBmV 38.8dB 683155 4
53 306750000 Hz QAM256 6.2dBmV 38.6dB 1585947 82
54 314750000 Hz QAM256 6.0dBmV 38.2dB 3964153 64

Up
3 27400000 Hz ATDMA 46.3 dBmV kQPSK 6400000 10240 Kbits/sec

[Qtx]

Want sky's number? or are you going to struggle for a while longer?

[Dash: CF noob]

Tempting, its not been like this for months.

[Qtx]

The waiting was the killer. My graphs looked a lot like yours on and off for a long time.

Stress went once I switched

[img]Download Failed (1)[/img]

Downloaded numerous GB today

[Dash: CF noob]

FTTC due end of june i think then i may be off.

[Qtx]

Not long to wait at all. Fingers crossed

[Chrysalis]

Originally Posted by Sephiroth

Yeah - I can back that up. 17:15 and the packet loss (at the time - not always there) stopped.

on the 22nd the day before qas posted I had a little loss (almost gone but still there), then last 2 days its back with a bang, here ie yesterday.



However in the past 20 mins or so BT have made a routing change, my latency has gone up, I thought they changed a setting on my line but they havent so its something done on the routing.

Here can see the routing drop but with minimal affetc on latency on my gateway.



Here on my line but with base latency going up.

[Kymmy]

Can I remind members for the last time that this is NOT the BT infinity thread.

[Sephiroth]

[img]Download Failed (1)[/img]

As an aside, my Infinity graph had the same TBB stoppage. So TBB glitched.

In deference to the moderation, I've started an FTTC TBB thread here.

[babis3g]

Today's packet packet lost was exactly the same and with VM and my ADSL connection
Seems was affected every service ... but VM is not via twister cable ... wonder what happened and every service same monitor packet lost issue

[Chrysalis]

Originally Posted by Sephiroth

As an aside, my Infinity graph had the same TBB stoppage. So TBB glitched.

In deference to the moderation, I've started an FTTC TBB thread here.

Ok so that was a change tbb side then.