High Pings earlier .

Started by maxping, Jan 06, 2007, 18:56:56

Previous topic - Next topic

0 Members and 2 Guests are viewing this topic.

Print
Go Down Pages1 2 3 4 All
User actions

maxping

Jan 06, 2007, 18:56:56
I have been getting pings into the 80's in the last couple of Horus so tried the BT log in (as explained in the first post in the "how to fix high pings" thread)
I didn't use the speed test just logged in and then put my idnet user name back in and rebooted router.

Before using BT log in

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

Reply from 212.69.36.10: bytes=32 time=64ms TTL=60
Reply from 212.69.36.10: bytes=32 time=44ms TTL=60
Reply from 212.69.36.10: bytes=32 time=54ms TTL=60
Reply from 212.69.36.10: bytes=32 time=70ms TTL=60

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

After using BT log in.

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

Reply from 212.69.36.10: bytes=32 time=32ms TTL=60
Reply from 212.69.36.10: bytes=32 time=30ms TTL=60
Reply from 212.69.36.10: bytes=32 time=27ms TTL=60
Reply from 212.69.36.10: bytes=32 time=34ms TTL=60
Reply from 212.69.36.10: bytes=32 time=43ms TTL=60
Reply from 212.69.36.10: bytes=32 time=34ms TTL=60
Reply from 212.69.36.10: bytes=32 time=45ms TTL=60
Reply from 212.69.36.10: bytes=32 time=57ms TTL=60
Reply from 212.69.36.10: bytes=32 time=33ms TTL=60
Reply from 212.69.36.10: bytes=32 time=39ms TTL=60
Reply from 212.69.36.10: bytes=32 time=30ms TTL=60
Reply from 212.69.36.10: bytes=32 time=39ms TTL=60
Reply from 212.69.36.10: bytes=32 time=29ms TTL=60
Reply from 212.69.36.10: bytes=32 time=31ms TTL=60
Reply from 212.69.36.10: bytes=32 time=52ms TTL=60
Reply from 212.69.36.10: bytes=32 time=55ms TTL=60
Reply from 212.69.36.10: bytes=32 time=32ms TTL=60
Reply from 212.69.36.10: bytes=32 time=29ms TTL=60
Reply from 212.69.36.10: bytes=32 time=35ms TTL=60
Reply from 212.69.36.10: bytes=32 time=38ms TTL=60
Reply from 212.69.36.10: bytes=32 time=45ms TTL=60
Reply from 212.69.36.10: bytes=32 time=40ms TTL=60
Reply from 212.69.36.10: bytes=32 time=36ms TTL=60
Reply from 212.69.36.10: bytes=32 time=43ms TTL=60
Reply from 212.69.36.10: bytes=32 time=32ms TTL=60
Reply from 212.69.36.10: bytes=32 time=30ms TTL=60
Reply from 212.69.36.10: bytes=32 time=33ms TTL=60
Reply from 212.69.36.10: bytes=32 time=26ms TTL=60
Reply from 212.69.36.10:

maxping

#1
Jan 06, 2007, 19:00:54 Last Edit: Jan 06, 2007, 19:07:46 by maxping
Seems fine again now not even getting the spikes into the 50's

For those not used to pinging from start/progs/accessories/command prompt.

Type ping -t idnet.net (or whatever address you want to ping)

Adding the -t will let the test run for as long as you want it to , stop it by right clicking once , click "mark" , left click and drag the white box over the part you want to save and hit "enter" to save it so you can paste it into your post.



