bgpreport

Network · data from 2026-11-12

AS396904 QualiSpace

Registry name: QUALISPACE-ASN - QualiSpace Inc, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS396904, 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.
23.226.125.0/24 Invalid: origin RIR databaseARIN 1 0%low visibility 1
23.226.120.0/24 Valid RIR databaseARIN 673 100% 66
23.226.124.0/24 Valid RIR databaseARIN 673 100% 66
23.226.126.0/24 Valid RIR databaseARIN 673 100% 66
23.226.127.0/24 Valid RIR databaseARIN 673 100% 66
103.14.96.0/24 Valid RIR databaseAPNIC 672 100% 66
103.14.97.0/24 Valid RIR databaseAPNIC 672 100% 66
103.14.99.0/24 Valid RIR databaseAPNIC 672 100% 66
103.14.98.0/24 Valid RIR databaseAPNIC 661 98% 66

AS-SET

AS396904'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 1 are in fix.csv.

  • ROA: origin1
ChangePrefix or setDetailFull-table peers
ROA: origin23.226.125.0/24ROAs covering it name AS29802, not AS396904. If AS396904 should announce it, add a ROA for AS396904.1 of 673

Route objects not announced

Every route object with origin AS396904 is announced.

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.