TeamViewer-DE
BGP inherited
Cluster stats
| Netblocks | 8 · 600 IPv4 addresses |
| All fragments | 9 blocks across 2 clusters |
| Cluster ID | 211200362 |
| 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 (8)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 185.245.28.0/24 | TeamViewer-DE | RIPE | LIR-PARTITIONED PA | ● low |
| 185.245.29.32/28 | TeamViewer-DE | RIPE | LIR-PARTITIONED PA | ● low |
| 185.245.29.64/28 | TeamViewer-DE | RIPE | LIR-PARTITIONED PA | ● low |
| 185.245.29.96/28 | TeamViewer-DE | RIPE | LIR-PARTITIONED PA | ● low |
| 185.245.29.112/28 | TeamViewer-DE | RIPE | LIR-PARTITIONED PA | ● low |
| 185.245.29.144/28 | TeamViewer-DE | RIPE | LIR-PARTITIONED PA | ● low |
| 185.245.29.176/28 | TeamViewer-DE | RIPE | LIR-PARTITIONED PA | ● low |
| 185.245.30.0/24 | TeamViewer-DE | RIPE | LIR-PARTITIONED PA | ● low |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “TeamViewer DE” — 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.
- TeamViewer-DE-GP 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.
- Teamviewer1 sub-allocation
- GNC-TEAMVIEWER-MONITIS via GNC-Alfa CJSC sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(8 of 8)
No discrepancies found among checked blocks.
NIC Handles
DUMY-RIPE
DUMY-RIPE
de-teamviewer-1-mnt