bgpreport

Network · data from 2026-11-12

AS45530 AGODA-AS-AP - Agoda Company Pte. Ltd.

Registry name: AGODA-AS-AP - Agoda Company Pte. Ltd., TH · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS45530, 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.
45.113.60.0/23 No ROA Other IRR onlyNTTCOM 673 100% 67
103.6.182.0/23 No ROA Other IRR onlyNTTCOM 673 100% 67
103.23.246.0/24 No ROA Other IRR onlyRADB 673 100% 67
103.43.136.0/24 No ROA Other IRR onlyNTTCOM, RADB 673 100% 68
202.94.90.0/23 No ROA Other IRR onlyNTTCOM 673 100% 67
203.160.137.0/24 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67
103.200.108.0/23 No ROA Other IRR onlyNTTCOM 671 100% 67
65.181.114.0/23 Valid RIR databaseAPNIC 673 100% 67
58.137.65.0/24 Valid RIR databaseAPNIC, RADB 672 100% 66

AS-SET

AS45530 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 23 are in fix.csv.

  • ROA: none7
  • Route object: RIR7
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none45.113.60.0/23No ROA covers it. Add a ROA for AS45530, maxLength 23.673 of 673
Route object: RIR45.113.60.0/23Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none103.6.182.0/23No ROA covers it. Add a ROA for AS45530, maxLength 23.673 of 673
Route object: RIR103.6.182.0/23Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none103.23.246.0/24No ROA covers it. Add a ROA for AS45530, maxLength 24.673 of 673
Route object: RIR103.23.246.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none103.43.136.0/24No ROA covers it. Add a ROA for AS45530, maxLength 24.673 of 673
Route object: RIR103.43.136.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none202.94.90.0/23No ROA covers it. Add a ROA for AS45530, maxLength 23.673 of 673
Route object: RIR202.94.90.0/23Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none203.160.137.0/24No ROA covers it. Add a ROA for AS45530, maxLength 24.673 of 673
Route object: RIR203.160.137.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none103.200.108.0/23No ROA covers it. Add a ROA for AS45530, maxLength 23.671 of 673
Route object: RIR103.200.108.0/23Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

45.113.60.0/24NTTCOMNo ROA
45.113.61.0/24NTTCOMNo ROA
65.181.114.0/24APNICValid
65.181.115.0/24APNICValid
103.6.182.0/24RADBNo ROA
103.6.183.0/24RADBNo ROA
202.84.90.0/23NTTCOMNo ROA
202.84.90.0/24NTTCOMNo ROA
202.84.91.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.