AS35613 NETDATACOMM FASTER CZ spol. s r.o.
🇨🇿Org handle: ORG-FCss1-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
7total
5 IPv42 IPv6
IPv4 Addresses
Allocated (RIR)8,960
Announced (BGP)9,216
IPv6 Addresses
Allocated (RIR)1.5×10²⁹
Announced (BGP)1.5×10²⁹
Announced Prefixes
(BGP)7|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
193.200.251.0/24MOAS | Valid | RIPE | 2026-10-11 |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)6Prefix | Country | RIR | Status |
|---|---|---|---|
| 176.74.128.0/19 | 🇨🇿 CZ | RIPENCC | allocated |
| 193.200.244.0/24 | 🇨🇿 CZ | RIPENCC | allocated |
| 193.200.246.0/24 | 🇨🇿 CZ | RIPENCC | allocated |
| 193.200.252.0/24 | 🇨🇿 CZ | RIPENCC | allocated |
| 2a00:9c80::/32 | 🇨🇿 CZ | RIPENCC | allocated |
| 2a02:e9c::/32 | 🇨🇿 CZ | RIPE | assigned |
All 7 announced prefixes of AS35613 →
BGP Neighbours
(seen in AS paths)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 AS35613 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/35613Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/35613" | jq