bgpreport

Network · data from 2026-11-12

AS140222 APNA-AS-AP - Apna Network

Registry name: APNA-AS-AP - Apna Network, BD · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS140222, 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.127.95.0/24 Invalid: origin Other origin only 12 2%low visibility 8
103.144.104.0/24 Valid RIR databaseAPNIC 673 100% 69
157.20.57.0/24 Valid RIR databaseAPNIC 673 100% 69
2001:df1:bc80::/48 Valid RIR databaseAPNIC 636 100% 69

AS-SET

AS140222 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 2 are in fix.csv.

  • ROA: origin1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: origin103.127.95.0/24ROAs covering it name AS150774, not AS140222. If AS140222 should announce it, add a ROA for AS140222.12 of 673
Route object: none103.127.95.0/24Route objects for it name AS138509, AS150774. Add a route object with origin AS140222 in the RIR database for the space.12 of 673

Route objects not announced

Every route object with origin AS140222 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.