bgpreport

Network · data from 2026-11-12

AS151080 Asiatel Network

Registry name: ANL-AS-AP - Asiatel Network Limited, BD · PeeringDB

3IPv4 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
66Route objects not announced registered with origin AS151080, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS151080, 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.131.100.0/23 Valid RIR databaseAPNIC 673 100% 66
103.131.101.0/24 Valid RIR databaseAPNIC 673 100% 66
103.159.173.0/24 Valid RIR databaseAPNIC 673 100% 66

AS-SET

AS151080'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 66 are in fix.csv.

  • Route object: not announced66

Route objects not announced

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

103.131.100.0/24APNICValid
103.137.160.0/24APNICValid
2001:df1:c340::/48APNICValid
2001:df2:4340::/48APNICValid
2400:6ae0::/32APNICValid
2400:6ae0::/33APNICValid
2400:6ae0::/34APNICValid
2400:6ae0::/35APNICValid
2400:6ae0::/36APNICValid
2400:6ae0:1000::/36APNICValid
2400:6ae0:2000::/35APNICValid
2400:6ae0:2000::/36APNICValid
2400:6ae0:3000::/36APNICValid
2400:6ae0:4000::/34APNICValid
2400:6ae0:4000::/35APNICValid
2400:6ae0:4000::/36APNICValid
2400:6ae0:5000::/36APNICValid
2400:6ae0:6000::/35APNICValid
2400:6ae0:6000::/36APNICValid
2400:6ae0:7000::/36APNICValid
2400:6ae0:8000::/33APNICValid
2400:6ae0:8000::/34APNICValid
2400:6ae0:8000::/35APNICValid
2400:6ae0:8000::/36APNICValid
2400:6ae0:9000::/36APNICValid
2400:6ae0:a000::/35APNICValid
2400:6ae0:a000::/36APNICValid
2400:6ae0:b000::/36APNICValid
2400:6ae0:c000::/34APNICValid
2400:6ae0:c000::/35APNICValid
2400:6ae0:c000::/36APNICValid
2400:6ae0:d000::/36APNICValid
2400:6ae0:e000::/35APNICValid
2400:6ae0:e000::/36APNICValid
2400:6ae0:f000::/36APNICValid
2402:76c0::/32APNICValid
2402:76c0::/33APNICValid
2402:76c0::/34APNICValid
2402:76c0::/35APNICValid
2402:76c0::/36APNICValid
2402:76c0:1000::/36APNICValid
2402:76c0:2000::/35APNICValid
2402:76c0:2000::/36APNICValid
2402:76c0:3000::/36APNICValid
2402:76c0:4000::/34APNICValid
2402:76c0:4000::/35APNICValid
2402:76c0:4000::/36APNICValid
2402:76c0:5000::/36APNICValid
2402:76c0:6000::/35APNICValid
2402:76c0:6000::/36APNICValid
2402:76c0:7000::/36APNICValid
2402:76c0:8000::/33APNICValid
2402:76c0:8000::/34APNICValid
2402:76c0:8000::/35APNICValid
2402:76c0:8000::/36APNICValid
2402:76c0:9000::/36APNICValid
2402:76c0:a000::/35APNICValid
2402:76c0:a000::/36APNICValid
2402:76c0:b000::/36APNICValid
2402:76c0:c000::/34APNICValid
2402:76c0:c000::/35APNICValid
2402:76c0:c000::/36APNICValid
2402:76c0:d000::/36APNICValid
2402:76c0:e000::/35APNICValid
2402:76c0:e000::/36APNICValid
2402:76c0:f000::/36APNICValid

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.