Network · data from 2026-11-12
AS112 DNS-OARC-112
Registry name: AS112-PROJECT - DNS-OARC, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS112, 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.
| 192.31.196.1/32 | Invalid: maxLength | Nonecovered by 192.31.196.0/24 | 2 0%low visibility |
| 192.175.48.1/32 | Invalid: maxLength | Nonecovered by 192.175.48.0/24 | 2 0%low visibility |
| 192.175.48.6/32 | Invalid: maxLength | Nonecovered by 192.175.48.0/24 | 2 0%low visibility |
| 192.175.48.42/32 | Invalid: maxLength | Nonecovered by 192.175.48.0/24 | 2 0%low visibility |
| 192.175.48.0/24 | Valid | RIR databaseALTDB, ARIN, NTTCOM, RADB, RIPE-NONAUTH | 670 100% |
| 192.31.196.0/24 | Valid | RIR databaseARIN, NTTCOM, RADB, RIPE-NONAUTH | 664 99% |
| 2620:4f:8000::/48 | Valid | RIR databaseARIN, RADB, RIPE-NONAUTH | 633 100% |
| 2001:4:112::/48 | Valid | RIR databaseARIN, NTTCOM, RADB, RIPE-NONAUTH | 621 98% |
AS-SET
PeeringDB's irr_as_set for AS112: AS112. 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 (AS112 isn't in the set, or no route object for AS112 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 | AS112 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS112 | A single AS number, not a set: AS112 (this network), 4 route objects. | |||||
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 8 are in fix.csv.
- ROA: maxLength4
- Route object: none4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 192.31.196.1/32 | ROA 192.31.196.0/24 AS112 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 192.31.196.1/32. |
| Route object: none | 192.31.196.1/32 | No route object for it. A route object for 192.31.196.0/24 with origin AS112 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS112 in the RIR database for the space. |
| ROA: maxLength | 192.175.48.1/32 | ROA 192.175.48.0/24 AS112 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 192.175.48.1/32. |
| Route object: none | 192.175.48.1/32 | No route object for it. A route object for 192.175.48.0/24 with origin AS112 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS112 in the RIR database for the space. |
| ROA: maxLength | 192.175.48.6/32 | ROA 192.175.48.0/24 AS112 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 192.175.48.6/32. |
| Route object: none | 192.175.48.6/32 | No route object for it. A route object for 192.175.48.0/24 with origin AS112 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS112 in the RIR database for the space. |
| ROA: maxLength | 192.175.48.42/32 | ROA 192.175.48.0/24 AS112 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 192.175.48.42/32. |
| Route object: none | 192.175.48.42/32 | No route object for it. A route object for 192.175.48.0/24 with origin AS112 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS112 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS112 is announced.
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.