Network · data from 2026-11-12
AS398482 Schneider's Computing
Registry name: SCHNEIDERS-COMPUTING-LTD - Schneider's Computing Ltd., CA · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS398482, 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.135.88.0/24 | No ROA | RIR databaseARIN | 671 100% |
| 209.59.255.0/24 | No ROA | RIR databaseARIN, RADB | 671 100% |
AS-SET
PeeringDB's irr_as_set for AS398482: ARIN::AS-SCL-544. 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 (AS398482 isn't in the set, or no route object for AS398482 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 | AS398482 in it | Not covered |
|---|---|---|---|---|---|
| ARIN::AS-SCL-544 | ARIN | 1 | 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 4 are in fix.csv.
- ROA: none2
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 23.135.88.0/24 | No ROA covers it. Add a ROA for AS398482, maxLength 24. |
| ROA: none | 209.59.255.0/24 | No ROA covers it. Add a ROA for AS398482, maxLength 24. |
Route objects not announced
Route objects with origin AS398482 whose prefix no peer sees AS398482 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 207.174.92.0/23 | ARIN | No ROA |
| 2602:fbe4::/36 | ARIN | No ROA |
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.