Network · data from 2026-11-12
AS26329 InServer Networks
Registry name: INSERVER-NETWORKS - InServer Networks, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS26329, 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.
| 2604:6b00::/48 | No ROA | Nonecovered by 2604:6b00::/32 | 635 100% |
| 208.80.88.0/24 | Valid | RIR databaseARIN | 671 100% |
| 64.207.192.0/24 | Valid | RIR databaseARIN, RADB | 670 100% |
| 64.207.193.0/24 | Valid | RIR databaseARIN | 668 99% |
| 208.80.90.0/24 | Valid | RIR databaseARIN | 2 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS26329: AS26329:AS-PEERS. 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 (AS26329 isn't in the set, or no route object for AS26329 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 | AS26329 in it | Not covered |
|---|---|---|---|---|---|
| AS26329:AS-PEERS | ARIN | 2 | 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 9 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2604:6b00::/48 | No ROA covers it. Add a ROA for AS26329, maxLength 48. |
| Route object: none | 2604:6b00::/48 | No route object for it. A route object for 2604:6b00::/32 with origin AS26329 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26329 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS26329 whose prefix no peer sees AS26329 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 64.207.192.0/22 | ARIN | Valid |
| 64.207.194.0/24 | RADB | Valid |
| 64.207.195.0/24 | ARIN, RADB | Valid |
| 208.80.88.0/22 | ARIN | Valid |
| 208.80.89.0/24 | ARIN | Valid |
| 208.80.91.0/24 | ARIN | Valid |
| 2604:6b00::/32 | 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.