bgpreport

Network · data from 2026-11-12

AS399468 EG-CORE-INFRA - EngineFresh LLC

Registry name: EG-CORE-INFRA - EngineFresh LLC, US · not in PeeringDB

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

Announced routes

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

195.40.156.0/22 No ROA Other origin only 673 100% 67
195.172.122.0/23 No ROA None 673 100% 67
114.119.192.0/24 No ROA None 13 2%low visibility 8
114.119.193.0/24 No ROA None 13 2%low visibility 8
114.119.194.0/24 No ROA None 13 2%low visibility 8
114.119.195.0/24 No ROA None 13 2%low visibility 8
87.82.48.0/23 Valid RIR databaseRIPE 673 100% 67
114.119.200.0/24 Valid RIR databaseAPNIC 673 100% 67
114.119.201.0/24 Valid RIR databaseAPNIC 673 100% 67
114.119.202.0/24 Valid RIR databaseAPNIC 673 100% 67
114.119.203.0/24 Valid RIR databaseAPNIC 673 100% 67
130.12.76.0/22 Valid RIR databaseARIN 673 100% 67
131.143.148.0/22 Valid RIR databaseARIN 673 100% 67
131.143.216.0/22 Valid RIR databaseARIN 673 100% 67
155.103.8.0/22 Valid RIR databaseARIN 673 100% 67
162.210.64.0/22 Valid RIR databaseARIN 673 100% 67
169.128.196.0/22 Valid RIR databaseARIN 673 100% 67
195.162.224.0/21 Valid RIR databaseRIPE 673 100% 67
195.162.232.0/21 Valid RIR databaseRIPE 673 100% 67
212.212.0.0/21 Valid RIR databaseRIPE 673 100% 67
212.212.8.0/21 Valid RIR databaseRIPE 673 100% 67
212.23.219.0/24 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

AS399468 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 16 are in fix.csv.

  • ROA: none6
  • Route object: none6
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none195.40.156.0/22No ROA covers it. Add a ROA for AS399468, maxLength 22.673 of 673
Route object: none195.40.156.0/22Route objects for it name AS3257. Add a route object with origin AS399468 in the RIR database for the space.673 of 673
ROA: none195.172.122.0/23No ROA covers it. Add a ROA for AS399468, maxLength 23.673 of 673
Route object: none195.172.122.0/23No route object for it. Add a route object with origin AS399468 in the RIR database for the space.673 of 673
ROA: none114.119.192.0/24No ROA covers it. Add a ROA for AS399468, maxLength 24.13 of 673
Route object: none114.119.192.0/24No route object for it. Add a route object with origin AS399468 in the RIR database for the space.13 of 673
ROA: none114.119.193.0/24No ROA covers it. Add a ROA for AS399468, maxLength 24.13 of 673
Route object: none114.119.193.0/24No route object for it. Add a route object with origin AS399468 in the RIR database for the space.13 of 673
ROA: none114.119.194.0/24No ROA covers it. Add a ROA for AS399468, maxLength 24.13 of 673
Route object: none114.119.194.0/24No route object for it. Add a route object with origin AS399468 in the RIR database for the space.13 of 673
ROA: none114.119.195.0/24No ROA covers it. Add a ROA for AS399468, maxLength 24.13 of 673
Route object: none114.119.195.0/24No route object for it. Add a route object with origin AS399468 in the RIR database for the space.13 of 673

Route objects not announced

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

114.119.200.0/22APNICValid
114.119.200.0/23APNICValid
114.119.202.0/23APNICValid
217.60.52.0/22RIPEValid

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.