AS205801 synalabs Padok SAS
🇫🇷Org handle: ORG-SS734-RIPE
-----BEGIN TOKEN-----0a21e7f51ac76ae26a33af2ec010d893035f637d58777c5129424c60ef555f29937ec9179284ff6a6829c6a1373a5351eb5c354d0da2cbd7f2d3f38bb038e645-----END TOKEN-----
RIPE NCCallocated
Announced Prefixes (BGP)
1total
1 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)1,024
Announced (BGP)1,024
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)0
Announced Prefixes
(BGP)1|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 185.199.184.0/22 | 🇫🇷 FR | RIPENCC | allocated |
| 2a0a:9a40::/29 | 🇫🇷 FR | RIPENCC | allocated |
All 1 announced prefix of AS205801 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS205801 hands its own prefixes to: transit providers, or peers at an exchange.
- AS16276OVH SAS1
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 AS205801 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/205801Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/205801" | jq