AS42323 CONNECT-AS Limited Liability Company "TTK-Svyaz"
๐ท๐บOrg handle: ORG-LLC51-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
3total
3 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)4,096
Announced (BGP)4,096
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Prefix Limit (IPv4)
10
Prefix Limit (IPv6)
5
Country
๐ท๐บ RURIR
RIPE NCCStatus
allocated
Allocated
2008-02-21
Announced Prefixes
(BGP)3|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | Other IRRRIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | Other IRRRIPE | 2026-10-11 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 91.202.140.0/22 | ๐ท๐บ RU | RIPENCC | allocated |
| 109.197.128.0/21 | ๐ท๐บ RU | RIPENCC | allocated |
| 195.238.100.0/22 | ๐ท๐บ RU | RIPENCC | allocated |
All 3 announced prefixes of AS42323 โ
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS42323 hands its own prefixes to: transit providers, or peers at an exchange.
- AS21127ZSTTKAS Joint Stock Company TransTeleCom3
Transfer History
Registry transfers of AS42323 between organisations.
- AS42323M&A ยท
- AS42323M&A ยท
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 AS42323 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/42323Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/42323" | jq