AS51357 SMARTCOM LLC "SMARTCOM"
🇺🇦Org handle: ORG-LA1860-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
2total
2 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)1,792
Announced (BGP)1,536
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)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 77.95.171.0/24 | 🇺🇦 UA | RIPENCC | allocated |
| 91.232.0.0/22 | 🇺🇦 UA | RIPENCC | assigned |
| 195.225.48.0/23 | 🇺🇦 UA | RIPENCC | assigned |
All 2 announced prefixes of AS51357 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS51357 hands its own prefixes to: transit providers, or peers at an exchange.
- AS1820WNET TELECOM USA2
Transfer History
Registry transfers of AS51357 between organisations.
- AS51357Transfer ·
- AS51357Transfer ·
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 AS51357 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/51357Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/51357" | jq