bgpreport

Network · data from 2026-11-12

AS25176 AC-Net Externservice

Registry name: AC-NET AC-Net AB, SE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS25176, 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.
192.36.10.0/24 No ROA RIR databaseRIPE 673 100% 66
84.244.192.0/18 No ROA RIR databaseRIPE 672 100% 66
192.36.40.0/24 No ROA RIR databaseRIPE 672 100% 66
192.121.141.0/24 No ROA RIR databaseRIPE 672 100% 66
192.121.142.0/23 No ROA RIR databaseRIPE 672 100% 66
192.165.169.0/24 No ROA RIR databaseRIPE 672 100% 66
193.180.128.0/19 No ROA RIR databaseRIPE 672 100% 66
193.234.253.0/24 No ROA RIR databaseRIPE 672 100% 66
213.199.64.0/18 No ROA RIR databaseRIPE 672 100% 66
92.39.0.0/20 Valid RIR databaseRIPE 673 100% 66
95.140.64.0/20 Valid RIR databaseRIPE 673 100% 66
193.254.4.0/22 Valid RIR databaseRIPE 673 100% 66
194.69.6.0/23 Valid RIR databaseRIPE 673 100% 66
194.69.8.0/21 Valid RIR databaseRIPE 673 100% 66
194.153.32.0/19 Valid RIR databaseRIPE 673 100% 66
194.153.64.0/21 Valid RIR databaseRIPE 673 100% 66
80.88.96.0/19 Valid RIR databaseRIPE 672 100% 66
81.8.128.0/17 Valid RIR databaseRIPE 672 100% 66
85.194.128.0/18 Valid RIR databaseRIPE 672 100% 66
185.80.208.0/22 Valid RIR databaseRIPE 672 100% 66
193.10.32.0/24 Valid RIR databaseRIPE 672 100% 66
81.8.204.0/24 Valid RIR databaseRIPE 671 100% 66
81.8.226.0/24 Valid RIR databaseRIPE 671 100% 66
2a00:1718::/32 Valid RIR databaseRIPE 636 100% 69
2a01:4040::/32 Valid RIR databaseRIPE 636 100% 69
2a03:7c80::/32 Valid RIR databaseRIPE 635 100% 69

AS-SET

AS25176'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 9 are in fix.csv.

  • ROA: none9
ChangePrefix or setDetailFull-table peers
ROA: none192.36.10.0/24No ROA covers it. Add a ROA for AS25176, maxLength 24.673 of 673
ROA: none84.244.192.0/18No ROA covers it. Add a ROA for AS25176, maxLength 18.672 of 673
ROA: none192.36.40.0/24No ROA covers it. Add a ROA for AS25176, maxLength 24.672 of 673
ROA: none192.121.141.0/24No ROA covers it. Add a ROA for AS25176, maxLength 24.672 of 673
ROA: none192.121.142.0/23No ROA covers it. Add a ROA for AS25176, maxLength 23.672 of 673
ROA: none192.165.169.0/24No ROA covers it. Add a ROA for AS25176, maxLength 24.672 of 673
ROA: none193.180.128.0/19No ROA covers it. Add a ROA for AS25176, maxLength 19.672 of 673
ROA: none193.234.253.0/24No ROA covers it. Add a ROA for AS25176, maxLength 24.672 of 673
ROA: none213.199.64.0/18No ROA covers it. Add a ROA for AS25176, maxLength 18.672 of 673

Route objects not announced

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