bgpreport

Network · data from 2026-11-12

AS30462 NexGen Integrated Communications

Registry name: NEXGEN - NexGen Integrated Communications LLC, US · PeeringDB

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

Announced routes

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

63.85.88.0/22 Invalid: origin None 2 0%low visibility 2
63.86.8.0/22 Invalid: origin None 2 0%low visibility 2
116.66.129.0/24 No ROA None 673 100% 67
207.45.95.0/24 Valid Nonecovered by 207.45.80.0/20 671 100% 67
207.45.80.0/24 Valid Nonecovered by 207.45.80.0/20 98 15% 37
207.45.87.0/24 Valid Nonecovered by 207.45.80.0/20 98 15% 37
207.45.80.0/20 Valid RIR databaseARIN 673 100% 67
136.175.52.0/22 Valid RIR databaseARIN 671 100% 67

AS-SET

PeeringDB's irr_as_set for AS30462: AS30462:AS-NGISP. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS30462 isn't in the set, or no route object for AS30462 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS30462 in itNot covered
AS30462:AS-NGISP ARIN 2146 Yes 3

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

  • ROA: origin2
  • ROA: none1
  • Route object: none6
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin63.85.88.0/22An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS30462 should announce it, add a ROA for AS30462.2 of 673
Route object: none63.85.88.0/22No route object for it. Add a route object with origin AS30462 in the RIR database for the space.2 of 673
ROA: origin63.86.8.0/22An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS30462 should announce it, add a ROA for AS30462.2 of 673
Route object: none63.86.8.0/22No route object for it. Add a route object with origin AS30462 in the RIR database for the space.2 of 673
ROA: none116.66.129.0/24No ROA covers it. Add a ROA for AS30462, maxLength 24.673 of 673
Route object: none116.66.129.0/24No route object for it. Add a route object with origin AS30462 in the RIR database for the space.673 of 673
Route object: none207.45.95.0/24No route object for it. A route object for 207.45.80.0/20 with origin AS30462 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30462 in the RIR database for the space.671 of 673
Route object: none207.45.80.0/24No route object for it. A route object for 207.45.80.0/20 with origin AS30462 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30462 in the RIR database for the space.98 of 673
Route object: none207.45.87.0/24No route object for it. A route object for 207.45.80.0/20 with origin AS30462 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30462 in the RIR database for the space.98 of 673

Route objects not announced

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

2602:ffb4::/36ARINValid

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.