Network · data from 2026-11-12
AS11918 DIALLOGTORONTOCORE - Diallog Telecommunications
Registry name: DIALLOGTORONTOCORE - Diallog Telecommunications, CA · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS11918, 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.
| 66.7.84.0/24 | No ROA | None | 672 100% |
| 23.130.32.0/24 | No ROA | Other IRR onlyBELL | 672 100% |
| 66.7.80.0/24 | No ROA | Other IRR onlyBELL | 672 100% |
| 66.7.81.0/24 | No ROA | Other IRR onlyBELL | 672 100% |
| 66.7.82.0/24 | No ROA | Other IRR onlyBELL | 672 100% |
| 66.7.83.0/24 | No ROA | Other IRR onlyBELL | 672 100% |
| 66.7.94.0/24 | No ROA | Other IRR onlyBELL | 672 100% |
| 66.7.95.0/24 | No ROA | Other IRR onlyBELL | 672 100% |
| 207.167.88.0/22 | No ROA | Other IRR onlyBELL | 672 100% |
AS-SET
AS11918 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 20 are in fix.csv.
- ROA: none9
- Route object: none1
- Route object: RIR8
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 66.7.84.0/24 | No ROA covers it. Add a ROA for AS11918, maxLength 24. |
| Route object: none | 66.7.84.0/24 | No route object for it. Add a route object with origin AS11918 in the RIR database for the space. |
| ROA: none | 23.130.32.0/24 | No ROA covers it. Add a ROA for AS11918, maxLength 24. |
| Route object: RIR | 23.130.32.0/24 | Route object only in BELL. Add it in the RIR database for the space. |
| ROA: none | 66.7.80.0/24 | No ROA covers it. Add a ROA for AS11918, maxLength 24. |
| Route object: RIR | 66.7.80.0/24 | Route object only in BELL. Add it in the RIR database for the space. |
| ROA: none | 66.7.81.0/24 | No ROA covers it. Add a ROA for AS11918, maxLength 24. |
| Route object: RIR | 66.7.81.0/24 | Route object only in BELL. Add it in the RIR database for the space. |
| ROA: none | 66.7.82.0/24 | No ROA covers it. Add a ROA for AS11918, maxLength 24. |
| Route object: RIR | 66.7.82.0/24 | Route object only in BELL. Add it in the RIR database for the space. |
| ROA: none | 66.7.83.0/24 | No ROA covers it. Add a ROA for AS11918, maxLength 24. |
| Route object: RIR | 66.7.83.0/24 | Route object only in BELL. Add it in the RIR database for the space. |
| ROA: none | 66.7.94.0/24 | No ROA covers it. Add a ROA for AS11918, maxLength 24. |
| Route object: RIR | 66.7.94.0/24 | Route object only in BELL. Add it in the RIR database for the space. |
| ROA: none | 66.7.95.0/24 | No ROA covers it. Add a ROA for AS11918, maxLength 24. |
| Route object: RIR | 66.7.95.0/24 | Route object only in BELL. Add it in the RIR database for the space. |
| ROA: none | 207.167.88.0/22 | No ROA covers it. Add a ROA for AS11918, maxLength 22. |
| Route object: RIR | 207.167.88.0/22 | Route object only in BELL. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS11918 whose prefix no peer sees AS11918 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 64.147.64.0/19 | NTTCOM | No ROA |
| 192.157.96.0/19 | BELL | 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.