Pings

[maxping]

Interleaving still on but pings fairly stable here .

Pinging www.bbc.co.uk with 32 bytes of data:
Reply from 212.58.224.113 bytes:32 Time:49ms TTL:249
Reply from 212.58.224.113 bytes:32 Time:50ms TTL:249
Reply from 212.58.224.113 bytes:32 Time:52ms TTL:249
Reply from 212.58.224.113 bytes:32 Time:51ms TTL:249
Reply from 212.58.224.113 bytes:32 Time:51ms TTL:249
Reply from 212.58.224.113 bytes:32 Time:50ms TTL:249
Reply from 212.58.224.113 bytes:32 Time:52ms TTL:249
Reply from 212.58.224.113 bytes:32 Time:50ms TTL:249
Reply from 212.58.224.113 bytes:32 Time:50ms TTL:249
Reply from 212.58.224.113 bytes:32 Time:50ms TTL:249
Reply from 212.58.224.113 bytes:32 Time:51ms TTL:249
Reply from 212.58.224.113 bytes:32 Time:52ms TTL:249
Reply from 212.58.224.113 bytes:32 Time:54ms TTL:249
Reply from 212.58.224.113 bytes:32 Time:51ms TTL:249
Reply from 212.58.224.113 bytes:32 Time:53ms TTL:249
Reply from 212.58.224.113 bytes:32 Time:62ms TTL:249
Reply from 212.58.224.113 bytes:32 Time:52ms TTL:249
Reply from 212.58.224.113 bytes:32 Time:55ms TTL:249
Reply from 212.58.224.113 bytes:32 Time:51ms TTL:249
Reply from 212.58.224.113 bytes:32 Time:49ms TTL:249
Reply from 212.58.224.113 bytes:32 Time:50ms TTL:249
Reply from 212.58.224.113 bytes:32 Time:51ms TTL:249
Reply from 212.58.224.113 bytes:32 Time:53ms TTL:249
Reply from 212.58.224.113 bytes:32 Time:50ms TTL:249
Reply from 212.58.224.113 bytes:32 Time:50ms TTL:249
Reply from 212.58.224.113 bytes:32 Time:51ms TTL:249
Reply from 212.58.224.113 bytes:32 Time:52ms TTL:249
Reply from 212.58.224.113 bytes:32 Time:50ms TTL:249
Reply from 212.58.224.113 bytes:32 Time:49ms TTL:249
Reply from 212.58.224.113 bytes:32 Time:52ms TTL:249
Ping statistics for www.bbc.co.uk :
Packets: Sent = 30, Received = 30, Lost = 0 (0%) loss),
Approximate round trip times in milli-seconds:
Minimum = 49ms, Maximum = 62ms, Average = 51ms

[Danni]

My connection is having frequent disconnects, and it's nothing to do with sitting on the stairs as it's quieter here

Spoke to Simon before, and he's asked me to monitor it for a bit longer, before they go yell at BT. We've already got interleaving on, but are currently synced at 7mb.

Current pinging situation (to gateway):

danni@Luciana:~$ ping 212.69.63.45
PING 212.69.63.45 (212.69.63.45) 56(84) bytes of data.
64 bytes from 212.69.63.45: icmp_seq=1 ttl=254 time=43.9 ms
64 bytes from 212.69.63.45: icmp_seq=2 ttl=254 time=197 ms
64 bytes from 212.69.63.45: icmp_seq=3 ttl=254 time=92.6 ms
64 bytes from 212.69.63.45: icmp_seq=4 ttl=254 time=43.9 ms
64 bytes from 212.69.63.45: icmp_seq=5 ttl=254 time=137 ms
64 bytes from 212.69.63.45: icmp_seq=6 ttl=254 time=461 ms
64 bytes from 212.69.63.45: icmp_seq=7 ttl=254 time=54.4 ms
64 bytes from 212.69.63.45: icmp_seq=8 ttl=254 time=132 ms
64 bytes from 212.69.63.45: icmp_seq=9 ttl=254 time=170 ms
64 bytes from 212.69.63.45: icmp_seq=10 ttl=254 time=453 ms
64 bytes from 212.69.63.45: icmp_seq=11 ttl=254 time=264 ms
64 bytes from 212.69.63.45: icmp_seq=12 ttl=254 time=448 ms
64 bytes from 212.69.63.45: icmp_seq=13 ttl=254 time=563 ms
64 bytes from 212.69.63.45: icmp_seq=14 ttl=254 time=625 ms
64 bytes from 212.69.63.45: icmp_seq=15 ttl=254 time=683 ms
64 bytes from 212.69.63.45: icmp_seq=16 ttl=254 time=588 ms
64 bytes from 212.69.63.45: icmp_seq=17 ttl=254 time=470 ms
64 bytes from 212.69.63.45: icmp_seq=18 ttl=254 time=516 ms
64 bytes from 212.69.63.45: icmp_seq=19 ttl=254 time=432 ms
64 bytes from 212.69.63.45: icmp_seq=20 ttl=254 time=459 ms
64 bytes from 212.69.63.45: icmp_seq=22 ttl=254 time=481 ms

