bgpreport

Network · data from 2026-11-12

AS28941 NOVA NETWORKS S.R.L.

Registry name: novanetworks NOVA NETWORKS S.R.L., IT · PeeringDB

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

Announced routes

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

149.100.172.0/22 No ROA Other IRR onlyRIPE-NONAUTH 670 100% 67
185.103.112.0/22 Valid RIR databaseRIPE 671 100% 67

AS-SET

PeeringDB's irr_as_set for AS28941: AS28941. 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 (AS28941 isn't in the set, or no route object for AS28941 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 objectsAS28941 in itNot covered
AS28941 A single AS number, not a set: AS28941 (this network), 10 route objects.

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

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none149.100.172.0/22No ROA covers it. Add a ROA for AS28941, maxLength 22.670 of 673
Route object: RIR149.100.172.0/22Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

149.100.172.0/24RIPE-NONAUTHNo ROA
149.100.173.0/24RIPE-NONAUTHNo ROA
149.100.174.0/24RIPE-NONAUTHNo ROA
149.100.175.0/24RIPE-NONAUTHNo ROA
185.103.112.0/24RIPEValid
185.103.113.0/24RIPEValid
185.103.114.0/24RIPEValid
185.103.115.0/24RIPEValid

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.