Pings

[maxping]

Can someone tell me if theres a 30 days notice or anything like that? ie, my billing data is around the 26th...if i left before that...would i pay again orrrr?

Why not give them time to fix the problem?

*EDIT*

Looks like you may have more info on Monday (just read Kavs post on last page)

[equk]

I should have said earlier, I had a nice phonecall from Miriam yesterday, who said they've been very busy over the last couple of weeks, so what she's planning on doing is looking at the ping problem during this coming weekend when there won't be a lot of phonecalls to interrupt it, and let us know on Monday what the situation is, so it might be worth hanging on until then.

Cool, I hope they sort it out over the weekend then as it's stupid and as you say it's not acceptable or usable for GAMING.

[AvengerUK]

Well, it might and might not. @ MAX : yes, but i sent an email a week or so ago also....

@ karvala - weve heard this before, i cant simply beleive them at all presently, considering weve heard lots and lots of "we'll be doing..." and "were looking into.." over the last month and a 1/2....

At present my pings have stabilised - so for now i can atleast do some gaming!

[AvengerUK]

Can someone tell me if theres a 30 days notice or anything like that? ie, my billing data is around the 26th...if i left before that...would i pay again orrrr?

Why not give them time to fix the problem?

*EDIT*

Looks like you may have more info on Monday (just read Kavs post on last page)

(1 1/2 months theve had max....)

[maxping]

(1 1/2 months theve had max....)

I can see how frustrating it must be but how much actual contact have you had with CS?

All i see is 3 people posting graph after graph and ping results in an endless loop, there seems to be hardly any mention of conversations with Customer Support , when i had my recent interleaving problem i was getting phone calls and emails regularly, i did have to phone a couple of times to ask why i had not got a reply but it was usually down to the office being extremely busy.

[AvengerUK]

Maybe its because IDnet havent emailed me back? - All the convosations with support weve had are posted here!

[equk]

still the same

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.302 ms  0.674 ms  0.645 ms
2  192.168.0.1 (192.168.0.1)  3.187 ms  2.753 ms  3.218 ms
3  telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  164.098 ms  167.151 ms  165.721 ms
4  telehouse-gw-bb.idnet.net (212.69.63.9)  159.070 ms  133.486 ms  108.909 ms
5  redbus-gw.idnet.net (212.69.63.1)  110.896 ms  111.619 ms  102.508 ms
6  www.idnet.net (212.69.36.10)  98.858 ms  106.987 ms  114.605 ms
l8nc graph looks stupid, for 4hours it's been over 100ms ping.

[maxping]

- All the convosations with support weve had are posted here!

If you look back through the thread there hasn't been a lot of feedback in the posts  about your or anyone anyones CS conversations.

As its a free number why haven't you phoned  daily , I'm sure i would be on the phone every day until it was sorted as you are paying for a service you are not getting.

[AvengerUK]

still the same

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.302 ms  0.674 ms  0.645 ms
2  192.168.0.1 (192.168.0.1)  3.187 ms  2.753 ms  3.218 ms
3  telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  164.098 ms  167.151 ms  165.721 ms
4  telehouse-gw-bb.idnet.net (212.69.63.9)  159.070 ms  133.486 ms  108.909 ms
5  redbus-gw.idnet.net (212.69.63.1)  110.896 ms  111.619 ms  102.508 ms
6  www.idnet.net (212.69.36.10)  98.858 ms  106.987 ms  114.605 ms
l8nc graph looks stupid, for 4hours it's been over 100ms ping.

My graph has settled down for the last 20mins, however i doubt it will stay like that - it did this yesterday also, brief periods of "ok" lol

I said why before max....tracerts and l8nc grpahs cant be sent over a phone call. All my talks with simon also required results (on the whole) to be sent via email - etc etc. Max, are you deliberatly trying to sorta say in a none-direct way somewhere along the lines of "Were all talking absoulute rubbish and IDnet are not to blame?// Were not doing what we should be doing?" etc etc

[Scott]

Now then ladies 

As you will undoubtedly see this thread has run and run. I've no intention of closing things and getting heavy-handed but lets stay focussed on the topic and not let frustrations or problems result in " 'aving a go at one another" in a none-too-subtle ' you lookin' at me ? ' fashion

