AS198239 OLLINK-AS OLLINK SARL
π«π·Org handle: ORG-SGCA1-RIPE
OLLINK
RIPE NCCallocated
Announced Prefixes (BGP)
11total
9 IPv42 IPv6
IPv4 Addresses
Allocated (RIR)2,048
Announced (BGP)3,072
IPv6 Addresses
Allocated (RIR)2.4Γ10Β²β΄
Announced (BGP)2.4Γ10Β²β΄
Prefix Limit (IPv4)
20
Prefix Limit (IPv6)
10
Country
π«π· FRRIR
RIPE NCCStatus
allocated
Allocated
2011-11-23
Routing hygiene
Score 46/100 Β· Medium riskRPKI ROA coverage
9.1%
no RPKI invalid prefixes
IRR route objects
90.9%
1 prefix registered for another origin
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
2
diversity 30/100
- 91% of announced prefixes (10 of 11) have no valid ROA
- 1 prefix registered in IRR route objects for another active network and not authorized by a ROA
- Routes concentrated on one upstream (82% of routes)
Based on 11 announced prefixes, updated daily (2026-10-18). How the score works Β· RPKI explained
Announced Prefixes
(BGP)11|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | RIPE | 2026-10-26 | |
| No ROA | RIPE | 2026-10-26 | |
| No ROA | RIPE | 2026-10-26 | |
| No ROA | RIPE | 2026-10-26 | |
| No ROA | RIPE | 2026-10-26 | |
| No ROA | RIPE | 2026-10-26 | |
| Valid | ARIN | 2026-10-26 | |
| No ROA | RIPE | 2026-10-26 | |
193.17.196.0/24MOAS | No ROA | - | 2026-10-26 |
| No ROA | RIPE | 2026-10-26 |
1-10 of 11
1 / 2
Allocated Prefixes
(RIR)7Prefix | Country | RIR | Status |
|---|---|---|---|
| 80.245.34.0/24 | π«π· FR | RIPE | assigned |
| 80.245.46.0/24 | π«π· FR | RIPE | assigned |
| 91.232.224.0/24 | π«π· FR | RIPENCC | assigned |
| 185.198.76.0/22 | π«π· FR | RIPENCC | allocated |
| 193.17.196.0/24 | π«π· FR | RIPENCC | assigned |
| 2001:67c:25e4::/48 | π«π· FR | RIPENCC | assigned |
| 2001:978:9e01::/48 | π«π· FR | RIPE | assigned |
All 11 announced prefixes of AS198239 β
BGP Neighbours
(seen in AS paths)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 AS198239 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/198239Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/198239" | jq