Wireless Provider
Data as of 2026-07-26
BGP inherited
Cluster stats
| Netblocks | 4 · 513 IPv4 addresses |
| IPv6 | 1 prefix (largest 2803:cd60:6414:7::28/128) |
| Cluster ID | 214594982 |
| Registry | BGP |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 2 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
5 weekly snapshots · JSON
11
-1 netblocks since 2026-07-05
2026-07-05
peak 12
2026-07-19
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 45.68.26.128/32 | Wireless Provider | PEERINGDB | ASSIGNED | ● high |
| 2803:cd60:6414:7::28/128 | Wireless Provider | PEERINGDB | ASSIGNED | ● high |
| 181.191.220.0/24 | Wireless Provider | BGP | ANNOUNCED | ● low |
| 181.191.222.0/24 | Wireless Provider | BGP | ANNOUNCED | ● 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
(4 of 4)
Possible discrepancies (2)
These blocks are registered to Wireless Provider 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.
| 181.191.220.0/24 /24 | authorized for AS264619 — AS264619 |
| 181.191.222.0/24 /24 | authorized for AS264619 — AS264619 |
NIC Handles
AS264619
AS264619