bgpreport

Network · data from 2026-11-12

AS80 GE-CRD

Registry name: GE-CRD - General Electric Company, US · PeeringDB

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

Announced routes

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

8.23.90.0/24 No ROA None 672 100% 67
8.29.116.0/24 No ROA None 672 100% 67
65.90.67.0/24 No ROA None 672 100% 67
165.156.25.0/24 Valid RIR databaseARIN 673 100% 67
165.156.40.0/24 Valid RIR databaseARIN 673 100% 67
165.156.56.0/24 Valid RIR databaseARIN 673 100% 67
165.156.78.0/23 Valid RIR databaseARIN 673 100% 67
165.156.57.0/24 Valid RIR databaseARIN 672 100% 67

AS-SET

AS80'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 59 are in fix.csv.

  • ROA: none3
  • Route object: none3
  • Route object: not announced53
ChangePrefix or setDetailFull-table peers
ROA: none8.23.90.0/24No ROA covers it. Add a ROA for AS80, maxLength 24.672 of 673
Route object: none8.23.90.0/24No route object for it. Add a route object with origin AS80 in the RIR database for the space.672 of 673
ROA: none8.29.116.0/24No ROA covers it. Add a ROA for AS80, maxLength 24.672 of 673
Route object: none8.29.116.0/24No route object for it. Add a route object with origin AS80 in the RIR database for the space.672 of 673
ROA: none65.90.67.0/24No ROA covers it. Add a ROA for AS80, maxLength 24.672 of 673
Route object: none65.90.67.0/24No route object for it. Add a route object with origin AS80 in the RIR database for the space.672 of 673

Route objects not announced

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

129.201.0.0/16ALTDBNo ROA
129.202.0.0/16ALTDBNo ROA
165.156.0.0/16ALTDB, NTTCOMNo ROA
168.239.0.0/16ALTDBNo ROA
192.35.26.0/24ALTDBNo ROA
192.35.36.0/24ALTDBNo ROA
192.35.38.0/24ALTDBNo ROA
192.46.160.0/22NTTCOMNo ROA
192.53.38.0/24NTTCOM, RADBNo ROA
192.82.141.0/24NTTCOM, RADBNo ROA
192.104.171.0/24NTTCOM, RADBNo ROA
192.131.161.0/24ALTDBNo ROA
192.131.162.0/24ALTDBNo ROA
192.131.163.0/24ALTDBNo ROA
192.131.164.0/24ALTDBNo ROA
192.131.166.0/24ALTDBNo ROA
192.131.169.0/24ALTDBNo ROA
192.131.170.0/24ALTDBNo ROA
192.131.173.0/24ALTDBNo ROA
192.131.178.0/24ALTDBNo ROA
192.131.187.0/24ALTDBNo ROA
192.131.202.0/24ALTDBNo ROA
192.131.204.0/24ALTDBNo ROA
192.131.207.0/24ALTDBNo ROA
192.131.210.0/24ALTDBNo ROA
192.131.217.0/24ALTDBNo ROA
192.131.219.0/24ALTDBNo ROA
192.131.220.0/24ALTDBNo ROA
192.131.230.0/24ALTDBNo ROA
198.151.160.0/24NTTCOM, RADBNo ROA
198.177.148.0/24NTTCOM, RADBNo ROA
198.204.0.0/19NTTCOMNo ROA
198.204.23.0/24ALTDBNo ROA
198.204.24.0/24ALTDBNo ROA
198.204.27.0/24ALTDBNo ROA
199.38.134.0/23NTTCOMNo ROA
199.38.135.0/24ALTDBNo ROA
199.38.136.0/24NTTCOM, RADBNo ROA
199.127.16.0/20NTTCOMNo ROA
199.181.100.0/22NTTCOMNo ROA
205.173.88.0/21NTTCOMNo ROA
205.173.92.0/24ALTDBNo ROA
208.234.185.0/24ALTDB, NTTCOM, RADBNo ROA
209.17.224.0/19NTTCOMNo ROA
209.17.247.0/24ALTDBNo ROA
209.17.248.0/24ALTDBNo ROA
209.17.249.0/24ALTDBNo ROA
209.17.250.0/24ALTDBNo ROA
209.17.251.0/24ALTDBNo ROA
209.17.252.0/24ALTDBNo ROA
209.17.253.0/24ALTDBNo ROA
209.17.254.0/24ALTDBNo ROA
209.17.255.0/24ALTDBNo ROA

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.