From mboxrd@z Thu Jan  1 00:00:00 1970
From: Peter =?utf-8?q?M=C3=BCller?= <peter.mueller@ipfire.org>
To: location@lists.ipfire.org
Subject: Re: ASNs without AS name information (LACNIC and JPNIC)
Date: Thu, 09 Dec 2021 23:10:05 +0100
Message-ID: <c0bdf546-3d90-7c1d-cf60-35f5f06370e2@ipfire.org>
In-Reply-To: <8a2f35a2-12d1-4bdd-a7da-d9040993758c@riseup.net>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0524893848568885845=="
List-Id: <location.lists.ipfire.org>

--===============0524893848568885845==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hello nusenu,

thanks for your mail. Please excuse my tardy reply.

>   Network                 : 133.175.0.0/16
>   Country                 : Japan
>   Autonomous System       : AS2519
>=20
>=20
>   Network                 : 49.242.192.0/18
>   Country                 : Japan
>   Autonomous System       : AS10013=20

Both AS lack an "aut-num" object in JPNIC, which is why there is no parseable=
 information
for them at hand in there. Not sure where RIPEstat gets their description fro=
m...

Anyways, ARIN, LACNIC and a better approach to missing data is on my list for=
 next week.
I'll see what we can to then.

Thanks, and best regards,
Peter M=C3=BCller

--===============0524893848568885845==--