Lambda Telecom
Cluster stats
| Netblocks | 16 |
| All fragments | 107 blocks across 13 clusters |
| Cluster ID | 191653923 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 14 shared RIR contact/maintainer handles |
| Registry names | 7 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
2 weekly snapshots · JSON
16
0 netblocks since 2026-07-05
2026-07-05
peak 16
2026-07-06
IP Ranges (16)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 192.51.248.0/24 | LAMBDA-NET1 | APNIC | ASSIGNED PORTABLE | ● high |
| 192.51.249.0/24 | LAMBDA-NET2 | APNIC | ASSIGNED PORTABLE | ● high |
| 192.77.144.0/24 | Lambda Telecom | BGP | ANNOUNCED | ● high |
| 192.152.115.0/24 | Lambda Telecom | BGP | ANNOUNCED | ● high |
| 192.206.124.0/24 | Lambda Telecom | BGP | ANNOUNCED | ● high |
| 198.49.251.0/24 | Lambda Telecom | BGP | ANNOUNCED | ● high |
| 198.178.225.0/24 | Lambda Telecom | BGP | ANNOUNCED | ● high |
| 198.183.206.0/23 | Lambda Telecom | BGP | ANNOUNCED | ● high |
| 198.183.208.0/23 | Lambda Telecom | BGP | ANNOUNCED | ● high |
| 206.51.7.90/32 | Lambda AI | PEERINGDB | ASSIGNED | ● high |
| 206.51.7.181/32 | Lambda AI | PEERINGDB | ASSIGNED | ● high |
| 2001:504:1b:1::90/128 | Lambda AI | PEERINGDB | ASSIGNED | ● high |
| 2001:504:1b:1::181/128 | Lambda AI | PEERINGDB | ASSIGNED | ● high |
| 80.124.197.0/28 | LAMBDA_TELECOM | RIPE | ASSIGNED PA | ● low |
| 86.65.157.120/29 | LAMBDA-TELECOM | RIPE | ASSIGNED PA | ● low |
| 91.83.51.24/29 | Lambda-Com | RIPE | ASSIGNED PA | ● low |
Network trust
what's this?
RPKI hygiene: D
how networks compare →
43.8%
of checked blocks have valid RPKI ROA coverage
(7 of 16)
No discrepancies found among checked blocks.
NIC Handles
AJ382-AP
APNIC-HM
AS11588
AS12301-MNT
AS6950
CEGETEL-ENTREPRISES
DUMY-RIPE
DUMY-RIPE
HO58-AP
HO58-AP
LDCOM-MNT
LDCOM-PRO-MNT
+2 more