Leaptel
Data as of 2026-09-27
Registry
This organisation
| Netblocks | 122 · 21,009 IPv4 addresses |
| IPv6 | 48 prefixes (largest 2400:a840::/28) |
| Registered in | Australia (86) · New Zealand (1) |
| Also registered under this name | 143 netblocks across 2 separate records |
| Record ID | 245538385 |
| Registry | APNIC |
| Customers | see who runs inside this network → |
Evidence & provenance ?
| Attribution | Registry record |
| Shared handles | clustered on 8 shared RIR contact/maintainer handles |
| Registry names | 3 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
IP Ranges (122)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 27.106.192.40/32 | Leaptel | PEERINGDB | ASSIGNED | ● high |
| 43.243.21.139/32 | Leaptel | PEERINGDB | ASSIGNED | ● high |
| 45.127.172.238/32 | Leaptel | PEERINGDB | ASSIGNED | ● high |
| 45.249.116.0/23 | Leaptel | BGP | ANNOUNCED | ● high |
| 45.249.116.0/22 | Leaptel | BGP | ANNOUNCED | ● high |
| 45.249.118.0/23 | Leaptel | BGP | ANNOUNCED | ● high |
| 66.203.240.0/22 | Leaptel | BGP | ANNOUNCED | ● high |
| 66.203.240.0/21 | Leaptel | BGP | ANNOUNCED | ● high |
| 66.203.240.0/23 | Leaptel | BGP | ANNOUNCED | ● high |
| 66.203.244.0/22 | Leaptel | BGP | ANNOUNCED | ● high |
| 103.26.68.194/32 | Leaptel | PEERINGDB | ASSIGNED | ● high |
| 103.26.70.91/32 | Leaptel | PEERINGDB | ASSIGNED | ● high |
| 103.26.71.89/32 | Leaptel | PEERINGDB | ASSIGNED | ● high |
| 103.51.112.0/23 | Leaptel | BGP | ANNOUNCED | ● high |
| 103.51.112.0/22 | Leaptel | BGP | ANNOUNCED | ● high |
| 103.51.114.0/23 | Leaptel | BGP | ANNOUNCED | ● high |
| 103.85.36.0/22 | Leaptel | BGP | ANNOUNCED | ● high |
| 103.85.36.0/23 | Leaptel | BGP | ANNOUNCED | ● high |
| 103.85.38.0/23 | Leaptel | BGP | ANNOUNCED | ● high |
| 103.95.112.0/22 | Leaptel | BGP | ANNOUNCED | ● high |
| 103.95.112.0/23 | Leaptel | BGP | ANNOUNCED | ● high |
| 103.95.114.0/23 | Leaptel | BGP | ANNOUNCED | ● high |
| 103.106.88.0/23 | Leaptel | BGP | ANNOUNCED | ● high |
| 103.106.88.0/22 | Leaptel | BGP | ANNOUNCED | ● high |
| 103.106.90.0/23 | Leaptel | BGP | ANNOUNCED | ● high |
| 103.136.101.38/32 | Leaptel | PEERINGDB | ASSIGNED | ● high |
| 103.136.102.37/32 | Leaptel | PEERINGDB | ASSIGNED | ● high |
| 103.136.103.11/32 | Leaptel | PEERINGDB | ASSIGNED | ● high |
| 113.29.240.0/22 | Leaptel | BGP | ANNOUNCED | ● high |
| 113.29.240.0/23 | Leaptel | BGP | ANNOUNCED | ● high |
| 113.29.242.0/23 | Leaptel | BGP | ANNOUNCED | ● high |
| 123.253.188.0/23 | Leaptel | BGP | ANNOUNCED | ● high |
| 123.253.188.0/22 | Leaptel | BGP | ANNOUNCED | ● high |
| 123.253.190.0/23 | Leaptel | BGP | ANNOUNCED | ● high |
| 124.158.96.0/22 | Leaptel | BGP | ANNOUNCED | ● high |
| 124.158.96.0/23 | Leaptel | BGP | ANNOUNCED | ● high |
| 124.158.98.0/23 | Leaptel | BGP | ANNOUNCED | ● high |
| 131.149.248.0/22 | Leaptel | BGP | ANNOUNCED | ● high |
| 131.149.248.0/23 | Leaptel | BGP | ANNOUNCED | ● high |
| 131.149.250.0/23 | Leaptel | BGP | ANNOUNCED | ● high |
| 148.222.0.0/23 | Leaptel | BGP | ANNOUNCED | ● high |
| 148.222.0.0/22 | Leaptel | BGP | ANNOUNCED | ● high |
| 148.222.2.0/23 | Leaptel | BGP | ANNOUNCED | ● high |
| 148.222.4.0/23 | Leaptel | BGP | ANNOUNCED | ● high |
| 148.222.4.0/22 | Leaptel | BGP | ANNOUNCED | ● high |
| 148.222.6.0/23 | Leaptel | BGP | ANNOUNCED | ● high |
| 165.99.26.0/24 | Leaptel | BGP | ANNOUNCED | ● high |
| 165.99.26.0/23 | Leaptel | BGP | ANNOUNCED | ● high |
| 165.99.27.0/24 | Leaptel | BGP | ANNOUNCED | ● high |
| 175.111.176.0/22 | Leaptel | BGP | ANNOUNCED | ● high |
| 175.111.176.0/23 | Leaptel | BGP | ANNOUNCED | ● high |
| 175.111.178.0/23 | Leaptel | BGP | ANNOUNCED | ● high |
| 183.177.61.52/32 | Leaptel | PEERINGDB | ASSIGNED | ● high |
| 202.12.243.37/32 | Leaptel | PEERINGDB | ASSIGNED | ● high |
| 202.77.88.34/32 | Leaptel | PEERINGDB | ASSIGNED | ● high |
| 202.77.90.20/32 | Leaptel | PEERINGDB | ASSIGNED | ● high |
| 202.128.112.0/22 | Leaptel | BGP | ANNOUNCED | ● high |
| 202.128.112.0/21 | Leaptel | BGP | ANNOUNCED | ● high |
| 202.128.116.0/22 | Leaptel | BGP | ANNOUNCED | ● high |
| 202.128.120.0/21 | Leaptel | BGP | ANNOUNCED | ● high |
| 202.128.120.0/22 | Leaptel | BGP | ANNOUNCED | ● high |
| 202.128.124.0/22 | Leaptel | BGP | ANNOUNCED | ● high |
| 202.179.128.0/22 | Leaptel | BGP | ANNOUNCED | ● high |
| 202.179.128.0/23 | Leaptel | BGP | ANNOUNCED | ● high |
| 202.179.130.0/23 | Leaptel | BGP | ANNOUNCED | ● high |
| 216.235.244.0/22 | Leaptel | BGP | ANNOUNCED | ● high |
| 216.235.244.0/23 | Leaptel | BGP | ANNOUNCED | ● high |
| 216.235.246.0/23 | Leaptel | BGP | ANNOUNCED | ● high |
| 218.100.52.178/32 | Leaptel | PEERINGDB | ASSIGNED | ● high |
| 218.100.54.42/32 | Leaptel | PEERINGDB | ASSIGNED | ● high |
| 218.100.76.87/32 | Leaptel | PEERINGDB | ASSIGNED | ● high |
| 218.100.78.73/32 | Leaptel | PEERINGDB | ASSIGNED | ● high |
| 2001:7fa:11:0:2:bca:0:1/128 | Leaptel | PEERINGDB | ASSIGNED | ● high |
| 2001:7fa:11:1:2:bca:0:1/128 | Leaptel | PEERINGDB | ASSIGNED | ● high |
| 2001:7fa:11:2:2:bca:0:1/128 | Leaptel | PEERINGDB | ASSIGNED | ● high |
| 2001:7fa:11:3:2:bca:0:1/128 | Leaptel | PEERINGDB | ASSIGNED | ● high |
| 2001:7fa:11:4:2:bca:0:1/128 | Leaptel | PEERINGDB | ASSIGNED | ● high |
| 2001:7fa:11:6:2:bca:0:1/128 | Leaptel | PEERINGDB | ASSIGNED | ● high |
| 2001:de8:6::13:4090:1/128 | Leaptel | PEERINGDB | ASSIGNED | ● high |
| 2001:de8:6:1:0:13:4090:1/128 | Leaptel | PEERINGDB | ASSIGNED | ● high |
| 2001:dea:0:10::c2/128 | Leaptel | PEERINGDB | ASSIGNED | ● high |
| 2001:dea:0:20::5b/128 | Leaptel | PEERINGDB | ASSIGNED | ● high |
| 2001:dea:0:30::59/128 | Leaptel | PEERINGDB | ASSIGNED | ● high |
| 2001:dea:0:50::25/128 | Leaptel | PEERINGDB | ASSIGNED | ● high |
| 2001:df0:680:2::27/128 | Leaptel | PEERINGDB | ASSIGNED | ● high |
| 2001:df0:680:3::25/128 | Leaptel | PEERINGDB | ASSIGNED | ● high |
| 2001:df0:680:4::b/128 | Leaptel | PEERINGDB | ASSIGNED | ● high |
| 2001:df0:680:5::22/128 | Leaptel | PEERINGDB | ASSIGNED | ● high |
| 2001:df0:680:6::14/128 | Leaptel | PEERINGDB | ASSIGNED | ● high |
| 2400:a840::/31 | Leaptel | BGP | ANNOUNCED | ● high |
| 2400:a840::/32 | Leaptel | BGP | ANNOUNCED | ● high |
| 2400:a841::/32 | Leaptel | BGP | ANNOUNCED | ● high |
| 2400:a842::/31 | Leaptel | BGP | ANNOUNCED | ● high |
| 2400:a842::/32 | Leaptel | BGP | ANNOUNCED | ● high |
| 2400:a843::/32 | Leaptel | BGP | ANNOUNCED | ● high |
| 2400:a844::/31 | Leaptel | BGP | ANNOUNCED | ● high |
| 2400:a844::/32 | Leaptel | BGP | ANNOUNCED | ● high |
| 2400:a845::/32 | Leaptel | BGP | ANNOUNCED | ● high |
| 2400:a846::/31 | Leaptel | BGP | ANNOUNCED | ● high |
| 2400:a846::/32 | Leaptel | BGP | ANNOUNCED | ● high |
| 2400:a847::/32 | Leaptel | BGP | ANNOUNCED | ● high |
| 2400:a848::/32 | Leaptel | BGP | ANNOUNCED | ● high |
| 2400:a848::/31 | Leaptel | BGP | ANNOUNCED | ● high |
| 2400:a849::/32 | Leaptel | BGP | ANNOUNCED | ● high |
| 2400:a84a::/31 | Leaptel | BGP | ANNOUNCED | ● high |
| 2400:a84a::/32 | Leaptel | BGP | ANNOUNCED | ● high |
| 2400:a84b::/32 | Leaptel | BGP | ANNOUNCED | ● high |
| 2400:a84c::/32 | Leaptel | BGP | ANNOUNCED | ● high |
| 2400:a84c::/31 | Leaptel | BGP | ANNOUNCED | ● high |
| 2400:a84d::/32 | Leaptel | BGP | ANNOUNCED | ● high |
| 2400:a84e::/31 | Leaptel | BGP | ANNOUNCED | ● high |
| 2400:a84e::/32 | Leaptel | BGP | ANNOUNCED | ● high |
| 2400:a84f::/32 | Leaptel | BGP | ANNOUNCED | ● high |
| 2402:920::/32 | Leaptel | BGP | ANNOUNCED | ● high |
| 2402:920::/33 | Leaptel | BGP | ANNOUNCED | ● high |
| 2402:920:8000::/33 | Leaptel | BGP | ANNOUNCED | ● high |
| 2402:2c80::/33 | Leaptel | BGP | ANNOUNCED | ● high |
| 2402:2c80::/32 | Leaptel | BGP | ANNOUNCED | ● high |
| 2402:2c80:8000::/33 | Leaptel | BGP | ANNOUNCED | ● high |
| 148.222.0.0/21 | Leaptel | APNIC | ALLOCATED PORTABLE | ● low |
| 202.128.112.0/20 | Leaptel | APNIC | ALLOCATED PORTABLE | ● low |
| 2400:a840::/28 | Leaptel | APNIC | ALLOCATED PORTABLE | ● low |
IPv6 ranges (48)
Footprint over time
14 weekly snapshots · JSON
136
0 netblocks since 2026-07-05
2026-07-05
peak 136
2026-09-27
Customer-delegated space
how is this classified?
Unclassified
102 (83.6%)
Operator infrastructure (named)
34 (27.9%)
Network trust
what's this?
RPKI hygiene: B
how networks compare →
93.4%
of checked blocks have valid RPKI ROA coverage
(127 of 136)
No discrepancies found among checked blocks.
NIC Handles
AL1815-AP
APNIC-HM
AS134090
AS134090
LTPL7-AP
LTPL7-AP
MAINT-LEAP-AU
ORG-LA59-AP