Reply from 212.69.36.10: bytes=32 time=25ms TTL=60
Reply from 212.69.36.10: bytes=32 time=31ms TTL=60
Reply from 212.69.36.10: bytes=32 time=35ms TTL=60
Reply from 212.69.36.10: bytes=32 time=28ms TTL=60
Reply from 212.69.36.10: bytes=32 time=25ms TTL=60
Reply from 212.69.36.10: bytes=32 time=25ms TTL=60
Reply from 212.69.36.10: bytes=32 time=32ms TTL=60
Reply from 212.69.36.10: bytes=32 time=27ms TTL=60
Reply from 212.69.36.10: bytes=32 time=27ms TTL=60
Reply from 212.69.36.10: bytes=32 time=28ms TTL=60
Reply from 212.69.36.10: bytes=32 time=24ms TTL=60
Reply from 212.69.36.10: bytes=32 time=26ms TTL=60
Reply from 212.69.36.10: bytes=32 time=27ms TTL=60
Reply from 212.69.36.10: bytes=32 time=25ms TTL=60
Reply from 212.69.36.10: bytes=32 time=25ms TTL=60
Reply from 212.69.36.10: bytes=32 time=29ms TTL=60
Reply from 212.69.36.10: bytes=32 time=25ms TTL=60
Reply from 212.69.36.10: bytes=32 time=27ms TTL=60
Reply from 212.69.36.10: bytes=32 time=26ms TTL=60
Reply from 212.69.36.10: bytes=32 time=28ms TTL=60
Reply from 212.69.36.10: bytes=32 time=29ms TTL=60
Reply from 212.69.36.10: bytes=32 time=28ms TTL=60
Reply from 212.69.36.10: bytes=32 time=29ms TTL=60
Reply from 212.69.36.10: bytes=32 time=26ms TTL=60
Reply from 212.69.36.10: bytes=32 time=26ms TTL=60
Reply from 212.69.36.10: bytes=32 time=28ms TTL=60
Reply from 212.69.36.10: bytes=32 time=27ms TTL=60
Reply from 212.69.36.10: bytes=32 time=30ms TTL=60
Reply from 212.69.36.10: bytes=32 time=27ms TTL=60
Reply from 212.69.36.10: bytes=32 time=25ms TTL=60
Reply from 212.69.36.10: bytes=32 time=30ms TTL=60
Reply from 212.69.36.10: bytes=32 time=28ms TTL=60
Reply from 212.69.36.10: bytes=32 time=24ms TTL=60
Reply from 212.69.36.10: bytes=32 time=27ms TTL=60
Reply from 212.69.36.10: bytes=32 time=30ms TTL=60
Reply from 212.69.36.10: bytes=32 time=32ms TTL=60
Reply from 212.69.36.10: bytes=32 time=40ms TTL=60
Reply from 212.69.36.10: bytes=32 time=34ms TTL=60
Reply from 212.69.36.10: bytes=32 time=27ms TTL=60
Reply from 212.69.36.10: bytes=32 time=40ms TTL=60
Reply from 212.69.36.10: bytes=32 time=28ms TTL=60
Reply from 212.69.36.10: bytes=32 time=28ms TTL=60
Reply from 212.69.36.10: bytes=32 time=32ms TTL=60
Reply from 212.69.36.10: bytes=32 time=31ms TTL=60
Reply from 212.69.36.10: bytes=32 time=41ms TTL=60
Reply from 212.69.36.10: bytes=32 time=40ms TTL=60
Reply from 212.69.36.10: bytes=32 time=28ms TTL=60
Reply from 212.69.36.10: bytes=32 time=26ms TTL=60
Reply from 212.69.36.10: bytes=32 time=25ms TTL=60
Reply from 212.69.36.10: bytes=32 time=42ms TTL=60
Reply from 212.69.36.10: bytes=32 time=34ms TTL=60
Reply from 212.69.36.10: bytes=32 time=35ms TTL=60
Reply from 212.69.36.10: bytes=32 time=33ms TTL=60
Reply from 212.69.36.10: bytes=32 time=26ms TTL=60
Reply from 212.69.36.10: bytes=32 time=28ms TTL=60
Reply from 212.69.36.10: bytes=32 time=29ms TTL=60
Reply from 212.69.36.10: bytes=32 time=30ms TTL=60
Reply from 212.69.36.10: bytes=32 time=26ms TTL=60
Reply from 212.69.36.10: bytes=32 time=33ms TTL=60
Reply from 212.69.36.10: bytes=32 time=31ms TTL=60
Reply from 212.69.36.10: bytes=32 time=27ms TTL=60
Reply from 212.69.36.10: bytes=32 time=26ms TTL=60
Reply from 212.69.36.10: bytes=32 time=26ms TTL=60
Reply from 212.69.36.10: bytes=32 time=26ms TTL=60
Reply from 212.69.36.10: bytes=32 time=33ms TTL=60

mrapoc

#2
Jan 06, 2007, 19:13:26
all normal here - i wasnt on my pc at the time you got high pings, too busy watching the gunner pwn liverpool 3-1  :D

