AS51800 FIBERNET-ASN FIBER Network s.r.o.
🇨🇿Org handle: ORG-FNs4-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
2total
1 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)7,168
Announced (BGP)2,048
IPv6 Addresses
Allocated (RIR)7.9×10²⁸
Announced (BGP)7.9×10²⁸
Announced Prefixes
(BGP)2|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)4Prefix | Country | RIR | Status |
|---|---|---|---|
| 185.153.80.0/22 | 🇨🇿 CZ | RIPENCC | allocated |
| 217.28.80.0/20 | 🇨🇿 CZ | RIPENCC | allocated |
| 217.28.80.0/21 | 🇨🇿 CZ | RIPE | assigned |
| 2a02:28a8::/32 | 🇨🇿 CZ | RIPENCC | allocated |
All 2 announced prefixes of AS51800 →
BGP Neighbours
(seen in AS paths)Upstreams (2)
Networks AS51800 hands its own prefixes to: transit providers, or peers at an exchange.
Other adjacent networks (1)
Adjacent to AS51800 in the transit part of AS paths: peers, providers or customers.
- AS42000KAORA Futruy S.R.O2
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 AS51800 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/51800Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/51800" | jq