bgpreport

Network · data from 2026-11-12

AS58247 NETVEILLANCE SC NETVEILLANCE SRL

Registry name: NETVEILLANCE SC NETVEILLANCE SRL, RO · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS58247, 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.
44.32.30.0/24 No ROA Nonecovered by 44.32.16.0/20 673 100% 67
44.32.16.0/20 No ROA Other IRR onlyRADB 673 100% 66
94.176.6.0/24 No ROA RIR databaseRIPE 673 100% 66
81.180.160.0/24 No ROA RIR databaseRIPE 672 100% 66
81.181.65.0/24 No ROA RIR databaseRIPE 672 100% 66
81.181.71.0/24 No ROA RIR databaseRIPE 672 100% 66
81.180.161.0/24 No ROA RIR databaseRIPE 671 100% 66
2001:67c:29d4::/48 Valid RIR databaseRIPE 636 100% 67
2a0e:4540:cafe::/48 Valid RIR databaseRIPE 636 100% 67

AS-SET

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

  • ROA: none7
  • Route object: none1
  • Route object: RIR1
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none44.32.30.0/24No ROA covers it. Add a ROA for AS58247, maxLength 24.673 of 673
Route object: none44.32.30.0/24No route object for it. A route object for 44.32.16.0/20 with origin AS58247 covers it (filters allowing more-specifics accept it). Add a route object with origin AS58247 in the RIR database for the space.673 of 673
ROA: none44.32.16.0/20No ROA covers it. Add a ROA for AS58247, maxLength 20.673 of 673
Route object: RIR44.32.16.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none94.176.6.0/24No ROA covers it. Add a ROA for AS58247, maxLength 24.673 of 673
ROA: none81.180.160.0/24No ROA covers it. Add a ROA for AS58247, maxLength 24.672 of 673
ROA: none81.181.65.0/24No ROA covers it. Add a ROA for AS58247, maxLength 24.672 of 673
ROA: none81.181.71.0/24No ROA covers it. Add a ROA for AS58247, maxLength 24.672 of 673
ROA: none81.180.161.0/24No ROA covers it. Add a ROA for AS58247, maxLength 24.671 of 673

Route objects not announced

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

44.182.0.0/20ALTDBNo ROA
81.180.160.0/23RIPENo ROA
194.9.22.0/24RIPEInvalid: origin
2001:67c:29d4::/49RIPEInvalid: maxLength
2001:67c:29d4:8000::/49RIPEValid

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.