High Pings earlier .

Started by maxping, Jan 06, 2007, 18:56:56

Previous topic - Next topic

0 Members and 5 Guests are viewing this topic.

AvengerUK

Here also!  ;D

C:\Documents and Settings\Simon>ping idnet.net

Pinging idnet.net [212.69.36.10] with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=37ms TTL=60
Reply from 212.69.36.10: bytes=32 time=38ms TTL=60
Reply from 212.69.36.10: bytes=32 time=38ms TTL=60
Reply from 212.69.36.10: bytes=32 time=37ms TTL=60

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

Lance

mine seem much higher now @ 20:04...

Pinging www.idnet.net [212.69.36.10] with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=111ms TTL=60
Reply from 212.69.36.10: bytes=32 time=124ms TTL=60
Reply from 212.69.36.10: bytes=32 time=105ms TTL=60
Reply from 212.69.36.10: bytes=32 time=88ms TTL=60
Reply from 212.69.36.10: bytes=32 time=105ms TTL=60
Reply from 212.69.36.10: bytes=32 time=82ms TTL=60
Reply from 212.69.36.10: bytes=32 time=89ms TTL=60
Reply from 212.69.36.10: bytes=32 time=70ms TTL=60
Reply from 212.69.36.10: bytes=32 time=86ms TTL=60
Reply from 212.69.36.10: bytes=32 time=48ms TTL=60

Ping statistics for 212.69.36.10:
    Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 48ms, Maximum = 124ms, Average = 90ms

Would seem its now the "peak" time on the interweb!
Lance
_____

This post reflects my own views, opinions and experience, not those of IDNet.

maxping

Still fine here.

As Simon has said there is a problem , the solution is coming .
They are trying to balance the traffic so hopefully this will help until the end of Feb.
I would like to thank Simon for coming to what is an unofficial forum to tell us there is a problem and how they intend to deal with it.
How many ISP's Customer Support staff would have done the same?


Pinging idnet.net [212.69.36.10] with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=26ms TTL=60
Reply from 212.69.36.10: bytes=32 time=38ms TTL=60
Reply from 212.69.36.10: bytes=32 time=25ms TTL=60
Reply from 212.69.36.10: bytes=32 time=26ms TTL=60

Ping statistics for 212.69.36.10:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 25ms, Maximum = 38ms, Average = 28ms

RostokMcSpoons

My ping sucks so much I can't play :(


Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Ross>ping idnet.net

Pinging idnet.net [212.69.36.10] with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=200ms TTL=61
Reply from 212.69.36.10: bytes=32 time=218ms TTL=61
Reply from 212.69.36.10: bytes=32 time=203ms TTL=61
Reply from 212.69.36.10: bytes=32 time=185ms TTL=61

Ping statistics for 212.69.36.10:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
    Minimum = 185ms, Maximum = 218ms, Average = 201ms

maxping

#54
Quote from: RostokMcSpoons on Jan 09, 2007, 20:39:06
My ping sucks so much I can't play :(


I know its a p.i.t.a mate but try turning the router off for 30 mins.
Its going to be a bumpy ride for the next few days , hopefully Simon and the team can get the balancing act sorted and keep things ticking over until the end of next month when they get  more capacity.

I have just checked my ping and its high again i will try turning the m/router off and see how things go. ;)

Jobe

This is terrible, any info on when Idnet will fix these issue's?  I am pinging Jolt now over 250ms.

I came from Virgin who had the same problem of GREED and I left for that very reason; being a gamer I need low pings! This is smells like the exact same thing happening here   not happy.

I have tried everything, Had the router off 60 mins and the problem remains.

Hi all btw hehe. 

AvengerUK

Quote from: Jobe on Jan 09, 2007, 20:54:07
This is terrible, any info on when Idnet will fix these issue's?  I am pinging Jolt now over 250ms.

I came from Virgin who had the same problem of GREED and I left for that very reason; being a gamer I need low pings! This is smells like the exact same thing happening here   not happy.

I have tried everything, Had the router off 60 mins and the problem remains.

Hi all btw hehe. 


There really isnt much IDnet can do - apart from help with balancing, but that may not fix anything either. I *used* to be a gamer - but i only play Xbox live these days, which isnt badly affected.

Really the only thing you can do is wait, unlike virgin Idnet have told us of the issue(s) and are making attempts to manually rebalance so that the wait for the new capacity wont be *as hard* - but this may still mean high pings.

FYI - quite a few ISP's have had this exact problem recently, so its not just IDNet :)

Jobe

I do respect Idnet telling us of the problems, But I was told the very same thing by a few Virgin insiders before I moved ISP's.

I knew in the end that it was going to take a lot longer to fix the problem with Virgin. Infact I know it will take Virgin until March to fix this (Or so they say), but they also told me back in September it would be done by December.

The only difference here is that idnet have made it public!

