bgpreport

Network · data from 2026-11-12

AS13173 FORESHORE-AS Foreshore Limited

Registry name: FORESHORE-AS Foreshore Limited, JE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS13173, 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.
213.167.69.0/24 Valid Nonecovered by 213.167.64.0/20 673 100% 67
213.167.72.0/24 Valid Nonecovered by 213.167.64.0/20 673 100% 67
213.167.74.0/23 Valid Nonecovered by 213.167.64.0/20 673 100% 67
213.167.77.0/24 Valid Nonecovered by 213.167.64.0/20 673 100% 67
213.167.78.0/24 Valid Nonecovered by 213.167.64.0/20 673 100% 67
213.167.80.0/23 Valid Nonecovered by 213.167.80.0/20 673 100% 67
213.167.92.0/23 Valid Nonecovered by 213.167.80.0/20 673 100% 67
213.167.94.0/23 Valid Nonecovered by 213.167.80.0/20 673 100% 67
213.167.93.0/24 Valid Nonecovered by 213.167.80.0/20 2 0%low visibility 2
213.167.64.0/19 Valid RIR databaseRIPE 672 100% 67
185.70.156.0/22 Valid RIR databaseRIPE 670 100% 67
213.167.64.0/24 Valid RIR databaseRIPE 670 100% 67
213.167.67.0/24 Valid RIR databaseRIPE 670 100% 67
2a00:f180::/32 Valid RIR databaseRIPE 636 100% 67

AS-SET

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

  • Route object: none9
  • Route object: not announced14
ChangePrefix or setDetailFull-table peers
Route object: none213.167.69.0/24No route object for it. A route object for 213.167.64.0/20 with origin AS13173 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13173 in the RIR database for the space.673 of 673
Route object: none213.167.72.0/24No route object for it. A route object for 213.167.64.0/20 with origin AS13173 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13173 in the RIR database for the space.673 of 673
Route object: none213.167.74.0/23No route object for it. A route object for 213.167.64.0/20 with origin AS13173 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13173 in the RIR database for the space.673 of 673
Route object: none213.167.77.0/24No route object for it. A route object for 213.167.64.0/20 with origin AS13173 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13173 in the RIR database for the space.673 of 673
Route object: none213.167.78.0/24No route object for it. A route object for 213.167.64.0/20 with origin AS13173 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13173 in the RIR database for the space.673 of 673
Route object: none213.167.80.0/23No route object for it. A route object for 213.167.80.0/20 with origin AS13173 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13173 in the RIR database for the space.673 of 673
Route object: none213.167.92.0/23No route object for it. A route object for 213.167.80.0/20 with origin AS13173 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13173 in the RIR database for the space.673 of 673
Route object: none213.167.94.0/23No route object for it. A route object for 213.167.80.0/20 with origin AS13173 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13173 in the RIR database for the space.673 of 673
Route object: none213.167.93.0/24No route object for it. A route object for 213.167.80.0/20 with origin AS13173 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13173 in the RIR database for the space.2 of 673

Route objects not announced

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

185.70.158.0/24RIPEValid
185.70.159.0/24RIPEValid
213.167.64.0/20RIPEValid
213.167.68.144/29RIPEInvalid: maxLength
213.167.68.160/28RIPEInvalid: maxLength
213.167.69.120/29RIPEInvalid: maxLength
213.167.70.144/28RIPEInvalid: maxLength
213.167.72.128/26RIPEInvalid: maxLength
213.167.74.128/28RIPEInvalid: maxLength
213.167.79.0/27RIPEInvalid: maxLength
213.167.80.0/20RIPEValid
213.167.82.0/24RIPEValid
213.167.93.0/26RIPEInvalid: maxLength
213.167.95.144/29RIPEInvalid: maxLength

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.