bgpreport

Network · data from 2026-11-12

AS398797 Nubesec

Registry name: NUBESEC - Nubesec LLC, US · PeeringDB

1IPv4 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
7Route objects not announced registered with origin AS398797, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS398797, 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.
199.255.148.0/24 Valid RIR databaseARIN 672 100% 67

AS-SET

AS398797's PeeringDB record names no 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 7 are in fix.csv.

  • Route object: not announced7

Route objects not announced

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

199.255.148.0/22ARIN, NTTCOMNo ROA
199.255.148.0/23ARINNo ROA
199.255.149.0/24ARINInvalid: origin
199.255.150.0/23ARINInvalid: origin
199.255.150.0/24ARINInvalid: origin
199.255.151.0/24ARINInvalid: origin
2602:fd1e::/36ARIN, NTTCOMValid

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.