AS42611 ZZOOMM Full Fibre Limited
🇬🇧Org handle: ORG-FFL5-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
8total
7 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)10,240
Announced (BGP)26,880
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)6.3×10²⁹
Announced Prefixes
(BGP)8|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| No ROA | ARIN | 2026-10-11 | |
| No ROA | ARIN | 2026-10-11 | |
| No ROA | ARIN | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)4Prefix | Country | RIR | Status |
|---|---|---|---|
| 84.18.224.0/19 | 🇬🇧 GB | RIPENCC | allocated |
| 85.208.12.0/22 | 🇬🇧 GB | RIPENCC | allocated |
| 91.193.8.0/22 | 🇬🇧 GB | RIPENCC | allocated |
| 2a09:8040::/29 | 🇬🇧 GB | RIPENCC | allocated |
All 8 announced prefixes of AS42611 →
BGP Neighbours
(seen in AS paths)Transfer History
Registry transfers of AS42611 between organisations.
- AS42611Transfer ·
- AS42611Transfer ·
ASPA
No ASPA
Abuse Contact
External Links
Learn more
- What is an ASN?Autonomous systems, ASN ranges and how they are assigned
- RPKI and route origin validationWhat the RPKI badges on the prefix list mean
- ASPA explainedWhy AS42611 should publish an ASPA object
- IPv4 transfers in the RIPE NCC regionMonthly volume and the latest registry transfers
- ASN data in AI agents and SIEMMCP server and API integrations
API
Open https://api.ipctl.io/v1/asn/42611Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/42611" | jq