bgpreport

Network · data from 2026-11-12

AS56596 EDP Mechashvim E.D.P. LTD

Registry name: EDP Mechashvim E.D.P. LTD, IL · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS56596, 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.
147.234.0.0/24 No ROA RIR databaseRIPE 671 100% 67
45.8.56.0/24 Valid Nonecovered by 45.8.56.0/22 671 100% 67
45.8.57.0/24 Valid Nonecovered by 45.8.56.0/22 671 100% 67
45.8.58.0/24 Valid Nonecovered by 45.8.56.0/22 671 100% 67
45.8.59.0/24 Valid Nonecovered by 45.8.56.0/22 671 100% 67
195.128.145.0/24 Valid RIR databaseRIPE 673 100% 67
147.234.6.0/23 Valid RIR databaseRIPE 672 100% 66
185.172.80.0/22 Valid RIR databaseRIPE 672 100% 66
147.234.6.0/24 Valid RIR databaseRIPE 671 100% 67
147.234.7.0/24 Valid RIR databaseRIPE 671 100% 67
147.234.16.0/24 Valid RIR databaseRIPE 671 100% 67
185.172.80.0/24 Valid RIR databaseRIPE 671 100% 67
185.172.81.0/24 Valid RIR databaseRIPE 671 100% 67
185.172.82.0/24 Valid RIR databaseRIPE 671 100% 67
185.172.83.0/24 Valid RIR databaseRIPE 671 100% 67

AS-SET

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

  • ROA: none1
  • Route object: none4
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none147.234.0.0/24No ROA covers it. Add a ROA for AS56596, maxLength 24.671 of 673
Route object: none45.8.56.0/24No route object for it. A route object for 45.8.56.0/22 with origin AS56596 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56596 in the RIR database for the space.671 of 673
Route object: none45.8.57.0/24No route object for it. A route object for 45.8.56.0/22 with origin AS56596 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56596 in the RIR database for the space.671 of 673
Route object: none45.8.58.0/24No route object for it. A route object for 45.8.56.0/22 with origin AS56596 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56596 in the RIR database for the space.671 of 673
Route object: none45.8.59.0/24No route object for it. A route object for 45.8.56.0/22 with origin AS56596 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56596 in the RIR database for the space.671 of 673

Route objects not announced

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

45.8.56.0/22RIPENo ROA
185.172.80.0/23RIPEValid
185.172.82.0/23RIPEValid

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.