bgpreport

Network · data from 2026-11-12

AS14401 SolidNetwork Technologies, Inc.

Registry name: SOLIDNETWORK-AS-02 - SolidNetwork Technologies, Inc., US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS14401, 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.
140.235.228.0/22 Invalid: origin Other origin only 1 0%low visibility 1
74.123.244.0/22 Valid RIR databaseARIN 671 100% 68
104.247.88.0/24 Valid RIR databaseARIN 671 100% 68
104.247.89.0/24 Valid RIR databaseARIN 671 100% 68
104.247.90.0/23 Valid RIR databaseARIN 671 100% 68
140.235.230.0/23 Valid RIR databaseARIN 671 100% 68
2607:6880::/32 Valid RIR databaseARIN 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS14401: ARIN::AS14401:AS-SOLIDNETWORK. 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 (AS14401 isn't in the set, or no route object for AS14401 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 objectsAS14401 in itNot covered
ARIN::AS14401:AS-SOLIDNETWORK ARIN 6350 Yes 1

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

  • ROA: origin1
  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin140.235.228.0/22ROAs covering it name AS1299, not AS14401. If AS14401 should announce it, add a ROA for AS14401.1 of 673
Route object: none140.235.228.0/22Route objects for it name AS1299. Add a route object with origin AS14401 in the RIR database for the space.1 of 673

Route objects not announced

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

2001:470:12b::/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.