AS50399 OPENLINE-AS Open Line BV
π³π±Org handle: ORG-OLB2-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
34total
26 IPv48 IPv6
IPv4 Addresses
Allocated (RIR)8,192
Announced (BGP)18,176
IPv6 Addresses
Allocated (RIR)7.1Γ10Β²βΉ
Announced (BGP)3.1Γ10Β²βΉ
Prefix Limit (IPv4)
100
Prefix Limit (IPv6)
50
Country
π³π± NLRIR
RIPE NCCStatus
allocated
Allocated
2010-01-06
Announced Prefixes
(BGP)34|
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 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 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 34
1 / 4
Allocated Prefixes
(RIR)13Prefix | Country | RIR | Status |
|---|---|---|---|
| 91.209.213.0/24 | π³π± NL | RIPENCC | assigned |
| 92.42.232.0/21 | π³π± NL | RIPENCC | allocated |
| 109.232.40.0/21 | π³π± NL | RIPENCC | allocated |
| 185.3.204.0/22 | π³π± NL | RIPENCC | allocated |
| 185.3.204.0/23 | π³π± NL | RIPE | assigned |
| 185.3.206.0/23 | π³π± NL | RIPE | assigned |
| 185.23.218.0/23 | π³π± NL | RIPE | assigned |
| 185.223.140.0/22 | π³π± NL | RIPENCC | allocated |
| 185.223.143.0/24 | π³π± NL | RIPE | assigned |
| 2001:678:1288::/48 | π³π± NL | RIPENCC | assigned |
1-10 of 13
1 / 2
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 AS50399 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/50399Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/50399" | jq