bgpreport

Network · data from 2026-11-12

AS205157 CIDNOC Daniel Cid

Registry name: CIDNOC Daniel Cid, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS205157, 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.
76.76.0.0/24 Valid Other IRR onlyRADB 671 100% 66
76.76.1.0/24 Valid Other IRR onlyRADB 671 100% 66
185.70.162.0/24 Valid Other IRR onlyRADB 671 100% 66
2a0d:2a00:c0::/48 Valid Other IRR onlyRADB 634 100% 70
2a0d:2a00:ab1::/48 Valid Other IRR onlyRADB 634 100% 70
2a0d:2a00:ab2::/48 Valid Other IRR onlyRADB 634 100% 70
185.228.168.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
185.228.169.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
185.228.170.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
185.228.171.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
2a0d:2a00:1::/48 Valid RIR databaseRADB, RIPE 635 100% 70
2a0d:2a00:2::/48 Valid RIR databaseRADB, RIPE 635 100% 70

AS-SET

AS205157 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 8 are in fix.csv.

  • Route object: RIR6
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: RIR76.76.0.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR76.76.1.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR185.70.162.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2a0d:2a00:c0::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2a0d:2a00:ab1::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2a0d:2a00:ab2::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

76.76.0.0/23RADBNo ROA
185.70.163.0/24RADBNo 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.