bgpreport

Network · data from 2026-11-12

AS42818 AXITEA Axitea S.p.A.

Registry name: AXITEA Axitea S.p.A., IT · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS42818, 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.
77.244.89.0/24 Invalid: maxLength Nonecovered by 77.244.80.0/20 14 2%low visibility 8
77.244.80.0/20 Valid RIR databaseRIPE 673 100% 67

AS-SET

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

  • ROA: maxLength1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: maxLength77.244.89.0/24ROA 77.244.80.0/20 AS42818 has maxLength 20; the route is a /24. Raise the maxLength, or add a ROA for 77.244.89.0/24.14 of 673
Route object: none77.244.89.0/24No route object for it. A route object for 77.244.80.0/20 with origin AS42818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42818 in the RIR database for the space.14 of 673

Route objects not announced

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