bgpreport

Network · data from 2026-11-12

AS56781 NetPro IT Solution SRL

Registry name: AS-ASNETPROIT NetPro IT Solution SRL, IT · PeeringDB

0IPv4 routes
3IPv6 routes 100.0% RPKI valid · 100.0% with a route object
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
13Route objects not announced registered with origin AS56781, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS56781, 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.
2a10:ba87:ff00::/44 Valid RIR databaseRIPE 634 100% 68
2a10:ba87:ff10::/44 Valid RIR databaseRIPE 634 100% 68
2a10:ba87:ff20::/44 Valid RIR databaseRIPE 634 100% 68

AS-SET

AS56781's PeeringDB record names no 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 13 are in fix.csv.

  • Route object: not announced13

Route objects not announced

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

2a10:ba87:ff30::/44RIPEValid
2a10:ba87:ff40::/44RIPEValid
2a10:ba87:ff50::/44RIPEValid
2a10:ba87:ff60::/44RIPEValid
2a10:ba87:ff70::/44RIPEValid
2a10:ba87:ff80::/44RIPEValid
2a10:ba87:ff90::/44RIPEValid
2a10:ba87:ffa0::/44RIPEValid
2a10:ba87:ffb0::/44RIPEValid
2a10:ba87:ffc0::/44RIPEValid
2a10:ba87:ffd0::/44RIPEValid
2a10:ba87:ffe0::/44RIPEValid
2a10:ba87:fff0::/44RIPEValid

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.