Warning

 

Close

Confirm Action

Are you sure you wish to do this?

Confirm Cancel
BCM
User Panel

Site Notices
Arrow Left Previous Page
Page / 2
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.


 
Link Posted: 5/22/2015 11:16:41 PM EDT
[#1]
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
Link Posted: 5/22/2015 11:17:28 PM EDT
[#2]
110/120/113



Wired/Cable
Link Posted: 5/22/2015 11:19:43 PM EDT
[#3]
103/103/103 DSL
Link Posted: 5/22/2015 11:23:34 PM EDT
[#4]
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
Link Posted: 5/22/2015 11:23:51 PM EDT
[#5]
94/99/95



cable

Link Posted: 5/22/2015 11:24:29 PM EDT
[#6]
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.
Link Posted: 5/22/2015 11:27:07 PM EDT
[#7]
--- 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
Link Posted: 5/22/2015 11:36:21 PM EDT
[#8]
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


Link Posted: 5/22/2015 11:37:48 PM EDT
[#9]
--- 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


Link Posted: 5/22/2015 11:40:58 PM EDT
[#10]

Discussion ForumsJump to Quoted PostQuote History
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
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?
Link Posted: 5/22/2015 11:41:06 PM EDT
[#11]
Average 47ms on Wifi DSL
Link Posted: 5/22/2015 11:42:14 PM EDT
[#12]
Discussion ForumsJump to Quoted PostQuote History
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
Discussion ForumsJump to Quoted PostQuote History
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
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?
Thats why I checked google and speedtest.net.  Not sure why ar15.com would have such a higher ping, either.

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
Link Posted: 5/22/2015 11:43:58 PM EDT
[#13]
40/76/53
Link Posted: 5/23/2015 12:38:15 AM EDT
[#14]
Discussion ForumsJump to Quoted PostQuote History
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.
Link Posted: 5/23/2015 12:44:54 AM EDT
[#15]
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.
Link Posted: 5/23/2015 12:50:04 AM EDT
[#16]
88/95 avg 91

For as shitty as it is I'm pleasntly surprised.

ETA I tried youporn and I timed out.
Link Posted: 5/23/2015 12:52:34 AM EDT
[#17]
shitass editor





81ms




 
Link Posted: 5/23/2015 1:01:38 AM EDT
[#18]
avg 84



WiFi/DSL




Fuck Suddenlink
Link Posted: 5/23/2015 1:05:45 AM EDT
[#19]
Hughes Net
Link Posted: 5/23/2015 1:10:52 AM EDT
[#20]
Geographically racist.

Servers are in NY.

Get about 85ms from MT.
Link Posted: 5/23/2015 1:40:06 AM EDT
[#21]

    36ms/66ms/46ms
Link Posted: 5/23/2015 1:49:14 AM EDT
[#22]
Why? What game are they hosting?

Link Posted: 5/23/2015 1:55:01 AM EDT
[#23]
49/52/50
Link Posted: 5/23/2015 2:03:33 AM EDT
[#24]


Lightower Fiber
Link Posted: 5/23/2015 2:04:45 AM EDT
[#25]
86/90/87

Yep, 87 average.
Link Posted: 5/23/2015 2:07:32 AM EDT
[#26]
have no idea what you are talking about
Link Posted: 5/23/2015 2:11:51 AM EDT
[#27]
Lightower might even be available in CentriLogic's datacenter. Mine is going to be tough to beat.
Link Posted: 5/23/2015 2:14:58 AM EDT
[#28]
Pinging ar15.com [209.251.48.101] with 32 bytes of data:



Reply from 209.251.48.101: bytes=32 time=53ms TTL=53



Reply from 209.251.48.101: bytes=32 time=53ms TTL=53



Reply from 209.251.48.101: bytes=32 time=53ms TTL=53



Reply from 209.251.48.101: bytes=32 time=53ms 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 = 53ms, Maximum = 53ms, Average = 53ms





EDIT:  My internet sucks






 
Link Posted: 5/23/2015 2:32:07 AM EDT
[#29]
min = 42ms
max - 52ms
avg - 50ms
Link Posted: 5/23/2015 2:37:56 AM EDT
[#30]

--- 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



Link Posted: 5/23/2015 2:40:28 AM EDT
[#31]
This is bad, right?

Link Posted: 5/23/2015 2:49:10 AM EDT
[#32]
1.206/1.556 /1.481 ms

Decent tonight... (10Gbps fiber into L3)
Link Posted: 5/23/2015 3:13:56 AM EDT
[#33]
88/94/90
Link Posted: 5/23/2015 4:23:46 AM EDT
[#34]
59ms high, low, and average
Link Posted: 5/23/2015 4:37:32 AM EDT
[#35]
min=55, max=61, ave=57

Link Posted: 5/23/2015 4:44:24 AM EDT
[#36]


22/37/26.


Link Posted: 5/23/2015 5:40:33 AM EDT
[#37]
What fun!  DDOS'ing Arfcom!    


31/32/31
Link Posted: 5/23/2015 5:43:50 AM EDT
[#38]
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

Link Posted: 5/23/2015 5:46:36 AM EDT
[#39]
Ok I have no life to do this at 5:44 am 32ms
Link Posted: 5/23/2015 5:53:03 AM EDT
[#40]
min 23, max 242, avg 78
FIOS
Link Posted: 5/23/2015 5:56:49 AM EDT
[#41]
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
Link Posted: 5/23/2015 6:58:38 AM EDT
[#42]
average 37ms (comcast cable)
Link Posted: 5/23/2015 7:10:58 AM EDT
[#43]
29 min
32 max
30 avg
Link Posted: 5/23/2015 7:25:33 AM EDT
[#44]
Discussion ForumsJump to Quoted PostQuote History


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.
Link Posted: 5/23/2015 7:25:40 AM EDT
[#45]
56-58
Link Posted: 5/23/2015 7:27:58 AM EDT
[#46]

202/204/202

Of course, I am on the other side of the globe so there's that.  


Link Posted: 5/23/2015 7:45:00 AM EDT
[#47]
I dont know what any of you are talking about.
Link Posted: 5/23/2015 7:47:19 AM EDT
[#48]
58/59/58

Cable via wifi
Link Posted: 5/23/2015 7:55:24 AM EDT
[#49]
24ms  15.49Mbps dl, 2.78 up





cable


 



Eta:  ookla speed test, not pinging ar15.com.  
Link Posted: 5/23/2015 8:13:46 AM EDT
[#50]
I have no hope in this contest since I'm 4,100 miles (with a intentional fudge factor of ±50) from the ar15.com server. But here are my results anyway (VDSL with automatically connecting HSPA backup)::

Pinging ar15.com [209.251.48.101] with 32 bytes of data:

Reply from 209.251.48.101: bytes=32 time=133ms TTL=51
Reply from 209.251.48.101: bytes=32 time=133ms TTL=51
Reply from 209.251.48.101: bytes=32 time=134ms TTL=51
Reply from 209.251.48.101: bytes=32 time=136ms TTL=51

Ping statistics for 209.251.48.101:
   Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
   Minimum = 133ms, Maximum = 136ms, Average = 134ms
View Quote


Pinging google.fi [193.229.108.94] with 32 bytes of data:

Reply from 193.229.108.94: bytes=32 time=17ms TTL=60
Reply from 193.229.108.94: bytes=32 time=17ms TTL=60
Reply from 193.229.108.94: bytes=32 time=17ms TTL=60
Reply from 193.229.108.94: bytes=32 time=17ms TTL=60

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


Arrow Left Previous Page
Page / 2
Close Join Our Mail List to Stay Up To Date! Win a FREE Membership!

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.


By signing up you agree to our User Agreement. *Must have a registered ARFCOM account to win.
Top Top