AS21221 InfoPact-AS Infopact Netwerkdiensten B.V.
🇳🇱Org handle: ORG-INB2-RIPE
The Netherlands
RIPE NCCallocated
Announced Prefixes (BGP)
28total
21 IPv47 IPv6
IPv4 Addresses
Allocated (RIR)99,584
Announced (BGP)101,632
IPv6 Addresses
Allocated (RIR)1.5×10³⁰
Announced (BGP)1.5×10³⁰
Prefix Limit (IPv4)
100
Prefix Limit (IPv6)
50
Country
🇳🇱 NLRIR
RIPE NCCStatus
allocated
Allocated
2001-10-02
Announced Prefixes
(BGP)28|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
45.14.0.0/24MOAS | Valid | - | 2026-10-11 |
| Valid | - | 2026-10-11 | |
| Valid | - | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
1-10 of 28
1 / 3
Allocated Prefixes
(RIR)23Prefix | Country | RIR | Status |
|---|---|---|---|
| 2.56.224.0/23 | 🇳🇱 NL | RIPE | assigned |
| 2.56.226.0/23 | 🇳🇱 NL | RIPE | assigned |
| 46.182.176.0/21 | 🇳🇱 NL | RIPENCC | allocated |
| 82.150.140.0/22 | 🇳🇱 NL | RIPE | assigned |
| 82.210.96.0/19 | 🇳🇱 NL | RIPENCC | allocated |
| 84.35.0.0/16 | 🇳🇱 NL | RIPENCC | allocated |
| 89.106.160.0/21 | 🇳🇱 NL | RIPENCC | allocated |
| 109.71.104.0/22 | 🇳🇱 NL | RIPENCC | allocated |
| 139.28.112.0/22 | 🇳🇱 NL | RIPENCC | allocated |
| 139.28.115.0/24 | 🇳🇱 NL | RIPE | assigned |
1-10 of 23
1 / 3
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 AS21221 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/21221Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/21221" | jq