Network · data from 2026-11-12
AS197170 TECHTIES-AS
Registry name: TECHTIES-AS TechTies Inc., SC · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS197170, 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.
| 85.11.167.0/24 | Valid | Other origin only | 665 99% |
| 93.152.221.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 94.26.106.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.245.62.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.245.63.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 91.92.42.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 91.92.47.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 87.121.84.0/24 | Valid | RIR databaseRIPE | 665 99% |
| 91.92.40.0/24 | Valid | RIR databaseRIPE | 665 99% |
| 176.65.132.0/24 | Valid | RIR databaseRIPE | 665 99% |
| 45.153.34.0/24 | Valid | RIR databaseRIPE | 664 99% |
| 45.156.87.0/24 | Valid | RIR databaseRIPE | 663 99% |
| 2a0f:ca80:b00b::/48 | Valid | RIR databaseRIPE | 631 99% |
AS-SET
AS197170's PeeringDB record names no AS-SET.
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 3 are in fix.csv.
- Route object: none1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 85.11.167.0/24 | Route objects for it name AS209630. Add a route object with origin AS197170 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS197170 whose prefix no peer sees AS197170 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 109.160.32.0/24 | RIPE | Valid |
| 163.5.200.0/24 | RIPE | 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.