AS204562 ASJavelin JAVELIN BROADBAND LIMITED
🇬🇧Org handle: ORG-JBL15-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
5total
4 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)1,280
Announced (BGP)1,792
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)6.3×10²⁹
Announced Prefixes
(BGP)5|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | - | 2026-10-11 | |
| Valid | - | 2026-10-11 | |
| Valid | - | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 185.245.240.0/22 | 🇬🇧 GB | RIPENCC | allocated |
| 185.245.241.0/24 | 🇬🇧 GB | RIPE | assigned |
| 2a0d:6e80::/29 | 🇬🇧 GB | RIPENCC | allocated |
All 5 announced prefixes of AS204562 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS204562 hands its own prefixes to: transit providers, or peers at an exchange.
- AS61231Neos Networks Neos Networks Limited5
Downstreams (1)
Networks whose own prefixes AS204562 passes on: usually its customers.
- AS47535Javelinbroadband JAVELIN BROADBAND LIMITED2
Other adjacent networks (1)
Adjacent to AS204562 in the transit part of AS paths: peers, providers or customers.
- AS174Cogent Communications2
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 AS204562 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/204562Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/204562" | jq