bgpreport

Network · data from 2026-11-12

AS23029 ESTREET - E Street

Registry name: ESTREET - E Street, US · not in PeeringDB

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

Announced routes

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

65.175.26.0/23 No ROA Other origin only 673 100% 67
66.7.166.0/23 No ROA Other origin only 673 100% 67
66.7.182.0/23 No ROA Other origin only 673 100% 67
66.7.184.0/23 No ROA Other origin only 673 100% 67
66.17.141.0/24 No ROA Other origin only 673 100% 67
66.227.10.0/24 No ROA None 673 100% 67
66.227.111.0/24 No ROA None 673 100% 67
76.74.124.0/22 No ROA None 673 100% 67
208.116.135.0/24 No ROA Other IRR onlyRADB 673 100% 67

AS-SET

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

  • ROA: none9
  • Route object: none8
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: none65.175.26.0/23No ROA covers it. Add a ROA for AS23029, maxLength 23.673 of 673
Route object: none65.175.26.0/23Route objects for it name AS6517. Add a route object with origin AS23029 in the RIR database for the space.673 of 673
ROA: none66.7.166.0/23No ROA covers it. Add a ROA for AS23029, maxLength 23.673 of 673
Route object: none66.7.166.0/23Route objects for it name AS6517. Add a route object with origin AS23029 in the RIR database for the space.673 of 673
ROA: none66.7.182.0/23No ROA covers it. Add a ROA for AS23029, maxLength 23.673 of 673
Route object: none66.7.182.0/23Route objects for it name AS6517. Add a route object with origin AS23029 in the RIR database for the space.673 of 673
ROA: none66.7.184.0/23No ROA covers it. Add a ROA for AS23029, maxLength 23.673 of 673
Route object: none66.7.184.0/23Route objects for it name AS6517. Add a route object with origin AS23029 in the RIR database for the space.673 of 673
ROA: none66.17.141.0/24No ROA covers it. Add a ROA for AS23029, maxLength 24.673 of 673
Route object: none66.17.141.0/24Route objects for it name AS6517. Add a route object with origin AS23029 in the RIR database for the space.673 of 673
ROA: none66.227.10.0/24No ROA covers it. Add a ROA for AS23029, maxLength 24.673 of 673
Route object: none66.227.10.0/24No route object for it. Add a route object with origin AS23029 in the RIR database for the space.673 of 673
ROA: none66.227.111.0/24No ROA covers it. Add a ROA for AS23029, maxLength 24.673 of 673
Route object: none66.227.111.0/24No route object for it. Add a route object with origin AS23029 in the RIR database for the space.673 of 673
ROA: none76.74.124.0/22No ROA covers it. Add a ROA for AS23029, maxLength 22.673 of 673
Route object: none76.74.124.0/22No route object for it. Add a route object with origin AS23029 in the RIR database for the space.673 of 673
ROA: none208.116.135.0/24No ROA covers it. Add a ROA for AS23029, maxLength 24.673 of 673
Route object: RIR208.116.135.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

Every route object with origin AS23029 is announced.

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.