Have any problems been reported?

Started by psp83, Apr 06, 2010, 15:10:29

Previous topic - Next topic

0 Members and 2 Guests are viewing this topic.

psp83

Quote from: esh on Apr 07, 2010, 12:34:22
"For the last 2 days all 21CN-BS BRASs have been showing increased peak and minimum latency between the hours of 9am - 5pm."

So say the broadband gods of AAISP.

Thats what I'm seeing. Last night it cleared in the evening but back again today. I bet it clears up tonight again.

psp83

Well thats weird.

I've noticed that since being on ADSL2, When support check your line / run diagnostics it now disconnects me. Never happened on ADSL1.

Can't wait for the holidays to be over, Pings getting higher and higher!

Rik

I've never had that happen, Paul, except on one occasion when they warned me it would.
Rik
--------------------

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

psp83

Happened both times support has checked my line now, Doesn't worry me thou, everytime they do it I sync higher!  ;D

Rik

I must get them to test my line more often. ;D
Rik
--------------------

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

psp83

lol..


Just a little frustrated with support at the mo  :(

Rik

Rik
--------------------

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

psp83

Quote from: Rik on Apr 07, 2010, 15:20:30
Why?

It just seems like they don't want to look into it or care. Thats twice now it feels like they've just pushed it to the side.

QuoteThe ping results carried out using the Windows command prompt with the PC booted into safe mode are perfectly fine and show no problems although are an improvement over the initial pings when not booted into safe mode. The connection is currently on fast path so has not been interleaved. it may be worth testing the connection using a different router and PC on the connection to determine if any improvement is seen.

As I replied to the email, I dont think those pings are acceptable, esp for voice comms and online games and with todays pings being over 120ms.

Also said I've tried with Vista, Win 7, XP and Linux, Plus this is my 4th router in 3yrs since being with IDnet and since I've joined I've always had a ping around 15ms (except when BT delayed the pipe upgrade for IDnet)

And that it can't be the router if my pings went back to normal last night after 6pm.

Rik

It's difficult for them too look into. Ping times are no part of the BT spec for the service, so it's virtually impossible to raise a fault on it. They seem to be suggesting the possibilities for any local issues, so that you can try them if you want to. The fact that pings improved after 6pm tallies with my theory that it's exchange congestion during the school holidays, we see it at Christmas as well. The fact that safe mode improved things, as I read it, says that there's some background process affecting the machine.

I'll see if I can find out anything more for you.
Rik
--------------------

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

psp83

Today I've been doing all my ping tests directly from the router so windows is not there to causes any problems, everytime I've done it, pings have been into the hundred+ range, I also do it from XP on my netbook over wireless and from this main pc (ethernet) from command prompt so I get an average, I know operating systems always adds a few ms ontop, I allow for 10ms to be added.

psp83

#60
I think its congestion aswell, as its getting later my pings are dropping slowly. Its just frustrating. I was meant to have a voice chat with a firm in india today about some work but can't because of it breaking up / not connecting.

From this earlier :

C:\Users\Paul>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  192.168.0.1
  2   124 ms   117 ms   119 ms  telehouse-gw2-lo1.idnet.net [212.69.63.51]
  3   113 ms   113 ms   121 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
  4   136 ms   132 ms   124 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5   131 ms   125 ms   117 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6   121 ms   122 ms   130 ms  www.idnet.net [212.69.36.10]

Trace complete.



To now :

C:\Users\Paul>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  192.168.0.1
  2    35 ms    35 ms    36 ms  telehouse-gw2-lo1.idnet.net [212.69.63.51]
  3    37 ms    37 ms    40 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
  4    27 ms    22 ms    21 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5    21 ms    21 ms    22 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6    22 ms    18 ms    20 ms  www.idnet.net [212.69.36.10]

Trace complete.

Rik

Have you tried doing a speedtest when the pings are high?
Rik
--------------------

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

psp83

Yeh, speed test always come back fine, between 4.5mb - 5.3mb on a 5500 profile.

Rik

Which would argue against congestion. As there are no widespread reports of ping issues, that leaves is with a local problem, your pings are consistently around the same level at every hop of the tracert.
Rik
--------------------

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

psp83

And its weird AAISP has posted something on there status page saying about increased ping times between 9am - 5pm for the past 2 days, exactly when my problems started.

My mate is on ADSL1 on the same exchange and he has no problems which makes me believe the AAISP post is correct or something along them lines.

Rik

Rik
--------------------

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

psp83

And to prove my point even more..

Directly from the router :

PING 212.69.36.10 (212.69.36.10): 56 data bytes
64 bytes from 212.69.36.10: icmp_seq=0 ttl=60 time=15.0 ms
64 bytes from 212.69.36.10: icmp_seq=1 ttl=60 time=15.0 ms
64 bytes from 212.69.36.10: icmp_seq=2 ttl=60 time=15.0 ms
64 bytes from 212.69.36.10: icmp_seq=3 ttl=60 time=15.0 ms

--- 212.69.36.10 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 15.0/15.0/15.0 ms



From this pc :

C:\Users\Paul>tracert www.idnet.net

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

  1     2 ms    <1 ms    <1 ms  192.168.0.1
  2    26 ms    19 ms    19 ms  telehouse-gw2-lo1.idnet.net [212.69.63.51]
  3    19 ms    19 ms    19 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
  4    20 ms    19 ms    18 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5    20 ms    19 ms    19 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6    19 ms    20 ms    20 ms  www.idnet.net [212.69.36.10]

Trace complete.


Its getting towards the evening and pings starting to get low again.


Rik

Quote from: psp83 on Apr 07, 2010, 16:06:33
And its weird AAISP has posted something on there status page saying about increased ping times between 9am - 5pm for the past 2 days, exactly when my problems started.

It goes on too say it's only affecting 1.88% of users, Paul, which seems contradictory. My pings remain at 13-15ms, so clearly it's not as simple as AAISP report. BT have not advised IDNet of any issues, so IDNet are checking and will let me know.
Rik
--------------------

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

psp83

Cheers. I put in the email to support about the AAISP post anyways. Its weird that my problems started the same time they noticed an issue with 21cn lines and was fine before.

And as my pings show above.. they get better as the evening gets here.

Rik

BT deny all knowledge of the AAISP claim. There are, however, a series of emergency planned engineering works, starting tonight in north and east London, to increase capacity on 21CN. This should not be affecting you however, particularly given the speeds you are seeing. Typically, if affacted (and I have been in the past), speeds will drop to 5-600k.
Rik
--------------------

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

psp83

Typical BT though, Deny everything!

Just got an email from Simon, Looks like I will have to dig through the loft to find my other netgear out.

Rik

Rik
--------------------

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

Technical Ben

Quote from: Rik on Apr 07, 2010, 15:59:09
Which would argue against congestion. As there are no widespread reports of ping issues, that leaves is with a local problem, your pings are consistently around the same level at every hop of the tracert.
I got some days with high bandwidth, but low pings (latency) when I was on O2. That was down to congestion on the virtual path (if that's the correct name). My exchange gets no congestion, but O2 did not have the bandwidth.
Other than that, have you done traces throughout the day? Could it be possible the connection is going over more "hops" when the ping is high?
[edit] Oh, could it be maintenance in the day? Like someone digging the road up?
I use to have a signature, then it all changed to chip and pin.

psp83

#73
Well whatever BT is doing tonight my connection is really cr*p at the mo.

Websites taking ages to load.



Just hope its better when I get up.

psp83