Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Register

Quick Links


Categories

In this Discussion

› › SEATTLE - Ryzen @ $5.95/mo, Xeon @ $6.80/mo. SSD, Unmetered gigE & BGP. FREE CREDITS!!!!! - Page 21
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

SEATTLE - Ryzen @ $5.95/mo, Xeon @ $6.80/mo. SSD, Unmetered gigE & BGP. FREE CREDITS!!!!!

1…1819212324…33

Comments

  • forkfork Barred

    Free Credits <3

  • HoomanHooman Barred

    Free Credits....

  • HoomanHooman Barred

    Free Credits....

  • HoomanHooman Barred

    Free Credits....

  • u104b230u104b230 Member

    FREE CREDITS!!!!

  • ehabehab Member

    @fork said:
    Free Credits <3

    i love u 2 my son.

  • ats5181ats5181 Member

    FREE CREDITS,nice.

  • raindog308raindog308 Administrator, Veteran

    Not quite seeing the same ping from Portland, OR...

    $ ping -c 10 104.224.52.1
PING 104.224.52.1 (104.224.52.1): 56 data bytes
64 bytes from 104.224.52.1: icmp_seq=0 ttl=53 time=88.161 ms
64 bytes from 104.224.52.1: icmp_seq=1 ttl=53 time=60.106 ms
64 bytes from 104.224.52.1: icmp_seq=2 ttl=53 time=51.449 ms
64 bytes from 104.224.52.1: icmp_seq=3 ttl=53 time=59.949 ms
64 bytes from 104.224.52.1: icmp_seq=4 ttl=53 time=62.697 ms
64 bytes from 104.224.52.1: icmp_seq=5 ttl=53 time=60.136 ms
64 bytes from 104.224.52.1: icmp_seq=6 ttl=53 time=49.892 ms
64 bytes from 104.224.52.1: icmp_seq=7 ttl=53 time=63.322 ms
64 bytes from 104.224.52.1: icmp_seq=8 ttl=53 time=66.879 ms
64 bytes from 104.224.52.1: icmp_seq=9 ttl=53 time=57.116 ms

--- 104.224.52.1 ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 49.892/61.971/88.161/10.017 ms

    ...though that's from my laptop. From a Vultr in Seattle:

    # ping -c 10 104.224.52.1
PING 104.224.52.1 (104.224.52.1) 56(84) bytes of data.
64 bytes from 104.224.52.1: icmp_seq=1 ttl=60 time=0.425 ms
64 bytes from 104.224.52.1: icmp_seq=2 ttl=60 time=0.467 ms
64 bytes from 104.224.52.1: icmp_seq=3 ttl=60 time=0.506 ms
64 bytes from 104.224.52.1: icmp_seq=4 ttl=60 time=0.481 ms
64 bytes from 104.224.52.1: icmp_seq=5 ttl=60 time=0.474 ms
64 bytes from 104.224.52.1: icmp_seq=6 ttl=60 time=0.497 ms
64 bytes from 104.224.52.1: icmp_seq=7 ttl=60 time=0.508 ms
64 bytes from 104.224.52.1: icmp_seq=8 ttl=60 time=1.93 ms
64 bytes from 104.224.52.1: icmp_seq=9 ttl=60 time=0.499 ms
64 bytes from 104.224.52.1: icmp_seq=10 ttl=60 time=0.522 ms

--- 104.224.52.1 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9173ms
rtt min/avg/max/mdev = 0.425/0.630/1.925/0.432 ms
  • protonproton Barred

    FREE CREDITS!

  • protonproton Barred

    FREE CREDITS!

  • protonproton Barred

    FREE CREDITS!

  • protonproton Barred

    FREE CREDITS!

  • protonproton Barred

    FREE CREDITS!

  • DvoDvo Veteran

    @raindog308 said:
    Not quite seeing the same ping from Portland, OR...

    Without a traceroute, can't do much. Off the HE LG for Portland, it's show 5~ ms.

    If I had to guess, I'd say you're getting routed through California via your ISP.

  • raindog308raindog308 Administrator, Veteran

    @Dvo said: If I had to guess, I'd say you're getting routed through California via your ISP.

    No but apparently getting out of my neighborhood injects a lot of latency.

    $ traceroute 104.224.52.1
traceroute to 104.224.52.1 (104.224.52.1), 64 hops max, 52 byte packets
 1  192.168.52.1 (192.168.52.1)  35.034 ms  2.586 ms  2.261 ms
 2  10.0.0.1 (10.0.0.1)  16.317 ms  2.311 ms  3.751 ms
 3  100.92.102.66 (100.92.102.66)  29.521 ms
    100.92.102.67 (100.92.102.67)  58.689 ms
    100.92.102.66 (100.92.102.66)  18.360 ms
 4  162.151.214.133 (162.151.214.133)  29.685 ms  22.764 ms  38.349 ms
 5  po-400-xar02.troutdale.or.bverton.comcast.net (96.216.158.101)  58.532 ms
    po-2-rur402.troutdale.or.bverton.comcast.net (24.124.129.46)  37.700 ms
    po-400-xar02.troutdale.or.bverton.comcast.net (96.216.158.101)  15.409 ms
 6  po-400-xar02.troutdale.or.bverton.comcast.net (96.216.158.101)  11.349 ms
    96.216.158.37 (96.216.158.37)  40.205 ms  17.087 ms
 7  be-36221-cs02.seattle.wa.ibone.comcast.net (68.86.93.53)  53.544 ms
    be-36241-cs04.seattle.wa.ibone.comcast.net (68.86.93.61)  61.699 ms
    96.216.158.37 (96.216.158.37)  34.774 ms
 8  be-36241-cs04.seattle.wa.ibone.comcast.net (68.86.93.61)  15.941 ms  16.900 ms
    be-36211-cs01.seattle.wa.ibone.comcast.net (68.86.93.49)  39.625 ms
 9  * 50.208.233.194 (50.208.233.194)  35.722 ms
    be-2313-pe13.seattle.wa.ibone.comcast.net (96.110.44.90)  43.494 ms
10  xe-1-3-0.igw3.limewave.net (104.224.52.1)  47.449 ms  17.970 ms  19.251 m

    Pinging a Vultr Seattle:

    10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 17.232/23.797/56.004/11.041 ms

    All good...was just curious.

  • NFSCNFSC Member

    FREE CREDITS!~

  • dom1024dom1024 Member

    FREE CREDITS

  • dom1024dom1024 Member

    FREE CREDITS

  • dom1024dom1024 Member

    FREE CREDITS

  • dom1024dom1024 Member

    FREE CREDITS

  • anand_1zanand_1z Member

    Free Credits!!!

  • dom1024dom1024 Member

    FREE CREDITS

  • dom1024dom1024 Member

    FREE CREDITS

  • rattlecattlerattlecattle Member

    Fire Credits

  • rattlecattlerattlecattle Member

    Fine Credits

  • HoomanHooman Barred

    Thanked by 1ehab
  • HoomanHooman Barred

    Thanked by 1ehab
  • ehabehab Member

    @Dvo we need a weekend winner if it fits your soup credits schedule
    :)

  • forkfork Barred

    FREE CREDITS

  • forkfork Barred

    FREE CREDITS

Sign In or Register to comment.