Network · data from 2026-11-12
AS15261 ZT - Zellius Telecommunications Inc.
Registry name: ZT - Zellius Telecommunications Inc., PR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS15261, 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.
| 162.222.108.0/24 | Valid | Nonecovered by 162.222.108.0/22 | 667 99% |
| 162.222.110.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 162.222.111.0/24 | Valid | Other IRR onlyRADB | 673 100% |
AS-SET
AS15261 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 6 are in fix.csv.
- Route object: none1
- Route object: RIR2
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 162.222.108.0/24 | No route object for it. A route object for 162.222.108.0/22 with origin AS15261 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15261 in the RIR database for the space. |
| Route object: RIR | 162.222.110.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 162.222.111.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS15261 whose prefix no peer sees AS15261 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 67.230.89.0/24 | RADB | No ROA |
| 69.89.36.0/24 | RADB | No ROA |
| 162.222.108.0/22 | RADB | No ROA |
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.