bgpreport

Network · data from 2026-11-12

AS11325 AS11325 - Altus Communications Inc.

Registry name: AS11325 - Altus Communications Inc., US · not in PeeringDB

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

Announced routes

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

154.36.80.0/22 No ROA Other IRR onlyRADB 2 0%low visibility 2
154.37.64.0/22 No ROA Other IRR onlyRADB 2 0%low visibility 2
204.217.202.0/23 No ROA Other IRR onlyRADB 2 0%low visibility 2
204.217.204.0/23 No ROA Other IRR onlyRADB 2 0%low visibility 2
45.80.96.0/22 Valid RIR databaseRADB, RIPE 672 100% 67
142.228.124.0/23 Valid RIR databaseRIPE 672 100% 67
142.228.128.0/23 Valid RIR databaseRIPE 672 100% 67
198.33.108.0/22 Valid RIR databaseRIPE 672 100% 67
198.33.124.0/22 Valid RIR databaseRIPE 672 100% 67
64.79.224.0/19 Valid RIR databaseARIN 671 100% 67

AS-SET

AS11325 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 20 are in fix.csv.

  • ROA: none4
  • Route object: RIR4
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
ROA: none154.36.80.0/22No ROA covers it. Add a ROA for AS11325, maxLength 22.2 of 673
Route object: RIR154.36.80.0/22Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none154.37.64.0/22No ROA covers it. Add a ROA for AS11325, maxLength 22.2 of 673
Route object: RIR154.37.64.0/22Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none204.217.202.0/23No ROA covers it. Add a ROA for AS11325, maxLength 23.2 of 673
Route object: RIR204.217.202.0/23Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none204.217.204.0/23No ROA covers it. Add a ROA for AS11325, maxLength 23.2 of 673
Route object: RIR204.217.204.0/23Route object only in RADB. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

64.79.248.0/24ARINValid
104.251.81.0/24ARIN, RADBValid
167.100.97.0/24ARINInvalid: origin
167.100.108.0/22ARINInvalid: origin
168.91.112.0/22ARINInvalid: origin
172.84.176.0/20ARINNo ROA
172.102.196.0/24ARINInvalid: origin
172.102.212.0/24ARINInvalid: origin
204.217.145.0/24ARINNo ROA
204.217.146.0/23ARINNo ROA
206.232.47.0/24ARINNo ROA
206.232.48.0/23ARINNo ROA

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.