bgpreport

Network · data from 2026-11-12

AS149421 PADMA ONLINE

Registry name: PADMAONLINE-AS-AP - PADMA ONLINE, BD · PeeringDB

6IPv4 routes 83.3% RPKI valid · 83.3% with a route object
2IPv6 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
2Route objects not announced registered with origin AS149421, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS149421, 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.
163.52.25.0/24 Invalid: origin Other origin only 0 0%low visibility 1
157.10.175.0/24 Valid RIR databaseAPNIC 673 100% 69
103.179.25.0/24 Valid RIR databaseAPNIC 672 100% 67
160.20.121.0/24 Valid RIR databaseAPNIC 671 100% 69
202.50.113.0/24 Valid RIR databaseAPNIC 671 100% 69
103.179.24.0/24 Valid RIR databaseAPNIC 669 99% 68
2402:35a0::/32 Valid RIR databaseAPNIC 635 100% 70
2001:df0:4540::/48 Valid RIR databaseAPNIC 634 100% 70

AS-SET

AS149421'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 4 are in fix.csv.

  • ROA: origin1
  • Route object: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin163.52.25.0/24ROAs covering it name AS153528, not AS149421. If AS149421 should announce it, add a ROA for AS149421.0 of 673
Route object: none163.52.25.0/24Route objects for it name AS153528. Add a route object with origin AS149421 in the RIR database for the space.0 of 673

Route objects not announced

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

103.179.24.0/23APNICValid
2402:35a0:1::/48APNICValid

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.