AS203980 ITLUCKS-AS FOP Mospan Maksym Igorevich
🇺🇦Org handle: ORG-FMMI1-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
2total
2 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)512
Announced (BGP)512
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
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 |
|---|---|---|---|
| 46.172.76.0/24 | 🇺🇦 UA | RIPE | assigned |
| 185.253.74.0/24 | 🇺🇦 UA | RIPENCC | allocated |
All 2 announced prefixes of AS203980 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS203980 hands its own prefixes to: transit providers, or peers at an exchange.
- AS48422IT STARCOM IT STARCOM2
Downstreams (2)
Networks whose own prefixes AS203980 passes on: usually its customers.
Other adjacent networks (1)
Adjacent to AS203980 in the transit part of AS paths: peers, providers or customers.
- AS35297DATALINE1
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 AS203980 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/203980Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/203980" | jq