bgpreport

Network · data from 2026-11-12

AS36384 GOOGLE-IT - Google LLC

Registry name: GOOGLE-IT - Google LLC, US · not in PeeringDB

4IPv4 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
6Low visibility seen by under 10% of full-table peers
16Route objects not announced registered with origin AS36384, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS36384, 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.
104.132.0.0/14 Valid Other IRR onlyRADB, RIPE-NONAUTH 669 99% 69
104.132.254.0/24 Valid Other IRR onlyRADB 669 99% 69
89.207.229.0/24 Valid Other IRR onlyRADB 11 2%low visibility 9
89.207.224.0/24 Valid Other IRR onlyRADB 10 1%low visibility 8
2a00:79e1:800::/42 Valid Other IRR onlyRADB 2 0%low visibility 2
2a00:79e1:abc::/46 Valid Other IRR onlyRADB 2 0%low visibility 2
2a00:79e1:f00::/40 Valid Other IRR onlyRADB 2 0%low visibility 2
2a00:79e1:f000::/38 Valid Other IRR onlyRADB 1 0%low visibility 1
2a00:79e1::/32 Valid RIR databaseRADB, RIPE 633 100% 69

AS-SET

AS36384 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 24 are in fix.csv.

  • Route object: RIR8
  • Route object: not announced16
ChangePrefix or setDetailFull-table peers
Route object: RIR104.132.0.0/14Route object only in RADB, RIPE-NONAUTH. Add it in the RIR database for the space.669 of 673
Route object: RIR104.132.254.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR89.207.229.0/24Route object only in RADB. Add it in the RIR database for the space.11 of 673
Route object: RIR89.207.224.0/24Route object only in RADB. Add it in the RIR database for the space.10 of 673
Route object: RIR2a00:79e1:800::/42Route object only in RADB. Add it in the RIR database for the space.2 of 636
Route object: RIR2a00:79e1:abc::/46Route object only in RADB. Add it in the RIR database for the space.2 of 636
Route object: RIR2a00:79e1:f00::/40Route object only in RADB. Add it in the RIR database for the space.2 of 636
Route object: RIR2a00:79e1:f000::/38Route object only in RADB. Add it in the RIR database for the space.1 of 636

Route objects not announced

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

89.207.224.0/21RADBNo ROA
89.207.224.0/23RADBNo ROA
89.207.225.0/24RADBNo ROA
89.207.226.0/23RADBNo ROA
89.207.226.0/24RADBNo ROA
89.207.227.0/24RADBNo ROA
89.207.228.0/23RADBNo ROA
89.207.230.0/23RADBNo ROA
89.207.230.0/24RADBNo ROA
136.126.0.0/15RADBValid
185.25.28.0/22RADBNo ROA
185.25.30.0/23RADBNo ROA
185.25.31.0/24RADBNo ROA
193.200.222.0/24RADBNo ROA
2a00:79e0::/31RIPEInvalid: origin
2a00:79e0::/32RIPEInvalid: origin

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.