Have any problems been reported?

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

Previous topic - Next topic

0 Members and 3 Guests are viewing this topic.

Rik

Your results don't quite make sense, Paul, slower speeds and lower pings are the opposite of what I'd expect to see with congestion.
Rik
--------------------

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

esh

Nice and steady 12ms +/- 0.5ms from where I am at, not that that's any surprise or consolation.

The only relation I can think of Rik, is that ping times obviously decrease with packet size. Though it would be far too strange to see *that* changing. It just sounds like a terrible misconfiguration somewhere along the line I'd guess...
CompuServe 28.8k/33.6k 1994-1998, BT 56k 1998-2001, NTL Cable 512k 2001-2004, 2x F2S 1M 2004-2008, IDNet 8M 2008 - LLU 11M 2011

Rik

It still 'feels' like a congested VP to me, esh...
Rik
--------------------

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

esh

Perhaps the load balancing is wonky. That would be indirectly related to congestion.
CompuServe 28.8k/33.6k 1994-1998, BT 56k 1998-2001, NTL Cable 512k 2001-2004, 2x F2S 1M 2004-2008, IDNet 8M 2008 - LLU 11M 2011

Rik

There's no load balancing as such, now that everyone is on the hostlink.
Rik
--------------------

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

esh

Ah, yes... well I guess we're just back to congestion now :( I've only had it really bad once and luckily a router reset made it all go away.

You see, people should run fancy plotting software like mine and make a gigantic graph with ludicrously arbitrary numerical schemes and then try and make sense of it all. It's the way forward!  :angel:
CompuServe 28.8k/33.6k 1994-1998, BT 56k 1998-2001, NTL Cable 512k 2001-2004, 2x F2S 1M 2004-2008, IDNet 8M 2008 - LLU 11M 2011

Rik

 ;D

I struggle to make sense of life. ;)
Rik
--------------------

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

psp83

Quote from: Rik on Apr 08, 2010, 08:40:10
Your results don't quite make sense, Paul, slower speeds and lower pings are the opposite of what I'd expect to see with congestion.

Welcome to the world of my line!  ;D

I've just put my old router in, My trusted Netgear DG834G.

Pings are up and down but gunna give it 30 mins to settle in and warm up since its been in the cold loft for months.

One thing I have noticed, I get better stats from this one.

ADSL Link     Downstream     Upstream
Connection Speed    7048 kbps    1024 kbps
Line Attenuation    39 db    11.5 db
Noise Margin    15 db    5 db

500k increase on downstream,
200k increase on upstream,
downstream line attenuation has dropped from 42 to 39.

So maybe the new router started to dislike my line?

psp83

Well pings have seem to settle..

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  www.routerlogin.com [192.168.0.1]
  2    80 ms    75 ms    72 ms  telehouse-gw2-lo1.idnet.net [212.69.63.51]
  3    83 ms    84 ms    81 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
  4    76 ms    77 ms    80 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5    78 ms    83 ms    82 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6    63 ms    66 ms    64 ms  www.idnet.net [212.69.36.10]

Trace complete.




:(

psp83


Rik

So are things better or not, Paul?
Rik
--------------------

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

psp83

No, Still high pings with this 2nd router.

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  www.routerlogin.com [192.168.0.1]
  2    96 ms    94 ms    97 ms  telehouse-gw2-lo1.idnet.net [212.69.63.51]
  3    84 ms    86 ms    89 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
  4   111 ms   110 ms   118 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5   110 ms   109 ms   100 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6   101 ms   105 ms   106 ms  www.idnet.net [212.69.36.10]

Trace complete.


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=130.0 ms
64 bytes from 212.69.36.10: icmp_seq=1 ttl=60 time=100.0 ms
64 bytes from 212.69.36.10: icmp_seq=2 ttl=60 time=120.0 ms
64 bytes from 212.69.36.10: icmp_seq=3 ttl=60 time=100.0 ms

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

Getting the same thing from support each time I phone, Just at the stage of giving up.

Rik

The same thing being? How are you pinging, manually or via software like ping plotter?
Rik
--------------------

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

psp83

Pings are not guaranteed, nothing they can do etc.

I do ping tests from command prompt and from the diagnostic page on the router.

This one is done by command prompt ran as admin.

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  www.routerlogin.com [192.168.0.1]
  2    96 ms    94 ms    97 ms  telehouse-gw2-lo1.idnet.net [212.69.63.51]
  3    84 ms    86 ms    89 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
  4   111 ms   110 ms   118 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5   110 ms   109 ms   100 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6   101 ms   105 ms   106 ms  www.idnet.net [212.69.36.10]

Trace complete.



This one is done from the diagnostics page on 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=130.0 ms
64 bytes from 212.69.36.10: icmp_seq=1 ttl=60 time=100.0 ms
64 bytes from 212.69.36.10: icmp_seq=2 ttl=60 time=120.0 ms
64 bytes from 212.69.36.10: icmp_seq=3 ttl=60 time=100.0 ms

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

Rik

Well, they are right, I said before that pings are not considered in BT's service spec. About the only thing I can suggest is to move to a business package if you're not already on one...
Rik
--------------------

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

psp83

And my arguement with support is, how can I have great low pings of 15ms for 3yrs then suddenly one night everything changes without a reason. Something must be wrong somewhere. I've done all the test support has asked me to do.

psp83

Quote from: Rik on Apr 08, 2010, 15:14:12
Well, they are right, I said before that pings are not considered in BT's service spec. About the only thing I can suggest is to move to a business package if you're not already on one...

Sorry but I'm not paying more money for less of a service. If I do move, it'll be to another ISP that charges less if I cant get the low pings.

Rik

I can understand that. If you have LLU available, that should escape the issues of BT's inadequacies.
Rik
--------------------

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

psp83

I'm gunna wait until AAISP stop reporting a problem and see if it clears my problem up aswell.

QuoteDetails
Yesterday 11:58:18    

For the last 2 days all 21CN-BS BRASs have been showing increased peak and minimum latency between the hours of 9am - 5pm.

BT have been advised and are investigating

Update
Yesterday 14:55:10    

BT have raised an incident, and BTO are investigating.

Update
Yesterday 16:50:06    

Upgrade is required to fix the problem.
BT are working on it.

Update
Today 10:29:13    

Still awaiting update on the required upgrade.

Update
Today 15:00:08    

Upgrade is still under planning.

If it doesn't show no improvement on the 20th, when the kids are back at school then I will be looking for a new ISP.

psp83

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  www.routerlogin.com [192.168.0.1]
  2    25 ms    17 ms    18 ms  telehouse-gw2-lo1.idnet.net [212.69.63.51]
  3    17 ms    17 ms    16 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
  4    20 ms    20 ms    17 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5    17 ms    18 ms    17 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6    18 ms    17 ms    17 ms  www.idnet.net [212.69.36.10]

Trace complete.

First set of pings to come back under 20ms in the afternoon for a few days :eek4:

Rik

It's sunny, the kids are outside?
Rik
--------------------

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

Glenn

Glenn
--------------------

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

psp83

Quote from: Rik on Apr 08, 2010, 16:17:51
It's sunny, the kids are outside?

Its been sunny with blue skys all week here. Perhaps thats the cause  ;)

Rik

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

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

Rik

Quote from: psp83 on Apr 08, 2010, 16:21:26
Its been sunny with blue skys all week here. Perhaps thats the cause  ;)

I must move. :)
Rik
--------------------

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