Network report

Who holds an IP address, prefix or AS number, how it is routed (origin AS, RPKI, IRR), its reverse DNS, blocklist listings and PeeringDB record, with what to fix first.

AS1 · 1 second ago

curl -s "https://thenetworkery.com/api/v1/network-report?query=AS1"

JSON Docs

Warning: AS1 (LVLT-1) announces 6 IPv4 and 0 IPv6 prefixes. 4 warnings

AS page	AS1
Holder	LVLT-1 - Level 3 Parent, LLC
Allocation	ARIN, United States (US), assigned 2001-09-20
Prefixes (IPv4 / IPv6)	6 / 0
RPKI valid	0% (0 / 6)
Upstreams and peers	6

What to fix

Warning

No IPv6 prefixes announced.

Networks without IPv6 force their users through NAT64 or leave them unreachable from IPv6-only networks.

Fix: Get an IPv6 allocation from your RIR (usually free with your IPv4 membership) and announce it.

Open in ASN & BGP prefix lookup
Warning
6 of 6 announced prefixes have no ROA (RPKI not found): 177.75.88.0/24, 177.75.90.0/24, 177.75.93.0/24, 191.7.35.0/24, 205.207.214.0/24 (+1).

Without a ROA, networks cannot tell your routes from a hijack.

Fix: Create a ROA for each at your RIR portal, with origin AS1 and a max length equal to the prefix length:
```
177.75.88.0/24 AS1 max-length /24
177.75.90.0/24 AS1 max-length /24
177.75.93.0/24 AS1 max-length /24
191.7.35.0/24 AS1 max-length /24
205.207.214.0/24 AS1 max-length /24
212.94.84.0/22 AS1 max-length /22
```
Open in RPKI / ROA validator Guide
Warning
6 of 6 announced prefixes have no IRR route object: 212.94.84.0/22, 205.207.214.0/24, 177.75.88.0/24, 177.75.93.0/24, 177.75.90.0/24 (+1).

Many networks build their prefix filters from IRR data; without route objects some of them drop the routes.

Fix: Create route (IPv4) and route6 (IPv6) objects with origin AS1 in your RIR’s IRR database (or RADB).
```
route: 212.94.84.0/22
origin: AS1

route: 205.207.214.0/24
origin: AS1

route: 177.75.88.0/24
origin: AS1
```
Open in ASN & BGP prefix lookup
Warning

PeeringDB did not answer: HTTP 404

Fix: Try again in a minute.

Open in PeeringDB lookup

Checks

Routing and RPKI No IPv6 prefixes announced.

Pass: AS1 announces 6 IPv4 and 0 IPv6 prefixes.
Warning: No IPv6 prefixes announced.
Warning: 6 of 6 announced prefixes have no ROA (RPKI not found): 177.75.88.0/24, 177.75.90.0/24, 177.75.93.0/24, 191.7.35.0/24, 205.207.214.0/24 (+1).
Warning: 6 of 6 announced prefixes have no IRR route object: 212.94.84.0/22, 205.207.214.0/24, 177.75.88.0/24, 177.75.93.0/24, 177.75.90.0/24 (+1).
Info: 6 upstreams and peers, 1 downstream networks seen.

Holder	LVLT-1 - Level 3 Parent, LLC
IPv4 prefixes	6
IPv6 prefixes	0
RPKI	6 not found
Without IRR route object	6
Downstream networks	1

Routes to fix

Prefix	RPKI
177.75.88.0/24	No ROA
177.75.90.0/24	No ROA
177.75.93.0/24	No ROA
191.7.35.0/24	No ROA
205.207.214.0/24	No ROA
212.94.84.0/22	No ROA

Upstreams and peers seen to the left 6

AS263309 LaraNet Telecomunicações e Serviços AS29132 IMAGEWORLD-AS AS7046 RFC2270-UUNET-CUSTOMER AS262544 Sulcom Informatica LTDA AS264773 GOZFLY S.A AS396455 CMM-CMH

Announced prefixes 6

177.75.88.0/24 177.75.90.0/24 177.75.93.0/24 191.7.35.0/24 205.207.214.0/24 212.94.84.0/22

Source: RIPEstat (RIPE NCC RIS, Routinator, IRR); AS names: Team Cymru

Open in ASN & BGP prefix lookup

Registration Found at rdap.arin.net.

Pass: Found at rdap.arin.net.

Name	LVLT-1
Handle	AS1
Range	AS1
Status	active
Registered	2001-09-20T00:00:00-04:00
Last changed	2024-06-18T15:47:14-04:00
Abuse contact	abuse@level3.com

Allocation

Registry (RIR)	ARIN
Country	United States (US)
Delegated on	2001-09-20
Status	Assigned
Delegated range	AS1

Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.

Contacts

Role	Name	Email
registrant	Level 3 Parent, LLC

Source: https://rdap.arin.net/registry/autnum/1. Registration data from rdap.arin.net, shown under its terms of use (terms): not for marketing or bulk collection.

Open in WHOIS / RDAP lookup

PeeringDB PeeringDB did not answer: HTTP 404

Warning: PeeringDB did not answer: HTTP 404

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup