TYNTEC LIMITED
tyntec GmbH
GLEIF verified
LEI
391200K13ZW9ZYE55Y96
Registered name
TYNTEC LIMITED
Jurisdiction
Ultimate parent
No parent on file in GLEIF
Cluster stats
| Netblocks | 31 · 18,686 IPv4 addresses |
| Registered in | Germany (15) · Netherlands (2) · KH (1) · Poland (1) |
| Cluster ID | 208803936 |
| Registry | BGP |
| Owner jurisdiction | GB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | GLEIF legal-entity match |
| Legal identity | LEI 391200K13ZW9ZYE55Y96 |
| Shared handles | clustered on 10 shared RIR contact/maintainer handles |
| Registry names | 4 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
5 weekly snapshots · JSON
31
0 netblocks since 2026-07-05
2026-07-05
peak 31
2026-07-19
IP Ranges (31)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 78.110.224.0/21 | tyntec GmbH | BGP | ANNOUNCED | ● high |
| 78.110.224.0/20 | tyntec GmbH | BGP | ANNOUNCED | ● high |
| 78.110.232.0/21 | tyntec GmbH | BGP | ANNOUNCED | ● high |
| 78.110.234.0/24 | tyntec GmbH | BGP | ANNOUNCED | ● high |
| 80.81.197.13/32 | tyntec | PEERINGDB | ASSIGNED | ● high |
| 80.81.197.26/32 | tyntec | PEERINGDB | ASSIGNED | ● high |
| 80.249.214.209/32 | tyntec | PEERINGDB | ASSIGNED | ● high |
| 80.249.214.227/32 | tyntec | PEERINGDB | ASSIGNED | ● high |
| 103.7.144.79/32 | tyntec | PEERINGDB | ASSIGNED | ● high |
| 178.23.24.0/21 | tyntec GmbH | BGP | ANNOUNCED | ● high |
| 178.23.24.0/22 | tyntec GmbH | BGP | ANNOUNCED | ● high |
| 178.23.28.0/22 | tyntec GmbH | BGP | ANNOUNCED | ● high |
| 185.1.170.173/32 | tyntec | PEERINGDB | ASSIGNED | ● high |
| 185.1.171.21/32 | tyntec | PEERINGDB | ASSIGNED | ● high |
| 194.146.118.61/32 | tyntec | PEERINGDB | ASSIGNED | ● high |
| 194.146.118.62/32 | tyntec | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8::aa2e:0:1/128 | tyntec | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8::aa2e:0:2/128 | tyntec | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:1::a504:3566:1/128 | tyntec | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:1::a504:3566:2/128 | tyntec | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:8::aa2e:0:1/128 | tyntec | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:8::aa2e:0:2/128 | tyntec | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:9e::aa2e:0:1/128 | tyntec | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:9e::aa2e:0:2/128 | tyntec | PEERINGDB | ASSIGNED | ● high |
| 2a11:7f80::/33 | tyntec GmbH | BGP | ANNOUNCED | ● high |
| 2a11:7f80::/32 | tyntec GmbH | BGP | ANNOUNCED | ● high |
| 2a11:7f80:8000::/33 | tyntec GmbH | BGP | ANNOUNCED | ● high |
| 78.110.224.0/20 | tyntec GmbH | RIPE | ALLOCATED PA | ● medium |
| 178.23.24.0/21 | tyntec GmbH | RIPE | ALLOCATED PA | ● medium |
| 2a11:7f80::/32 | tyntec GmbH | RIPE | ALLOCATED-BY-RIR | ● medium |
| 217.149.249.0/29 | Tyntec-NET | RIPE | ASSIGNED PA | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
96.8%
of checked blocks have valid RPKI ROA coverage
(30 of 31)
No discrepancies found among checked blocks.
NIC Handles
AS43566
AS43566
ATMAN-MNT
DUMY-RIPE
DUMY-RIPE
ORG-TG32-RIPE
RIPE-NCC-HM-MNT
TynTec_Maintainer
TynTec_Maintainer
Tyntec_Maintainer