Network · data from 2026-11-12
AS39959 AS-INTERNEXE-1 - iTeract inc.
Registry name: AS-INTERNEXE-1 - iTeract inc., CA · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS39959, 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.
| 148.59.220.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 148.59.221.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 192.81.12.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 192.81.13.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 192.81.14.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 192.81.15.0/24 | Valid | Other IRR onlyRADB | 670 100% |
AS-SET
AS39959 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 8 are in fix.csv.
- Route object: RIR6
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 148.59.220.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 148.59.221.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 192.81.12.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 192.81.13.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 192.81.14.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 192.81.15.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS39959 whose prefix no peer sees AS39959 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 148.59.220.0/23 | ARIN | Valid |
| 192.81.12.0/22 | ARIN, RADB | 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.