bgpreport

Network · data from 2026-11-12

AS61005 AS-OPENTLD1 OpenTLD BV

Registry name: AS-OPENTLD1 OpenTLD BV, NL · not in PeeringDB

5IPv4 routes 0.0% RPKI valid · 40.0% with a route object
2IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
7No ROA 3 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
12Route objects not announced registered with origin AS61005, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS61005, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.

83.223.37.0/24 No ROA None 673 100% 67
83.223.40.0/24 No ROA Other origin only 673 100% 67
83.223.43.0/24 No ROA Other origin only 652 97% 67
80.80.80.0/24 No ROA RIR databaseRIPE 670 100% 67
80.80.81.0/24 No ROA RIR databaseRIPE 670 100% 67
2a04:1b00:80::/48 No ROA RIR databaseRIPE 636 100% 68
2a04:1b00:81::/48 No ROA RIR databaseRIPE 636 100% 67

AS-SET

AS61005 isn't in PeeringDB, where networks name their AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 22 are in fix.csv.

  • ROA: none7
  • Route object: none3
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
ROA: none83.223.37.0/24No ROA covers it. Add a ROA for AS61005, maxLength 24.673 of 673
Route object: none83.223.37.0/24No route object for it. Add a route object with origin AS61005 in the RIR database for the space.673 of 673
ROA: none83.223.40.0/24No ROA covers it. Add a ROA for AS61005, maxLength 24.673 of 673
Route object: none83.223.40.0/24Route objects for it name AS60679. Add a route object with origin AS61005 in the RIR database for the space.673 of 673
ROA: none83.223.43.0/24No ROA covers it. Add a ROA for AS61005, maxLength 24.652 of 673
Route object: none83.223.43.0/24Route objects for it name AS60679. Add a route object with origin AS61005 in the RIR database for the space.652 of 673
ROA: none80.80.80.0/24No ROA covers it. Add a ROA for AS61005, maxLength 24.670 of 673
ROA: none80.80.81.0/24No ROA covers it. Add a ROA for AS61005, maxLength 24.670 of 673
ROA: none2a04:1b00:80::/48No ROA covers it. Add a ROA for AS61005, maxLength 48.636 of 636
ROA: none2a04:1b00:81::/48No ROA covers it. Add a ROA for AS61005, maxLength 48.636 of 636

Route objects not announced

Route objects with origin AS61005 whose prefix no peer sees AS61005 announce. Many are kept on purpose (backup routes, space announced only in some places).

185.21.168.0/24NTTCOM, REACH, RIPENo ROA
185.21.169.0/24NTTCOM, REACH, RIPENo ROA
2a04:1b00::/48RIPENo ROA
2a04:1b00:1::/48RIPENo ROA
2a04:1b00:4::/48RIPENo ROA
2a04:1b00:5::/48RIPENo ROA
2a04:1b00:8::/48RIPENo ROA
2a04:1b00:9::/48RIPENo ROA
2a04:1b00:c::/48RADB, RIPENo ROA
2a04:1b00:d::/48RADB, RIPENo ROA
2a04:1b00:10::/48RADB, RIPENo ROA
2a04:1b00:11::/48RADB, RIPENo ROA

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.