bgpreport

Network · data from 2026-11-12

AS16550 Google Private Cloud

Registry name: GOOGLE-PRIVATE-CLOUD - Google LLC, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS16550, 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.
208.54.46.0/24 Invalid: origin Other origin only 24 4%low visibility 20
208.54.48.0/24 Invalid: origin Other origin only 24 4%low visibility 20
208.54.50.0/24 Invalid: origin Other origin only 24 4%low visibility 20
35.199.192.0/19 No ROA Other origin only 1 0%low visibility 1
200.107.8.0/24 Valid Other origin onlycovered by 200.107.0.0/18 671 100% 67
200.107.30.0/24 Valid Other origin onlycovered by 200.107.0.0/18 671 100% 67
151.207.24.0/24 Valid RIR databaseARIN 671 100% 68
151.207.26.0/24 Valid RIR databaseARIN 671 100% 68
137.75.122.0/24 Valid RIR databaseARIN 667 99% 68

AS-SET

AS16550's PeeringDB record names no 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 11 are in fix.csv.

  • ROA: origin3
  • ROA: none1
  • Route object: none6
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin208.54.46.0/24ROAs covering it name AS21928, not AS16550. If AS16550 should announce it, add a ROA for AS16550.24 of 673
Route object: none208.54.46.0/24Route objects for it name AS21928. Add a route object with origin AS16550 in the RIR database for the space.24 of 673
ROA: origin208.54.48.0/24ROAs covering it name AS21928, not AS16550. If AS16550 should announce it, add a ROA for AS16550.24 of 673
Route object: none208.54.48.0/24Route objects for it name AS21928. Add a route object with origin AS16550 in the RIR database for the space.24 of 673
ROA: origin208.54.50.0/24ROAs covering it name AS21928, not AS16550. If AS16550 should announce it, add a ROA for AS16550.24 of 673
Route object: none208.54.50.0/24Route objects for it name AS21928. Add a route object with origin AS16550 in the RIR database for the space.24 of 673
ROA: none35.199.192.0/19No ROA covers it. Add a ROA for AS16550, maxLength 19.1 of 673
Route object: none35.199.192.0/19Route objects for it name AS15169. Add a route object with origin AS16550 in the RIR database for the space.1 of 673
Route object: none200.107.8.0/24Route objects for it name AS15169, AS396982. A route object for 200.107.0.0/18 with origin AS16550 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16550 in the RIR database for the space.671 of 673
Route object: none200.107.30.0/24Route objects for it name AS396982. A route object for 200.107.0.0/18 with origin AS16550 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16550 in the RIR database for the space.671 of 673

Route objects not announced

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

200.107.0.0/18LACNICValid

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.