bgpreport

Network · data from 2026-11-12

AS31362 PROTECTNET NETPROTECT SRL

Registry name: PROTECTNET NETPROTECT SRL, RO · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS31362, 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.
80.96.24.0/24 No ROA RIR databaseRIPE 669 99% 67
80.96.204.0/24 No ROA RIR databaseRIPE 669 99% 67
31.14.53.0/24 Valid RIR databaseRIPE 673 100% 66
31.14.54.0/24 Valid RIR databaseRIPE 673 100% 66
31.14.43.0/24 Valid RIR databaseRIPE 670 100% 67
37.156.245.0/24 Valid RIR databaseRIPE 670 100% 67
86.104.124.0/24 Valid RIR databaseRIPE 668 99% 67
89.35.55.0/24 Valid RIR databaseRIPE 668 99% 67
89.36.19.0/24 Valid RIR databaseRIPE 668 99% 67
89.41.63.0/24 Valid RIR databaseRIPE 668 99% 67
89.42.14.0/24 Valid RIR databaseRIPE 668 99% 67
89.42.35.0/24 Valid RIR databaseRIPE 668 99% 67
89.42.214.0/24 Valid RIR databaseRIPE 668 99% 67
89.44.104.0/24 Valid RIR databaseRIPE 668 99% 67

AS-SET

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

  • ROA: none2
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none80.96.24.0/24No ROA covers it. Add a ROA for AS31362, maxLength 24.669 of 673
ROA: none80.96.204.0/24No ROA covers it. Add a ROA for AS31362, maxLength 24.669 of 673

Route objects not announced

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

89.34.5.0/24RIPEValid
89.34.93.0/24RIPEValid
89.36.92.0/24RIPEValid
185.99.91.0/24RIPEValid
188.240.12.0/24RIPEValid
188.241.104.0/23RIPENo ROA
217.19.9.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.