bgpreport

Network · data from 2026-11-12

AS23893 Bangla Phone

Registry name: BPL-BD - Bangla Phone Ltd, BD · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS23893, 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.

180.210.128.0/24 Valid RIR databaseAPNIC 672 100% 67
180.210.129.0/24 Valid RIR databaseAPNIC 672 100% 67
180.210.130.0/24 Valid RIR databaseAPNIC 672 100% 67
180.210.131.0/24 Valid RIR databaseAPNIC 672 100% 67
180.210.135.0/24 Valid RIR databaseAPNIC 672 100% 67
180.210.150.0/24 Valid RIR databaseAPNIC 672 100% 67
180.210.151.0/24 Valid RIR databaseAPNIC 672 100% 67

AS-SET

AS23893's PeeringDB record names no 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 41 are in fix.csv.

  • Route object: not announced41

Route objects not announced

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

180.210.128.0/19APNICValid
180.210.128.0/23APNICValid
180.210.130.0/23APNICValid
180.210.133.0/24APNICValid
180.210.134.0/23APNICValid
180.210.134.0/24APNICValid
180.210.136.0/23APNICValid
180.210.136.0/24APNICValid
180.210.137.0/24APNICValid
180.210.138.0/23APNICValid
180.210.138.0/24APNICValid
180.210.139.0/24APNICValid
180.210.140.0/23APNICValid
180.210.140.0/24APNICValid
180.210.141.0/24APNICValid
180.210.142.0/23APNICValid
180.210.142.0/24APNICValid
180.210.143.0/24APNICValid
180.210.144.0/23APNICValid
180.210.144.0/24APNICValid
180.210.145.0/24APNICValid
180.210.146.0/23APNICValid
180.210.146.0/24APNICValid
180.210.147.0/24APNICValid
180.210.148.0/23APNICValid
180.210.148.0/24APNICValid
180.210.149.0/24APNICValid
180.210.150.0/23APNICValid
180.210.152.0/23APNICValid
180.210.152.0/24APNICValid
180.210.153.0/24APNICValid
180.210.154.0/23APNICValid
180.210.154.0/24APNICValid
180.210.155.0/24APNICValid
180.210.156.0/23APNICValid
180.210.156.0/24APNICValid
180.210.157.0/24APNICValid
180.210.158.0/23APNICValid
180.210.158.0/24APNICValid
180.210.159.0/24APNICValid
2404:b00::/32APNICValid

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.