So slow

Started by Lawman, Aug 30, 2006, 21:30:13

Previous topic - Next topic

0 Members and 2 Guests are viewing this topic.

Lawman

Must say I'm really disappointed..  :(
Speeds & ping have been diabolical since Sunday.
Only once have I hit 6.2 MB download, and pings of 26
Most of the time I have been getting, between 600kb/s and 800kb/s pings vary from 48 to 100+

Before that I was hitting, pings of 24 to 28 and speeds 5 Mb up to 6.4 MB regularly
Though my Sync rate has remained a very stable 8128.
To dare is to Do

maxping

Quote from: Lawman on Aug 30, 2006, 21:30:13

Most of the time I have been getting, between 600kb/s and 800kb/s pings vary from 48 to 100+





Having read the forums here and at ADSL Guide i would say the average speeds are around the 4000kbps mark , my speeds fluctuate between 40000 & 5000kbps.

Obviously at 600kbps there is something wrong , how long have you been with IDNet?

Lawman

Only a week, but everything was normal until late Sunday
This morning I had no connection at all, reset my router (netgear384G v 2)
did a set up wizard.. could not find..any dns/IP,

So put all information back in manually, still no connection.
spent 40 Min's trying, through out My Connection sync showed 8128, even after I did a factory reset. was about to dig out my old modem,
thought have one more go, and everything was back,
speed fine / ping fine


Must have been an Outage this morning...
To dare is to Do

equk