Stay on target...
[oh dear !  Name the film !]

[AvengerUK]

 

Stay on target...
[oh dear !   Name the film !]

- i dont get it 

Pings are still stable to my suprise however!

[equk]

I just re-synced the router and it seems to be better again, tried reconnect first which did nothing but on a re-sync it seems to be back to how it was.

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.275 ms  0.683 ms  0.645 ms
2  192.168.0.1 (192.168.0.1)  3.140 ms  2.801 ms *
3  telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  25.456 ms  33.927 ms  23.670 ms
4  telehouse-gw-bb.idnet.net (212.69.63.9)  26.657 ms  23.342 ms  27.088 ms
5  * redbus-gw.idnet.net (212.69.63.1)  195.557 ms  328.839 ms
6  www.idnet.net (212.69.36.10)  26.135 ms  24.906 ms  23.717 ms

[AvengerUK]

check the second to last line:

5  * redbus-gw.idnet.net (212.69.63.1)  195.557 ms  328.839 ms

[karvala]

[LOL, Use the Force, Luke]

Let me clarify the situation regarding the thread and IDNet.  I've certainly been having some communication with IDNet about the issue, but I haven't mentioned most of the correspondence because to me e-mail or telephone communication is essentially private; I wouldn't want IDNet staff to think that if they contacted me, the resultant conversation would be plastered all over the internet.  That would seem unfair on them, hence I tend not to mention it; that shouldn't be mistaken for thinking that there has been no correspondence, however.

In addition, I post regularly in this thread not as a way of trying to attract attention, or let off steam, or anything like that, but rather simply to provide as much information as I can to help the IDNet staff diagnose what appears to be a difficult problem.  I could e-mail them all the details (and have done, when requested by them), but it would seem rude and intrusive to me to hammer their e-mail or telephone all day long with ping problem information, so I prefer to post the information here, and let them view it at their leisure.

I should also add that there are definitely more than three people experiencing the problem.  There are at least half a dozen who've posted relatively recently in this thread alone that are still experiencing it, and as probably only gamers and hardcore techies would even notice the problem most of the time, especially as it tends to be limited to the time that most people are at work, I suspect in reality there could be ten times that number or more who actually have the problem.  To treat it as an isolated problem for just two or three people would, IMO, be a mistake.  In support of this, I could point out that the 65s ping response spike of one of the routers was declared as an isolated problem affecting only a handful of people until we got a few more people to test it, and then had it properly looked at, and in fact turned out to affect everyone (though not a problem in the end), just most people wouldn't have noticed it because they don't routinely ping that router.

