bgpreport

Network · data from 2026-11-12

AS139070 Google Cloud Korea

Registry name: GOOGLE-AS-AP - Google Asia Pacific Pte. Ltd., SG · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS139070, 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.
57.140.230.0/24 Valid None 16 2%low visibility 11
34.64.0.0/16 Valid Other IRR onlyRADB 671 100% 69
34.116.0.0/20 Valid Other IRR onlyRADB 671 100% 69
35.203.224.0/23 Valid Other IRR onlyRADB 671 100% 69
2404:f340::/34 Valid Other IRR onlyRADB 634 100% 69
34.0.96.0/19 Valid Other IRR onlyRADB 18 3%low visibility 12
34.4.128.0/18 Valid Other IRR onlyRADB 18 3%low visibility 12
34.190.24.0/21 Valid Other IRR onlyRADB 18 3%low visibility 12
35.216.0.0/17 Valid Other IRR onlyRADB 18 3%low visibility 12
34.1.86.0/24 Valid Other IRR onlyRADB 16 2%low visibility 12
57.140.227.0/24 Valid Other IRR onlyRADB 16 2%low visibility 12
66.22.228.0/24 Valid Other IRR onlyRADB 16 2%low visibility 12
66.22.229.0/24 Valid Other IRR onlyRADB 16 2%low visibility 12
152.65.246.0/24 Valid RIR databaseAPNIC, RADB 16 2%low visibility 12

AS-SET

AS139070'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 17 are in fix.csv.

  • Route object: none1
  • Route object: RIR12
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
Route object: none57.140.230.0/24No route object for it. Add a route object with origin AS139070 in the RIR database for the space.16 of 673
Route object: RIR34.64.0.0/16Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR34.116.0.0/20Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR35.203.224.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2404:f340::/34Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR34.0.96.0/19Route object only in RADB. Add it in the RIR database for the space.18 of 673
Route object: RIR34.4.128.0/18Route object only in RADB. Add it in the RIR database for the space.18 of 673
Route object: RIR34.190.24.0/21Route object only in RADB. Add it in the RIR database for the space.18 of 673
Route object: RIR35.216.0.0/17Route object only in RADB. Add it in the RIR database for the space.18 of 673
Route object: RIR34.1.86.0/24Route object only in RADB. Add it in the RIR database for the space.16 of 673
Route object: RIR57.140.227.0/24Route object only in RADB. Add it in the RIR database for the space.16 of 673
Route object: RIR66.22.228.0/24Route object only in RADB. Add it in the RIR database for the space.16 of 673
Route object: RIR66.22.229.0/24Route object only in RADB. Add it in the RIR database for the space.16 of 673

Route objects not announced

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

57.140.168.0/24ARINValid
57.140.171.0/24ARINValid
66.22.228.0/23RIPEValid
2600:1902:60::/44RADBValid

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.