AS205125 IPv6-TUNNELBROKER-ASN IP MARKET - FZCO
🇦🇪Org handle: ORG-IMF1-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
4total
1 IPv43 IPv6
IPv4 Addresses
Allocated (RIR)256
Announced (BGP)256
IPv6 Addresses
Allocated (RIR)2.3×10²⁹
Announced (BGP)2.3×10²⁹
Announced Prefixes
(BGP)4|
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 |
Allocated Prefixes
(RIR)4Prefix | Country | RIR | Status |
|---|---|---|---|
| 45.95.201.0/24 | 🇺🇦 UA | RIPE | assigned |
| 2a03:e2c0::/32 | 🇻🇬 VG | RIPENCC | allocated |
| 2a0d:8340::/32 | 🇷🇺 RU | RIPE | assigned |
| 2a0d:8343::/32 | 🇷🇺 RU | RIPE | assigned |
All 4 announced prefixes of AS205125 →
BGP Neighbours
(seen in AS paths)Transfer History
Registry transfers of AS205125 between organisations.
- AS205125Transfer ·
- AS205125Transfer ·
- AS205125Transfer ·
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 AS205125 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/205125Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/205125" | jq