#3
here's my results  :'(



on adslmax connected at 3.9mb  :-X :-\
e6400 @ 3.2Ghz 38°C 45°C | ATI X1900XT | P5W DH | ss: linux | osx
migration complete - sync 5mb 500k - stable low ping times

mrapoc

are u still in the 10 day training period? if so this is pretty much expected

turning off ur router for 30 mins usually helps

Lawman

I don't think so, I think I just went straight in on my old profile,
but who knows , if anyone could second guess BT, they would make a fortune
To dare is to Do

equk

Quote from: mrapoc on Aug 31, 2006, 10:58:08
are u still in the 10 day training period? if so this is pretty much expected

turning off ur router for 30 mins usually helps
yer I'm still on the 10day thing :(

10th day is sunday so not long and hopefully all the problems will be sorted. My pings have gone up by 5-10ms also so maybe they put on interleaving or something  :-X

routing issues still not sorted either.
e6400 @ 3.2Ghz 38°C 45°C | ATI X1900XT | P5W DH | ss: linux | osx
migration complete - sync 5mb 500k - stable low ping times

Simon_idnet

Hi equk

We've cut out Hurricane Electric by establishing direct peering with Xs4all for you. Please can you let me know what routing issue you are seeing now?

Cheers
Simon

equk

Quote from: simon on Aug 31, 2006, 19:23:53
Hi equk

We've cut out Hurricane Electric by establishing direct peering with Xs4all for you. Please can you let me know what routing issue you are seeing now?

Cheers
Simon
cool, here's a traceroute:
traceroute to 194.109.69.93 (194.109.69.93), 30 hops max, 40 byte packets
1  cisco (192.168.1.1)  0.953 ms  0.934 ms  0.906 ms
2  telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  18.689 ms  21.867 ms *
3  telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  19.862 ms  18.469 ms  17.944 ms
4  telehouse-gw.idnet.net (212.69.40.1)  19.964 ms  18.553 ms  19.972 ms
5  * redbus-gw.idnet.net (212.69.63.1)  19.965 ms  20.541 ms
6  ams-ix.sara.xs4all.net (195.69.144.48)  87.881 ms  86.319 ms  66.464 ms
7  0.so-6-0-0.xr2.3d12.xs4all.net (194.109.5.5)  61.420 ms  70.770 ms  65.711 ms
8  0.so-3-0-0.cr2.3d12.xs4all.net (194.109.5.94)  61.863 ms  70.570 ms  73.963 ms
9  quake3-04.xs4all.nl (194.109.69.93)  77.847 ms  91.298 ms  77.899 ms

ping seems strangely high tho  :-[
e6400 @ 3.2Ghz 38°C 45°C | ATI X1900XT | P5W DH | ss: linux | osx
migration complete - sync 5mb 500k - stable low ping times

Simon_idnet

Well your trace is showing 18/19ms through the IDNet network and then we hand over to xs4all at our POP in Amsterdam. I'm afraid it's there's not much we can do about your traffic once it is inside another network...
Simon

equk

Quote from: simon on Aug 31, 2006, 19:53:04
Well your trace is showing 18/19ms through the IDNet network and then we hand over to xs4all at our POP in Amsterdam. I'm afraid it's there's not much we can do about your traffic once it is inside another network...
Simon
I can understand that, I know I sound like I'm being picky etc and really am pleased that you are actively doing something (better than most other ISPs).

I'm just looking at this post which is pinging 27ms to that same IP.  :-\

As I said before I have adsl mainly for gaming, so obviously ping times matter. Like a lot of other people on here. I guess it's unfortunate, but if I cannot game at all there's not much point in having it  :'( each day I check the ping thread and each day there are more posts  :-\
e6400 @ 3.2Ghz 38°C 45°C | ATI X1900XT | P5W DH | ss: linux | osx
migration complete - sync 5mb 500k - stable low ping times

equk

I'm not sure what's happened to my connection atm tho as bt are doing stuff I guess so that could be a factor until the 10days is over. I guess if someone else on idnet tried it could give a better result.  ???

My ping times today are up 10+ms from what they were on friday to everything :(
e6400 @ 3.2Ghz 38°C 45°C | ATI X1900XT | P5W DH | ss: linux | osx
migration complete - sync 5mb 500k - stable low ping times

Gilba

It seems ok at my end, just done a couple tracerts

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.0.1
  2    16 ms    16 ms    16 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
  3    17 ms    17 ms    18 ms  telehouse-gw.idnet.net [212.69.40.1]
  4    18 ms    17 ms    18 ms  redbus-gw.idnet.net [212.69.63.1]
  5    46 ms    33 ms    35 ms  ams-ix.sara.xs4all.net [195.69.144.48]
  6    35 ms    34 ms    34 ms  0.so-6-0-0.xr2.3d12.xs4all.net [194.109.5.5]
  7    34 ms    34 ms    35 ms  0.so-3-0-0.cr2.3d12.xs4all.net [194.109.5.94]
  8    34 ms    39 ms    34 ms  quake3-04.xs4all.nl [194.109.69.93]

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.0.1
  2    16 ms    16 ms    15 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
  3    17 ms    17 ms    17 ms  telehouse-gw.idnet.net [212.69.40.1]
  4    18 ms    17 ms    17 ms  redbus-gw.idnet.net [212.69.63.1]
  5    56 ms    34 ms    37 ms  ams-ix.sara.xs4all.net [195.69.144.48]
  6    35 ms    35 ms    34 ms  0.so-6-0-0.xr2.3d12.xs4all.net [194.109.5.5]
  7    49 ms    33 ms    35 ms  0.so-3-0-0.cr2.3d12.xs4all.net [194.109.5.94]
  8    35 ms    37 ms    35 ms  quake3-04.xs4all.nl [194.109.69.93]

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.0.1
  2    16 ms    16 ms    16 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
  3    16 ms    17 ms    16 ms  telehouse-gw.idnet.net [212.69.40.1]
  4    18 ms    18 ms    18 ms  redbus-gw.idnet.net [212.69.63.1]
  5    34 ms    36 ms    33 ms  ams-ix.sara.xs4all.net [195.69.144.48]
  6    34 ms    36 ms    34 ms  0.so-6-0-0.xr2.3d12.xs4all.net [194.109.5.5]
  7    34 ms    34 ms    34 ms  0.so-3-0-0.cr2.3d12.xs4all.net [194.109.5.94]
  8    35 ms    37 ms    36 ms  quake3-04.xs4all.nl [194.109.69.93]

maxping

#13
Wish i could say the same, I'm still stuck on this minimum of 50 ping, i use my pc for gaming most of the time and this is beginning to get annoying. >:(

Bt say they have turned interleaving off yet its still showing as on (see below)    ::)



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

  1     *        *        *     Request timed out.
  2    51 ms    49 ms    50 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
  3    53 ms    50 ms    51 ms  telehouse-gw.idnet.net [212.69.40.1]
  4    51 ms    50 ms    52 ms  redbus-gw.idnet.net [212.69.63.1]
  5    68 ms    72 ms    71 ms  ams-ix.sara.xs4all.net [195.69.144.48]
  6    67 ms    69 ms    72 ms  0.so-6-0-0.xr2.3d12.xs4all.net [194.109.5.5]
  7    69 ms    68 ms    70 ms  0.so-3-0-0.cr2.3d12.xs4all.net [194.109.5.94]
  8    69 ms    68 ms    68 ms  quake3-04.xs4all.nl [194.109.69.93]



  1     *        *        *     Request timed out.
  2    53 ms    50 ms    49 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
  3    57 ms    60 ms    57 ms  telehouse-gw.idnet.net [212.69.40.1]
  4    51 ms    51 ms    50 ms  redbus-gw.idnet.net [212.69.63.1]
  5    68 ms    69 ms    70 ms  ams-ix.sara.xs4all.net [195.69.144.48]
  6    68 ms    69 ms    69 ms  0.so-6-0-0.xr2.3d12.xs4all.net [194.109.5.5]
  7    69 ms    67 ms    74 ms  0.so-3-0-0.cr2.3d12.xs4all.net [194.109.5.94]
  8    72 ms    67 ms    72 ms  quake3-04.xs4all.nl [194.109.69.93]


  1     *        *        *     Request timed out.
  2    51 ms    50 ms    52 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
  3    50 ms    50 ms    52 ms  telehouse-gw.idnet.net [212.69.40.1]
  4    52 ms    52 ms    55 ms  redbus-gw.idnet.net [212.69.63.1]
  5   128 ms    83 ms    74 ms  ams-ix.sara.xs4all.net [195.69.144.48]
  6   102 ms    78 ms    67 ms  0.so-6-0-0.xr2.3d12.xs4all.net [194.109.5.5]
  7   134 ms    96 ms    68 ms  0.so-3-0-0.cr2.3d12.xs4all.net [194.109.5.94]
  8    74 ms    72 ms    72 ms  quake3-04.xs4all.nl [194.109.69.93]

Gilba

 ::)

Trust BT to cock it up.

karvala

Quote from: maxping on Aug 31, 2006, 22:42:16
Wish i could say the same, I'm still stuck on this minimum of 50 ping, i use my pc for gaming most of the time and this is beginning to get annoying. >:(

Bt say they have turned interleaving off yet its still showing as on (see below)    ::)



Yes, I have exactly the same thing.  Interleaving supposedly switched off about a week ago, and the router rebooted a number of times since then, and left off for longer than 30 minutes, and yet mine also shows those same sync speeds and interleaving clearly present.  Methinks BTW are not being entirely honest (yeah, enormously surprising, isn't it?  ::) ).