bgpreport

Network · data from 2026-11-12

AS394082 GOOGLE-PEER - rootcloud LLC

Registry name: GOOGLE-PEER - rootcloud LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS394082, 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.

2a09:33c0::/29 No ROA Other origin only 633 100% 67
2a09:3440::/29 No ROA Other origin only 633 100% 67
2a09:72c0::/29 No ROA Other origin only 633 100% 67
2a09:d840::/29 No ROA Other origin only 633 100% 67
2a09:fe40::/29 No ROA Other origin only 633 100% 67

AS-SET

AS394082 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 14 are in fix.csv.

  • ROA: none5
  • Route object: none5
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none2a09:33c0::/29No ROA covers it. Add a ROA for AS394082, maxLength 29.633 of 636
Route object: none2a09:33c0::/29Route objects for it name AS46573, AS214264, AS399989. Add a route object with origin AS394082 in the RIR database for the space.633 of 636
ROA: none2a09:3440::/29No ROA covers it. Add a ROA for AS394082, maxLength 29.633 of 636
Route object: none2a09:3440::/29Route objects for it name AS46573, AS214264, AS399989. Add a route object with origin AS394082 in the RIR database for the space.633 of 636
ROA: none2a09:72c0::/29No ROA covers it. Add a ROA for AS394082, maxLength 29.633 of 636
Route object: none2a09:72c0::/29Route objects for it name AS46573, AS214264, AS399989. Add a route object with origin AS394082 in the RIR database for the space.633 of 636
ROA: none2a09:d840::/29No ROA covers it. Add a ROA for AS394082, maxLength 29.633 of 636
Route object: none2a09:d840::/29Route objects for it name AS46573, AS214264, AS399989. Add a route object with origin AS394082 in the RIR database for the space.633 of 636
ROA: none2a09:fe40::/29No ROA covers it. Add a ROA for AS394082, maxLength 29.633 of 636
Route object: none2a09:fe40::/29Route objects for it name AS46573, AS214264, AS399989. Add a route object with origin AS394082 in the RIR database for the space.633 of 636

Route objects not announced

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

23.146.200.0/24ARINNo ROA
23.181.176.0/24ARINNo ROA
66.118.4.0/22ARINNo ROA
2606:5440::/32ARINNo 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.