bgpreport

Network · data from 2026-11-12

AS23268 NEULION - NeuLion, Inc.

Registry name: NEULION - NeuLion, Inc., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS23268, 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.
208.78.10.0/24 No ROA None 2 0%low visibility 2
208.92.36.0/24 No ROA None 2 0%low visibility 2
208.92.37.0/24 No ROA Other origin only 2 0%low visibility 2
209.87.132.0/24 No ROA None 2 0%low visibility 3
209.87.140.0/24 No ROA None 2 0%low visibility 2
209.87.141.0/24 No ROA None 2 0%low visibility 2
208.78.9.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
208.92.39.0/24 Valid RIR databaseARIN 672 100% 67

AS-SET

AS23268 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 17 are in fix.csv.

  • ROA: none7
  • Route object: none6
  • Route object: RIR1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none208.78.10.0/24No ROA covers it. Add a ROA for AS23268, maxLength 24.2 of 673
Route object: none208.78.10.0/24No route object for it. Add a route object with origin AS23268 in the RIR database for the space.2 of 673
ROA: none208.92.36.0/24No ROA covers it. Add a ROA for AS23268, maxLength 24.2 of 673
Route object: none208.92.36.0/24No route object for it. Add a route object with origin AS23268 in the RIR database for the space.2 of 673
ROA: none208.92.37.0/24No ROA covers it. Add a ROA for AS23268, maxLength 24.2 of 673
Route object: none208.92.37.0/24Route objects for it name AS15019. Add a route object with origin AS23268 in the RIR database for the space.2 of 673
ROA: none209.87.132.0/24No ROA covers it. Add a ROA for AS23268, maxLength 24.2 of 673
Route object: none209.87.132.0/24No route object for it. Add a route object with origin AS23268 in the RIR database for the space.2 of 673
ROA: none209.87.140.0/24No ROA covers it. Add a ROA for AS23268, maxLength 24.2 of 673
Route object: none209.87.140.0/24No route object for it. Add a route object with origin AS23268 in the RIR database for the space.2 of 673
ROA: none209.87.141.0/24No ROA covers it. Add a ROA for AS23268, maxLength 24.2 of 673
Route object: none209.87.141.0/24No route object for it. Add a route object with origin AS23268 in the RIR database for the space.2 of 673
ROA: none208.78.9.0/24No ROA covers it. Add a ROA for AS23268, maxLength 24.2 of 673
Route object: RIR208.78.9.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

208.78.8.0/24RADBNo ROA
2620:10e:c000::/44ARINNo ROA
2620:10e:c000:11::/64ARINNo 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.