bgpreport

Network · data from 2026-11-12

AS45566 GSPL-AS-AP - Google Singapore Pte. Ltd.

Registry name: GSPL-AS-AP - Google Singapore Pte. Ltd., SG · not in PeeringDB

5IPv4 routes 100.0% RPKI valid · 100.0% with a route object
4IPv6 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
5Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS45566, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS45566, 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.
2620:0:1000::/40 Valid Other IRR onlyRADB 633 100% 69
2620:15c::/36 Valid Other IRR onlyRADB 633 100% 69
2a00:79e0::/32 Valid Other IRR onlyRADB 633 100% 69
89.207.228.0/24 Valid Other IRR onlyRADB 10 1%low visibility 8
89.207.231.0/24 Valid Other IRR onlyRADB 10 1%low visibility 8
104.135.253.0/24 Valid Other IRR onlyRADB 10 1%low visibility 8
104.135.254.0/24 Valid Other IRR onlyRADB 10 1%low visibility 8
185.25.28.0/23 Valid Other IRR onlyRADB 2 0%low visibility 2
2401:fa00::/32 Valid RIR databaseAPNIC, RADB 633 100% 69

AS-SET

AS45566 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 9 are in fix.csv.

  • Route object: RIR8
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: RIR2620:0:1000::/40Route object only in RADB. Add it in the RIR database for the space.633 of 636
Route object: RIR2620:15c::/36Route object only in RADB. Add it in the RIR database for the space.633 of 636
Route object: RIR2a00:79e0::/32Route object only in RADB. Add it in the RIR database for the space.633 of 636
Route object: RIR89.207.228.0/24Route object only in RADB. Add it in the RIR database for the space.10 of 673
Route object: RIR89.207.231.0/24Route object only in RADB. Add it in the RIR database for the space.10 of 673
Route object: RIR104.135.253.0/24Route object only in RADB. Add it in the RIR database for the space.10 of 673
Route object: RIR104.135.254.0/24Route object only in RADB. Add it in the RIR database for the space.10 of 673
Route object: RIR185.25.28.0/23Route object only in RADB. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

2620:15c:ffe::/48RADBValid

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.