TNS-Plus LLP
BGP inherited
Cluster stats
| Netblocks | 32 · 4,874 IPv4 addresses |
| Registered in | KZ (14) · Russia (6) · Germany (1) |
| Cluster ID | 208794223 |
| Registry | BGP |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 12 shared RIR contact/maintainer handles |
| Registry names | 6 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (32)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 46.227.186.0/24 | TNS-Plus LLP | BGP | ANNOUNCED | ● high |
| 46.227.187.0/24 | TNS-Plus LLP | BGP | ANNOUNCED | ● high |
| 46.227.188.0/24 | TNS-Plus LLP | BGP | ANNOUNCED | ● high |
| 46.227.189.0/24 | TNS-Plus LLP | BGP | ANNOUNCED | ● high |
| 80.81.192.220/32 | TNS-Plus Core | PEERINGDB | ASSIGNED | ● high |
| 89.38.164.0/24 | TNS-Plus LLP | BGP | ANNOUNCED | ● high |
| 89.38.164.0/22 | TNS-Plus LLP | RIPE | ALLOCATED PA | ● high |
| 89.38.164.0/22 | TNS-Plus LLP | BGP | ANNOUNCED | ● high |
| 89.38.166.0/24 | TNS-Plus LLP | BGP | ANNOUNCED | ● high |
| 89.38.167.0/24 | TNS-Plus LLP | BGP | ANNOUNCED | ● high |
| 89.42.206.0/23 | TNS-Plus LLP | BGP | ANNOUNCED | ● high |
| 185.79.213.14/32 | TNS-Plus Core | PEERINGDB | ASSIGNED | ● high |
| 195.208.208.63/32 | TNS-Plus Core | PEERINGDB | ASSIGNED | ● high |
| 195.208.208.204/32 | TNS-Plus Core | PEERINGDB | ASSIGNED | ● high |
| 195.208.209.116/32 | TNS-Plus Core | PEERINGDB | ASSIGNED | ● high |
| 195.208.209.220/32 | TNS-Plus Core | PEERINGDB | ASSIGNED | ● high |
| 195.208.210.104/32 | TNS-Plus Core | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8::8960:0:1/128 | TNS-Plus Core | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:20:101::208:63/128 | TNS-Plus Core | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:20:101::208:204/128 | TNS-Plus Core | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:20:101::209:116/128 | TNS-Plus Core | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:20:101::209:220/128 | TNS-Plus Core | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:20:101::210:104/128 | TNS-Plus Core | PEERINGDB | ASSIGNED | ● high |
| 2a01:68c0::/32 | TNS-Plus LLP | BGP | ANNOUNCED | ● high |
| 2a01:7640:9400::14/128 | TNS-Plus Core | PEERINGDB | ASSIGNED | ● high |
| 2a01:b0c0:1101::/48 | TNS-Plus LLP | BGP | ANNOUNCED | ● high |
| 82.200.159.52/30 | TNS_Plus | RIPE | ASSIGNED PA | ● low |
| 89.42.206.0/23 | TNS-Plus LLP | RIPE | ALLOCATED PA | ● low |
| 92.47.62.72/30 | TNS_Plus | RIPE | ASSIGNED PA | ● low |
| 178.16.155.16/28 | TNS-LAN | RIPE | ASSIGNED PA | ● low |
| 2a01:68c0::/29 | TNS-Plus LLP | RIPE | ALLOCATED-BY-RIR | ● low |
| 2a04:bc40:ffff::/48 | TNS-IPV6 | RIPE | ALLOCATED-BY-LIR | ● low |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
65.6%
of checked blocks have valid RPKI ROA coverage
(21 of 32)
No discrepancies found among checked blocks.
NIC Handles
AS35168
AS35168
ATOM-MNT
DUMY-RIPE
DUMY-RIPE
KNIC-MNT
OBIT-MNT
ORG-TL194-RIPE
RIPE-NCC-HM-MNT
VM24770-MNT
VM24770-MNT
kz-ipnet-kar-tel-1-mnt