Profiles

Started by psp83, Mar 29, 2008, 13:31:10

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Cookiemonster

Pinging www.idnetters.co.uk [212.69.36.28] with 32 bytes of data:
Reply from 212.69.36.28: bytes=32 time=45ms TTL=59
Reply from 212.69.36.28: bytes=32 time=43ms TTL=59
Reply from 212.69.36.28: bytes=32 time=49ms TTL=59
Request timed out.
Reply from 212.69.36.28: bytes=32 time=56ms TTL=59
Request timed out.
Reply from 212.69.36.28: bytes=32 time=56ms TTL=59
Reply from 212.69.36.28: bytes=32 time=57ms TTL=59
Reply from 212.69.36.28: bytes=32 time=46ms TTL=59
Reply from 212.69.36.28: bytes=32 time=46ms TTL=59
Reply from 212.69.36.28: bytes=32 time=45ms TTL=59
Reply from 212.69.36.28: bytes=32 time=51ms TTL=59
Reply from 212.69.36.28: bytes=32 time=52ms TTL=59
Reply from 212.69.36.28: bytes=32 time=39ms TTL=59
Reply from 212.69.36.28: bytes=32 time=42ms TTL=59
Reply from 212.69.36.28: bytes=32 time=53ms TTL=59
Reply from 212.69.36.28: bytes=32 time=52ms TTL=59
Reply from 212.69.36.28: bytes=32 time=45ms TTL=59
Reply from 212.69.36.28: bytes=32 time=40ms TTL=59
Reply from 212.69.36.28: bytes=32 time=33ms TTL=59

Ping statistics for 212.69.36.28:
    Packets: Sent = 20, Received = 18, Lost = 2 (10% loss),
Approximate round trip times in milli-seconds:
    Minimum = 33ms, Maximum = 57ms, Average = 47ms

Slow forum affecting me too Rik

Inactive

Quote from: Sebby on Mar 29, 2008, 14:08:37
Click Start then Run, type in cmd and hit enter. On the command prompt, type ping www.idnetters.co.uk -n 20 and hit enter again. Voila. :)

Thanks Seb, but I will leave it those that know better. ;D
Anything and everything that I post on here is purely my opinion, it ain't going to change the world, you are under no obligation to agree with me, it is purely my expressed opinion.

Simon

Just out of curiosity, what's the 'n 20' bit?

Mine's looking better now too:

Pinging www.idnetters.co.uk [212.69.36.28] with 32 bytes of data:

Reply from 212.69.36.28: bytes=32 time=66ms TTL=59
Reply from 212.69.36.28: bytes=32 time=190ms TTL=59
Reply from 212.69.36.28: bytes=32 time=30ms TTL=59
Reply from 212.69.36.28: bytes=32 time=39ms TTL=59
Reply from 212.69.36.28: bytes=32 time=229ms TTL=59
Reply from 212.69.36.28: bytes=32 time=211ms TTL=59
Reply from 212.69.36.28: bytes=32 time=180ms TTL=59
Reply from 212.69.36.28: bytes=32 time=137ms TTL=59
Reply from 212.69.36.28: bytes=32 time=243ms TTL=59
Reply from 212.69.36.28: bytes=32 time=220ms TTL=59
Reply from 212.69.36.28: bytes=32 time=67ms TTL=59
Reply from 212.69.36.28: bytes=32 time=59ms TTL=59
Reply from 212.69.36.28: bytes=32 time=49ms TTL=59
Reply from 212.69.36.28: bytes=32 time=51ms TTL=59
Reply from 212.69.36.28: bytes=32 time=56ms TTL=59
Reply from 212.69.36.28: bytes=32 time=46ms TTL=59
Reply from 212.69.36.28: bytes=32 time=62ms TTL=59
Reply from 212.69.36.28: bytes=32 time=36ms TTL=59
Reply from 212.69.36.28: bytes=32 time=45ms TTL=59
Reply from 212.69.36.28: bytes=32 time=34ms TTL=59

Ping statistics for 212.69.36.28:
    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 30ms, Maximum = 243ms, Average = 102ms
Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.

Rik

Normally a ping sends 4 packets, Simon. The -n switch allows you to run a longer test, 10-100 will show up more issues than just 4, or you can use Ping Graph instead...
Rik
--------------------

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

Simon

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

madasahatter

Much better here as well  :)

Rik

Simon has a way with Samson. :)
Rik
--------------------

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

Cookiemonster

Quote from: madasahatter on Mar 29, 2008, 14:37:40
Much better here as well  :)

Yup i concur a marked improvement!

madasahatter

.......until it wnt down altogether - did Samson decide he didn't want to play at all?  ;D

Rik

Just had a complete 'down' on the forum, and email is currently down. :(
Rik
--------------------

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

Cookiemonster


madasahatter

that's not good  :(

Rik

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

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

Cookiemonster

Looks like customer login is down too! Can't access my account. :(

Rik

I suspect that there's an issue affecting a number of servers, hence I'm guessing it's a router.
Rik
--------------------

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

psp83

Everything is backup to speed now.. well except my pesky profile  >:(

Rik

The difference is, Paul, that that's under BT's control. :(
Rik
--------------------

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

Malc

Next time you want a rest Rik, please leave the PC on.  ;D

Rik

It was, I was pinging the site until the graph changed from red to blue. :)
Rik
--------------------

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

Malc

I hope they paid the electric bill  :rant2:

Rik

I haven't sent it yet, I was trying to calculate my profit margin. :)
Rik
--------------------

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

psp83

Quote from: Rik on Mar 29, 2008, 18:33:10
The difference is, Paul, that that's under BT's control. :(
Its backup to 5000 now  ;D

Rik

Blip is working. Wow!  :)
Rik
--------------------

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