bgpreport

Network · data from 2026-11-12

AS402270 SOFTERYX-INC

Registry name: SOFTERYX-INC - Softeryx, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS402270, 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.
2a0f:9400:6800::/40 Invalid: origin RIR databaseRIPE 23 4%low visibility 19
2602:f36a::/40 Valid RIR databaseARIN 1 0%low visibility 1

AS-SET

AS402270'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 2 are in fix.csv.

  • ROA: origin1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin2a0f:9400:6800::/40ROAs covering it name AS53356, not AS402270. If AS402270 should announce it, add a ROA for AS402270.23 of 636

Route objects not announced

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

2a06:9801:900::/40RIPEValid

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.