Is it about to get real?
Category Archives: Weird
Zombie Minks
Amazon.com
Very weird. I cannot access the website from this computer. It’s not a route issue, because I can get to it from her Windows machine, but on my Linux machine, it times out. Traceroute output is:
$ traceroute amazon.com
traceroute to amazon.com (176.32.98.166), 30 hops max, 60 byte packets
1 * * *
2 81.d6.9bc0.ip4.static.sl-reverse.com (192.155.214.129) 17.514 ms 17.540 ms 17.560 ms
3 ae22.dar01.sjc01.networklayer.com (50.23.118.158) 19.775 ms 17.523 ms 19.857 ms
4 ae9.bbr02.eq01.sjc02.networklayer.com (50.97.19.166) 19.543 ms 19.665 ms 19.535 ms
5 ae6.cbs02.eq01.sjc02.networklayer.com (50.97.17.78) 20.183 ms * *
6 ae0.cbs02.cs01.lax01.networklayer.com (50.97.17.86) 26.906 ms 27.243 ms 27.196 ms
7 * * *
8 * * *
9 ae2.dar01.dal13.networklayer.com (169.45.18.37) 57.537 ms 54.337 ms 55.683 ms
10 * ae16.cbs02.eq01.dal03.networklayer.com (169.45.18.90) 54.432 ms 57.155 ms
11 ae0.cbs01.tl01.atl01.networklayer.com (50.97.17.163) 82.146 ms 84.211 ms 85.019 ms
12 ae8.bbr01.tl01.atl01.networklayer.com (50.97.17.155) 72.644 ms 74.857 ms 72.502 ms
13 amazon.tieatl.telxgroup.net (198.32.132.95) 77.715 ms 74.947 ms 74.869 ms
14 * * *
15 * * *
16 * * *
17 178.236.3.31 (178.236.3.31) 88.314 ms 54.240.229.187 (54.240.229.187) 90.802 ms 54.240.229.217 (54.240.229.217) 84.928 ms
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
When I ping it, I get this:
$ ping amazon.com
PING amazon.com (176.32.103.205) 56(84) bytes of data.
64 bytes from 176.32.103.205 (176.32.103.205): icmp_seq=1 ttl=233 time=79.8 ms
64 bytes from 176.32.103.205 (176.32.103.205): icmp_seq=2 ttl=233 time=80.7 ms
64 bytes from 176.32.103.205 (176.32.103.205): icmp_seq=3 ttl=233 time=79.8 ms
64 bytes from 176.32.103.205 (176.32.103.205): icmp_seq=4 ttl=233 time=82.8 ms
64 bytes from 176.32.103.205 (176.32.103.205): icmp_seq=5 ttl=233 time=79.7 ms
64 bytes from 176.32.103.205 (176.32.103.205): icmp_seq=6 ttl=233 time=78.7 ms
64 bytes from 176.32.103.205 (176.32.103.205): icmp_seq=7 ttl=233 time=79.2 ms
^C
— amazon.com ping statistics —
7 packets transmitted, 7 received, 0% packet loss, time 6005ms
rtt min/avg/max/mdev = 78.697/80.101/82.796/1.235 ms
When I try to browse to that IP address, I get this:
Your connection is not private
Attackers might be trying to steal your information from 176.32.103.205 (for example, passwords, messages, or credit cards). Learn more
NET::ERR_CERT_COMMON_NAME_INVALID
This server could not prove that it is 176.32.103.205; its security certificate is from *.peg.a2z.com. This may be caused by a misconfiguration or an attacker intercepting your connection.
**************************************************************
Anyone have any idea what might be going on? This only started in the past day or so.
Note: I have the same problem on my virtual Windows machine. I simply cannot access Amazon from this hardware.
[Update a while later]
None of the proferred explanations so far explain why it’s only (AFAIK) amazon.com.
[Afternoon update]
OK, the problem is with ExpressVPN. When I disconnect it, and put Google’s nameserver in /etc/resolv.conf, it works. So I guess I need to talk to them.
[Late afternoon update]
OK, the problem seemed to be the San Francisco VPN server (the default). When I connected to LA instead, the problem went away.
The Prophet RBG?
All hail her.
“Commander Red”
…turns out to be yellow.
You’d have to have a heart of stone to not laugh out loud.
The Space Navy
Navy ranks for space has long been a topic at SF conventions. Now it’s becoming real.
Living A Million Years
I think that even I would get pretty bored after only a thousand or so.
A Proposed Coup
Yes, having the Chairman of the JCS call out the military if Trump refuses to leave office is a terrible idea, on multiple levels. This is Trump derangement to the max.
The Butterfly Effect
Quantum physicists say “don’t sweat it.”
That’s good news, I guess, if we ever get time travel.
“Off-World Vehicles Not Made On This Earth”
Well, things are getting interesting.
[Update a few minutes later]
As noted in comments, the grays broke the link. I’ve fixed it now.
[Update a while later]
How worried should we be that they’re buzzing our military assets?
As noted, the problem is not what we know about it, but what we don’t know.
[Late-afternoon update]
Today’s (other) fake news in space.