bgpreport

Network · data from 2026-11-12

AS47735 NOWIRE-AS NOWIRE s.r.l.

Registry name: NOWIRE-AS NOWIRE s.r.l., IT · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS47735, 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.
185.168.172.0/24 Invalid: maxLength RIR databaseRIPE 9 1%low visibility 12
185.168.173.0/24 Valid RIR databaseRIPE 672 100% 66
185.168.174.0/24 Valid RIR databaseRIPE 672 100% 66
185.168.175.0/24 Valid RIR databaseRIPE 672 100% 66

AS-SET

AS47735 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: not announced1
ChangePrefix or setDetailFull-table peers
ROA: maxLength185.168.172.0/24ROA 185.168.172.0/22 AS47735 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 185.168.172.0/24.9 of 673

Route objects not announced

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

185.168.172.0/22RIPEValid

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.