bgpreport

Network · data from 2026-11-12

AS200760 Dinova Srl

Registry name: ELOGIC-AS Dinova Srl, IT · PeeringDB

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

Announced routes

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

178.239.20.0/23 No ROA RIR databaseRIPE 673 100% 67
185.68.190.0/23 No ROA RIR databaseRIPE 673 100% 67
185.96.204.0/22 No ROA RIR databaseRIPE 673 100% 67
185.146.160.0/22 No ROA RIR databaseRIPE 673 100% 67
185.168.32.0/22 No ROA RIR databaseRIPE 673 100% 67
185.198.252.0/22 No ROA RIR databaseRIPE 673 100% 67
194.110.16.0/23 No ROA RIR databaseRIPE 673 100% 67
194.110.16.0/24 No ROA RIR databaseRIPE 673 100% 67
195.72.34.0/23 No ROA RIR databaseRIPE 673 100% 67
195.72.34.0/24 No ROA RIR databaseRIPE 673 100% 67
185.96.207.0/24 No ROA RIR databaseRIPE 671 100% 67
194.110.17.0/24 No ROA RIR databaseRIPE 671 100% 67
195.72.35.0/24 No ROA RIR databaseRIPE 671 100% 67
2a06:100::/32 No ROA RIR databaseRIPE 631 99% 67

AS-SET

PeeringDB's irr_as_set for AS200760: AS-MAGGIOLIGROUP. 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 (AS200760 isn't in the set, or no route object for AS200760 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 objectsAS200760 in itNot covered
AS-MAGGIOLIGROUP RIPE 2122 Yes 0

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

  • ROA: none14
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none178.239.20.0/23No ROA covers it. Add a ROA for AS200760, maxLength 23.673 of 673
ROA: none185.68.190.0/23No ROA covers it. Add a ROA for AS200760, maxLength 23.673 of 673
ROA: none185.96.204.0/22No ROA covers it. Add a ROA for AS200760, maxLength 22.673 of 673
ROA: none185.146.160.0/22No ROA covers it. Add a ROA for AS200760, maxLength 22.673 of 673
ROA: none185.168.32.0/22No ROA covers it. Add a ROA for AS200760, maxLength 22.673 of 673
ROA: none185.198.252.0/22No ROA covers it. Add a ROA for AS200760, maxLength 22.673 of 673
ROA: none194.110.16.0/23No ROA covers it. Add a ROA for AS200760, maxLength 23.673 of 673
ROA: none194.110.16.0/24No ROA covers it. Add a ROA for AS200760, maxLength 24.673 of 673
ROA: none195.72.34.0/23No ROA covers it. Add a ROA for AS200760, maxLength 23.673 of 673
ROA: none195.72.34.0/24No ROA covers it. Add a ROA for AS200760, maxLength 24.673 of 673
ROA: none185.96.207.0/24No ROA covers it. Add a ROA for AS200760, maxLength 24.671 of 673
ROA: none194.110.17.0/24No ROA covers it. Add a ROA for AS200760, maxLength 24.671 of 673
ROA: none195.72.35.0/24No ROA covers it. Add a ROA for AS200760, maxLength 24.671 of 673
ROA: none2a06:100::/32No ROA covers it. Add a ROA for AS200760, maxLength 32.631 of 636

Route objects not announced

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

185.96.204.0/23RIPENo ROA
185.96.206.0/24RIPENo ROA

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.