TELEMAN

Data as of 2026-10-11
BGP inherited
This organisation
Netblocks16 · 584 IPv4 addresses
Record ID245588245
RegistryRIPE
Customerssee who runs inside 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 · report an issue

IP Ranges (16)

⬇ export CSV
CIDR Org name Registry Status Confidence
77.74.107.0/28 TELEMAN RIPE ASSIGNED PA ● low
77.74.107.16/30 TELEMAN RIPE ASSIGNED PA ● low
77.74.107.20/30 TELEMAN RIPE ASSIGNED PA ● low
77.74.107.96/28 TELEMAN RIPE ASSIGNED PA ● low
77.74.111.0/27 TELEMAN RIPE ASSIGNED PA ● low
78.40.144.0/26 TELEMAN RIPE ASSIGNED PA ● low
78.40.144.72/30 TELEMAN RIPE ASSIGNED PA ● low
78.40.144.160/27 TELEMAN RIPE ASSIGNED PA ● low
78.40.144.192/26 TELEMAN RIPE ASSIGNED PA ● low
78.40.145.0/27 TELEMAN RIPE ASSIGNED PA ● low
78.40.145.96/28 TELEMAN RIPE ASSIGNED PA ● low
78.40.148.16/31 TELEMAN RIPE ASSIGNED PA ● low
78.40.150.176/29 TELEMAN RIPE ASSIGNED PA ● low
80.84.81.96/27 TELEMAN RIPE ASSIGNED PA ● low
80.84.88.0/24 TELEMAN RIPE ASSIGNED PA ● low
80.84.92.18/31 TELEMAN RIPE ASSIGNED PA ● low

Footprint over time

16 weekly snapshots · JSON
16 0 netblocks since 2026-07-05
2026-07-05 peak 16 2026-10-11

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (16 of 16)
Possible discrepancies (1)

These blocks are registered to TELEMAN 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.

80.84.88.0/24 /24 authorized for AS43545 — Teledata UK Limited

NIC Handles

DUMY-RIPE DUMY-RIPE MNT-TELE