bgpreport

Network · data from 2026-11-12

AS132092 ITBASE-AS-AP - Mir Mosharrof Hossain t/a IT Base

Registry name: ITBASE-AS-AP - Mir Mosharrof Hossain t/a IT Base, BD · not in PeeringDB

10IPv4 routes 100.0% RPKI valid · 100.0% with a route object
17IPv6 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
18Route objects not announced registered with origin AS132092, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS132092, 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.70.141.0/24 Valid RIR databaseAPNIC 673 100% 67
103.70.142.0/24 Valid RIR databaseAPNIC 673 100% 67
182.54.152.0/24 Valid RIR databaseAPNIC 673 100% 67
182.54.153.0/24 Valid RIR databaseAPNIC 673 100% 67
182.54.155.0/24 Valid RIR databaseAPNIC 673 100% 67
103.70.140.0/22 Valid RIR databaseAPNIC 672 100% 67
103.70.140.0/24 Valid RIR databaseAPNIC 672 100% 67
103.70.143.0/24 Valid RIR databaseAPNIC 672 100% 67
182.54.152.0/22 Valid RIR databaseAPNIC 672 100% 67
182.54.154.0/24 Valid RIR databaseAPNIC 672 100% 67
2406:c80::/32 Valid RIR databaseAPNIC 635 100% 69
2406:c80::/36 Valid RIR databaseAPNIC 635 100% 69
2406:c80:1000::/36 Valid RIR databaseAPNIC 635 100% 69
2406:c80:2000::/36 Valid RIR databaseAPNIC 635 100% 69
2406:c80:3000::/36 Valid RIR databaseAPNIC 635 100% 69
2406:c80:4000::/36 Valid RIR databaseAPNIC 635 100% 69
2406:c80:5000::/36 Valid RIR databaseAPNIC 635 100% 69
2406:c80:6000::/36 Valid RIR databaseAPNIC 635 100% 69
2406:c80:7000::/36 Valid RIR databaseAPNIC 635 100% 69
2406:c80:8000::/36 Valid RIR databaseAPNIC 635 100% 69
2406:c80:9000::/36 Valid RIR databaseAPNIC 635 100% 69
2406:c80:a000::/36 Valid RIR databaseAPNIC 635 100% 69
2406:c80:b000::/36 Valid RIR databaseAPNIC 635 100% 69
2406:c80:c000::/36 Valid RIR databaseAPNIC 635 100% 69
2406:c80:d000::/36 Valid RIR databaseAPNIC 635 100% 69
2406:c80:e000::/36 Valid RIR databaseAPNIC 635 100% 69
2406:c80:f000::/36 Valid RIR databaseAPNIC 635 100% 69

AS-SET

AS132092 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 18 are in fix.csv.

  • Route object: not announced18

Route objects not announced

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

103.70.140.0/23APNICValid
103.70.142.0/23APNICValid
182.54.152.0/23APNICValid
182.54.154.0/23APNICValid
2406:c80::/33APNICValid
2406:c80::/34APNICValid
2406:c80::/35APNICValid
2406:c80:2000::/35APNICValid
2406:c80:4000::/34APNICValid
2406:c80:4000::/35APNICValid
2406:c80:6000::/35APNICValid
2406:c80:8000::/33APNICValid
2406:c80:8000::/34APNICValid
2406:c80:8000::/35APNICValid
2406:c80:a000::/35APNICValid
2406:c80:c000::/34APNICValid
2406:c80:c000::/35APNICValid
2406:c80:e000::/35APNICValid

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.