DorsetBoy

#3
Jan 06, 2007, 19:14:15
Can't even get BT Speedtester to work!

Enter phone number................................................35 mins later still waiting for the next stage.

Forum took over a minute to open and signing in another 45 secs+.

::) ::)

maxping

#4
Jan 06, 2007, 20:13:49 Last Edit: Jan 06, 2007, 20:16:44 by maxping
I spoke too soon  :'(

Can a few of you peeps ping 87.117.208.22  for me and post the results , Ta.

I would try switching the router off for 30 mins but i wont be on again after 9:00 so  will try again in the morning.

Tracing route to 87.117.208.22 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.1.254
  2     *       31 ms    25 ms  telehouse-gw-msdp.idnet.net [212.69.63.41]
  3    24 ms    32 ms    33 ms  212.69.63.10
  4     *        *       27 ms  x-s-1.lon1.arbinet.net [213.232.64.54]
  5    38 ms    32 ms     *     lon-sb1.LON.GB.net.DTAG.DE [62.154.15.153]
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *       30 ms     *     87.117.208.22
10    28 ms     *       27 ms  87.117.208.22

Trace complete.



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

  1    <1 ms    <1 ms    <1 ms  192.168.1.254
  2     *       24 ms    25 ms  telehouse-gw-msdp.idnet.net [212.69.63.41]
  3    39 ms    44 ms    51 ms  212.69.63.10
  4    71 ms    62 ms    61 ms  redbus-gw.idnet.net [212.69.63.1]
  5    84 ms    96 ms    73 ms  www.idnet.net [212.69.36.10]

Trace complete.



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

  1    <1 ms    <1 ms    <1 ms  192.168.1.254
  2  2223 ms  1196 ms   177 ms  telehouse-gw-msdp.idnet.net [212.69.63.41]
  3    27 ms    26 ms    30 ms  212.69.63.10
  4    58 ms    41 ms    48 ms  redbus-gw.idnet.net [212.69.63.1]
  5    70 ms    58 ms    50 ms  www.idnet.net [212.69.36.10]

AvengerUK

#5
Jan 06, 2007, 21:05:27
my pings went high earily aswell not so bad now, However i am seeing alot of loss to some locations which i didnt previously get, also pings are still slightly suffering - but not as bad as before!

BTW: your IP as well with pinging multiplay times out alot (loss)

ou7shined

#6
Jan 06, 2007, 21:52:43
Here you go Max. Sorry I couldn't be bothered copying it out.


Rich.

Klaatu barada nikto!

maxping

#7
Jan 07, 2007, 11:22:49
Thanks - its as bad again this morning , i will wait and see if Simon sees the thread and can shed any light on it.



Tracing route to bbc.co.uk [212.58.228.155]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.254
  2   164 ms   308 ms   323 ms  telehouse-gw-msdp.idnet.net [212.69.63.41]
  3    22 ms    31 ms    23 ms  212.69.63.10
  4    23 ms    26 ms    23 ms  rt-lonap-a.thdo.bbc.co.uk [193.203.5.90]
  5    22 ms    24 ms    23 ms  212.58.238.153
  6    23 ms    24 ms    23 ms  212.58.238.36
  7    24 ms    25 ms    25 ms  pos6-0.rt1.mh.bbc.co.uk [212.58.239.254]
  8    24 ms    26 ms    26 ms  virtual0.mh.bbc.co.uk [212.58.228.155]

Trace complete.



Tracing route to bbc.co.uk [212.58.228.155]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.254
  2    22 ms    22 ms    23 ms  telehouse-gw-msdp.idnet.net [212.69.63.41]
  3    24 ms    24 ms    23 ms  212.69.63.10
  4    24 ms    24 ms    23 ms  rt-lonap-a.thdo.bbc.co.uk [193.203.5.90]
  5    22 ms    25 ms    24 ms  212.58.238.153
  6    24 ms    23 ms    24 ms  212.58.238.36
  7    25 ms    25 ms    26 ms  pos6-0.rt1.mh.bbc.co.uk [212.58.239.254]
  8    25 ms    26 ms    24 ms  virtual0.mh.bbc.co.uk [212.58.228.155]

Trace complete.


