bgpreport

Network · data from 2026-11-12

AS23729 Alo Communications

Registry name: ALO-AS-AP - Alo Communications limited, BD · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS23729, 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.
10.61.206.0/24 bogon No ROA None 0 0%low visibility 1
10.61.207.0/24 bogon No ROA None 0 0%low visibility 1
103.29.239.0/24 Valid RIR databaseAPNIC 673 100% 69
118.179.6.0/24 Valid RIR databaseAPNIC 673 100% 68
103.100.92.0/24 Valid RIR databaseAPNIC 672 100% 68
103.100.93.0/24 Valid RIR databaseAPNIC 672 100% 67
103.100.94.0/24 Valid RIR databaseAPNIC 672 100% 67
103.100.95.0/24 Valid RIR databaseAPNIC 672 100% 67
118.179.0.0/24 Valid RIR databaseAPNIC 672 100% 67
118.179.1.0/24 Valid RIR databaseAPNIC 672 100% 67
118.179.2.0/24 Valid RIR databaseAPNIC 672 100% 67
118.179.3.0/24 Valid RIR databaseAPNIC 672 100% 67
118.179.4.0/24 Valid RIR databaseAPNIC 672 100% 67
118.179.5.0/24 Valid RIR databaseAPNIC 672 100% 67
118.179.7.0/24 Valid RIR databaseAPNIC 672 100% 67
2401:bac0::/32 Valid RIR databaseAPNIC 44 7%low visibility 30

AS-SET

AS23729'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 10 are in fix.csv.

  • Bogon prefix2
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
Bogon prefix10.61.206.0/24In IANA's special-purpose registry: Private-Use (RFC 1918).0 of 673
Bogon prefix10.61.207.0/24In IANA's special-purpose registry: Private-Use (RFC 1918).0 of 673

Route objects not announced

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

103.100.92.0/22APNICValid
118.179.0.0/21APNICValid
118.179.0.0/22APNICValid
118.179.0.0/23APNICValid
118.179.2.0/23APNICValid
118.179.4.0/22APNICValid
118.179.4.0/23APNICValid
118.179.6.0/23APNICValid

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.