User Panel
Posted: 5/22/2015 11:15:10 PM EDT
1. Open Command Prompt (press the Windows key, type "cmd" + Enter)
2. Type "ping ar15.com" + Enter
3. Report minimum/maximum/average latencies on this thread 120/142/131ms for me ... that's via Wifi to a DSL connection. |
|
I must be bored. What the hell. 26 ms.
C:\Windows\System32>ping ar15.com Pinging ar15.com [209.251.48.101] with 32 bytes of data: Reply from 209.251.48.101: bytes=32 time=26ms TTL=53 Reply from 209.251.48.101: bytes=32 time=27ms TTL=53 Reply from 209.251.48.101: bytes=32 time=26ms TTL=53 Reply from 209.251.48.101: bytes=32 time=28ms TTL=53 Ping statistics for 209.251.48.101: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 26ms, Maximum = 28ms, Average = 26ms |
|
C:\Windows\system32>ping ar15.com -n 5
Pinging ar15.com [209.251.48.101] with 32 bytes of data: Reply from 209.251.48.101: bytes=32 time=49ms TTL=48 Reply from 209.251.48.101: bytes=32 time=49ms TTL=48 Reply from 209.251.48.101: bytes=32 time=50ms TTL=48 Reply from 209.251.48.101: bytes=32 time=49ms TTL=48 Reply from 209.251.48.101: bytes=32 time=49ms TTL=48 Ping statistics for 209.251.48.101: Packets: Sent = 5, Received = 5, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 49ms, Maximum = 50ms, Average = 49ms C:\Windows\system32> Uverse |
|
Min 38ms
Max 46ms Avg 40ms ETA: Damn I thought I had crappy interwebs. Some of you need to call rotorooter to clean out your pipes. |
|
--- ar15.com ping statistics ---
packets transmitted 4 received 4 packet loss 0 % time 3004 ms --- Round Trip Time (rtt) --- min 103.780 ms avg 105.994 ms max 107.742 ms mdev 1.809 ms |
|
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\Dennis>ping ar15.com Pinging ar15.com [209.251.48.101] with 32 bytes of data: Reply from 209.251.48.101: bytes=32 time=51ms TTL=52 Reply from 209.251.48.101: bytes=32 time=50ms TTL=52 Reply from 209.251.48.101: bytes=32 time=49ms TTL=52 Reply from 209.251.48.101: bytes=32 time=60ms TTL=52 Ping statistics for 209.251.48.101: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 49ms, Maximum = 60ms, Average = 52ms |
|
Quoted: --- ar15.com ping statistics --- 51 packets transmitted, 49 received, 3% packet loss, time 50080ms rtt min/avg/max/mdev = 99.764/104.240/106.154/1.316 ms --- google.com ping statistics --- 24 packets transmitted, 24 received, 0% packet loss, time 23036ms rtt min/avg/max/mdev = 14.888/15.805/17.363/0.547 ms http://www.speedtest.net/result/4379773649.png View Quote Isn't most packet loss within the LAN or between the modem and ISP? |
|
Quoted:
Why would you be getting packet loss to ar15.com, but not google.com? Isn't most packet loss within the LAN or between the modem and ISP? View Quote View All Quotes View All Quotes Quoted:
Quoted:
--- ar15.com ping statistics --- 51 packets transmitted, 49 received, 3% packet loss, time 50080ms rtt min/avg/max/mdev = 99.764/104.240/106.154/1.316 ms --- google.com ping statistics --- 24 packets transmitted, 24 received, 0% packet loss, time 23036ms rtt min/avg/max/mdev = 14.888/15.805/17.363/0.547 ms http://www.speedtest.net/result/4379773649.png Isn't most packet loss within the LAN or between the modem and ISP? ETA: --- google.com ping statistics --- 100 packets transmitted, 100 received, 0% packet loss, time 99133ms rtt min/avg/max/mdev = 14.697/15.824/17.012/0.566 ms --- ar15.com ping statistics --- 100 packets transmitted, 98 received, 2% packet loss, time 99139ms rtt min/avg/max/mdev = 97.682/103.752/107.315/2.022 ms |
|
Quoted:
Min 38ms Max 46ms Avg 40ms ETA: Damn I thought I had crappy interwebs. Some of you need to call rotorooter to clean out your pipes. View Quote A portion of the numbers posted here is going to be based on the physical distance from your location to the ar15.com servers, wherever those are located. You may have crappy interwebs. If you're next door to the host, it won't matter. Similarly, someone's going to have a high ping coming from Alaska if the host is in Texas, no matter how awesome their internet is. 51/53/52 here. |
|
At first I was like
138/162/153ms And then I was like Request timed out. Request timed out. 363/563/463ms And on my third try ... Request timed out. Request timed out. Request timed out. 147//147/147ms And on my fourth try ... Request timed out. Request timed out. Request timed out. 372//372/372ms 3G smoke signals ... at night. |
|
88/95 avg 91
For as shitty as it is I'm pleasntly surprised. ETA I tried youporn and I timed out. |
|
Geographically racist.
Servers are in NY. Get about 85ms from MT. |
|
Lightower might even be available in CentriLogic's datacenter. Mine is going to be tough to beat.
|
|
--- ar15.com ping statistics --- 10 packets transmitted, 10 received, 0% packet loss, time 9012ms rtt min/avg/max/mdev = 57.154/57.276/57.459/0.301 ms |
|
1.206/1.556 /1.481 ms
Decent tonight... (10Gbps fiber into L3) |
|
ping ar15.com
Pinging ar15.com [209.251.48.101] with 32 bytes of data: Reply from 209.251.48.101: bytes=32 time=26ms TTL=250 Reply from 209.251.48.101: bytes=32 time=27ms TTL=250 Reply from 209.251.48.101: bytes=32 time=26ms TTL=250 Reply from 209.251.48.101: bytes=32 time=26ms TTL=250 Ping statistics for 209.251.48.101: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 26ms, Maximum = 27ms, Average = 26ms |
|
hanzerik@hanzerik-1705 ~ $ ping ar15.com -c 4
PING ar15.com (209.251.48.101) 56(84) bytes of data. 64 bytes from 209.251.48.101: icmp_seq=1 ttl=46 time=87.4 ms 64 bytes from 209.251.48.101: icmp_seq=2 ttl=46 time=86.7 ms 64 bytes from 209.251.48.101: icmp_seq=3 ttl=46 time=86.7 ms 64 bytes from 209.251.48.101: icmp_seq=4 ttl=46 time=89.3 ms --- ar15.com ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3005ms rtt min/avg/max/mdev = 86.746/87.587/89.369/1.106 ms |
|
Quoted:
This is bad, right? http://i604.photobucket.com/albums/tt122/caboose314/Arfcom/12344_zpszcb8mhbv.jpg View Quote when you really think about it its pretty awesome. 1/2 sec to send an electronic request to a server 1000 miles away, that server to recieve, figure out it needs to send a response, the send back a response 1000 miles back...all in less that 1/2 a second... but yea that sucks. |
|
202/204/202 Of course, I am on the other side of the globe so there's that. |
|
24ms 15.49Mbps dl, 2.78 up
cable Eta: ookla speed test, not pinging ar15.com. |
|
Sign up for the ARFCOM weekly newsletter and be entered to win a free ARFCOM membership. One new winner* is announced every week!
You will receive an email every Friday morning featuring the latest chatter from the hottest topics, breaking news surrounding legislation, as well as exclusive deals only available to ARFCOM email subscribers.
AR15.COM is the world's largest firearm community and is a gathering place for firearm enthusiasts of all types.
From hunters and military members, to competition shooters and general firearm enthusiasts, we welcome anyone who values and respects the way of the firearm.
Subscribe to our monthly Newsletter to receive firearm news, product discounts from your favorite Industry Partners, and more.
Copyright © 1996-2024 AR15.COM LLC. All Rights Reserved.
Any use of this content without express written consent is prohibited.
AR15.Com reserves the right to overwrite or replace any affiliate, commercial, or monetizable links, posted by users, with our own.