Tracing route to 87.117.208.22 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.1.254
  2    23 ms    22 ms    22 ms  telehouse-gw-msdp.idnet.net [212.69.63.41]
  3    23 ms    23 ms    23 ms  212.69.63.10
  4    22 ms    24 ms     *     x-s-1.lon1.arbinet.net [213.232.64.54]
  5     *       23 ms    24 ms  lon-sb1.LON.GB.net.DTAG.DE [62.154.15.153]
  6    24 ms    24 ms    24 ms  217.239.39.230
  7    24 ms    25 ms    24 ms  217.6.48.238
  8    23 ms    25 ms     *     ge-1-24.pup.mer.lon.rapidswitch [87.117.214.2]
  9    24 ms    25 ms     *     87.117.208.22
10    27 ms    24 ms    25 ms  87.117.208.22

Trace complete.


Tracing route to 87.117.208.22 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.1.254
  2     *      192 ms    23 ms  telehouse-gw-msdp.idnet.net [212.69.63.41]
  3    23 ms    23 ms    22 ms  212.69.63.10
  4    23 ms    23 ms    23 ms  x-s-1.lon1.arbinet.net [213.232.64.54]
  5    23 ms    24 ms    23 ms  lon-sb1.LON.GB.net.DTAG.DE [62.154.15.153]
  6    23 ms    23 ms    75 ms  217.239.39.230
  7    25 ms    24 ms    25 ms  217.6.48.238
  8    25 ms    24 ms    23 ms  ge-1-24.pup.mer.lon.rapidswitch [87.117.214.2]
  9    26 ms    28 ms    25 ms  87.117.208.22

Trace complete.



Tracing route to 87.117.208.22 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.1.254
  2    23 ms    22 ms    22 ms  telehouse-gw-msdp.idnet.net [212.69.63.41]
  3    24 ms    23 ms    22 ms  212.69.63.10
  4    23 ms    25 ms    24 ms  x-s-1.lon1.arbinet.net [213.232.64.54]
  5    24 ms    23 ms    30 ms  lon-sb1.LON.GB.net.DTAG.DE [62.154.15.153]
  6    23 ms    25 ms    23 ms  217.239.39.230
  7    25 ms    23 ms    25 ms  217.6.48.238
  8    29 ms    32 ms    24 ms  ge-1-24.pup.mer.lon.rapidswitch [87.117.214.2]
  9    25 ms    24 ms    28 ms  87.117.208.22

Trace complete.


Tracing route to 87.117.208.22 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.1.254
  2    22 ms    23 ms    24 ms  telehouse-gw-msdp.idnet.net [212.69.63.41]
  3    24 ms    25 ms    23 ms  212.69.63.10
  4     *        *        *     Request timed out.
  5    24 ms    26 ms    24 ms  lon-sb1.LON.GB.net.DTAG.DE [62.154.15.153]
  6    24 ms    23 ms    23 ms  217.239.39.230
  7    28 ms    27 ms    26 ms  217.6.48.238
  8     *        *        *     Request timed out.
  9    24 ms     *        *     87.117.208.22
10    26 ms    24 ms    25 ms  87.117.208.22

Trace complete.

maxping

#8
Jan 07, 2007, 11:25:27
This is strange , i get no problems using the bbc   ???


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



Tracing route to bbc.co.uk [212.58.228.155]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.254
  2    22 ms    22 ms    28 ms  telehouse-gw-msdp.idnet.net [212.69.63.41]
  3    24 ms    23 ms    22 ms  212.69.63.10
  4    24 ms    24 ms    23 ms  rt-lonap-a.thdo.bbc.co.uk [193.203.5.90]
  5    23 ms    23 ms    23 ms  212.58.238.153
  6    24 ms    23 ms    23 ms  212.58.238.36
  7    24 ms    25 ms    25 ms  pos6-0.rt1.mh.bbc.co.uk [212.58.239.254]
  8    25 ms    25 ms    25 ms  virtual0.mh.bbc.co.uk [212.58.228.155]

Trace complete.



