AS42622 DCSTO-AS Videnca AB
πΈπͺOrg handle: ORG-TIMS1-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
2total
2 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)5,120
Announced (BGP)5,120
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Prefix Limit (IPv4)
10
Prefix Limit (IPv6)
5
Country
πΈπͺ SERIR
RIPE NCCStatus
allocated
Allocated
2007-03-22
Announced Prefixes
(BGP)2|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 80.72.0.0/20 | πΈπͺ SE | RIPENCC | allocated |
| 185.84.212.0/22 | πΈπͺ SE | RIPENCC | allocated |
All 2 announced prefixes of AS42622 β
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS42622 hands its own prefixes to: transit providers, or peers at an exchange.
- AS174Cogent Communications2
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 AS42622 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/42622Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/42622" | jq