BEAM TELECOM
Data as of 2026-08-16
BGP inherited
Limited data: only 3 ranges found registered
under this exact name. This may not reflect the organisation's full internet footprint — many companies'
web and cloud infrastructure is hosted under a third-party provider's own registration rather than their own.
Cluster stats
| Netblocks | 3 · 1,025 IPv4 addresses |
| IPv6 | 1 prefix (largest 2001:12f8:0:37::9/128) |
| Cluster ID | 222470656 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 6 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
Footprint over time
2 weekly snapshots · JSON
82
0 netblocks since 2026-07-13
2026-07-13
peak 82
2026-07-19
IP Ranges (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 200.219.143.9/32 | BEAM TELECOM | PEERINGDB | ASSIGNED | ● high |
| 2001:12f8:0:37::9/128 | BEAM TELECOM | PEERINGDB | ASSIGNED | ● high |
| 45.191.120.0/22 | BEAM TELECOM IMP EXP LTDA | ARIN | ALLOCATED | ● low |
IPv6 ranges (1)
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(3 of 3)
Possible discrepancies (1)
These blocks are registered to BEAM TELECOM 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.
| 45.191.120.0/22 /22 | authorized for AS269681 — AS269681 |
NIC Handles
34611001000194
AS269681
IRMHE5
IRMHE5
IRMHE5
p43