bgpreport

Network · data from 2026-11-12

AS401780 NNTC - Nucla Naturita Telephone

Registry name: NNTC - Nucla Naturita Telephone, US · not in PeeringDB

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

Announced routes

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

154.61.151.0/24 No ROA None 673 100% 67
38.106.192.0/24 No ROA None 672 100% 67
38.124.43.0/24 No ROA None 672 100% 67
2602:f9a3:1::/48 No ROA RIR databaseARIN 605 95% 67
169.128.4.0/24 Valid RIR databaseARIN 673 100% 67
169.128.5.0/24 Valid RIR databaseARIN 673 100% 67
169.128.6.0/24 Valid RIR databaseARIN 673 100% 67
169.128.7.0/24 Valid RIR databaseARIN 673 100% 67
2602:f9a3:2::/48 Valid RIR databaseARIN 605 95% 67
2602:f9a3:4::/48 Valid RIR databaseARIN 605 95% 67
2602:f9a3:6::/48 Valid RIR databaseARIN 605 95% 67
2602:f9a3:8::/48 Valid RIR databaseARIN 605 95% 67

AS-SET

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

  • ROA: none4
  • Route object: none3
  • Route object: not announced23
ChangePrefix or setDetailFull-table peers
ROA: none154.61.151.0/24No ROA covers it. Add a ROA for AS401780, maxLength 24.673 of 673
Route object: none154.61.151.0/24No route object for it. Add a route object with origin AS401780 in the RIR database for the space.673 of 673
ROA: none38.106.192.0/24No ROA covers it. Add a ROA for AS401780, maxLength 24.672 of 673
Route object: none38.106.192.0/24No route object for it. Add a route object with origin AS401780 in the RIR database for the space.672 of 673
ROA: none38.124.43.0/24No ROA covers it. Add a ROA for AS401780, maxLength 24.672 of 673
Route object: none38.124.43.0/24No route object for it. Add a route object with origin AS401780 in the RIR database for the space.672 of 673
ROA: none2602:f9a3:1::/48No ROA covers it. Add a ROA for AS401780, maxLength 48.605 of 636

Route objects not announced

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

169.128.4.0/22ARINNo ROA
2602:f9a3::/48ARINValid
2602:f9a3:3::/48ARINValid
2602:f9a3:5::/48ARINValid
2602:f9a3:7::/48ARINValid
2602:f9a3:9::/48ARINValid
2602:f9a3:a::/48ARINValid
2602:f9a3:b::/48ARINValid
2602:f9a3:c::/48ARINValid
2602:f9a3:d::/48ARINValid
2602:f9a3:e::/48ARINValid
2602:f9a3:f::/48ARINValid
2602:f9a3:10::/48ARINValid
2602:f9a3:11::/48ARINValid
2602:f9a3:12::/48ARINValid
2602:f9a3:13::/48ARINValid
2602:f9a3:14::/48ARINValid
2602:f9a3:15::/48ARINValid
2602:f9a3:16::/48ARINValid
2602:f9a3:17::/48ARINValid
2602:f9a3:18::/48ARINValid
2602:f9a3:19::/48ARINValid
2602:f9a3:20::/48ARINValid

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.