Network · data from 2026-11-12
AS2901 Oso Grande Technologies
Registry name: OGT-AS - Oso Grande Technologies, Inc., US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS2901, 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.
| 208.64.94.0/24 | Invalid: origin | None | 3 0%low visibility |
| 192.160.144.0/24 | No ROA | Other IRR onlyRADB | 670 100% |
| 198.59.96.0/19 | No ROA | Other IRR onlyRADB | 670 100% |
| 192.133.99.0/24 | Valid | RIR databaseARIN, RADB | 670 100% |
| 192.150.253.0/24 | Valid | RIR databaseARIN, RADB | 670 100% |
| 198.49.160.0/24 | Valid | RIR databaseARIN, RADB | 670 100% |
| 198.59.96.0/24 | Valid | RIR databaseARIN | 670 100% |
| 198.59.98.0/23 | Valid | RIR databaseARIN | 670 100% |
| 198.59.100.0/22 | Valid | RIR databaseARIN | 670 100% |
| 198.59.104.0/23 | Valid | RIR databaseARIN | 670 100% |
| 198.59.109.0/24 | Valid | RIR databaseARIN | 670 100% |
| 198.59.110.0/23 | Valid | RIR databaseARIN | 670 100% |
| 198.59.112.0/23 | Valid | RIR databaseARIN | 670 100% |
| 198.59.114.0/24 | Valid | RIR databaseARIN | 670 100% |
| 198.59.116.0/23 | Valid | RIR databaseARIN | 670 100% |
| 198.59.118.0/23 | Valid | RIR databaseARIN | 670 100% |
| 198.59.120.0/21 | Valid | RIR databaseARIN | 670 100% |
| 205.166.226.0/24 | Valid | RIR databaseARIN | 670 100% |
| 2605:800::/32 | Valid | RIR databaseARIN | 635 100% |
| 2620:44:a000::/48 | Valid | RIR databaseARIN | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS2901: RS-OGT. 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 (AS2901 isn't in the set, or no route object for AS2901 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 | AS2901 in it | Not covered | |
|---|---|---|---|---|---|---|
| RS-OGT | A route-set, not an AS-SET; route-sets aren't expanded. | |||||
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: origin1
- ROA: none2
- Route object: none1
- Route object: RIR2
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 208.64.94.0/24 | ROAs covering it name AS11996, not AS2901. If AS2901 should announce it, add a ROA for AS2901. |
| Route object: none | 208.64.94.0/24 | No route object for it. Add a route object with origin AS2901 in the RIR database for the space. |
| ROA: none | 192.160.144.0/24 | No ROA covers it. Add a ROA for AS2901, maxLength 24. |
| Route object: RIR | 192.160.144.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 198.59.96.0/19 | No ROA covers it. Add a ROA for AS2901, maxLength 19. |
| Route object: RIR | 198.59.96.0/19 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS2901 whose prefix no peer sees AS2901 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 198.187.251.0/24 | ARIN | Valid |
| 2001:470:298::/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.