High pings again

Started by glen, Jul 20, 2009, 10:34:43

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Wags

Quote from: Rik on Sep 16, 2009, 12:01:08
He never sleeps. ;)

So it would seem....and I thought I worked long hours :whistle:

Rik

I've had email from Simon at 4am, but then you have to ask why I was awake too. ;D
Rik
--------------------

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

Wags

Just popped home (living near my office has advantages!)
Rebooted the router after leaving it off for 15 mins:

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

Reply from 212.69.36.10: bytes=32 time=14ms TTL=59
Reply from 212.69.36.10: bytes=32 time=13ms TTL=59
Reply from 212.69.36.10: bytes=32 time=14ms TTL=59
Reply from 212.69.36.10: bytes=32 time=15ms 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 = 13ms, Maximum = 15ms, Average = 14ms

Simon

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

mrapoc

High pings for me now  >:(

2142 was giving me 130ms ish pings

not playable

QuoteC:\Users\Sam>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=111ms TTL=59
Reply from 212.69.36.10: bytes=32 time=94ms TTL=59
Reply from 212.69.36.10: bytes=32 time=156ms TTL=59
Reply from 212.69.36.10: bytes=32 time=181ms 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 = 94ms, Maximum = 181ms, Average = 135ms


1 min later

QuoteC:\Users\Sam>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=113ms TTL=59
Reply from 212.69.36.10: bytes=32 time=127ms TTL=59
Reply from 212.69.36.10: bytes=32 time=114ms TTL=59
Reply from 212.69.36.10: bytes=32 time=151ms 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 = 113ms, Maximum = 151ms, Average = 126ms

QuoteC:\Users\Sam>tracert www.idnet.net

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

  1     4 ms     3 ms     3 ms  home
  2    99 ms    90 ms   149 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3   123 ms   120 ms   122 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

  4   117 ms   121 ms   130 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5   114 ms   120 ms   138 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6   124 ms   125 ms   134 ms  www.idnet.net [212.69.36.10]

Trace complete.

Rik

Have you re-booted, Sam?
Rik
--------------------

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

Gary

I have to say I have never know a provider that asks you to reboot routers so often  ??? if you leave it be it resolves itself but thats not great for gaming, last night on the PS3 was murder.

When is Max going over to the giglink, Rik?
Damned, if you do damned if you don't

mrapoc

just turned off for up until now since last post

QuoteC:\Users\Sam>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=151ms TTL=59
Reply from 212.69.36.10: bytes=32 time=182ms TTL=59
Reply from 212.69.36.10: bytes=32 time=129ms TTL=59
Reply from 212.69.36.10: bytes=32 time=133ms 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 = 129ms, Maximum = 182ms, Average = 148ms

QuoteC:\Users\Sam>tracert www.idnet.net

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

 1     5 ms     5 ms     7 ms  home [192.168.1.254]
 2   193 ms   188 ms   185 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
 3   170 ms   147 ms   171 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

 4   205 ms   310 ms   271 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
 5   143 ms   149 ms   157 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
 6   173 ms   166 ms   172 ms  www.idnet.net [212.69.36.10]

Trace complete.

oh dear...

i cant be having this  :'(

hurts to say it but i had less ping problems with talktalk (although i didnt have internet most of the time xD)

Rik

Have a word with support, Sam.
Rik
--------------------

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

mrapoc

gotta email some pings in and TRY to get the bt speedtester to work which will be fun

Rik

It seems to have been better, lately, Sam. You've got no background activity going on, have you?
Rik
--------------------

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

mrapoc

nothing

whats the support email?

Rik

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

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

mrapoc

and ping www.idnet.net -t50 should give me 50 pings?

cheers

Rik

-n 50, Sam, don't forget the space.



Usage: ping [-t] [-a] [-n count] [-l size] [-f] [-i TTL] [-v TOS]
            [-r count] [-s count] [[-j host-list] | [-k host-list]]
            [-w timeout] target_name

Options:
    -t             Ping the specified host until stopped.
                   To see statistics and continue - type Control-Break;
                   To stop - type Control-C.
    -a             Resolve addresses to hostnames.
    -n count       Number of echo requests to send.
    -l size        Send buffer size.
    -f             Set Don't Fragment flag in packet.
    -i TTL         Time To Live.
    -v TOS         Type Of Service.
    -r count       Record route for count hops.
    -s count       Timestamp for count hops.
    -j host-list   Loose source route along host-list.
    -k host-list   Strict source route along host-list.
    -w timeout     Timeout in milliseconds to wait for each reply.


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

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

mrapoc

ok cool

ill share my results here too to see if it helps

seems the bt speedtester reset my connection and it improves again - for how long

QuoteHello, Just been on the phone about my ping problems and told to provide some tests.

This is after turning router off for 30 mins

No other activity on the network.

I did the bt speedtest but stupidly forgot to copy and paste, but apparently you (the isp) get the results anyway.

C:\Users\Sam>ping www.idnet.net -t

Pinging www.idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=133ms TTL=59
Reply from 212.69.36.10: bytes=32 time=135ms TTL=59
Reply from 212.69.36.10: bytes=32 time=165ms TTL=59
Reply from 212.69.36.10: bytes=32 time=143ms TTL=59
Reply from 212.69.36.10: bytes=32 time=129ms TTL=59
Reply from 212.69.36.10: bytes=32 time=159ms TTL=59
Reply from 212.69.36.10: bytes=32 time=173ms TTL=59
Reply from 212.69.36.10: bytes=32 time=138ms TTL=59
Reply from 212.69.36.10: bytes=32 time=94ms TTL=59
Reply from 212.69.36.10: bytes=32 time=126ms TTL=59
Reply from 212.69.36.10: bytes=32 time=156ms TTL=59
Reply from 212.69.36.10: bytes=32 time=164ms TTL=59
Reply from 212.69.36.10: bytes=32 time=144ms TTL=59
Reply from 212.69.36.10: bytes=32 time=127ms TTL=59
Reply from 212.69.36.10: bytes=32 time=169ms TTL=59
Reply from 212.69.36.10: bytes=32 time=116ms TTL=59
Reply from 212.69.36.10: bytes=32 time=152ms TTL=59
Reply from 212.69.36.10: bytes=32 time=177ms TTL=59
Reply from 212.69.36.10: bytes=32 time=156ms TTL=59
Reply from 212.69.36.10: bytes=32 time=170ms TTL=59
Reply from 212.69.36.10: bytes=32 time=180ms TTL=59
Reply from 212.69.36.10: bytes=32 time=113ms TTL=59
Reply from 212.69.36.10: bytes=32 time=119ms TTL=59
Reply from 212.69.36.10: bytes=32 time=114ms TTL=59
Reply from 212.69.36.10: bytes=32 time=112ms TTL=59
Reply from 212.69.36.10: bytes=32 time=89ms TTL=59
Reply from 212.69.36.10: bytes=32 time=152ms TTL=59
Reply from 212.69.36.10: bytes=32 time=129ms TTL=59
Reply from 212.69.36.10: bytes=32 time=97ms TTL=59
Reply from 212.69.36.10: bytes=32 time=118ms TTL=59
Reply from 212.69.36.10: bytes=32 time=40ms TTL=59
Reply from 212.69.36.10: bytes=32 time=63ms TTL=59
Reply from 212.69.36.10: bytes=32 time=104ms TTL=59
Reply from 212.69.36.10: bytes=32 time=137ms TTL=59
Reply from 212.69.36.10: bytes=32 time=69ms TTL=59
Reply from 212.69.36.10: bytes=32 time=95ms TTL=59
Reply from 212.69.36.10: bytes=32 time=159ms TTL=59
Reply from 212.69.36.10: bytes=32 time=141ms TTL=59
Reply from 212.69.36.10: bytes=32 time=165ms TTL=59
Reply from 212.69.36.10: bytes=32 time=120ms TTL=59
Reply from 212.69.36.10: bytes=32 time=115ms TTL=59
Reply from 212.69.36.10: bytes=32 time=118ms TTL=59
Reply from 212.69.36.10: bytes=32 time=178ms TTL=59
Reply from 212.69.36.10: bytes=32 time=191ms TTL=59
Reply from 212.69.36.10: bytes=32 time=90ms TTL=59
Reply from 212.69.36.10: bytes=32 time=131ms TTL=59
Reply from 212.69.36.10: bytes=32 time=157ms TTL=59
Reply from 212.69.36.10: bytes=32 time=173ms TTL=59
Reply from 212.69.36.10: bytes=32 time=138ms TTL=59
Reply from 212.69.36.10: bytes=32 time=148ms TTL=59
Reply from 212.69.36.10: bytes=32 time=186ms TTL=59
Reply from 212.69.36.10: bytes=32 time=127ms TTL=59
Reply from 212.69.36.10: bytes=32 time=125ms TTL=59
Reply from 212.69.36.10: bytes=32 time=142ms TTL=59
Reply from 212.69.36.10: bytes=32 time=102ms TTL=59
Reply from 212.69.36.10: bytes=32 time=89ms TTL=59
Reply from 212.69.36.10: bytes=32 time=92ms TTL=59
Reply from 212.69.36.10: bytes=32 time=107ms TTL=59
Reply from 212.69.36.10: bytes=32 time=113ms TTL=59
Reply from 212.69.36.10: bytes=32 time=121ms TTL=59
Reply from 212.69.36.10: bytes=32 time=92ms TTL=59
Reply from 212.69.36.10: bytes=32 time=63ms TTL=59
Reply from 212.69.36.10: bytes=32 time=88ms TTL=59
Reply from 212.69.36.10: bytes=32 time=138ms TTL=59
Reply from 212.69.36.10: bytes=32 time=113ms TTL=59
Reply from 212.69.36.10: bytes=32 time=117ms TTL=59
Reply from 212.69.36.10: bytes=32 time=131ms TTL=59
Reply from 212.69.36.10: bytes=32 time=160ms TTL=59
Reply from 212.69.36.10: bytes=32 time=149ms TTL=59
Reply from 212.69.36.10: bytes=32 time=129ms TTL=59
Reply from 212.69.36.10: bytes=32 time=166ms TTL=59
Reply from 212.69.36.10: bytes=32 time=173ms TTL=59
Reply from 212.69.36.10: bytes=32 time=134ms TTL=59
Reply from 212.69.36.10: bytes=32 time=144ms TTL=59
Reply from 212.69.36.10: bytes=32 time=111ms TTL=59
Reply from 212.69.36.10: bytes=32 time=179ms TTL=59
Reply from 212.69.36.10: bytes=32 time=157ms TTL=59
Reply from 212.69.36.10: bytes=32 time=139ms TTL=59
Reply from 212.69.36.10: bytes=32 time=154ms TTL=59
Reply from 212.69.36.10: bytes=32 time=150ms TTL=59
Reply from 212.69.36.10: bytes=32 time=151ms TTL=59
Reply from 212.69.36.10: bytes=32 time=99ms TTL=59
Reply from 212.69.36.10: bytes=32 time=80ms TTL=59
Reply from 212.69.36.10: bytes=32 time=41ms TTL=59
Reply from 212.69.36.10: bytes=32 time=87ms TTL=59
Reply from 212.69.36.10: bytes=32 time=88ms TTL=59
Reply from 212.69.36.10: bytes=32 time=141ms TTL=59
Reply from 212.69.36.10: bytes=32 time=130ms TTL=59
Reply from 212.69.36.10: bytes=32 time=162ms TTL=59
Reply from 212.69.36.10: bytes=32 time=106ms TTL=59
Reply from 212.69.36.10: bytes=32 time=112ms TTL=59
Reply from 212.69.36.10: bytes=32 time=112ms TTL=59
Reply from 212.69.36.10: bytes=32 time=149ms TTL=59
Reply from 212.69.36.10: bytes=32 time=118ms TTL=59
Reply from 212.69.36.10: bytes=32 time=91ms TTL=59
Reply from 212.69.36.10: bytes=32 time=121ms TTL=59
Reply from 212.69.36.10: bytes=32 time=121ms TTL=59
Reply from 212.69.36.10: bytes=32 time=64ms TTL=59
Reply from 212.69.36.10: bytes=32 time=98ms TTL=59
Reply from 212.69.36.10: bytes=32 time=66ms TTL=59
Reply from 212.69.36.10: bytes=32 time=71ms TTL=59
Reply from 212.69.36.10: bytes=32 time=108ms TTL=59
Reply from 212.69.36.10: bytes=32 time=91ms TTL=59
Reply from 212.69.36.10: bytes=32 time=79ms TTL=59
Reply from 212.69.36.10: bytes=32 time=127ms TTL=59
Reply from 212.69.36.10: bytes=32 time=135ms TTL=59
Reply from 212.69.36.10: bytes=32 time=116ms TTL=59
Reply from 212.69.36.10: bytes=32 time=88ms TTL=59
Reply from 212.69.36.10: bytes=32 time=160ms TTL=59
Reply from 212.69.36.10: bytes=32 time=158ms TTL=59
Reply from 212.69.36.10: bytes=32 time=186ms TTL=59
Reply from 212.69.36.10: bytes=32 time=97ms TTL=59
Reply from 212.69.36.10: bytes=32 time=156ms TTL=59
Reply from 212.69.36.10: bytes=32 time=132ms TTL=59
Reply from 212.69.36.10: bytes=32 time=148ms TTL=59
Reply from 212.69.36.10: bytes=32 time=184ms TTL=59
Reply from 212.69.36.10: bytes=32 time=146ms TTL=59
Reply from 212.69.36.10: bytes=32 time=151ms TTL=59
Reply from 212.69.36.10: bytes=32 time=129ms TTL=59
Reply from 212.69.36.10: bytes=32 time=137ms TTL=59
Reply from 212.69.36.10: bytes=32 time=133ms TTL=59
Reply from 212.69.36.10: bytes=32 time=138ms TTL=59
Reply from 212.69.36.10: bytes=32 time=163ms TTL=59
Reply from 212.69.36.10: bytes=32 time=117ms TTL=59
Reply from 212.69.36.10: bytes=32 time=137ms TTL=59
Reply from 212.69.36.10: bytes=32 time=76ms TTL=59
Reply from 212.69.36.10: bytes=32 time=120ms TTL=59
Reply from 212.69.36.10: bytes=32 time=157ms TTL=59
Reply from 212.69.36.10: bytes=32 time=101ms TTL=59
Reply from 212.69.36.10: bytes=32 time=100ms TTL=59
Reply from 212.69.36.10: bytes=32 time=72ms TTL=59
Reply from 212.69.36.10: bytes=32 time=65ms TTL=59
Reply from 212.69.36.10: bytes=32 time=33ms TTL=59
Reply from 212.69.36.10: bytes=32 time=40ms TTL=59
Reply from 212.69.36.10: bytes=32 time=38ms TTL=59
Reply from 212.69.36.10: bytes=32 time=44ms TTL=59
Reply from 212.69.36.10: bytes=32 time=37ms TTL=59
Reply from 212.69.36.10: bytes=32 time=37ms TTL=59
Reply from 212.69.36.10: bytes=32 time=80ms TTL=59
Reply from 212.69.36.10: bytes=32 time=53ms TTL=59
Reply from 212.69.36.10: bytes=32 time=42ms TTL=59
Reply from 212.69.36.10: bytes=32 time=40ms TTL=59
Reply from 212.69.36.10: bytes=32 time=42ms TTL=59
Reply from 212.69.36.10: bytes=32 time=40ms TTL=59
Reply from 212.69.36.10: bytes=32 time=40ms TTL=59
Reply from 212.69.36.10: bytes=32 time=98ms TTL=59
Reply from 212.69.36.10: bytes=32 time=72ms TTL=59
Reply from 212.69.36.10: bytes=32 time=109ms TTL=59
Reply from 212.69.36.10: bytes=32 time=43ms TTL=59
Reply from 212.69.36.10: bytes=32 time=43ms TTL=59
Reply from 212.69.36.10: bytes=32 time=43ms TTL=59
Reply from 212.69.36.10: bytes=32 time=71ms TTL=59
Reply from 212.69.36.10: bytes=32 time=41ms TTL=59
Reply from 212.69.36.10: bytes=32 time=34ms TTL=59
Reply from 212.69.36.10: bytes=32 time=34ms TTL=59
Reply from 212.69.36.10: bytes=32 time=36ms TTL=59
Reply from 212.69.36.10: bytes=32 time=37ms TTL=59
Reply from 212.69.36.10: bytes=32 time=46ms TTL=59
Reply from 212.69.36.10: bytes=32 time=46ms TTL=59
Reply from 212.69.36.10: bytes=32 time=54ms TTL=59
Reply from 212.69.36.10: bytes=32 time=43ms TTL=59
Reply from 212.69.36.10: bytes=32 time=36ms TTL=59
Reply from 212.69.36.10: bytes=32 time=73ms TTL=59
Reply from 212.69.36.10: bytes=32 time=65ms TTL=59
Reply from 212.69.36.10: bytes=32 time=36ms TTL=59
Reply from 212.69.36.10: bytes=32 time=37ms TTL=59
Reply from 212.69.36.10: bytes=32 time=35ms TTL=59
Reply from 212.69.36.10: bytes=32 time=37ms TTL=59
Reply from 212.69.36.10: bytes=32 time=66ms TTL=59
Reply from 212.69.36.10: bytes=32 time=34ms TTL=59
Reply from 212.69.36.10: bytes=32 time=34ms TTL=59
Reply from 212.69.36.10: bytes=32 time=38ms TTL=59
Reply from 212.69.36.10: bytes=32 time=50ms TTL=59
Reply from 212.69.36.10: bytes=32 time=62ms TTL=59
Reply from 212.69.36.10: bytes=32 time=62ms TTL=59
Reply from 212.69.36.10: bytes=32 time=57ms TTL=59
Reply from 212.69.36.10: bytes=32 time=37ms TTL=59
Reply from 212.69.36.10: bytes=32 time=52ms TTL=59
Reply from 212.69.36.10: bytes=32 time=35ms TTL=59
Reply from 212.69.36.10: bytes=32 time=59ms TTL=59
Reply from 212.69.36.10: bytes=32 time=73ms TTL=59
Reply from 212.69.36.10: bytes=32 time=126ms TTL=59
Reply from 212.69.36.10: bytes=32 time=79ms TTL=59
Reply from 212.69.36.10: bytes=32 time=101ms TTL=59
Reply from 212.69.36.10: bytes=32 time=174ms TTL=59
Reply from 212.69.36.10: bytes=32 time=171ms TTL=59
Reply from 212.69.36.10: bytes=32 time=94ms TTL=59
Reply from 212.69.36.10: bytes=32 time=88ms TTL=59
Reply from 212.69.36.10: bytes=32 time=74ms TTL=59
Reply from 212.69.36.10: bytes=32 time=77ms TTL=59
Reply from 212.69.36.10: bytes=32 time=34ms TTL=59
Reply from 212.69.36.10: bytes=32 time=116ms TTL=59
Reply from 212.69.36.10: bytes=32 time=67ms TTL=59
Reply from 212.69.36.10: bytes=32 time=39ms TTL=59
Reply from 212.69.36.10: bytes=32 time=38ms TTL=59
Reply from 212.69.36.10: bytes=32 time=37ms TTL=59
Reply from 212.69.36.10: bytes=32 time=72ms TTL=59
Reply from 212.69.36.10: bytes=32 time=103ms TTL=59
Reply from 212.69.36.10: bytes=32 time=160ms TTL=59
Reply from 212.69.36.10: bytes=32 time=128ms TTL=59
Reply from 212.69.36.10: bytes=32 time=115ms TTL=59

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

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

  1     8 ms     4 ms     5 ms  home [192.168.1.254]
  2    45 ms    47 ms    68 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3   379 ms   142 ms    39 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

  4    38 ms    44 ms    45 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5    51 ms    44 ms    37 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6    38 ms    37 ms    43 ms  www.idnet.net [212.69.36.10]

Trace complete.

Seems very varied

20 seconds later

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

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

  1     4 ms     8 ms     4 ms  home [192.168.1.254]
  2   246 ms    36 ms    33 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3    41 ms    37 ms    42 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

  4    82 ms    81 ms    79 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5    67 ms    70 ms    62 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6    40 ms    33 ms    36 ms  www.idnet.net [212.69.36.10]

Trace complete.

C:\Users\Sam>ping www.idnet.net -t

Pinging www.idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=45ms TTL=59
Reply from 212.69.36.10: bytes=32 time=52ms TTL=59
Reply from 212.69.36.10: bytes=32 time=41ms TTL=59
Reply from 212.69.36.10: bytes=32 time=42ms TTL=59
Reply from 212.69.36.10: bytes=32 time=36ms TTL=59
Reply from 212.69.36.10: bytes=32 time=39ms TTL=59
Reply from 212.69.36.10: bytes=32 time=38ms TTL=59
Reply from 212.69.36.10: bytes=32 time=41ms TTL=59
Reply from 212.69.36.10: bytes=32 time=36ms TTL=59
Reply from 212.69.36.10: bytes=32 time=44ms TTL=59
Reply from 212.69.36.10: bytes=32 time=40ms TTL=59
Reply from 212.69.36.10: bytes=32 time=46ms TTL=59
Reply from 212.69.36.10: bytes=32 time=37ms TTL=59
Reply from 212.69.36.10: bytes=32 time=45ms TTL=59
Reply from 212.69.36.10: bytes=32 time=45ms TTL=59

Seems the bt speetest reset my connection again

Rik

It shouldn't reset it, Sam.  :dunno:
Rik
--------------------

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

mrapoc

well my pings improved after?

reset as in reconnected to my isp? i dunno

pings are back high again

QuoteC:\Users\Sam>ping www.idnet.net -n 50

Pinging www.idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=112ms TTL=59
Reply from 212.69.36.10: bytes=32 time=142ms TTL=59
Reply from 212.69.36.10: bytes=32 time=115ms TTL=59
Reply from 212.69.36.10: bytes=32 time=109ms TTL=59
Reply from 212.69.36.10: bytes=32 time=128ms TTL=59
Reply from 212.69.36.10: bytes=32 time=117ms TTL=59
Reply from 212.69.36.10: bytes=32 time=161ms TTL=59
Reply from 212.69.36.10: bytes=32 time=149ms TTL=59
Reply from 212.69.36.10: bytes=32 time=173ms TTL=59
Reply from 212.69.36.10: bytes=32 time=152ms TTL=59
Reply from 212.69.36.10: bytes=32 time=154ms TTL=59
Reply from 212.69.36.10: bytes=32 time=177ms TTL=59
Reply from 212.69.36.10: bytes=32 time=126ms TTL=59
Reply from 212.69.36.10: bytes=32 time=158ms TTL=59
Reply from 212.69.36.10: bytes=32 time=171ms TTL=59
Reply from 212.69.36.10: bytes=32 time=107ms TTL=59
Reply from 212.69.36.10: bytes=32 time=99ms TTL=59
Reply from 212.69.36.10: bytes=32 time=124ms TTL=59
Reply from 212.69.36.10: bytes=32 time=104ms TTL=59
Reply from 212.69.36.10: bytes=32 time=92ms TTL=59
Reply from 212.69.36.10: bytes=32 time=126ms TTL=59
Reply from 212.69.36.10: bytes=32 time=191ms TTL=59
Reply from 212.69.36.10: bytes=32 time=161ms TTL=59
Reply from 212.69.36.10: bytes=32 time=122ms TTL=59
Reply from 212.69.36.10: bytes=32 time=122ms TTL=59
Reply from 212.69.36.10: bytes=32 time=93ms TTL=59
Reply from 212.69.36.10: bytes=32 time=103ms TTL=59
Reply from 212.69.36.10: bytes=32 time=135ms TTL=59
Reply from 212.69.36.10: bytes=32 time=141ms TTL=59
Reply from 212.69.36.10: bytes=32 time=125ms TTL=59
Reply from 212.69.36.10: bytes=32 time=141ms TTL=59
Reply from 212.69.36.10: bytes=32 time=118ms TTL=59
Reply from 212.69.36.10: bytes=32 time=106ms TTL=59
Reply from 212.69.36.10: bytes=32 time=142ms TTL=59
Reply from 212.69.36.10: bytes=32 time=126ms TTL=59
Reply from 212.69.36.10: bytes=32 time=145ms TTL=59
Reply from 212.69.36.10: bytes=32 time=90ms TTL=59
Reply from 212.69.36.10: bytes=32 time=98ms TTL=59
Reply from 212.69.36.10: bytes=32 time=90ms TTL=59
Reply from 212.69.36.10: bytes=32 time=46ms TTL=59
Reply from 212.69.36.10: bytes=32 time=85ms TTL=59
Reply from 212.69.36.10: bytes=32 time=105ms TTL=59
Reply from 212.69.36.10: bytes=32 time=146ms TTL=59
Reply from 212.69.36.10: bytes=32 time=137ms TTL=59
Reply from 212.69.36.10: bytes=32 time=137ms TTL=59
Reply from 212.69.36.10: bytes=32 time=123ms TTL=59
Reply from 212.69.36.10: bytes=32 time=124ms TTL=59
Reply from 212.69.36.10: bytes=32 time=92ms TTL=59
Reply from 212.69.36.10: bytes=32 time=55ms TTL=59
Reply from 212.69.36.10: bytes=32 time=113ms TTL=59

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

Rik

I think you've made my line go slow now, Sam. :(
Rik
--------------------

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

mrapoc

dreadfully sorry :(

its infectious!

Steve

Mine are in 3 figures as well this pm ,dropping ppp for 2 mins made no difference. A reboot has got them back to normal . I wonder for how long?
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

Rik

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

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

mrapoc

down again =/

QuoteC:\Users\Sam>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=38ms TTL=59
Reply from 212.69.36.10: bytes=32 time=46ms TTL=59
Reply from 212.69.36.10: bytes=32 time=41ms TTL=59
Reply from 212.69.36.10: bytes=32 time=35ms 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 = 35ms, Maximum = 46ms, Average = 40ms

Rik

I bet your speed hasn't dropped to half though, Sam. :)
Rik
--------------------

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

esh

Well I'm down in the 19ms regime (/cross fingers).

Could this be some BT router somewhere or what?
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