AS211736 FDN3 - FOP Dmytro Nedilskyi
RIPE NCCreserved
Announced Prefixes (BGP)
3total
3 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)768
Announced (BGP)768
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Announced Prefixes
(BGP)3|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
88.210.63.0/24MOAS | Invalid | - | 2026-10-11 |
92.63.197.0/24MOAS | Invalid | - | 2026-10-11 |
185.156.73.0/24MOAS | Invalid | - | 2026-10-11 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 88.210.63.0/24 | 🇳🇱 NL | RIPE | assigned |
| 92.63.197.0/24 | 🇳🇱 NL | RIPE | assigned |
| 185.156.73.0/24 | 🇳🇱 NL | RIPE | assigned |
All 3 announced prefixes of AS211736 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS211736 hands its own prefixes to: transit providers, or peers at an exchange.
- AS202425INT NETWORK IP Volume3
ASPA
No ASPA
Abuse Contact
+31205354444
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 AS211736 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/211736Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/211736" | jq