bgpreport

Network · data from 2026-11-12

AS31391 ISOC Israel

Registry name: ISOC-IL-AS Israel Internet Association, IL · PeeringDB

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

Announced routes

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

2a01:4280:7::/48 Valid Nonecovered by 2a01:4280::/43 636 100% 67
192.115.0.0/23 Valid Nonecovered by 192.115.0.0/21 33 5%low visibility 27
192.115.2.0/23 Valid Nonecovered by 192.115.0.0/21 33 5%low visibility 27
192.115.6.0/23 Valid Nonecovered by 192.115.0.0/21 33 5%low visibility 27
192.115.208.0/23 Valid Nonecovered by 192.115.208.0/22 1 0%low visibility 1
192.115.210.0/23 Valid Nonecovered by 192.115.208.0/22 1 0%low visibility 1
192.115.0.0/21 Valid RIR databaseRIPE 673 100% 67
192.115.0.0/24 Valid RIR databaseRIPE 673 100% 70
192.115.3.0/24 Valid RIR databaseRIPE 673 100% 70
192.115.4.0/24 Valid RIR databaseRIPE 673 100% 70
192.115.7.0/24 Valid RIR databaseRIPE 673 100% 70
192.115.208.0/22 Valid RIR databaseRIPE 673 100% 67
192.115.209.0/24 Valid RIR databaseRIPE 673 100% 70
192.115.210.0/24 Valid RIR databaseRIPE 673 100% 70
192.115.211.0/24 Valid RIR databaseRIPE 673 100% 70
2a01:4280::/43 Valid RIR databaseRIPE 636 100% 67
2a01:4280:1::/48 Valid RIR databaseRIPE 636 100% 67
2a01:4280::/32 Valid RIR databaseRIPE 635 100% 67

AS-SET

AS31391's PeeringDB record names no 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 12 are in fix.csv.

  • Route object: none6
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
Route object: none2a01:4280:7::/48No route object for it. A route object for 2a01:4280::/43 with origin AS31391 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31391 in the RIR database for the space.636 of 636
Route object: none192.115.0.0/23No route object for it. A route object for 192.115.0.0/21 with origin AS31391 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31391 in the RIR database for the space.33 of 673
Route object: none192.115.2.0/23No route object for it. A route object for 192.115.0.0/21 with origin AS31391 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31391 in the RIR database for the space.33 of 673
Route object: none192.115.6.0/23No route object for it. A route object for 192.115.0.0/21 with origin AS31391 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31391 in the RIR database for the space.33 of 673
Route object: none192.115.208.0/23No route object for it. A route object for 192.115.208.0/22 with origin AS31391 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31391 in the RIR database for the space.1 of 673
Route object: none192.115.210.0/23No route object for it. A route object for 192.115.208.0/22 with origin AS31391 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31391 in the RIR database for the space.1 of 673

Route objects not announced

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

192.115.1.0/24RIPEValid
192.115.2.0/24RIPEValid
192.115.5.0/24RIPEValid
192.115.6.0/24RIPEValid
192.115.208.0/24RIPEValid
2a01:4280:2::/48RIPEValid

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.