AS58015 Tievolu Collin Schneeweiss trading as Tievolu GbR
🇩🇪Org handle: ORG-CSTA6-RIPE
Tievolu - The Internet Carrier
RIPE NCCallocated
Announced Prefixes (BGP)
2total
1 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)256
Announced (BGP)256
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)6.3×10²⁹
Routing hygiene
Score 5/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
2
diversity 50/100
- All announced prefixes have a valid ROA and a matching IRR route object
Based on 2 announced prefixes, updated daily (2026-10-23). How the score works · RPKI explained
Announced Prefixes
(BGP)2|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 5.231.97.0/24 | 🇩🇪 DE | RIPE | assigned |
| 2a0d:b080::/29 | 🇩🇪 DE | RIPENCC | allocated |
All 2 announced prefixes of AS58015 →
Downstream Customers(1)
| ASN | Name |
|---|---|
| AS47536 | 🇩🇪PathConnect PathConnect GmbH |
BGP Neighbours
(seen in AS paths)Upstreams (2)
Networks AS58015 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (3)
Networks whose own prefixes AS58015 passes on: usually its customers.
Transfer History
Registry transfers of AS58015 between organisations.
- AS58015Transfer ·
- AS58015Transfer ·
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/58015Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/58015" | jq