AS50522 SEWAN-NL Sewan Nederland B.V.
🇳🇱Org handle: ORG-PB32-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
12total
11 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)16,384
Announced (BGP)16,384
IPv6 Addresses
Allocated (RIR)7.9×10²⁸
Announced (BGP)7.9×10²⁸
Announced Prefixes
(BGP)12|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - |
1-10 of 12
1 / 2
Allocated Prefixes
(RIR)12Prefix | Country | RIR | Status |
|---|---|---|---|
| 81.23.244.0/22 | 🇳🇱 NL | RIPENCC | allocated |
| 81.173.0.0/22 | 🇳🇱 NL | RIPENCC | allocated |
| 81.173.7.0/24 | 🇳🇱 NL | RIPENCC | allocated |
| 81.173.32.0/22 | 🇳🇱 NL | RIPE | assigned |
| 81.173.48.0/20 | 🇳🇱 NL | RIPENCC | allocated |
| 81.173.64.0/20 | 🇳🇱 NL | RIPENCC | allocated |
| 81.173.96.0/22 | 🇳🇱 NL | RIPENCC | allocated |
| 81.173.125.0/24 | 🇳🇱 NL | RIPENCC | allocated |
| 81.173.126.0/23 | 🇳🇱 NL | RIPENCC | allocated |
| 109.235.32.0/21 | 🇳🇱 NL | RIPENCC | allocated |
1-10 of 12
1 / 2
All 12 announced prefixes of AS50522 →
BGP Neighbours
(seen in AS paths)Upstreams (2)
Networks AS50522 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (2)
Networks whose own prefixes AS50522 passes on: usually its customers.
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 AS50522 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/50522Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/50522" | jq