Network · data from 2026-11-12
AS395047 Artix Networks LLC
Registry name: ARTIX-NET - Artix Networks LLC, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS395047, 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:61a0::/44 | No ROA | RIR databaseRIPE | 634 100% |
| 202.155.148.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 14.137.241.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 82.115.9.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 23.134.20.0/24 | Valid | RIR databaseARIN | 670 100% |
| 2602:f6f8::/40 | Valid | RIR databaseARIN | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS395047: AS395047:AS-ALL. 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 (AS395047 isn't in the set, or no route object for AS395047 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.
| Name | Database | ASNs | Sets | AS395047 in it | Not covered |
|---|---|---|---|---|---|
| AS395047:AS-ALL | RADB | 6 | 1 | Yes | 0 |
| ARIN (also) | 6 | 1 | Yes | 0 |
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 6 are in fix.csv.
- ROA: none1
- Route object: RIR2
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2a0f:9400:61a0::/44 | No ROA covers it. Add a ROA for AS395047, maxLength 44. |
| Route object: RIR | 202.155.148.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 14.137.241.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS395047 whose prefix no peer sees AS395047 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.238.131.0/24 | RADB | Valid |
| 2001:470:45b::/48 | ARIN | Valid |
| 2001:470:45c::/48 | ARIN | Valid |
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.