bgpreport

Network · data from 2026-11-12

AS132490 MBSM-AS-AP - Mbsm Enterprise

Registry name: MBSM-AS-AP - Mbsm Enterprise, BD · not in PeeringDB

9IPv4 routes 100.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
0No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
20Route objects not announced registered with origin AS132490, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS132490, 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.183.141.0/24 Valid RIR databaseAPNIC 672 100% 67
103.183.140.0/24 Valid RIR databaseAPNIC 671 100% 67
103.102.236.0/23 Valid RIR databaseAPNIC 666 99% 67
103.102.236.0/24 Valid RIR databaseAPNIC 666 99% 67
103.102.237.0/24 Valid RIR databaseAPNIC 666 99% 67
103.102.238.0/23 Valid RIR databaseAPNIC 666 99% 67
103.102.238.0/24 Valid RIR databaseAPNIC 666 99% 67
103.102.239.0/24 Valid RIR databaseAPNIC 666 99% 67
103.102.236.0/22 Valid RIR databaseAPNIC 665 99% 67
2001:df0:87c0::/48 Valid RIR databaseAPNIC 635 100% 69

AS-SET

AS132490 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.

  • Route object: not announced20

Route objects not announced

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

101.251.80.0/20NTTCOMNo ROA
101.251.96.0/20NTTCOMNo ROA
101.251.112.0/22NTTCOMNo ROA
101.251.116.0/22NTTCOMNo ROA
101.251.120.0/21NTTCOMNo ROA
103.17.120.0/22NTTCOMNo ROA
103.31.240.0/22NTTCOMNo ROA
103.231.84.0/22NTTCOMNo ROA
118.126.0.0/19NTTCOM, RADBNo ROA
118.126.0.0/24NTTCOM, RADBNo ROA
118.126.20.0/22RADBNo ROA
180.150.160.0/19NTTCOMNo ROA
180.150.160.0/23NTTCOM, RADBNo ROA
180.150.160.0/24NTTCOM, RADBNo ROA
210.16.140.0/22NTTCOM, RADBNo ROA
210.16.144.0/22NTTCOMNo ROA
2401:ebc0::/32APNICValid
2401:ebc0::/40APNICValid
2401:ebc0:100::/40APNICValid
2401:ebc0:ff00::/40APNICValid

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.