From: bqt@update.uu.se (Johnny Billquist)
Subject: [TUHS] Ping times (was: Code bloat)
Date: Thu, 9 Feb 2017 22:13:06 +0100 [thread overview]
Message-ID: <5ba92030-a44e-bfd1-6d41-195fc42b46c1@update.uu.se> (raw)
In-Reply-To: <mailman.220.1486670111.3779.tuhs@minnie.tuhs.org>
On 2017-02-09 20:55, corey at lod.com (Corey Lindsly) wrote:
>
>> In spite of that, I'm typing away to you all, I'm 3ms away from 8.8.8.8
>> (Google's dns server). Go wireless. It's pretty remarkable to be here
>> and have decent net connectivity.
>>
>> I do not yearn for the days of SLIP.
>> --
>> ---
>> Larry McVoy lm at mcvoy.com http://www.mcvoy.com/lm
> 3ms? Really? I'm impressed, and I'd like to see your traceroute. We peer
> directly with Google and I get 4-5ms. Do share.
Meh. From Uppsala in Sweden I seem to have about 2ms ping time to 8.8.8.8...
Psilocybe:update/bqt> ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_req=1 ttl=56 time=2.10 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=56 time=1.93 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=56 time=2.05 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=56 time=1.89 ms
64 bytes from 8.8.8.8: icmp_req=5 ttl=56 time=2.02 ms
64 bytes from 8.8.8.8: icmp_req=6 ttl=56 time=2.05 ms
64 bytes from 8.8.8.8: icmp_req=7 ttl=56 time=2.00 ms
64 bytes from 8.8.8.8: icmp_req=8 ttl=56 time=1.97 ms
64 bytes from 8.8.8.8: icmp_req=9 ttl=56 time=2.03 ms
64 bytes from 8.8.8.8: icmp_req=10 ttl=56 time=2.10 ms
^C
--- 8.8.8.8 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9011ms
rtt min/avg/max/mdev = 1.894/2.020/2.108/0.067 ms
Psilocybe:update/bqt> traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
1 r1.n.it.uu.se (130.238.19.254) 1.986 ms 2.324 ms 2.717 ms
2 l-uu-1-b1.uu.se (130.238.6.251) 0.288 ms 0.680 ms 0.646 ms
3 uu-r1.sunet.se (130.242.6.148) 0.686 ms 0.685 ms 0.673 ms
4 uppsala-upa-r1.sunet.se (130.242.4.138) 0.672 ms 0.661 ms 0.657 ms
5 stockholm-fre-r1.sunet.se (130.242.4.26) 3.503 ms 3.468 ms 3.483 ms
6 se-fre.nordu.net (109.105.102.9) 24.456 ms 24.532 ms 24.153 ms
7 se-kst2.nordu.net (109.105.97.27) 1.934 ms 1.902 ms 1.891 ms
8 as15169-te-tc1.sthix.net (192.121.80.47) 2.204 ms 2.189 ms
72.14.196.42 (72.14.196.42) 1.872 ms
9 216.239.40.29 (216.239.40.29) 1.862 ms 1.941 ms 216.239.40.27
(216.239.40.27) 1.995 ms
10 209.85.251.233 (209.85.251.233) 2.398 ms 209.85.245.61
(209.85.245.61) 2.778 ms 72.14.234.85 (72.14.234.85) 2.385 ms
11 google-public-dns-a.google.com (8.8.8.8) 2.372 ms 2.366 ms 2.337 ms
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
next parent reply other threads:[~2017-02-09 21:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.220.1486670111.3779.tuhs@minnie.tuhs.org>
2017-02-09 21:13 ` Johnny Billquist [this message]
2017-02-09 23:03 ` Joerg Schilling
2017-02-09 23:09 ` [TUHS] Ping times Johnny Billquist
2017-02-10 2:07 ` [TUHS] Ping times (was: Code bloat) Jason Stevens
2017-02-10 4:15 ` Corey Lindsly
2017-02-10 8:05 ` [TUHS] Ping times Johnny Billquist
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5ba92030-a44e-bfd1-6d41-195fc42b46c1@update.uu.se \
--to=bqt@update.uu.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).