bgpreport

Network · data from 2026-11-12

AS23732 SAGILITY-AS-AP - Sagility Philippines B.V. Branch Office

Registry name: SAGILITY-AS-AP - Sagility Philippines B.V. Branch Office, PH · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS23732, 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.
202.162.161.0/24 No ROA Other IRR onlyALTDB, NTTCOM, RADB 673 100% 66
202.162.169.0/24 No ROA Other IRR onlyALTDB, NTTCOM, RADB 673 100% 68
202.162.173.0/24 No ROA Other IRR onlyALTDB, NTTCOM, RADB 673 100% 66
202.162.160.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
202.162.163.0/24 Valid RIR databaseALTDB, APNIC, NTTCOM 673 100% 69
202.162.168.0/24 Valid RIR databaseALTDB, APNIC, NTTCOM, RADB 673 100% 66
202.162.174.0/24 Valid RIR databaseALTDB, APNIC, NTTCOM 673 100% 67
202.162.175.0/24 Valid RIR databaseALTDB, APNIC, NTTCOM 673 100% 69
202.162.164.0/24 Valid RIR databaseALTDB, APNIC, NTTCOM, RADB 671 100% 69

AS-SET

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

  • ROA: none3
  • Route object: RIR3
  • Route object: not announced11
ChangePrefix or setDetailFull-table peers
ROA: none202.162.161.0/24No ROA covers it. Add a ROA for AS23732, maxLength 24.673 of 673
Route object: RIR202.162.161.0/24Route object only in ALTDB, NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none202.162.169.0/24No ROA covers it. Add a ROA for AS23732, maxLength 24.673 of 673
Route object: RIR202.162.169.0/24Route object only in ALTDB, NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none202.162.173.0/24No ROA covers it. Add a ROA for AS23732, maxLength 24.673 of 673
Route object: RIR202.162.173.0/24Route object only in ALTDB, NTTCOM, RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

65.244.214.0/24RADBNo ROA
121.100.160.0/20ALTDBNo ROA
121.100.176.0/20ALTDBNo ROA
202.162.160.0/23RADBNo ROA
202.162.162.0/24ALTDBNo ROA
202.162.165.0/24ALTDBNo ROA
202.162.166.0/24ALTDBNo ROA
202.162.167.0/24ALTDBNo ROA
202.162.170.0/24ALTDBNo ROA
202.162.171.0/24ALTDBNo ROA
202.162.172.0/24ALTDB, APNIC, NTTCOMValid

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.