AS6858 SEVEREN_COMLINK-AS JSC "Severen-Telecom"
🇷🇺Org handle: ORG-SL18-RIPE
St.Petersburg, Russia
RIPE NCCallocated
Announced Prefixes (BGP)
2total
2 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)9,216
Announced (BGP)9,216
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Announced Prefixes
(BGP)2|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 185.247.80.0/22 | 🇷🇺 RU | RIPENCC | allocated |
| 195.182.128.0/19 | 🇷🇺 RU | RIPENCC | allocated |
All 2 announced prefixes of AS6858 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS6858 hands its own prefixes to: transit providers, or peers at an exchange.
- AS35000SEVEREN TELECOM TRANSIT JSC "Severen Telecom"2
Transfer History
Registry transfers of AS6858 between organisations.
- AS6858Transfer ·
- AS6858M&A ·
ASPA
No ASPA
Abuse Contact
+31205354444
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 AS6858 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/6858Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/6858" | jq