AS49357 AS-UTECH-RU Klick Ltd
๐ท๐บOrg handle: ORG-KL327-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
4total
4 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)1,280
Announced (BGP)2,304
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Prefix Limit (IPv4)
10
Prefix Limit (IPv6)
5
Country
๐ท๐บ RURIR
RIPE NCCStatus
allocated
Allocated
2009-05-25
Announced Prefixes
(BGP)4|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 46.8.159.0/24 | ๐ท๐บ RU | RIPE | assigned |
| 94.141.116.0/22 | ๐ท๐บ RU | RIPENCC | allocated |
All 4 announced prefixes of AS49357 โ
BGP Neighbours
(seen in AS paths)Upstreams (3)
Networks AS49357 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (1)
Networks whose own prefixes AS49357 passes on: usually its customers.
- AS43595UGRESHA NET Ugresha Network2
Other adjacent networks (1)
Adjacent to AS49357 in the transit part of AS paths: peers, providers or customers.
- AS35598INETCOM CARRIER2
Transfer History
Registry transfers of AS49357 between organisations.
- AS49357Transfer ยท
- AS49357Transfer ยท
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 AS49357 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/49357Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/49357" | jq