News for hackers. Stuff that matters.
Re:Tell HN: Amazon now owns 3.0.0.0/8 by akulbe on Thursday November 08, 2018 @11:12AM (#18407239)
I wonder what they got it for? if just for more IPs for AWS stuff, or if it's for something like IoT stuff?
Re:Tell HN: Amazon now owns 3.0.0.0/8 by bklyn11201 on Thursday November 08, 2018 @11:23AM (#18407349)
At $18 per IP: 2^24 * $18 = $302mm

At $14 per IP: 2^24 * $14 = $235mm

Price per IP estimated from:

  https://www.ipv4auctions.com/
In 2011, Microsoft paid $11.25 per IP to Nortel for 666k addresses
Re:Tell HN: Amazon now owns 3.0.0.0/8 by ttul on Thursday November 08, 2018 @08:19PM (#18411663)
I bought a /20 in 2015 for $6.00/address. I am feeling very lucky.
Re:Tell HN: Amazon now owns 3.0.0.0/8 by adobeeee on Thursday November 08, 2018 @10:56PM (#18412227)
How does one buy one? I'm in the eastern Europe.
Re:Tell HN: Amazon now owns 3.0.0.0/8 by hartator on Friday November 09, 2018 @09:45AM (#18414691)
Very curious as well.
Re:Tell HN: Amazon now owns 3.0.0.0/8 by exikyut on Friday November 09, 2018 @02:09AM (#18412850)
(A /20 is 1,048,576 IPs, so this would have been $6,291,456. OP appears to be a small ISP.)
Re:Tell HN: Amazon now owns 3.0.0.0/8 by grogers on Friday November 09, 2018 @08:46AM (#18414260)
No, a /20 is 2^12=4096 addresses.
Re:Tell HN: Amazon now owns 3.0.0.0/8 by peeters on Thursday November 08, 2018 @11:19AM (#18407313)
I'm not sure IoT is the best use of a contiguous IPv4 range... you're talking about less than 17 million addresses.

Depending on how much it actually cost I feel like it could be a number of things from simple branding to nefarious traffic shaping. If you're an AWS shop maybe they want you to be able to set simple bypass/static route for 3.0.0.0/8.

Re:Tell HN: Amazon now owns 3.0.0.0/8 by bradgnar on Thursday November 08, 2018 @11:41AM (#18407530)
you could make 17 million networks with it, entry point into aws vpcs has to be somewhere
Re:Tell HN: Amazon now owns 3.0.0.0/8 by nothis on Thursday November 08, 2018 @11:31AM (#18407420)
What's up with IPv6, anyways?
Re:Tell HN: Amazon now owns 3.0.0.0/8 by AtlasBarfed on Thursday November 08, 2018 @10:13PM (#18412086)
Every time I deal with IPv6 it just strikes me how little the designers cared about migration from IPv4.

No clear prescriptions for legacy v4 <-> v6 translations, religious hate of NAT, unfortunate separator character (the colon) that is used for domain:port separation. Separate stack prescriptions.

I honestly think it would have been easier to do a rolling upgrade of the internet to support bigger numbers in the four coordinates of IP addresses and increase the number of ports.

I'm obviously not a deep networking expert, but as I've been exposed to IPv6 test conversions it's been painful.

Re:Tell HN: Amazon now owns 3.0.0.0/8 by akvadrako on Friday November 09, 2018 @01:49AM (#18412792)
IPv6 is a total mess; it was intended to be a clean break from IPv4 and do things more correctly. Turns out that they didn't really think it though; besides more bits anything from IPv6 was either easy to add to v4 or turned out to be a bad idea (like SLAAC).

It should never have been adopted in the first place but now it's the only practical option for moving forward.

Re:Tell HN: Amazon now owns 3.0.0.0/8 by OedipusRex on Thursday November 08, 2018 @11:35AM (#18407470)
Enough address space for every atom on the surface of the earth.
Re:Tell HN: Amazon now owns 3.0.0.0/8 by noselasd on Thursday November 08, 2018 @03:43PM (#18409812)
And I have a /64 from my ISP giving me about eighteen quintillion addresses, but no sane/supported/easy way to further subnet that locally. IPv6/rfc7421 is great ...
Re:Tell HN: Amazon now owns 3.0.0.0/8 by AndrewDucker on Thursday November 08, 2018 @11:38AM (#18407511)
Re:Tell HN: Amazon now owns 3.0.0.0/8 by johnp_ on Thursday November 08, 2018 @07:04PM (#18411217)
~~No, really. He's talking about the earths surface, the xkcd is about the earths volume.~~

Ok, the xkcd is about nanobots with a volume of "a few cubic microns"[1], whereas atoms are much smaller.

[1] https://www.explainxkcd.com/wiki/index.php/865:_Nanobots

Re:Tell HN: Amazon now owns 3.0.0.0/8 by dijit on Thursday November 08, 2018 @11:37AM (#18407497)
Yet as far as I can tell no cloud provider is taking it seriously.

GCP only supports it on the edge for their load balancers for instance.

Re:Tell HN: Amazon now owns 3.0.0.0/8 by _wldu on Thursday November 08, 2018 @01:03PM (#18408316)
IPv6 works fine in AWS. I have several v6 only resources there now... no problems. No SSH scans, no elastic IP fees, no log noise from all the IPv4 idiots. It's heaven.
Re:Tell HN: Amazon now owns 3.0.0.0/8 by rsync on Thursday November 08, 2018 @11:46AM (#18407590)
All rsync.net locations[1] have ipv6 addresses.

[1] Cali., Denver, Zurich, Hong Kong

Re:Tell HN: Amazon now owns 3.0.0.0/8 by cbm-vic-20 on Thursday November 08, 2018 @11:59AM (#18407714)
Been a customer of yours for ten years. No BS. Just works.
Re:Tell HN: Amazon now owns 3.0.0.0/8 by diegoperini on Thursday November 08, 2018 @11:38AM (#18407498)
So abundant, has no value.
Re:Tell HN: Amazon now owns 3.0.0.0/8 by Zrdr on Thursday November 08, 2018 @12:00PM (#18407718)
I would say "no cost".

On the hosting service I use, you can rent an IPv6 only host and you pay less. Why would you pay for an IPv4 address if you don't need it ?

Re:Tell HN: Amazon now owns 3.0.0.0/8 by asdkhadsj on Thursday November 08, 2018 @12:15PM (#18407861)
I'd love to use it, but honestly it's fairly complex to even understand if I can use it. From my home ISP to my compute provider(s), I've not even done enough research to know if I can use it.

Last I recall (years ago) my buddy was running some type of VPN through Comcast just to be able to use IPv6 properly. That's when I decided it was still too new for me.

Clearly I don't know anything on the subject, and I'm not claiming to. These are one of the areas where I don't know, don't desire to know, and want it to "just work". I am however interested in making my applications compliant asap, but until I can reliably use it, I've not even attempted.

So with that big pile of ignorance, are we "there yet"? Ie, could I build applications and run them on a IPv6 compatible host, with hit it with my home ISP with a reasonable expectation that everything will work? (assuming my code works, of course).

I feel like I need a "caniuseIPv6.com" site, similar to https://caniuse.com. From the outside, IPv6 implementation and support seems bizarrely cryptic.

Re:Tell HN: Amazon now owns 3.0.0.0/8 by CaliforniaKarl on Thursday November 08, 2018 @12:34PM (#18408020)
I'm a current Comcast customer. I own my own (non-Comcast-purchased) router (an RT-AC68U) and cable modem (a Motorola Surfboard).

On the modem side, nothing needed to be done for IPv6. Any firmware updates or configuration needed is done by Comcast.

On the router side, there is a dedicated IPv6 configuration page. Settings are:

• Connection Type: Native

• All other available settings: Set to either 'Enable' or 'Stateless'.

That was it. My Mac has IPv6 configuration set to configure 'Automatically', and I get an IP. If I go to plain Google and ask it "what's my ip" I get a IPv6 IP back.

On my iPhone, on wifi, if I do the same "what's my ip" Google search, I get an IPv6 back. My carrier is Ting GSM; if I turn off wifi and do the same Google search, I get a different IPv6 IP back.

At work, IPv6 is rolling out _very_ slowly, but I was able to get a fixed IPv6 address. That has been programmed into the configuration for my laptop's USB-Ethernet adapter, so I have IPv6 at my desk at work. Although most work services are not IPv6-enabled, DNS is.

And at home, IPv6 is enabled and is in active use, both on desktop and on mobile.

As for testing, I suggest https://test-ipv6.com and https://ipv6test.google.com

Re:Tell HN: Amazon now owns 3.0.0.0/8 by OedipusRex on Thursday November 08, 2018 @12:43PM (#18408107)
Re:Tell HN: Amazon now owns 3.0.0.0/8 by ams6110 on Thursday November 08, 2018 @02:32PM (#18409172)
If I'm at home and my computer has an IPv6 address, and I want to visit a site that has only IPv4 address, where does the NAT happen? Or does it happen? Or is it sort of like ASCII in UTF-8; all IPv4 addresses are directly representable in the IPv6 format? But even if that, how does the IPv4 service send a response back to me?
Re:Tell HN: Amazon now owns 3.0.0.0/8 by tialaramex on Thursday November 08, 2018 @02:53PM (#18409369)
At home you will be "dual stack". That means your operating system implements an entire IPv4 network stack and an entire IPv6 stack, it will see this site only has IPv4, and use IPv4. If your IPv4 access goes through a NAT, then it will use the NAT exactly as if you didn't have IPv6 at all.

(Yes, all IPv4 addresses can be represented as IPv6 addresses in a reserved zero prefix network, some network APIs just offer IPv6 and then treat IPv4 addresses this way for convenience, but we obviously don't route packets this way since those would be IPv6 packets, yet they're for an IPv4 destination which can't read them)

In some very large deployments they do v6-only. Everything internally is IPv6, when you connect to that IPv4 only site you'd actually connect to a company-provided gateway that speaks IPv6 on your side but IPv4 to the outside world.

If you're big enough this makes loads of sense - now you have this vast address space for everything, all your systems are simply configured for IPv6 only (not twice the configuration) and it pretty much just works. You buy some specialist appliances at the edge for that translation, but your users only have IPv6 stuff.

Re:Tell HN: Amazon now owns 3.0.0.0/8 by AtlasBarfed on Thursday November 08, 2018 @10:17PM (#18412103)
Wouldn't it have been nice for IPv6 to provide a basic translation protocol or mapping for seamless migration and backwards compatibility? Where your IPv4 address is also an IPv6 address?

I'd welcome someone showing me how that was basically impossible, but I don't see why the entire IPv4 space isn't in a special prefix / address space of ipv6 since they allegedly have so many atoms of mappings.

Re:Tell HN: Amazon now owns 3.0.0.0/8 by fulafel on Friday November 09, 2018 @01:26AM (#18412709)
This was done, it was called 6to4 and it worked pretty well when native IPv6 was less available. The gateways had an anycast IPv6 address too so you didn't have to manually configure the address of your gateway to the real IPv6 internet.
Re:Tell HN: Amazon now owns 3.0.0.0/8 by DDub on Thursday November 08, 2018 @12:58PM (#18408265)
As an example, if we look at https://github.com/GoogleCloudPlatform/container-vm-guestboo... then there are a couple of things here that are IPv4 only. The first is that the application is only configured to listen on the IPv4 address family, app.run(host='0.0.0.0', port=80), on linux if that was changed to app.run(host='::', port=80) this the application would be able to receive both IPv4 and IPv6 requests (on windows the situation is different however) The second, and less important change, is that the redis connection is using 127.0.0.1, and if instead it was using "localhost" then that would resolve to the correct address family. This is less important as it is only relevant if there is no IPv4 on the server host, the first change would allow your app to accept IPv6 traffic.

Neither of these changes are required if there is a dual stack proxy or CDN that sits infront of your application, as they will most likely talk to your application over IPv4.

The other gotcha is if you try to interrogate clientIP for analytics, authorization, geo-ip etc, which may need a little more care.

Re:Tell HN: Amazon now owns 3.0.0.0/8 by syncsynchalt on Thursday November 08, 2018 @01:46PM (#18408763)
From your point of view it will "just work". One day you'll get an IPv6 address, if you haven't already, and it will look and feel identical to your IPv4 address. So I wouldn't worry about it.

(As a comcast customer that "one day" for me was several years ago)

Re:Tell HN: Amazon now owns 3.0.0.0/8 by stevekemp on Thursday November 08, 2018 @01:07PM (#18408356)
I had an IPv6-only host last year, sucked that I couldn't clone my dotfiles from github - because they were IPv4-only.

Lots of things fail if you're IPv6 only, but it was a useful experiment and I'll try it again in a year or two.

Right now most of my hosts are dual-stack, and I have a /64 setup for my home network.

Re:Tell HN: Amazon now owns 3.0.0.0/8 by forgot-my-pw on Thursday November 08, 2018 @11:36AM (#18407483)
Adoption rate varies from country to country: https://www.google.com/intl/en/ipv6/statistics.html
Re:Tell HN: Amazon now owns 3.0.0.0/8 by ConceptJunkie on Thursday November 08, 2018 @12:18PM (#18407886)
It's interesting to note there's a definite variation on a 24-hour cycle... because there's a correlation between longitude and IPv6 adoption...?
Re:Tell HN: Amazon now owns 3.0.0.0/8 by tialaramex on Thursday November 08, 2018 @12:52PM (#18408210)
Corporates. At work your network is IPv4 only, it passes through a badly made "anti-exfiltration" appliance, a "policy enforcement" appliance and half a dozen more, you have that six year old laptop that's missing some crucial patches because they were incompatible with the Java applet used to order coffee in the board room, and so on.

At home you've been using IPv6 passively for 18 months, it works and you never noticed.

Hence the big up spike on weekends and major holidays.

Re:Tell HN: Amazon now owns 3.0.0.0/8 by 4bpp on Thursday November 08, 2018 @03:04PM (#18409453)
It's on a weekly cycle, with peaks presumably on the weekends. Maybe more home internet connections than workspace internet connections are IPv6, so there is an uptick in registered IPv6 connections when people are at home. (Note how the trough between Dec 24th and 31st is also significantly more shallow than the usual one.)
Re:Tell HN: Amazon now owns 3.0.0.0/8 by zzzcpan on Thursday November 08, 2018 @11:41AM (#18407538)
IPv6 adoption is approaching a big wall. Maybe the industry will finally start reconsidering it and doing honest research into something that can actually get wide spread adoption.
Re:Tell HN: Amazon now owns 3.0.0.0/8 by throwaway2048 on Thursday November 08, 2018 @11:52AM (#18407643)
There is no magical ipv4 compatible protocol that is possible at scale that is simply being denied to the masses by the Ivory Tower IETF.

IPv6 is the future of IP connectivity, that is not going to change.

Re:Tell HN: Amazon now owns 3.0.0.0/8 by zzzcpan on Thursday November 08, 2018 @11:57AM (#18407689)
How so? There is unlimited amount of compatible protocols that can be made to run on top of IPv4.
Re:Tell HN: Amazon now owns 3.0.0.0/8 by wmf on Thursday November 08, 2018 @12:03PM (#18407747)
And they all suck in various (usually non-obvious) ways.
Re:Tell HN: Amazon now owns 3.0.0.0/8 by zzzcpan on Thursday November 08, 2018 @12:21PM (#18407917)
That's the thing. Any idea done in software on top of existing ones sucks infinitely less, than any incompatible idea backed by hardware.
Re:Tell HN: Amazon now owns 3.0.0.0/8 by vertex-four on Thursday November 08, 2018 @12:51PM (#18408204)
Here’s the thing - all the hardware supports it now. Has done for the last couple of decades. Your home router almost definitely does, your carrier’s switches and routers almost definitely do, there’s ipv6 support all the way to Google and Amazon and Netflix and whoever else you want to connect to. It’s a pile of people refusing to implement software (mostly proprietary software - again, open-source systems have supported IPv6 for a very long time) and administrative support for it that’s the issue.

If you want an IPv6 address over your existing IPv4 connectivity, you can get one in a number of ways - that’s an overlay network that is already supported by a massive amount of hardware and free software.

Re:Tell HN: Amazon now owns 3.0.0.0/8 by jkaplowitz on Thursday November 08, 2018 @01:29PM (#18408559)
IPv6 is software in almost all implementations, just like IPv4.
Re:Tell HN: Amazon now owns 3.0.0.0/8 by dcow on Thursday November 08, 2018 @02:10PM (#18408971)
Not actually true. There are plenty of hardware L3/4 switching/routing/flow acceleration chips. IP4 is fast on 32bit machines but IP6 is 4 times the word size there. Hardware does matter.
Re:Tell HN: Amazon now owns 3.0.0.0/8 by jkaplowitz on Thursday November 08, 2018 @03:06PM (#18409476)
Yeah, it exists in hardware implementations too, but most devices that have IP stacks (of either IP version) do it in software because they're general-purpose computing devices.

And it's the general-purpose computing devices that are lagging in IPv6 support, not the networking-centric hardware implementations. It's been quite a while since business-quality networking devices shipped without IPv6 support.

For those home / small-business routers which still lack support, that is probably going to be a software implementation either way, and at the very least the software nature of any IPv6 implementation added through a "firmware" update (really just an OS update) won't be a performance bottleneck for those devices.

In some of those cases a firmware update has even been released by the manufacturer, just not applied. In many more, IPv6 is supported by the networking device and the software/firmware but simply disabled, or not supported by one or both of the ISP and the end-user device.

Re:Tell HN: Amazon now owns 3.0.0.0/8 by icebraining on Thursday November 08, 2018 @12:39PM (#18408065)
How does that solve anything? If you still need an IPv4 address, what's the point?
Re:Tell HN: Amazon now owns 3.0.0.0/8 by zzzcpan on Thursday November 08, 2018 @12:41PM (#18408083)
You don't need a routable IPv4 address, only your ISP needs it. Think overlay networks.
Re:Tell HN: Amazon now owns 3.0.0.0/8 by icebraining on Thursday November 08, 2018 @12:55PM (#18408233)
So, NAT? We already have that, no need for new protocols.
Re:Tell HN: Amazon now owns 3.0.0.0/8 by zzzcpan on Thursday November 08, 2018 @01:23PM (#18408504)
Imagine an overlay network that consists of nodes running directly on end users' computers. It has its own routing system and it can establish connections to other nodes via local network, via internet, punching holes through NAT, etc. If popular things like web browsers implement support for that overlay network, ISPs don't even have to provide NAT or routable IP addresses to customers that want to access the web, they can just run some nodes themselves that have internet connectivity and expect end users' nodes to find those nodes over local network and get web connectivity over that overlay network. Of course there are no limits of how integrated overlay networks can become. But notice how little change overlay networks can be made to impose on everyone and to support effortless gradual transition.
Re:Tell HN: Amazon now owns 3.0.0.0/8 by throwaway2048 on Friday November 09, 2018 @01:21PM (#18416572)
You can already use ipv6 as an overlay network ontop of ipv4 and not worry about whatever wacky shit middle nodes are doing

https://tunnelbroker.net/

https://en.wikipedia.org/wiki/List_of_IPv6_tunnel_brokers

https://en.wikipedia.org/wiki/6to4

The time to bikeshed this stuff is long, long passed, take the time, understand the options, stop writing off ipv6 as impractical, or never going to happen, nobody is writing a (different) overlay network.

Re:Tell HN: Amazon now owns 3.0.0.0/8 by kiallmacinnes on Friday November 09, 2018 @11:58AM (#18415866)
Except educating users on how to install their overlay network of choice.

And how many will they need to install? Will everyone install a generic one that all software just works with? Kinda sounds like IPv6, just with the added network in network overheads, and a competitor (IPv6) that's years ahead in terms of real world deployment.

And then there's the suggestion ISPs could run these popular overlay network nodes, that customers don't even need IP. I'll pass on slicing up the internet into walled gardens that's ISPs get to choose which overlay networks you can access!

Re:Tell HN: Amazon now owns 3.0.0.0/8 by zzzcpan on Friday November 09, 2018 @12:08PM (#18415941)
Web browsers could bundle everything with the next update or use the one already installed, see tor browser bundle for example. No need to educate users. Other software could rely on preinstalled daemons and guide users to "install the internet" on first use if necessary.

And ISPs shouldn't be able to do any harm with those transport nodes, they shouldn't be able to even see what kind of stuff those nodes proxy.

Re:Tell HN: Amazon now owns 3.0.0.0/8 by kiallmacinnes on Friday November 09, 2018 @04:03PM (#18417996)
How is this any better than IPv6? Each browser having its own overlay sounds like the good old days of AOL.

Ignoring that massive issue, which daemons get installed? Who installs them? Who updates them? End users won't. So it's up to the Software+OS vendor and ISP - Just like IPv6.

Don't get me wrong, IPv6 has been, so far, a pretty epic failure in terms of adoption. But your plan seems to put it all in the hands of the exact same people, but at the same time, gives them a massive incentive to partition the internet into a whole bunch of tiny walled gardens.

Why should this turn out any better than IPv6?

Re:Tell HN: Amazon now owns 3.0.0.0/8 by sigi45 on Thursday November 08, 2018 @12:14PM (#18407857)
We needed a few static ipv4 addresses for interconnects.

Customer <> us Office <> us Us @aws <> us @azure

With having so many customers there are probably enough with use cases which requires that ipv4 and having them is probably a necessity.

Re:Tell HN: Amazon now owns 3.0.0.0/8 by tootie on Thursday November 08, 2018 @07:35PM (#18411432)
I haven't worked much in IoT but I kinda assumed devices get private IPs on whatever LAN and phone home to traverse NAT.
[dead]
Re:Tell HN: Amazon now owns 3.0.0.0/8 by mturmon on Thursday November 08, 2018 @11:24AM (#18407354)
Correct strategy in the case of early down votes that you think are incorrect is (1) review what you wrote to see if its tone was flame-bait; (2) wait it out quietly until votes equilibrate. Usually something reasonable comes out over time.
Re:Tell HN: Amazon now owns 3.0.0.0/8 by wheelie_boy on Thursday November 08, 2018 @11:41AM (#18407536)
Yeah, that seems like a better strategy than a salty comment, which almost always just gets downvoted too.
Re:Tell HN: Amazon now owns 3.0.0.0/8 by pbhjpbhj on Thursday November 08, 2018 @11:30AM (#18407415)
Meh, HN seems to hate questions when they think the questioner isn't genuine: Basically if they wish the answer weren't true. That's been my recent experience anyway.

Better suggestion - stop politicking and answer the question or move on.

Sure if the question is badly made then downvote it. Whilst downvote for disagreement is encouraged here (by the site owners) you can't "disagree" with a question, that's nonsensical.

Re:Tell HN: Amazon now owns 3.0.0.0/8 by rdiddly on Thursday November 08, 2018 @11:51AM (#18407636)
Downvoting for disagreement is encouraged? That's news to me! Not welcome news either, because I like the idea that the "quality" of the comment matters more.
Re:Tell HN: Amazon now owns 3.0.0.0/8 by pdpi on Thursday November 08, 2018 @12:07PM (#18407782)
Personally, while I don't downvote for disagreement, I definitely will downvote (what I perceive as) disingenuous questions — There's more productive ways to express an opinion.
Re:Tell HN: Amazon now owns 3.0.0.0/8 by icebraining on Thursday November 08, 2018 @12:43PM (#18408095)
pg (the site's creator) once wrote that it's ok[1], and the current mods have cited that post recently[2], indicating it's still the policy.

[1] https://news.ycombinator.com/item?id=117171

[2] https://news.ycombinator.com/item?id=17996858

Re:Tell HN: Amazon now owns 3.0.0.0/8 by dijit on Thursday November 08, 2018 @11:41AM (#18407528)
I make a habit of commenting if I downvote, sure, the commenter might not like what I have to say but I feel I owe it to them to be as honest about why I felt they weren't contributing to the discussion.

To answer your question: "how can you disagree with a question"; well, you can downvote a question that is loaded (with some kind of ignorant agenda) or a question that is so blisteringly ignorant by itself that it is plain and obvious that the commenter didn't read the article posted, even a skim-read.

Re:Tell HN: Amazon now owns 3.0.0.0/8 by sdegutis on Thursday November 08, 2018 @11:26AM (#18407378)
Downvotes just happen on HN, no need to let it upset you. I have a theory that some anarchists have bots running that just downvote new comments in an arbitrary pattern. You know, to keep things perfectly balanced, as all things should be. Similarly I wrote a Chrome extension that may or may not hide the top comment on any given HN post. Keeps you on your toes. https://github.com/sdegutis/PerfectlyBalancedHN
Re:Tell HN: Amazon now owns 3.0.0.0/8 by dsfyu404ed on Thursday November 08, 2018 @11:54AM (#18407659)
I actually wrote a script to track this and it's been running for a few months.

I generally post around 9am and 12pm US east coast time. When I take a substantial negative hit it's around noon or 3pm on the East coast. There's a baseline amount of up-votes and down-votes (with up-votes dominating) that seems to roughly correlate with the hours most people are awake in the US and Europe.

Someday I'm going to publish a write-up here.

Re:Tell HN: Amazon now owns 3.0.0.0/8 by sdegutis on Thursday November 08, 2018 @12:01PM (#18407732)
What's the conclusion? Seems to me like it could be that it's near the end of the work day for most casual HN readers and they're cranky (low blood sugar from a standard American diet) so they downvote whatever they see?
Re:Tell HN: Amazon now owns 3.0.0.0/8 by icedchai on Thursday November 08, 2018 @11:36AM (#18407479)
Probably because the answer is obvious: AWS. Just do a "whois" on 3.0.0.0 and you'll see the contacts are for AWS EC2.
Re:Tell HN: Amazon now owns 3.0.0.0/8 by gsich on Thursday November 08, 2018 @11:46AM (#18407592)
Truth hurts, that's why you get downvoted.