--- 212.69.63.45 ping statistics ---
23 packets transmitted, 21 received, 8% packet loss, time 22073ms
rtt min/avg/max/mdev = 43.991/348.730/683.163/206.634 ms
danni@Luciana:~$

Last disconnect:

Wed Sep 6 17:34:27 2006 -WAN PPPoE disconnected
Wed Sep 6 17:34:27 2006 -WAN : PADT sent
Wed Sep 6 17:35:27 2006 -WAN : PADI sent
Wed Sep 6 17:35:27 2006 -WAN : PADO received
Wed Sep 6 17:35:27 2006 -WAN : PADR sent
Wed Sep 6 17:35:28 2006 -WAN : PADS received
Wed Sep 6 17:35:37 2006 -WAN PPPoE connected

Hummm....

[browney]

I have had no problems for 2 days now i'm well happy

[equk]

Been reading a little on people getting 1.8mb on max within the 10day period

Sounds like a stuck BRAS profile, leave it alone for the remainder of the 10 day initial line training, and if after the 11th day you're still getting 1.8Mbps downloads, contact your ISP to get BT to unstick it.

speedtest someone got after doing this: link

Sounds possibly like what I was getting when I was on adslmax.

[equk]

quake3 netgraph is mostly red today 100+ms and a mental amount of packetloss   

still waiting for my l8nc account to become active will be able to post a link then, showing the stupid ping times 

[CatMangler]

Any one else had a complete loss of BB???!!

Was ok @ 5pm then I return at 8pm and nothing!!!!!!!!!!!!!!!!!!, I've only just got back on ffs.

WTF IS GOING ON

[browney]

No problems here

[AvengerUK]

Internet is fine (up), but the pings are now rising almost every 10seconds

[browney]

Really? no problems here

[sobranie]

I lost all BB this morning for 2+ hours.
Switched off router in the end and went shopping. When I got back, switched on and all OK.
Such is the power of shopping at TESCOS

[mrapoc]

I think its time for idnet to shout at bt or at least give us some more frequent updates

i can see a lot of people leaving over this - which would be bad for idnet and my social well being on idnetters

[AvengerUK]

I think its time for idnet to shout at bt or at least give us some more frequent updates

i can see a lot of people leaving over this - which would be bad for idnet and my social well being on idnetters

Who's to say its BT? - updates would be nice though, but its not looking for good for us gamers at present.

[equk]

I think we need info on the ongoing problem. A lot of us are totally unhappy with the service. I've emailed Simon asking exactly what's happening. It seems the community here are helping eachother with testing, analysis and problems more than CS.

I'm pretty sure unless people actually see something happening, they WILL leave.

The whole "it's your router" thing hasn't really helped their case so far either.

I do think in certain cases there is more than one problem tho.

[CatMangler]

Ok there it goes again, well I spose I have had it back for a whole hour, must share it around for other users

[equk]

hmm atm ping times don't seem as bad as they were in the day 

Code Select Expand

traceroute to 194.109.69.93 (194.109.69.93), 30 hops max, 40 byte packets
1  cisco (192.168.1.1)  1.233 ms  0.681 ms  0.670 ms
2  telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  21.207 ms  24.943 ms  21.190 ms
3  * telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  25.112 ms  29.566 ms
4  telehouse-gw.idnet.net (212.69.40.1)  22.064 ms  23.899 ms  22.048 ms
5  redbus-gw.idnet.net (212.69.63.1)  27.972 ms  22.186 ms *
6  ams-ix.sara.xs4all.net (195.69.144.48)  39.474 ms  137.770 ms  39.979 ms
7  0.so-6-0-0.xr2.3d12.xs4all.net (194.109.5.5)  39.983 ms  233.932 ms  39.894 ms
8  0.so-3-0-0.cr2.3d12.xs4all.net (194.109.5.94)  40.042 ms  62.086 ms  49.895 ms
9  quake3-04.xs4all.nl (194.109.69.93)  49.898 ms  39.948 ms  41.964 ms

--- 194.109.69.93 ping statistics ---
92 packets transmitted, 92 received, 0% packet loss, time 91563ms
rtt min/avg/max/mdev = 36.722/43.607/131.579/13.916 ms
still spiking to 130ms but I guess at least the gateway is below 100ms