While I'm here, some more info  .  I think philco is on the right lines in suggesting it's a bad pipe or gateway interface (the problem is certainly related to the gateway; that's crystal clear), and can change as a function of session.  My current l8c graph shows a step change in minimum ping time and reliability each time I disconnected, logged into the BT test connection, and then disconnected and logged back into IDNet.

[maxping]

Max, are you deliberatly trying to sorta say in a none-direct way somewhere along the lines of "Were all talking absoulute rubbish and IDnet are not to blame?// Were not doing what we should be doing?" etc etc

No i can see you have problems and i understand you cannot show pics on the phone.

I would be ringing and saying "get the thread over at idnetters on your screen and tell me why my ping is so high"

I would do this every day until i got an answer.

No one should have to put up with pings like that for 6 weeks.

[equk]

wow nice the re-sync lasted 30mins

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.299 ms  0.697 ms  0.658 ms
2  192.168.0.1 (192.168.0.1)  3.251 ms  2.788 ms  3.150 ms
3  * telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  137.405 ms  117.683 ms
4  telehouse-gw-bb.idnet.net (212.69.63.9)  131.417 ms  116.606 ms  125.616 ms
5  redbus-gw.idnet.net (212.69.63.1)  127.201 ms  105.649 ms  90.449 ms
6  www.idnet.net (212.69.36.10)  92.908 ms  74.662 ms  81.778 ms

Are we expected to re-sync every 30mins?  

[Scott]

Stay on target...
[oh dear !   Name the film !]

- i dont get it 

Pings are still stable to my suprise however!

Star wars....in the death star trench  now where did I put my coat ?

[AvengerUK]

Max, are you deliberatly trying to sorta say in a none-direct way somewhere along the lines of "Were all talking absoulute rubbish and IDnet are not to blame?// Were not doing what we should be doing?" etc etc

No i can see you have problems and i understand you cannot show pics on the phone.

I would be ringing and saying "get the thread over at idnetters on your screen and tell me why my ping is so high"

I would do this every day until i got an answer.

No one should have to put up with pings like that for 6 weeks.

Appolgies for *almost* loosing my temper...its been a long week 

[maxping]

No probs mate i know how frustrating things can be look at the fun i recently had with BT.

I hope it gets sorted as i don't want to see any regular leave.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Especially as you have the game server (only joking) 

[AvengerUK]

Thats one of things i like about IDnet....the community

So far this morning: Stable for 1hr

Now pings are steadily increasing 

[equk]

pings atm seem a bit high, altho stable

pinging servers that were 30ms at 60ms

Code Select Expand

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

  1     1 ms    <1 ms    <1 ms  cisco [192.168.1.1]
  2     3 ms     2 ms     2 ms  192.168.0.1
  3    37 ms    36 ms    36 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
  4    38 ms    35 ms    39 ms  telehouse-gw-bb.idnet.net [212.69.63.9]
  5    36 ms    37 ms    37 ms  redbus-gw.idnet.net [212.69.63.1]
  6    37 ms    37 ms    36 ms  www.idnet.net [212.69.36.10]

Trace complete.
36ms to the gateway 

[AvengerUK]

28ms to the gateway, slightly higer than normal, but nothing much.

However, spiking http://www.l8nc.com/graph.php?jid=58e61f6e3d3d258ec640ec3f21295d2e occasionally - nothing dire!

[karvala]

As you can see, mine's been fine today: http://www.l8nc.com/graph.php?sid=3e558fac2c207d467e5e2158e6aa1359&jid=aaa18fb159292b32e9b02f8f3ebacecf&day=today.  I've just rebooted the router, though, so we'll see what the connection's like now.

[equk]

looking at my latency graph there are timeouts or disconnects at 10:20, then at 11:00 to 11:30, and again at 12:05 also seems to be a hike in ping times by 10ms after the timeout at 12:05.

Ping to the gateway  is also still 36ms 

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.287 ms  0.684 ms  0.640 ms
2  192.168.0.1 (192.168.0.1)  3.196 ms  2.773 ms  3.187 ms
3  telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  36.354 ms  35.050 ms *
4  telehouse-gw-bb.idnet.net (212.69.63.9)  34.310 ms  35.051 ms  36.036 ms
5  redbus-gw.idnet.net (212.69.63.1)  35.591 ms  35.909 ms  35.391 ms
6  www.idnet.net (212.69.36.10)  34.772 ms  35.463 ms *

[equk]

re-sync seemed to sort it out for now, not sure for how long tho

Code Select Expand

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

  1    <1 ms    <1 ms    <1 ms  cisco [192.168.1.1]
  2     2 ms     2 ms     2 ms  192.168.0.1
  3    36 ms    34 ms    35 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
  4    35 ms    37 ms    37 ms  telehouse-gw-bb.idnet.net [212.69.63.9]
  5    36 ms    36 ms    37 ms  redbus-gw.idnet.net [212.69.63.1]
  6    37 ms    36 ms    37 ms  www.idnet.net [212.69.36.10]

Trace complete.

Code Select Expand

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

  1    <1 ms    <1 ms    <1 ms  cisco [192.168.1.1]
  2     2 ms     2 ms     3 ms  192.168.0.1
  3    24 ms    24 ms    24 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
  4    25 ms    25 ms    24 ms  telehouse-gw-bb.idnet.net [212.69.63.9]
  5    25 ms    25 ms    23 ms  redbus-gw.idnet.net [212.69.63.1]
  6    25 ms    25 ms    24 ms  www.idnet.net [212.69.36.10]