bgpreport

Network · data from 2026-11-12

AS45477 APTRANSIT-SG - AP TRANSIT PTE LTD

Registry name: APTRANSIT-SG - AP TRANSIT PTE LTD, SG · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS45477, 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.
103.153.245.0/24 No ROA Other IRR onlyRADB 671 100% 66
113.29.224.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, REACH 671 100% 66
113.29.225.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, REACH 671 100% 66
113.29.227.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, REACH 671 100% 66
113.29.234.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, REACH 671 100% 66
113.29.235.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, REACH 671 100% 66
113.29.236.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, REACH 671 100% 66
113.29.237.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, REACH 671 100% 66
113.29.238.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, REACH 671 100% 66
113.29.239.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, REACH 671 100% 66
2406:fc00::/32 Valid RIR databaseAPNIC 636 100% 69

AS-SET

AS45477 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 20 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced18
ChangePrefix or setDetailFull-table peers
ROA: none103.153.245.0/24No ROA covers it. Add a ROA for AS45477, maxLength 24.671 of 673
Route object: RIR103.153.245.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

103.17.32.0/24REACHInvalid: origin
113.29.224.0/20NTTCOM, RADBNo ROA
113.29.224.0/21NTTCOM, RADBNo ROA
113.29.224.0/22NTTCOM, RADBNo ROA
113.29.224.0/23NTTCOM, RADBNo ROA
113.29.226.0/23NTTCOM, RADBNo ROA
113.29.228.0/22NTTCOM, RADBNo ROA
113.29.228.0/23NTTCOM, RADBNo ROA
113.29.230.0/23NTTCOM, RADBNo ROA
113.29.232.0/21NTTCOM, RADBNo ROA
113.29.232.0/22NTTCOM, RADBNo ROA
113.29.232.0/23NTTCOM, RADBNo ROA
113.29.234.0/23NTTCOM, RADBNo ROA
113.29.236.0/22NTTCOM, RADBNo ROA
113.29.236.0/23NTTCOM, RADBNo ROA
113.29.238.0/23NTTCOM, RADBNo ROA
202.55.150.0/24NTTCOMNo ROA
202.55.153.0/24NTTCOMNo ROA

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.