AS199064 QWANT-AS QWANT SAS
🇫🇷Org handle: ORG-QS54-RIPE
-----BEGIN TOKEN-----2c19d67ae12136b1c2a23afaf5401300f3e35cb5e14f7822fa687dc177a8076443e826af4ee1a2adac7345a675ec3e59e88a16eea231c8026819a546769d1b29-----END TOKEN-----
RIPE NCCallocated
Announced Prefixes (BGP)
1total
1 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)1,536
Announced (BGP)256
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Announced Prefixes
(BGP)1|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | Other IRRRIPE | 2026-10-11 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 91.242.162.0/24 | 🇫🇷 FR | RIPENCC | assigned |
| 194.187.168.0/22 | 🇫🇷 FR | RIPENCC | allocated |
| 194.187.171.0/24 | 🇫🇷 FR | RIPE | assigned |
All 1 announced prefix of AS199064 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS199064 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 AS199064 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/199064Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/199064" | jq