Results 1 to 6 of 6
-
05-02-2003, 10:04 AM #1Junior Guru
- Join Date
- Jun 2002
- Location
- Sherbrooke, Québec
- Posts
- 184
Asking your help to verify connectivity
I would like to verify worldwide connectivity with a potential provider located in my area. I would be glad if you could tell me your location (city, country) and average response time from your place to the following IP: 207.253.3.1
Thanks for your help
- Tom
-
05-02-2003, 11:11 AM #2Web Hosting Guru
- Join Date
- Jul 2002
- Location
- Atlanta, Georgia
- Posts
- 339
Atlanta, Ga, US
Ping statistics for 207.253.3.1:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 59ms, Maximum = 150ms, Average = 65ms
pings were very irattic..
-
05-02-2003, 01:49 PM #3Web Hosting Master
- Join Date
- Apr 2002
- Location
- Southampton, UK
- Posts
- 1,025
Pinging 207.253.3.1 with 32 bytes of data:
Reply from 207.253.3.1: bytes=32 time=141ms TTL=246
Reply from 207.253.3.1: bytes=32 time=125ms TTL=246
Reply from 207.253.3.1: bytes=32 time=125ms TTL=246
Reply from 207.253.3.1: bytes=32 time=125ms TTL=246
Ping statistics for 207.253.3.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 125ms, Maximum = 141ms, Average = 129ms
Stable for me.
-
05-02-2003, 02:33 PM #4Web Hosting Master
- Join Date
- Nov 2000
- Posts
- 3,046
Idaho, US
Pinging 207.253.3.1 with 32 bytes of data:
Reply from 207.253.3.1: bytes=32 time=175ms TTL=241
Reply from 207.253.3.1: bytes=32 time=140ms TTL=241
Reply from 207.253.3.1: bytes=32 time=153ms TTL=241
Reply from 207.253.3.1: bytes=32 time=151ms TTL=241
Ping statistics for 207.253.3.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 140ms, Maximum = 175ms, Average = 154msA well-reasoned assumption is very close to fact.
- Adorno
-
05-02-2003, 04:01 PM #5Riiiiiiiiiiiiight...
- Join Date
- Apr 2002
- Location
- Hollywood, CA
- Posts
- 3,052
oh yeah..los angeles
Pinging 207.253.3.1 with 32 bytes of data:
Reply from 207.253.3.1: bytes=32 time=132ms TTL=242
Reply from 207.253.3.1: bytes=32 time=139ms TTL=242
Reply from 207.253.3.1: bytes=32 time=105ms TTL=242
Reply from 207.253.3.1: bytes=32 time=121ms TTL=242
Ping statistics for 207.253.3.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 105ms, Maximum = 139ms, Average = 124msLast edited by case; 05-02-2003 at 04:32 PM.
-
05-02-2003, 04:08 PM #6Web Hosting Master
- Join Date
- Oct 2001
- Location
- USA
- Posts
- 1,026
From Dallas, Texas, USA:
This must be during the peek hour (afternoon):
64 bytes from 207.253.3.1: icmp_seq=1 ttl=238 time=134 ms
64 bytes from 207.253.3.1: icmp_seq=2 ttl=238 time=121 ms
64 bytes from 207.253.3.1: icmp_seq=3 ttl=238 time=113 ms
64 bytes from 207.253.3.1: icmp_seq=4 ttl=238 time=108 ms
64 bytes from 207.253.3.1: icmp_seq=5 ttl=238 time=121 ms
--- 207.253.3.1 ping statistics ---
5 packets transmitted, 5 received, 0% loss, time 4006ms
rtt min/avg/max/mdev = 108.484/119.870/134.397/8.794 ms
Reyner