bgpreport

Network · data from 2026-11-12

AS13462 IEEE - Institute of Electrical and Electronics Engineers, Inc

Registry name: IEEE - Institute of Electrical and Electronics Engineers, Inc, US · not in PeeringDB

9IPv4 routes 33.3% RPKI valid · 22.2% with a route object
1IPv6 routes 0.0% RPKI valid · 0.0% with a route object
1RPKI invalid 0 origin · 1 maxLength
6No 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 AS13462, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS13462, 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.
140.98.202.0/24 Invalid: maxLength Nonecovered by 140.98.0.0/16 149 22% 49
63.84.220.0/22 No ROA None 673 100% 67
63.84.220.0/24 No ROA Other origin only 673 100% 67
63.84.221.0/24 No ROA Other origin only 673 100% 67
63.84.223.0/24 No ROA Other origin only 673 100% 67
2620:104:c000::/44 No ROA None 604 95% 67
199.172.136.0/24 No ROA Other IRR onlyNTTCOM 673 100% 67
140.98.210.0/24 Valid Nonecovered by 140.98.0.0/16 673 100% 67
140.98.193.0/24 Valid Nonecovered by 140.98.0.0/16 672 100% 66
140.98.0.0/16 Valid RIR databaseARIN, NTTCOM 673 100% 67

AS-SET

AS13462 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: maxLength1
  • ROA: none6
  • Route object: none8
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: maxLength140.98.202.0/24ROA 140.98.0.0/16 AS13462 has maxLength 16; the route is a /24. Raise the maxLength, or add a ROA for 140.98.202.0/24.149 of 673
Route object: none140.98.202.0/24No route object for it. A route object for 140.98.0.0/16 with origin AS13462 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13462 in the RIR database for the space.149 of 673
ROA: none63.84.220.0/22No ROA covers it. Add a ROA for AS13462, maxLength 22.673 of 673
Route object: none63.84.220.0/22No route object for it. Add a route object with origin AS13462 in the RIR database for the space.673 of 673
ROA: none63.84.220.0/24No ROA covers it. Add a ROA for AS13462, maxLength 24.673 of 673
Route object: none63.84.220.0/24Route objects for it name AS7046. Add a route object with origin AS13462 in the RIR database for the space.673 of 673
ROA: none63.84.221.0/24No ROA covers it. Add a ROA for AS13462, maxLength 24.673 of 673
Route object: none63.84.221.0/24Route objects for it name AS7046. Add a route object with origin AS13462 in the RIR database for the space.673 of 673
ROA: none63.84.223.0/24No ROA covers it. Add a ROA for AS13462, maxLength 24.673 of 673
Route object: none63.84.223.0/24Route objects for it name AS7046. Add a route object with origin AS13462 in the RIR database for the space.673 of 673
ROA: none2620:104:c000::/44No ROA covers it. Add a ROA for AS13462, maxLength 44.604 of 636
Route object: none2620:104:c000::/44No route object for it. Add a route object with origin AS13462 in the RIR database for the space.604 of 636
ROA: none199.172.136.0/24No ROA covers it. Add a ROA for AS13462, maxLength 24.673 of 673
Route object: RIR199.172.136.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: none140.98.210.0/24No route object for it. A route object for 140.98.0.0/16 with origin AS13462 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13462 in the RIR database for the space.673 of 673
Route object: none140.98.193.0/24No route object for it. A route object for 140.98.0.0/16 with origin AS13462 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13462 in the RIR database for the space.672 of 673

Route objects not announced

Every route object with origin AS13462 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.