Tracing route to bbc.co.uk [212.58.228.155]
over a maximum of 30 hops:

  1    <1 ms    <1 ms     2 ms  192.168.1.254
  2    23 ms    22 ms    24 ms  telehouse-gw-msdp.idnet.net [212.69.63.41]
  3    25 ms    23 ms    23 ms  212.69.63.10
  4    23 ms    24 ms    24 ms  rt-lonap-a.thdo.bbc.co.uk [193.203.5.90]
  5    23 ms    24 ms    25 ms  212.58.238.153
  6    23 ms    23 ms    23 ms  212.58.238.36
  7    25 ms    25 ms    26 ms  pos6-0.rt1.mh.bbc.co.uk [212.58.239.254]
  8    24 ms    24 ms    25 ms  virtual0.mh.bbc.co.uk [212.58.228.155]

Trace complete.



Tracing route to bbc.co.uk [212.58.228.155]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.254
  2    23 ms    22 ms    22 ms  telehouse-gw-msdp.idnet.net [212.69.63.41]
  3    24 ms    23 ms    24 ms  212.69.63.10
  4    25 ms    23 ms    26 ms  rt-lonap-a.thdo.bbc.co.uk [193.203.5.90]
  5    23 ms    23 ms    24 ms  212.58.238.153
  6    24 ms    23 ms    24 ms  212.58.238.36
  7    25 ms    24 ms    28 ms  pos6-0.rt1.mh.bbc.co.uk [212.58.239.254]
  8    25 ms    26 ms    24 ms  virtual0.mh.bbc.co.uk [212.58.228.155]

Trace complete.

Bill

#9
Jan 07, 2007, 12:00:44
When you're having high ping problems, why do you quote traceroutes? The intermediate figures mean nothing unless the the values go high at one point and remain high beyond it. The sporadic high value on the telehouse router just means it's fairly busy, it doesn't affect the time to the destination server.
Bill
BQMs-  IPv4  IPv6

DorsetBoy

#10
Jan 07, 2007, 12:04:14
I tried pinging IDNET last night........pings at 385ms :( ,  waited 2 minutes and pinged again.........only 42ms ???

My broadband connection has also been dropped though the router stats clearly showed that the power had NOT been off.

The speeds were so bad this morning I have rebooted the router and will have to see where this takes us.

cavillas

#11
Jan 07, 2007, 12:14:10
Quote from: Bill on Jan 07, 2007, 12:00:44
When you're having high ping problems, why do you quote traceroutes? The intermediate figures mean nothing unless the the values go high at one point and remain high beyond it. The sporadic high value on the telehouse router just means it's fairly busy, it doesn't affect the time to the destination server.

Just means that many people are probably pinging and tracerting.  ;)
------
Alf :)

maxping

#12
Jan 07, 2007, 12:21:25 Last Edit: Jan 07, 2007, 12:25:34 by maxping
Quote from: Bill on Jan 07, 2007, 12:00:44
When you're having high ping problems, why do you quote traceroutes?

Bill if i had of known that i wouldn't have  ;)


I did ping in the op before i tried the BT log in  and it shows high pings.

Before using BT log in

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

Reply from 212.69.36.10: bytes=32 time=64ms TTL=60
Reply from 212.69.36.10: bytes=32 time=44ms TTL=60
Reply from 212.69.36.10: bytes=32 time=54ms TTL=60
Reply from 212.69.36.10: bytes=32 time=70ms TTL=60

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


I have Pinged both servers this morning that were showing high last night and all seems well again, i will keep my fingers crossed.

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



Pinging 217.146.92.144 with 32 bytes of data:

Reply from 217.146.92.144: bytes=32 time=34ms TTL=120
Reply from 217.146.92.144: bytes=32 time=25ms TTL=120
Reply from 217.146.92.144: bytes=32 time=28ms TTL=120
Reply from 217.146.92.144: bytes=32 time=23ms TTL=120

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



Pinging 217.146.92.144 with 32 bytes of data:

Reply from 217.146.92.144: bytes=32 time=24ms TTL=120
Reply from 217.146.92.144: bytes=32 time=23ms TTL=120
Reply from 217.146.92.144: bytes=32 time=26ms TTL=120
Reply from 217.146.92.144: bytes=32 time=23ms TTL=120

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



Pinging 217.146.92.144 with 32 bytes of data:

Reply from 217.146.92.144: bytes=32 time=23ms TTL=120
Reply from 217.146.92.144: bytes=32 time=23ms TTL=120
Reply from 217.146.92.144: bytes=32 time=23ms TTL=120
Reply from 217.146.92.144: bytes=32 time=24ms TTL=120

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

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Pinging 87.117.208.22 with 32 bytes of data:

