TANGRAM CANADA INC
TANGRAM-CANADA-NL2-SERVERIUS-2-3
BGP inherited
Cluster stats
| Netblocks | 1 |
| All fragments | 5 blocks across 5 clusters |
| Cluster ID | 205105997 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| 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 | |
IP Ranges (1)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 109.72.145.224/28 | TANGRAM-CANADA-NL2-SERVERIUS-2-3 | RIPE | ASSIGNED PA | ● medium |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “TANGRAM CANADA NL2 SERVERIUS 2” — often
per-country or per-system registrations of the same brand, occasionally a different
organisation sharing the name. Not counted in this organisation's own footprint.
- TANGRAM-CANADA-NL2-SERVERIUS-2-1 1 blocks
- TANGRAM-CANADA-NL2-SERVERIUS-2-5 1 blocks
- TANGRAM-CANADA-NL2-SERVERIUS-2-4 1 blocks
- TANGRAM-CANADA-NL2-SERVERIUS-2-2 1 blocks
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own
naming convention, not a direct registration.
- TANGRAM-CANADA-NL3-SERVERIUS-1 sub-allocation
- TANGRAM-CANADA-NL-SERVERIUS-3-1 sub-allocation
- TANGRAM-CANADA-NL-SERVERIUS-2-1 sub-allocation
- TANGRAM-CANADA-NL-SERVERIUS-4-1 sub-allocation
- TANGRAM-CANADA-NL-SERVERIUS-1-3 sub-allocation
- TANGRAM-CANADA-NL-SERVERIUS-1-4 sub-allocation
- TANGRAM-CANADA-NL2-SERVERIUS-2-1 sub-allocation
- TANGRAM-CANADA-NL-SERVERIUS-1-1 sub-allocation
NIC Handles
DUMY-RIPE
DUMY-RIPE
TANGRAMCA-MNT