AS203160 OPENTEXT-AS-EU Open Text Corporation
🇨🇦Org handle: ORG-OTC8-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
21total
21 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)4,352
Announced (BGP)20,992
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Announced Prefixes
(BGP)21|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | - | 2026-10-09 | |
| No ROA | RIPE | 2026-10-09 | |
| No ROA | RIPE | 2026-10-09 | |
| No ROA | ARINOther IRR | 2026-10-09 | |
| No ROA | RIPE | 2026-10-09 | |
| No ROA | RIPE | 2026-10-09 | |
| No ROA | RIPE | 2026-10-09 | |
| No ROA | RIPE | 2026-10-09 | |
| No ROA | Other IRRRIPE | 2026-10-09 | |
| No ROA | Other IRRRIPE | 2026-10-09 |
1-10 of 21
1 / 3
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 91.209.6.0/24 | 🇺🇸 US | RIPENCC | assigned |
| 149.235.0.0/20 | 🇬🇧 GB | RIPE | assigned |
All 21 announced prefixes of AS203160 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS203160 hands its own prefixes to: transit providers, or peers at an exchange.
- AS6461Zayo Bandwidth21
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 AS203160 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/203160Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/203160" | jq