AS398781 OSL-188 - OCULUS NETWORKS INC
πΊπΈARINassigned
Announced Prefixes (BGP)
2,128total
2,128 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)61,952
Announced (BGP)678,144
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Prefix Limit (IPv4)
5,000
Prefix Limit (IPv6)
5
Country
πΊπΈ USRIR
ARINStatus
assigned
Allocated
2020-09-02
Listed on the threat map (2026-10-11)
Large hosting providers appear because attackers rent their servers, not necessarily because of the operator.
Announced Prefixes
(BGP)1,000 of 2,128|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | Other IRR | - | |
| Valid | Other IRR | - | |
| Valid | ARINOther IRR | - | |
31.13.193.0/24MOAS | Invalid | - | - |
| Valid | Other IRR | - | |
| Valid | ARINOther IRR | - | |
| Valid | ARINOther IRR | - | |
| Valid | ARINOther IRR | - | |
| Valid | ARINOther IRR | - | |
| Valid | ARINOther IRR | - |
1-10 of 1,000
1 / 100
Allocated Prefixes
(RIR)31Prefix | Country | RIR | Status |
|---|---|---|---|
| 31.13.211.0/24 | πΊπΈ US | RIPENCC | allocated |
| 45.81.39.0/24 | πΊπΈ US | RIPENCC | allocated |
| 45.152.188.0/24 | πΊπΈ US | RIPE | assigned |
| 80.76.48.0/24 | πΊπΈ US | RIPENCC | allocated |
| 81.31.193.0/24 | πΊπΈ US | RIPENCC | allocated |
| 87.120.4.0/24 | πΊπΈ US | RIPENCC | allocated |
| 87.120.38.0/24 | πΊπΈ US | RIPENCC | allocated |
| 87.120.59.0/24 | πΊπΈ US | RIPENCC | allocated |
| 87.120.60.0/24 | πΊπΈ US | RIPENCC | allocated |
| 87.120.98.0/24 | πΊπΈ US | RIPENCC | allocated |
1-10 of 31
1 / 4
All 2,128 announced prefixes of AS398781 β
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS398781 hands its own prefixes to: transit providers, or peers at an exchange.
- AS14713Hosted Backbone2,128
Transfer History
Registry transfers of AS398781 between organisations.
- AS398781M&A Β·
| Date | Resource | From | To | Type |
|---|---|---|---|---|
| AS398781 | OCULUS SOLUTIONS LLC | OCULUS NETWORKS INC | M&A |
ASPA
No ASPA
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 AS398781 should publish an ASPA object
- IPv4 transfers in the ARIN 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/398781Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/398781" | jq