Network · data from 2026-11-12
AS399106 TERIDION2 - Teridion inc
Registry name: TERIDION2 - Teridion inc, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS399106, 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.
| 136.228.23.0/24 | Valid | Other IRR onlyRADB | 673 100% |
AS-SET
AS399106 isn't in PeeringDB, where networks name their 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 9 are in fix.csv.
- Route object: RIR1
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 136.228.23.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS399106 whose prefix no peer sees AS399106 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 136.228.0.0/19 | ARIN | Valid |
| 136.228.17.0/24 | RADB | Valid |
| 136.228.18.0/24 | ARIN, RADB | Valid |
| 136.228.22.0/24 | RADB | Valid |
| 136.228.24.0/24 | RADB | Valid |
| 136.228.25.0/24 | RADB | Valid |
| 136.228.30.0/24 | RADB | Valid |
| 139.60.200.0/21 | 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.