Network · data from 2026-11-12
AS22691 ISPnet, Inc.
Registry name: ISPNET-1 - ISPnet, Inc., US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS22691, 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.
| 199.4.220.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 165.254.98.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 165.254.147.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 199.224.0.0/23 | Valid | Other IRR onlyRADB | 673 100% |
| 199.224.13.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 199.224.14.0/23 | Valid | Other IRR onlyRADB | 673 100% |
| 204.141.35.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 204.141.40.0/24 | Valid | Other IRR onlyRADB | 673 100% |
AS-SET
PeeringDB's irr_as_set for AS22691: AS-ISPNET. 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 (AS22691 isn't in the set, or no route object for AS22691 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 | AS22691 in it | Not covered |
|---|---|---|---|---|---|
| AS-ISPNET | RADBlists itself further down | 15 | 19 | 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 24 are in fix.csv.
- ROA: none1
- Route object: RIR8
- Route object: not announced15
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 199.4.220.0/24 | No ROA covers it. Add a ROA for AS22691, maxLength 24. |
| Route object: RIR | 199.4.220.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 165.254.98.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 165.254.147.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 199.224.0.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 199.224.13.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 199.224.14.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 204.141.35.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 204.141.40.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS22691 whose prefix no peer sees AS22691 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 69.48.128.0/18 | RADB | No ROA |
| 74.113.32.0/21 | RADB | No ROA |
| 165.254.66.0/24 | RADB | Valid |
| 165.254.101.0/24 | RADB | Valid |
| 165.254.120.0/24 | RADB | Valid |
| 199.224.1.0/24 | RADB | Valid |
| 199.224.6.0/24 | RADB | Valid |
| 199.224.9.0/24 | RADB | Valid |
| 199.224.12.0/24 | RADB | Valid |
| 199.224.14.0/24 | RADB | Valid |
| 199.224.15.0/24 | RADB | Valid |
| 204.141.36.0/24 | RADB | Valid |
| 207.156.182.0/24 | RADB | Valid |
| 216.44.0.0/22 | RADB | Valid |
| 2610:198::/32 | RADB | 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.