[AvengerUK]

Hmmm,

Ive decided to run a few tests to IDnet IP's (my own & there site) using "PingPlotter" - Im running it from one of my servers located on a differnt network, the ping times will be around 1ms to the idnet site but should show any spikes.

Ill edit and upload the results once theve completed.

note: Whats "Jttr" and why is it important?  Jttr is short for "Jitter" - Jitter is a number that represents how stable the latency responses have been. A low jitter number is usually an idication of a good, stable conncetion.  High jitter can mean poor response times, poor voice quality (for VOIP) and other connection problems.
In the below graphs - RED means its high!



Note: to those waiting for results, the ones to customer lines show a very very obvious issue.

Here they are:

IDnet site:



Shown by the red lined box - the jitter here is quite bad - and jumps every 20seconds!! - Arbinet.net shows the most problems...a whois check shows that arbinet.net are a USA based company "Abrinet-TheXchange Inc".

My line:



Again, Aribnet hop shows the most jitter- and the spikes are recorded underneath!

Note: all blacked out sections are either the servers IP range or my home IP address - security reasons

[maxping]

In the below graphs - RED means its high!

What graph?

[AvengerUK]

Paintiance! - Its almost done!

*DONE ABOVE*

[maxping]

Avenger i changed the graph colours in options and set them 0-50 , 51 - 10 , 101 on.

We seem to be having problems with hop 4.

[AvengerUK]

Avenger i changed the graph colours in options and set them 0-50 , 51 - 10 , 101 on.

We seem to be having problems with hop 4.

That problem is only with that route though - thing is that it happens for almost every route?? - and i know that Enta users dont have the problems we are getting anyway!

Note: There's been some work on the network this morning (ADSLGuide "problems" post, IDnet forum) - anyone notice any change in pings!?

Looking at my l8nc graph, downtime was for me around 6:10, once it came back, spikes were evedent for an hour...but currently my graph is totally flat

EDIT: Stable pings for almost 2 hours...could this be the end? 

Another EDIT: Spoke to soon.....just after 2 hours of almost flatness, the spikes return. 

Any else notice this breif period? First time since the problems began!

[equk]

hmm pings today:

Code Select Expand

traceroute to www.idnet.net (212.69.36.10), 30 hops max, 40 byte packets
1  cisco (192.168.1.1)  1.288 ms  0.711 ms  0.718 ms
2  telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  21.210 ms  25.638 ms  20.013 ms
3  * telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  23.582 ms  21.140 ms
4  212.69.63.9 (212.69.63.9)  235.923 ms  284.404 ms  293.875 ms
5  redbus-gw.idnet.net (212.69.63.1)  26.546 ms  21.747 ms  25.985 ms
6  www.idnet.net (212.69.36.10)  22.002 ms  28.095 ms  23.242 ms
Similar to last night, still spiking at 300ms tho. Probably won't be able to test any further today tho as I'm off to do some CAD work for someone

[AvengerUK]

Im not sure what IDnet are doing, but the problem seems to be *ALMOST* sorted, for me atleast.

L8NC Graph: http://www.l8nc.com/graph.php?jid=58e61f6e3d3d258ec640ec3f21295d2e

[browney]

Have you noticed on hop 3 that it now just has the ip

[equk]

here's some results on a F2S (pipex) connection

Code Select Expand

Tracing route to quake3-04.xs4all.nl [194.109.69.93]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    23 ms    26 ms    23 ms  l1.ar11.hx4.bb.pipex.net [194.106.38.251]
  3    23 ms    23 ms    24 ms  g1-2-0.cr10.hx4.bb.pipex.net [194.106.38.153]
  4    24 ms    23 ms    53 ms  pc1.cr05.hx2.bb.pipex.net [62.72.143.13]
  5    23 ms    21 ms    23 ms  g1-2.cr01.hx2.bb.pipex.net [62.72.143.37]
  6    32 ms    32 ms    31 ms  ge4-1-0-1000M.ar1.AMS1.gblx.net [195.69.144.80]
  7    30 ms    31 ms    31 ms  XS4ALL.so-7-0-0.nar1.AMS1.gblx.net [146.82.33.178]
  8    32 ms    35 ms    33 ms  0.so-6-0-0.xr2.3d12.xs4all.net [194.109.5.5]
  9    39 ms    32 ms    33 ms  0.so-3-0-0.cr2.3d12.xs4all.net [194.109.5.94]
10    33 ms    33 ms    32 ms  quake3-04.xs4all.nl [194.109.69.93]

Trace complete.
Lower and more stable than idnet lol 

[AvengerUK]

Have you noticed on hop 3 that it now just has the ip

hop 4 actually