AS216376 pinkfroot Pinkfroot Ltd
🇬🇧Org handle: ORG-PL544-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
1total
1 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)768
Announced (BGP)512
IPv6 Addresses
Allocated (RIR)7.9×10²⁸
Announced (BGP)0
Announced Prefixes
(BGP)1|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 185.77.98.0/23 | 🇬🇧 GB | RIPENCC | allocated |
| 185.241.205.0/24 | 🇬🇧 GB | RIPENCC | allocated |
| 2a13:ab40::/32 | 🇬🇧 GB | RIPENCC | allocated |
All 1 announced prefix of AS216376 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS216376 hands its own prefixes to: transit providers, or peers at an exchange.
- AS51048NEXT CONNEX WIFINITY LIMITED1
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 AS216376 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/216376Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/216376" | jq