bgpreport

Network · data from 2026-11-12

AS23486 NETSPAN

Registry name: NETSPAN - Foremost Telecommunications, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS23486, 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.
170.124.0.0/23 Invalid: origin None 18 3%low visibility 17
199.58.129.0/24 Invalid: maxLength Nonecovered by 199.58.128.0/21 18 3%low visibility 17
38.103.228.0/22 No ROA Other IRR onlyNTTCOM 670 100% 67
194.164.102.0/23 No ROA Other IRR onlyNTTCOM 670 100% 67
204.29.205.0/24 No ROA Other IRR onlyNTTCOM 670 100% 67
74.122.64.0/21 Valid RIR databaseARIN, NTTCOM 672 100% 67
199.58.128.0/21 Valid RIR databaseARIN, NTTCOM 672 100% 67
199.192.244.0/22 Valid RIR databaseARIN, NTTCOM 670 100% 67

AS-SET

AS23486'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 20 are in fix.csv.

  • ROA: origin1
  • ROA: maxLength1
  • ROA: none3
  • Route object: none2
  • Route object: RIR3
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
ROA: origin170.124.0.0/23ROAs covering it name AS6079, AS7029, not AS23486. If AS23486 should announce it, add a ROA for AS23486.18 of 673
Route object: none170.124.0.0/23No route object for it. Add a route object with origin AS23486 in the RIR database for the space.18 of 673
ROA: maxLength199.58.129.0/24ROA 199.58.128.0/21 AS23486 has maxLength 21; the route is a /24. Raise the maxLength, or add a ROA for 199.58.129.0/24.18 of 673
Route object: none199.58.129.0/24No route object for it. A route object for 199.58.128.0/21 with origin AS23486 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23486 in the RIR database for the space.18 of 673
ROA: none38.103.228.0/22No ROA covers it. Add a ROA for AS23486, maxLength 22.670 of 673
Route object: RIR38.103.228.0/22Route object only in NTTCOM. Add it in the RIR database for the space.670 of 673
ROA: none194.164.102.0/23No ROA covers it. Add a ROA for AS23486, maxLength 23.670 of 673
Route object: RIR194.164.102.0/23Route object only in NTTCOM. Add it in the RIR database for the space.670 of 673
ROA: none204.29.205.0/24No ROA covers it. Add a ROA for AS23486, maxLength 24.670 of 673
Route object: RIR204.29.205.0/24Route object only in NTTCOM. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

8.19.114.0/23NTTCOMNo ROA
170.76.243.0/24ARIN, NTTCOMValid
192.149.90.0/23NTTCOM, RADBNo ROA
198.22.170.0/24NTTCOMNo ROA
198.96.22.0/24NTTCOM, RADBNo ROA
198.232.222.0/23NTTCOMNo ROA
204.13.159.0/24NTTCOM, RADBNo ROA
204.141.240.0/22NTTCOMValid
208.65.16.0/22NTTCOMNo ROA
208.68.152.0/22NTTCOM, RADBNo 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.