AS44533 Davydov-NET Davydov Vladimir Dmitrievich
๐ท๐บOrg handle: ORG-FDVD1-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
20total
20 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)13,824
Announced (BGP)15,616
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Prefix Limit (IPv4)
50
Prefix Limit (IPv6)
5
Country
๐ท๐บ RURIR
RIPE NCCStatus
allocated
Allocated
2008-02-01
Announced Prefixes
(BGP)20|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | RIPE | 2026-10-10 | |
| No ROA | - | 2026-10-10 | |
| No ROA | RIPE | 2026-10-10 | |
| No ROA | RIPE | 2026-10-10 | |
| No ROA | RIPE | 2026-10-10 | |
91.213.117.0/24MOAS | Valid | RIPE | 2026-10-10 |
| No ROA | RIPE | 2026-10-10 | |
| No ROA | RIPE | 2026-10-10 | |
| No ROA | RIPE | 2026-10-10 | |
185.232.47.0/24MOAS | Valid | RIPE | 2026-10-10 |
1-10 of 20
1 / 2
Allocated Prefixes
(RIR)15Prefix | Country | RIR | Status |
|---|---|---|---|
| 45.66.168.0/22 | ๐ท๐บ RU | RIPENCC | allocated |
| 45.155.6.0/24 | ๐ท๐บ RU | RIPENCC | allocated |
| 89.251.160.0/20 | ๐ท๐บ RU | RIPENCC | allocated |
| 91.210.156.0/22 | ๐ท๐บ RU | RIPENCC | assigned |
| 91.234.98.0/24 | ๐ท๐บ RU | RIPENCC | allocated |
| 185.95.66.0/24 | ๐ท๐บ RU | RIPENCC | allocated |
| 185.239.116.0/22 | ๐ท๐บ RU | RIPENCC | allocated |
| 185.239.120.0/22 | ๐ท๐บ RU | RIPENCC | allocated |
| 185.239.128.0/22 | ๐ท๐บ RU | RIPENCC | allocated |
| 185.239.132.0/22 | ๐ท๐บ RU | RIPENCC | allocated |
1-10 of 15
1 / 2
All 20 announced prefixes of AS44533 โ
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS44533 hands its own prefixes to: transit providers, or peers at an exchange.
- AS6789CRELCOM NET CRELCOM20
Transfer History
Registry transfers of AS44533 between organisations.
- AS44533Transfer ยท
- AS44533Transfer ยท
| Date | Resource | From | To | Type |
|---|---|---|---|---|
| AS44533 | Alexey Geiner | Davydov Vladimir Dmitrievich | Transfer | |
| AS44533 | Production Company KRYMTEL Ltd. | Alexey Geiner | Transfer |
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 AS44533 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/44533Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/44533" | jq