AS215764 V4GUARD Ismael Munoz Hernandez
🇪🇸Org handle: ORG-IA2005-RIPE
v4Guard
RIPE NCCallocated
Announced Prefixes (BGP)
3total
3 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)768
Announced (BGP)768
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Announced Prefixes
(BGP)3|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | Other IRRRIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | Other IRRRIPE | 2026-10-11 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 31.6.14.0/24 | 🇦🇶 AQ | RIPE | assigned |
| 31.6.15.0/24 | 🇦🇶 AQ | RIPE | assigned |
| 31.6.16.0/24 | 🇦🇶 AQ | RIPE | assigned |
All 3 announced prefixes of AS215764 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS215764 hands its own prefixes to: transit providers, or peers at an exchange.
- AS60068CDN77 Datacamp Limited3
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 AS215764 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/215764Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/215764" | jq