AS206084 velosiot VELOS IOT JERSEY LIMITED
🇯🇪Org handle: ORG-JIL5-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
2total
2 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)512
Announced (BGP)512
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)0
Routing hygiene
Score 20/100 · Low riskRPKI ROA coverage
50%
no RPKI invalid prefixes
IRR route objects
100%
no origin mismatches
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
2
diversity 50/100
- 50% of announced prefixes (1 of 2) have no valid ROA
Based on 2 announced prefixes, updated daily (2026-10-12). How the score works · RPKI explained
Announced Prefixes
(BGP)2|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-12 | |
| No ROA | RIPE | 2026-10-12 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 194.15.251.0/24 | 🇪🇪 EE | RIPE | assigned |
| 213.134.23.0/24 | 🇯🇪 JE | RIPENCC | allocated |
| 2a0b:9740::/29 | 🇯🇪 JE | RIPENCC | allocated |
All 2 announced prefixes of AS206084 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS206084 hands its own prefixes to: transit providers, or peers at an exchange.
- AS202914Adeodc Adeo Datacenter ApS2
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 AS206084 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/206084Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/206084" | jq