bgpreport

Network · data from 2026-11-12

AS196865 Aircomm S.r.l.

Registry name: AIRCOMM Aircomm S.r.L., IT · PeeringDB

5IPv4 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
29Route objects not announced registered with origin AS196865, seen from no peer

Announced routes

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

109.232.136.0/21 Valid RIR databaseRIPE 673 100% 67
178.19.160.0/21 Valid RIR databaseRIPE 673 100% 67
178.19.168.0/22 Valid RIR databaseRIPE 673 100% 67
185.75.108.0/22 Valid RIR databaseRIPE 673 100% 67
185.142.168.0/22 Valid RIR databaseRIPE 673 100% 67

AS-SET

PeeringDB's irr_as_set for AS196865: AS-MICROSERVIZIAIRCOMM. 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 (AS196865 isn't in the set, or no route object for AS196865 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 objectsAS196865 in itNot covered
AS-MICROSERVIZIAIRCOMM RIPE 41134 Yes 0

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

  • Route object: not announced29

Route objects not announced

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

109.232.136.0/24RIPEValid
109.232.137.0/24RIPEValid
109.232.138.0/24RIPEValid
109.232.139.0/24RIPEValid
109.232.140.0/24RIPEValid
109.232.141.0/24RIPEValid
109.232.142.0/24RIPEValid
109.232.143.0/24RIPEValid
178.19.160.0/24RIPEValid
178.19.161.0/24RIPEValid
178.19.162.0/24RIPEValid
178.19.163.0/24RIPEValid
178.19.164.0/24RIPEValid
178.19.165.0/24RIPEValid
178.19.166.0/24RIPEValid
178.19.167.0/24RIPEValid
178.19.168.0/24RIPEValid
178.19.169.0/24RIPEValid
178.19.170.0/24RIPEValid
178.19.171.0/24RIPEValid
185.75.108.0/24RIPEValid
185.75.109.0/24RIPEValid
185.75.110.0/24RIPEValid
185.75.111.0/24RIPEValid
185.142.168.0/24RIPEValid
185.142.169.0/24RIPEValid
185.142.170.0/24RIPEValid
185.142.171.0/24RIPEValid
2a00:9ca0::/32RIPENo 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.