AS202932 QUANZA-CONNECT Quanza B.V.
🇳🇱Org handle: ORG-QEB3-RIPE
Quanza B.V.
RIPE NCCallocated
Announced Prefixes (BGP)
4total
3 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)3,328
Announced (BGP)3,072
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)6.3×10²⁹
Announced Prefixes
(BGP)4|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)5Prefix | Country | RIR | Status |
|---|---|---|---|
| 185.47.224.0/22 | 🇳🇱 NL | RIPENCC | allocated |
| 185.47.226.0/24 | 🇳🇱 NL | RIPE | assigned |
| 185.136.4.0/22 | 🇳🇱 NL | RIPENCC | allocated |
| 185.150.68.0/22 | 🇳🇱 NL | RIPENCC | allocated |
| 2a07:6e80::/29 | 🇳🇱 NL | RIPENCC | allocated |
All 4 announced prefixes of AS202932 →
BGP Neighbours
(seen in AS paths)Upstreams (3)
Networks AS202932 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (4)
Networks whose own prefixes AS202932 passes on: usually its customers.
Other adjacent networks (1)
Adjacent to AS202932 in the transit part of AS paths: peers, providers or customers.
- AS6204ZET NET INTERKVM HOST1
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 AS202932 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/202932Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/202932" | jq