bgpreport

Network · data from 2026-11-12

AS45121 EMS-AS-AP - Enterprise Managed Services Sdn. Bhd.

Registry name: EMS-AS-AP - Enterprise Managed Services Sdn. Bhd., MY · not in PeeringDB

12IPv4 routes 100.0% RPKI valid · 91.7% 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
4Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS45121, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS45121, 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.133.110.0/23 Valid Other origin onlycovered by 202.133.108.0/22 2 0%low visibility 2
202.133.111.0/24 Valid Other IRR onlyNTTCOM, RADB, REACH 672 100% 66
202.133.108.0/23 Valid Other IRR onlyREACH 2 0%low visibility 2
27.131.62.0/23 Valid RIR databaseAPNIC, RADB 672 100% 66
27.131.62.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, REACH 672 100% 66
27.131.63.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 66
103.221.63.0/24 Valid RIR databaseAPNIC 672 100% 66
122.0.31.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, REACH, RIPE-NONAUTH 672 100% 66
202.133.108.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, REACH 672 100% 66
202.133.109.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, REACH 672 100% 66
202.133.110.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, REACH 672 100% 66
202.133.108.0/22 Valid RIR databaseAPNIC, REACH 2 0%low visibility 2
2405:6400:4000::/36 Valid RIR databaseAPNIC, RADB 1 0%low visibility 1

AS-SET

AS45121 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 3 are in fix.csv.

  • Route object: none1
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
Route object: none202.133.110.0/23Route objects for it name AS23678. A route object for 202.133.108.0/22 with origin AS45121 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45121 in the RIR database for the space.2 of 673
Route object: RIR202.133.111.0/24Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.672 of 673
Route object: RIR202.133.108.0/23Route object only in REACH. Add it in the RIR database for the space.2 of 673

Route objects not announced

Every route object with origin AS45121 is announced.

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.