AS219148 AURONYS Jan Danko trading as BitsLab.io
🇸🇰Org handle: ORG-JDTA4-RIPE
-----BEGIN TOKEN-----1873ecd6ce9a77b8a73b6008350486c85d0180aabe27b6e6699057a40928414b2d0ac3e0469279615b3ca5805e31b3eaa8adecf3e2cf41c1f4fa0ad6945486d3-----END TOKEN-----
RIPE NCCallocated
Announced Prefixes (BGP)
1total
0 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)0
Announced (BGP)0
IPv6 Addresses
Allocated (RIR)1.2×10²⁴
Announced (BGP)1.2×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 1 announced prefix, updated daily (2026-10-21). How the score works · RPKI explained
Announced Prefixes
(BGP)1|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-23 |
Allocated Prefixes
(RIR)1Prefix | Country | RIR | Status |
|---|---|---|---|
| 2a06:9801:f1d::/48 | 🇸🇰 SK | RIPE | assigned |
All 1 announced prefix of AS219148 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS219148 hands its own prefixes to: transit providers, or peers at an exchange.
- AS218589DATAPATH Jan Benes1
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 AS219148 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/219148Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/219148" | jq