bgpreport

Network · data from 2026-11-12

AS10930 NOVA-INTERNET - Nova Internet Services, Inc.

Registry name: NOVA-INTERNET - Nova Internet Services, Inc., US · not in PeeringDB

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

Announced routes

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

209.251.224.0/24 Valid RIR databaseARIN, NTTCOM, RADB 672 100% 67
209.251.225.0/24 Valid RIR databaseARIN, NTTCOM, RADB 672 100% 67
209.251.227.0/24 Valid RIR databaseARIN, NTTCOM, RADB 672 100% 67
209.251.228.0/24 Valid RIR databaseARIN, NTTCOM, RADB 672 100% 67
209.251.229.0/24 Valid RIR databaseARIN, NTTCOM, RADB 672 100% 67
209.251.226.0/24 Valid RIR databaseARIN, NTTCOM, RADB 670 100% 67

AS-SET

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

  • Route object: not announced51

Route objects not announced

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

209.251.224.0/19NTTCOM, RADBNo ROA
209.251.224.0/20RADBNo ROA
209.251.224.0/21RADBNo ROA
209.251.224.0/22RADBNo ROA
209.251.224.0/23RADBNo ROA
209.251.226.0/23RADBNo ROA
209.251.228.0/22RADBNo ROA
209.251.228.0/23RADBNo ROA
209.251.230.0/23RADBNo ROA
209.251.230.0/24NTTCOM, RADBNo ROA
209.251.231.0/24NTTCOM, RADBNo ROA
209.251.232.0/21RADBNo ROA
209.251.232.0/22RADBNo ROA
209.251.232.0/23RADBNo ROA
209.251.232.0/24NTTCOM, RADBNo ROA
209.251.233.0/24NTTCOM, RADBNo ROA
209.251.234.0/23RADBNo ROA
209.251.234.0/24NTTCOM, RADBNo ROA
209.251.235.0/24NTTCOM, RADBNo ROA
209.251.236.0/22RADBNo ROA
209.251.236.0/23RADBNo ROA
209.251.236.0/24NTTCOM, RADBNo ROA
209.251.237.0/24NTTCOM, RADBNo ROA
209.251.238.0/23RADBNo ROA
209.251.238.0/24NTTCOM, RADBNo ROA
209.251.239.0/24NTTCOM, RADBNo ROA
209.251.240.0/20RADBNo ROA
209.251.240.0/21RADBNo ROA
209.251.240.0/22RADBNo ROA
209.251.240.0/23RADBNo ROA
209.251.240.0/24NTTCOM, RADBNo ROA
209.251.241.0/24NTTCOM, RADBNo ROA
209.251.242.0/23RADBNo ROA
209.251.242.0/24NTTCOM, RADBNo ROA
209.251.243.0/24NTTCOM, RADBNo ROA
209.251.244.0/22RADBNo ROA
209.251.244.0/23RADBNo ROA
209.251.244.0/24NTTCOM, RADBNo ROA
209.251.246.0/23RADBNo ROA
209.251.246.0/24NTTCOM, RADBNo ROA
209.251.247.0/24NTTCOM, RADBNo ROA
209.251.248.0/21RADBNo ROA
209.251.248.0/22RADBNo ROA
209.251.248.0/23RADBNo ROA
209.251.250.0/23RADBNo ROA
209.251.250.0/24NTTCOM, RADBNo ROA
209.251.251.0/24NTTCOM, RADBNo ROA
209.251.252.0/22RADBNo ROA
209.251.254.0/23RADBNo ROA
209.251.254.0/24NTTCOM, RADBNo ROA
209.251.255.0/24NTTCOM, 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.