TORONTO
Toronto
Data as of 2026-07-26
GLEIF verified
LEI
969500JAY9JXLWKIW192
Registered name
TORONTO
Jurisdiction
Ultimate parent
No parent on file in GLEIF
Cluster stats
| Netblocks | 1 |
| IPv6 | 1 prefix (largest 2a0a:6040:bf04::/48) |
| All fragments | 88 blocks across 13 clusters |
| Cluster ID | 216225266 |
| Registry | RIPE |
| Owner jurisdiction | FR |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | GLEIF legal-entity match |
| Legal identity | LEI 969500JAY9JXLWKIW192 |
| Shared handles | clustered on 3 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
IP Ranges (1)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 2a0a:6040:bf04::/48 | Toronto | RIPE | ASSIGNED | ● medium |
IPv6 ranges (1)
| CIDR |
|---|
| 2a0a:6040:bf04::/48 |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(1 of 1)
Possible discrepancies (1)
These blocks are registered to Toronto but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 2a0a:6040:bf04::/48 /48 | authorized for AS200255 — TIMEWARP IT Consulting GmbH |
NIC Handles
DUMY-RIPE
DUMY-RIPE
EIZ-MNT