bgpreport

Network · data from 2026-11-12

AS14280 NetNation Communications Inc.

Registry name: NETNATION - Ntirety, Inc., US · PeeringDB

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

Announced routes

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

2606:6a00::/48 No ROA Nonecovered by 2606:6a00::/32 634 100% 67
64.40.105.0/24 No ROA RIR databaseARIN 671 100% 67
66.113.192.0/24 No ROA RIR databaseARIN, RADB 671 100% 67
204.174.223.0/24 No ROA RIR databaseARIN, BELL, RADB 671 100% 67

AS-SET

PeeringDB's irr_as_set for AS14280: RADB::AS-NETNATION. 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 (AS14280 isn't in the set, or no route object for AS14280 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 objectsAS14280 in itNot covered
RADB::AS-NETNATION RADB 7240 Yes 0

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: none4
  • Route object: none1
  • Route object: not announced11
ChangePrefix or setDetailFull-table peers
ROA: none2606:6a00::/48No ROA covers it. Add a ROA for AS14280, maxLength 48.634 of 636
Route object: none2606:6a00::/48No route object for it. A route object for 2606:6a00::/32 with origin AS14280 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14280 in the RIR database for the space.634 of 636
ROA: none64.40.105.0/24No ROA covers it. Add a ROA for AS14280, maxLength 24.671 of 673
ROA: none66.113.192.0/24No ROA covers it. Add a ROA for AS14280, maxLength 24.671 of 673
ROA: none204.174.223.0/24No ROA covers it. Add a ROA for AS14280, maxLength 24.671 of 673

Route objects not announced

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

64.40.96.0/19RADBNo ROA
64.40.96.0/20BELL, RADBNo ROA
64.40.102.0/24RADBNo ROA
64.40.112.0/20RADBNo ROA
64.40.126.0/24RADBNo ROA
64.41.112.0/24RADBNo ROA
64.41.114.0/24RADBNo ROA
66.113.128.0/17RADBNo ROA
2606:6a00::/32ARIN, RADBNo ROA
2606:7e00:4::/48RADBNo ROA
2606:7e00:6::/48RADBNo 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.