bgpreport

Network · data from 2026-11-12

AS205564 INFINIDAT Infinidat Ltd

Registry name: INFINIDAT Infinidat Ltd, IL · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS205564, 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.
185.213.254.0/23 Valid Nonecovered by 185.213.252.0/22 673 100% 67
185.213.252.0/22 Valid RIR databaseRIPE 673 100% 67
185.213.253.0/24 Valid RIR databaseRIPE 673 100% 67

AS-SET

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

  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none185.213.254.0/23No route object for it. A route object for 185.213.252.0/22 with origin AS205564 covers it (filters allowing more-specifics accept it). Add a route object with origin AS205564 in the RIR database for the space.673 of 673

Route objects not announced

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

185.213.252.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.