AS51601 IPTP IPTP LTD
🇬🇧Org handle: ORG-IL238-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
4total
2 IPv42 IPv6
IPv4 Addresses
Allocated (RIR)1,280
Announced (BGP)1,280
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)4.9×10²⁷
Announced Prefixes
(BGP)4|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
185.65.175.0/24MOAS | Valid | Other IRRRIPE | 2026-10-11 |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 185.65.175.0/24 | 🇦🇪 AE | RIPE | assigned |
| 195.189.120.0/22 | 🇬🇧 GB | RIPENCC | assigned |
All 4 announced prefixes of AS51601 →
BGP Neighbours
(seen in AS paths)Upstreams (3)
Networks AS51601 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (7)
Networks whose own prefixes AS51601 passes on: usually its customers.
Other adjacent networks (1)
Adjacent to AS51601 in the transit part of AS paths: peers, providers or customers.
- AS6939Hurricane Electric1
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 AS51601 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/51601Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/51601" | jq