Reply from 87.117.208.22: bytes=32 time=26ms TTL=121
Reply from 87.117.208.22: bytes=32 time=24ms TTL=121
Reply from 87.117.208.22: bytes=32 time=25ms TTL=121
Reply from 87.117.208.22: bytes=32 time=25ms TTL=121

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


Pinging 87.117.208.22 with 32 bytes of data:

Reply from 87.117.208.22: bytes=32 time=24ms TTL=121
Reply from 87.117.208.22: bytes=32 time=26ms TTL=121
Reply from 87.117.208.22: bytes=32 time=24ms TTL=121
Reply from 87.117.208.22: bytes=32 time=24ms TTL=121

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



Pinging 87.117.208.22 with 32 bytes of data:

Reply from 87.117.208.22: bytes=32 time=24ms TTL=121
Reply from 87.117.208.22: bytes=32 time=24ms TTL=121
Reply from 87.117.208.22: bytes=32 time=27ms TTL=121
Reply from 87.117.208.22: bytes=32 time=26ms TTL=121

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

maxping

#13
Jan 07, 2007, 12:43:33
Just read this at the TB idnet forum in the "Latency Issues thread.

A co-lo customer had a problem with one of their sites being used to relay a flood of spam. They managed to fix that problem with help from our team. Apologies to anyone affected.
Simon

DorsetBoy

#14
Jan 07, 2007, 14:42:36
Quote from: maxping on Jan 07, 2007, 12:43:33
Just read this at the TB idnet forum in the "Latency Issues thread.

A co-lo customer had a problem with one of their sites being used to relay a flood of spam. They managed to fix that problem with help from our team. Apologies to anyone affected.
Simon


YES MAX............on the 28/12/2006 ;D ;D

maxping

#15
Jan 07, 2007, 14:59:58
Quote from: DorsetBoy on Jan 07, 2007, 14:42:36

YES MAX............on the 28/12/2006 ;D ;D

Ooooops  :-[  well spotted.

Seems to be sorted whatever it was.  ;)

DorsetBoy

#16
Jan 07, 2007, 15:31:59
Not sorted here.............too eratic to be worth having the PC running!

Nerval

#17
Jan 07, 2007, 16:23:55
Browsing erratic here too Dorset, and I'm  far away from Dorset.  :laugh:

AvengerUK

#18
Jan 07, 2007, 16:45:36
Also very erratic my end -  pings are "ok" to some places and awfull to others.

AvengerUK

#19
Jan 07, 2007, 16:50:25
Quote from: maxping on Jan 07, 2007, 14:59:58
Ooooops  :-[  well spotted.

Seems to be sorted whatever it was.  ;)
Just noticed: there is a reply from simon today in that thread - at around 1:30 "no network problems" apparently!

Bill

#20
Jan 07, 2007, 17:16:34
It's possible that school holidays, it's a weekend and this announcement may not be unconnected with the problem...
Bill
BQMs-  IPv4  IPv6

AvengerUK

#21
Jan 07, 2007, 17:19:26
actually school holidays ended *i believe* for most schools last week sometime?!

Anyway - pings are still the same ;) - its not bad so doesent stop me doing what i need to do though :)

maxping

#22
Jan 07, 2007, 17:24:29
Quote from: AvengerUK on Jan 07, 2007, 17:19:26
actually school holidays ended *i believe* for most schools last week sometime?!



My Sons first day back is tomorrow.

ou7shined

#23
Jan 07, 2007, 17:26:36
Quote from: AvengerUK on Jan 07, 2007, 16:50:25
Just noticed: there is a reply from simon today in that thread - at around 1:30 "no network problems" apparently!

Apparently indeed. :-\
Rich.

Klaatu barada nikto!

MikeT

#24
Jan 07, 2007, 22:53:09
I am getting very slow site page loading times with Pipex dsl too so it may be a big problem somewhere on the network. Even tried using their webcache and that sped things up a little for a while but now its just as bad. ADSLguide speed test for my 1meg connect just gave this result.

Date     07/01/07 22:35:45
Speed Down    389.38 Kbps ( 0.4 Mbps )
Speed Up    241.45 Kbps ( 0.2 Mbps )

So seems its something general to all, unless of course I am missing something.
Print
Go Up Pages1 2 3 4 All
User actions