Don't get me wrong I like Idnet alot as a ISP, there tech support is second to none (5 rings then a human) and I have never had a problem with them for the 2 months I have been with them, so far the last week or so it's been going down hill. It's just frutrating to suffer this again from another ISP after the months of hassle I had with my last ISP with the same problem thats all..
 

AvengerUK

Quote from: Jobe on Jan 09, 2007, 21:26:42
I do respect Idnet telling us of the problems, But I was told the very same thing by a few Virgin insiders before I moved ISP's.

I knew in the end that it was going to take a lot longer to fix the problem with Virgin. Infact I know it will take Virgin until March to fix this (Or so they say), but they also told me back in September it would be done by December.

The only difference here is that idnet have made it public!

Don't get me wrong I like Idnet alot as a ISP, there tech support is second to none (5 rings then a human) and I have never had a problem with them for the 2 months I have been with them, so far the last week or so it's been going down hill. It's just frutrating to suffer this again from another ISP after the months of hassle I had with my last ISP with the same problem thats all..
 

Suprisingly, i am also suffering a second time - Enta had the exact same problem, and i mean exact!, that lasted forever, then i escaped! - But, IDnet's problems are extremely small compaired to that!

Lance

and in my experience, when idnet have said they are going to fix a problem, they have done so on time (give or take a day or so!!!).
Lance
_____

This post reflects my own views, opinions and experience, not those of IDNet.

maxping

Quote from: Jobe on Jan 09, 2007, 20:54:07
This is terrible, any info on when Idnet will fix these issue's?  I am pinging Jolt now over 250ms.

If you read through the thread you would have seen the post from Simon (the owner of IDNet) who explained everything.

QuoteI came from Virgin who had the same problem of GREED and I left for that very reason; being a gamer I need low pings! This is smells like the exact same thing happening here   not happy.

Why do you say "GREED" ?
BT have a lead time of 3 months so therefor the order was already in place before the current ping issue hit , hardly "GREED" mate!



maxping

I have just run a test and my lowest ping was over 100

If this happens to you try this , it worked for me i am now getting this -

Pinging idnet.net [212.69.36.10] with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=30ms TTL=60
Reply from 212.69.36.10: bytes=32 time=26ms TTL=60
Reply from 212.69.36.10: bytes=32 time=25ms TTL=60
Reply from 212.69.36.10: bytes=32 time=26ms TTL=60

Ping statistics for 212.69.36.10:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 25ms, Maximum = 30ms, Average = 26ms


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Enter speedtest@speedtest_domain into the username in your routers set up.
Leave the password as is it doesn't use it.
Save reboot  then enter 217.35.209.142 into the address bar and hit go, you should now get the BT page asking you to enter your phone number to test.
You don't need to do this as you have achieved your goal , now go back to your username replace it with your IDNet user name and save/reboot and give it a try.
It has worked for me every time i have used it i hope it does for you. ;)





Jobe

Quote from: maxping on Jan 09, 2007, 22:17:27
If you read through the thread you would have seen the post from Simon (the owner of IDNet) who explained everything.

Why do you say "GREED" ?
BT have a lead time of 3 months so therefor the order was already in place before the current ping issue hit , hardly "GREED" mate!




Yes I saw Simons Post; like I said above I respect them for making the issue public. But that's all it is to me, I've been told this before a few times by another isp. I will sit back and wait, just like everyone else has to.

And about the second quote, that's what it is, more customers leading to capacity problems, other words taking on more ppl than there pipe can cope with. They would not of placed the order if they did not know they were going to have this problem by taking on more customers. I mean why else place an order for an upgrade if you were keeping the capacity to a certain limit? IMO they should have stopped taking on more ppl until the upgrade was placed to avoid any issues with existing customers. 

When I first joined Idnet I was told that this problem of "taking on more than they can cope with" was not going to happen by Idnet themselves on the phone, I mean it was the first thing I asked before joining. You can't blame me for being just a little peeved about it all. I don't spend hr's leeching everything there is to leech online, I just play game's for a few hr's every night. 

Peace out ! 

Thanks for the above tip, I will try that tomorrow around 8pm ;)

houseparty

hi

i know idnet are a good isp, but ive been having high pings for months now on and off, and i told Simon ages ago , i thought there where too may people now onIdnet pipes network.

It nows seems i was correct, for the last 4 or 5 months ive put up with high pings and the net being so slow, now again,i must say Ident are a good isp, but im wondering if its time too move on.

Ive been paying 25 pouinds a month for a service which is near unless too me(as i like to play online games and i cant with this connection) so i then dropped it too 17.99 a month 2 gig a month service.

I went round too a friends house the other day he has a 1 meg ntl internet connection and it was alot faster than my asdl max connection,pages loaded qiuckly no hanging etc it was really nice too be on the internet. Using my internet connection at the momnet is not enjoyable, and its been like that for a few months now.

Simon is a great guy and i do really like Idnet i know they are one of the best ISPs out there, it dont surprise me that Simon posted here letting us  know there are problems, but im now wondering if i move too another isp, im paying alot of money (im not at work)for a poor internet connection, and its really starting too bug me.

