AS2613 VAN_GULIK Association Romandix
🇨🇭Org handle: ORG-AR223-RIPE
RIPE NCCallocatedASPA Published
Announced Prefixes (BGP)
3total
2 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)512
Announced (BGP)512
IPv6 Addresses
Allocated (RIR)1.3×10³⁰
Announced (BGP)7.9×10²⁸
Routing hygiene
Score 10/100 · Low riskRPKI ROA coverage
100%
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
1
diversity 0/100
- Only one upstream seen in the AS paths of its routes
Based on 3 announced prefixes, updated daily (2026-10-24). How the score works · RPKI explained
Announced Prefixes
(BGP)3|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 |
Allocated Prefixes
(RIR)5Prefix | Country | RIR | Status |
|---|---|---|---|
| 91.218.38.0/24 | 🇨🇭 CH | RIPENCC | allocated |
| 193.135.150.0/24 | 🇨🇭 CH | RIPENCC | assigned |
| 2a07:e640::/29 | 🇨🇭 CH | RIPENCC | allocated |
| 2a0c:d0c0::/29 | 🇨🇭 CH | RIPENCC | allocated |
| 2a0c:d0c1::/32 | 🇨🇭 CH | RIPE | assigned |
All 3 announced prefixes of AS2613 →
Upstream Providers(5)
BGP Neighbours
(seen in AS paths)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
- How to run an ASPA checkVerify the upstream providers listed above
- 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/2613Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/2613" | jq