Aitire
Registry
Cluster stats
| Netblocks | 10 |
| Registered in | Germany (3) · Spain (2) |
| All fragments | 38 blocks across 9 clusters |
| Cluster ID | 208805898 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | Registry record |
| Shared handles | clustered on 1 shared RIR contact/maintainer handle |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
5 weekly snapshots · JSON
10
0 netblocks since 2026-07-05
2026-07-05
peak 10
2026-07-19
IP Ranges (10)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 185.1.119.46/32 | Aitire | PEERINGDB | ASSIGNED | ● high |
| 185.1.192.207/32 | Aitire | PEERINGDB | ASSIGNED | ● high |
| 185.1.193.0/32 | Aitire | PEERINGDB | ASSIGNED | ● high |
| 193.149.1.148/32 | Aitire | PEERINGDB | ASSIGNED | ● high |
| 193.149.1.200/32 | Aitire | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:f::148/128 | Aitire | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:f::200/128 | Aitire | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:a0:0:3:2ecf:0:1/128 | Aitire | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:a0:0:3:2ecf:0:2/128 | Aitire | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:10a:0:3:2ecf:0:1/128 | Aitire | PEERINGDB | ASSIGNED | ● high |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “Aitire” — often
per-country or per-system registrations of the same brand, occasionally a different
organisation sharing the name. Not counted in this organisation's own footprint.
- Aitire S.L 17 blocks
- Aitire_Cloud_Services_net03 2 blocks
- Aitire_Cloud_Services_net04 2 blocks
- Aitire_Cloud_Services_net01 2 blocks
- Aitire_Cloud_Services_net02 2 blocks
- AITIRE-IAAS-NET2 1 blocks
- AITIRE-IAAS 1 blocks
- Aitire_Cloud_Services_net05 1 blocks
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own
naming convention, not a direct registration.
- AITIREKS-LAN via "OBIT" Ltd. sub-allocation
- AITIRE-IAAS via SEWAN SAS sub-allocation
- AITIRE-IAAS-NET2 via SEWAN SAS sub-allocation
- Cloud Services via Aitire S.L sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(10 of 10)
No discrepancies found among checked blocks.
NIC Handles
AS208591