houseparty

AvengerUK

#64
NO ISP will EVER say: "No, were not taking orders anymore as were nearly full" - Its just not how buisness works. Best any ISP can do, is order ahead - and it would seem IDnet have done this. They must of ordered the new pipe way before christmass!


"i know idnet are a good isp, but ive been having high pings for months now on and off, and i told Simon ages ago , i thought there where too may people now on Idnet pipes network."

I havent had any issues since i returned HOWEVER if there has been an issue, it would be with balancing.

Lets use another ISP as an example, Enta who are rated higher than IDnet on some compairison sites. With Enta, Congestion quickly came upon them, and they ordered a new central - But, this order wasnt as "Pre-planned" - as in it wasnt ordered months in advance before they actually needed it (i waited 2 months before giving up, and that was with speeds of 200kbs...) , it would seem IDnet have "pre-Planned", but due to circumstances with recent downfalls of other ISP's there customer base has suddenly climbed quickly.

Its just a simple matter of waiting. I made the mistake of leaving with the last ping problem (which was ages and ages ago) - only to fall into a huge problem a month later!

Note: pings have been fine my end for atleast an hour!


maxping

Quote from: Jobe on Jan 09, 2007, 22:57:22
IMO they should have stopped taking on more ppl until the upgrade was placed to avoid any issues with existing customers.

The order was placed in November but BT have a 3 month lead time in November there were no ping issues its just unfortunate they have started now. 



QuoteThanks for the above tip, I will try that tomorrow around 8pm ;)


It worked for me i have just come from my fave server and my pings have been fine since doing the BT log in trick.

AvengerUK

Max, "It worked for me i have just come from my fave server and my pings have been fine since doing the BT log in trick." - my pings have also been fine since you posted your BT login thing...

Co-incidence, OR perhaps it does work and my pings just got better 5 or so minutes after..?

I'll give it a go tomorrow night, and see what happens, better to have more people try it :)

maxping

Bill posted that using the BT log in is  the same as turning the router off for 30 Min's but takes a lot less time. 
As you can see my pings have remained low since using the BT log in.

Pinging idnet.net [212.69.36.10] with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=25ms TTL=60
Reply from 212.69.36.10: bytes=32 time=25ms TTL=60
Reply from 212.69.36.10: bytes=32 time=24ms TTL=60
Reply from 212.69.36.10: bytes=32 time=25ms TTL=60

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

ou7shined

Quote from: simon on Jan 09, 2007, 14:18:15

The sudden increase in traffic has been due to an unforeseen influx of customers recently.


Oh shoot! That means it's al my fault then. Sorry guys. I'll get me jacket. :'( Maybe that's why I hold the record (I think) with a max ping of 826. :o
Rich.

Klaatu barada nikto!

ou7shined

Rich.

Klaatu barada nikto!

DorsetBoy

To put everything into perspective.............I visited my local Maplins store today and in conversation with some of the staff it became very clear that they and many of their customers are experiencing the same problems with speeds/pings/erratic connectiions.
Having spoken to 6 people there,all on different ISP's it is clear that there is a problem that is affecting the "net" in general.

AvengerUK

Quote from: DorsetBoy on Jan 10, 2007, 16:23:02
To put everything into perspective.............I visited my local Maplins store today and in conversation with some of the staff it became very clear that they and many of their customers are experiencing the same problems with speeds/pings/erratic connectiions.
Having spoken to 6 people there,all on different ISP's it is clear that there is a problem that is affecting the "net" in general.


The problems called "BT"  :D

maxping


Mohux_Jnr

#73
This is my results taken this morning, I am an online gamer and have noticed huge fluctuations in ping lately, my download speeds are top notch and exactly the reason I signed up but the primary role of my PC is gameplay, and spikes of over 1000, always at the same location are making me think twice. I also requested before xmas for interleaving to be disabled on my line but this appears to have been overlooked.
To me it appears that every ISP has problems with at least one of its services, Eclipse was poor download speed but good pings, IDNET the opposite, I just want someone who can achieve both  :'(.
Rant over, it can get filed now with the other 10,000 posts on high ping !.

C:\Documents and Settings\Jon>tracert www.idnet.net

Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms 
  2    36 ms    38 ms    35 ms  telehouse-gw-msdp.idnet.net [212.69.63.41]
  3   825 ms  4093 ms   938 ms  212.69.63.10
  4  1209 ms    60 ms  1713 ms  redbus-gw.idnet.net [212.69.63.1]
  5    51 ms    53 ms    52 ms  www.idnet.net [212.69.36.10]

Trace complete.

ou7shined

Woah that's one justified rant - 4093 ms  :o. I caught my pings peaking as high as 800 about a week ago but they seem to have magically finally settled down to around 30 again. I really hope yours gets sorted out soon, otherwise it's spawn kill city for you mate. :angel:
Rich.

Klaatu barada nikto!