Network · data from 2026-11-12
AS33693 TierPoint Wisconsin
Registry name: AS-TIERP-33693 - TierPoint, LLC, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS33693, 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.
| 64.157.123.0/24 | No ROA | Other IRR onlyRADB | 669 99% |
AS-SET
AS33693'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 6 are in fix.csv.
- ROA: none1
- Route object: RIR1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 64.157.123.0/24 | No ROA covers it. Add a ROA for AS33693, maxLength 24. |
| Route object: RIR | 64.157.123.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS33693 whose prefix no peer sees AS33693 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 38.119.157.0/24 | ALTDB | No ROA |
| 198.185.12.0/24 | ALTDB | No ROA |
| 198.185.15.0/24 | ALTDB | No ROA |
| 2607:fc38::/32 | ALTDB | Invalid: origin |
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.