increasing ping times

Started by coreservers, Apr 18, 2010, 21:11:50

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

coreservers

the connection has been relatively stable last couple of weeks, but tonight in the middle of some online flight simming. I got kicked off
I treid to re-connect but the lag was awful again. so did a tracert, and ping times etc are all above 50ms

DSLzoneUK is showing a connection of just over 1mb, and BT speedtester wont even load

http://www.dslzoneuk.net/speedtest/speedtest.php?id=1115856




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

C:\Documents and Settings\Sonas>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    55 ms    52 ms    57 ms  telehouse-gw4-lo2.idnet.net [212.69.63.99]
  3    63 ms    66 ms    51 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

  4    57 ms    49 ms    53 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5    61 ms    62 ms    60 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6    54 ms    58 ms    62 ms  www.idnet.net [212.69.36.10]

Trace complete.

C:\Documents and Settings\Sonas>ping www.idnet.net

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

Reply from 212.69.36.10: bytes=32 time=58ms TTL=59
Reply from 212.69.36.10: bytes=32 time=52ms TTL=59
Reply from 212.69.36.10: bytes=32 time=47ms TTL=59
Reply from 212.69.36.10: bytes=32 time=56ms TTL=59

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

C:\Documents and Settings\Sonas>
If you truly believe you need to pick a mobile phone that 'says something' about your personality, don't bother. You don't have a personality. A mental illness, maybe - but not a personality

RA-1972

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

C:\>ping idnet.net

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

Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=21ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=19ms TTL=59

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

>

coreservers

the lag posting pages (including posting on here is now 12-15 seconds between pressing the submit button and it changing
If you truly believe you need to pick a mobile phone that 'says something' about your personality, don't bother. You don't have a personality. A mental illness, maybe - but not a personality

coreservers

Date ISP Test Result % IP Test ID
18 Apr 2010, 21:14 IDNet 7178 648 9 1115858
18 Apr 2010, 21:01 IDNet 8128 1010 14 1115856


As you can see on here speed is suddenly dying again down to 648k
If you truly believe you need to pick a mobile phone that 'says something' about your personality, don't bother. You don't have a personality. A mental illness, maybe - but not a personality

Lance

That shows that you've had a resync. Its your upload which has dropped to 648k. Have you tried rebooting the router?
Lance
_____

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

coreservers

nah the download speeds are manually entered and the dsluk speed tester tests against that. I initially entered teh max line speed at 8mb and it tested at 1010, then entered the actual router sync speed at 7178, and it re-tested at 648k
If you truly believe you need to pick a mobile phone that 'says something' about your personality, don't bother. You don't have a personality. A mental illness, maybe - but not a personality

Steve

My connection with IDNet seems fine!





PING www.idnet.net (212.69.36.10): 56 data bytes
64 bytes from 212.69.36.10: icmp_seq=0 ttl=59 time=20.528 ms
64 bytes from 212.69.36.10: icmp_seq=1 ttl=59 time=20.201 ms
64 bytes from 212.69.36.10: icmp_seq=2 ttl=59 time=19.278 ms
64 bytes from 212.69.36.10: icmp_seq=3 ttl=59 time=19.807 ms
64 bytes from 212.69.36.10: icmp_seq=4 ttl=59 time=19.870 ms
64 bytes from 212.69.36.10: icmp_seq=5 ttl=59 time=19.519 ms
64 bytes from 212.69.36.10: icmp_seq=6 ttl=59 time=19.175 ms
64 bytes from 212.69.36.10: icmp_seq=7 ttl=59 time=19.808 ms
64 bytes from 212.69.36.10: icmp_seq=8 ttl=59 time=20.312 ms
64 bytes from 212.69.36.10: icmp_seq=9 ttl=59 time=19.312 ms

--- www.idnet.net ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 19.175/19.781/20.528/0.440 ms

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

zappaDPJ

I've had a few oddities as well tonight. BBC iPlayer tells me I have insufficient bandwidth to view programs and I've had some major lag issues with a voice comms program. I don't think it's a problem with IDNet because my speeds are great on a speed test and my pings are well...

QuoteMicrosoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\zappaDPJ>ping idnet.com

Pinging idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=9ms TTL=59
Reply from 212.69.36.10: bytes=32 time=8ms TTL=59
Reply from 212.69.36.10: bytes=32 time=9ms TTL=59
Reply from 212.69.36.10: bytes=32 time=9ms TTL=59

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

C:\Users\zappaDPJ>

Amazing!



I've no idea what the issue might be but it seems to lie outside of IDNet.
zap
--------------------

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

Rik

Another LINX problem maybe? Has anyone asked support?
Rik
--------------------

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

zappaDPJ

I haven't been in touch Rik but I became suspicious of that low ping which reminded me that I'd swap back to WBC when the last Lynx problem occurred and not swapped back. That connection appears to still have issues so it's probably local to me.
zap
--------------------

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

Rik

I'll see if there's any news.
Rik
--------------------

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