bgpreport

Network · data from 2026-11-12

AS40994 Alwyzon

Registry name: Alwyzon Hohl IT e.U., AT · PeeringDB

26IPv4 routes 96.2% RPKI valid · 96.2% with a route object
1IPv6 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
3Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS40994, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS40994, 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.
132.243.245.0/24 Invalid: origin Other origin only 2 0%low visibility 2
9.247.43.0/24 Valid RIR databaseRIPE 673 100% 67
46.102.156.0/24 Valid RIR databaseRIPE 673 100% 67
193.219.97.0/24 Valid RIR databaseRIPE 673 100% 67
203.98.67.0/24 Valid RIR databaseRIPE 673 100% 67
205.147.200.0/24 Valid RIR databaseRIPE 673 100% 67
46.37.113.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
31.14.17.0/24 Valid RIR databaseRIPE 671 100% 67
46.102.157.0/24 Valid RIR databaseRIPE 671 100% 67
83.138.55.0/24 Valid RIR databaseRIPE 671 100% 67
86.106.182.0/24 Valid RIR databaseRIPE 671 100% 67
86.106.183.0/24 Valid RIR databaseRIPE 671 100% 67
94.177.8.0/24 Valid RIR databaseRIPE 671 100% 67
94.177.9.0/24 Valid RIR databaseRIPE 671 100% 67
104.143.0.0/24 Valid RIR databaseRIPE 671 100% 67
104.143.1.0/24 Valid RIR databaseRIPE 671 100% 67
110.172.148.0/24 Valid RIR databaseRIPE 671 100% 67
203.34.137.0/24 Valid RIR databaseRIPE 671 100% 67
204.154.104.0/24 Valid RIR databaseRIPE 671 100% 67
204.154.105.0/24 Valid RIR databaseRIPE 671 100% 67
204.154.106.0/24 Valid RIR databaseRIPE 671 100% 67
204.154.107.0/24 Valid RIR databaseRIPE 671 100% 67
205.147.201.0/24 Valid RIR databaseRIPE 671 100% 67
163.245.59.0/24 Valid RIR databaseRIPE 670 100% 67
2a0d:f302::/32 Valid RIR databaseRIPE 636 100% 67
9.247.60.0/24 Valid RIR databaseRIPE 2 0%low visibility 1
163.245.58.0/24 Valid RIR databaseRIPE 2 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS40994: AS40994:AS-ALWYZON. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS40994 isn't in the set, or no route object for AS40994 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS40994 in itNot covered
AS40994:AS-ALWYZON RIPE 163565 Yes 1

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

  • ROA: origin1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: origin132.243.245.0/24ROAs covering it name AS218897, not AS40994. If AS40994 should announce it, add a ROA for AS40994.2 of 673
Route object: none132.243.245.0/24Route objects for it name AS218897. Add a route object with origin AS40994 in the RIR database for the space.2 of 673

Route objects not announced

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