Skip to main content

AS18129

ONI

OKAYAMA NETWORK INC.

Registry

Authoritative registration data

AS number
18129
Name
ONI
Organisation
OKAYAMA NETWORK INC.
Country
Flag of Japan JP Japan
RIR
APNIC
Registered
—
Source:asn:rdap retrieved

IPv4 prefixes

8

IPv6 prefixes

0

Total announced

8

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS18129
202.70.224.0/19 IPv4 /19 not checked
218.231.160.0/19 IPv4 /19 not checked
119.47.96.0/20 IPv4 /20 not checked
202.238.16.0/20 IPv4 /20 not checked
219.111.208.0/20 IPv4 /20 not checked
27.109.96.0/21 IPv4 /21 not checked
180.200.248.0/22 IPv4 /22 not checked
103.154.6.0/23 IPv4 /23 not checked

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS18129
Address families
BBIX Osaka 10,000 Mbps IPv4 · IPv6
BBIX Tokyo 20,000 Mbps IPv4 · IPv6
JPIX OSAKA 10,000 Mbps IPv4 · IPv6
JPNAP Tokyo: Peering 20,000 Mbps IPv4

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS18129 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS18129 in AS paths

Observed upstreams
Families
AS2914 NTT-DATA-2914 147 1,504
v4
AS17676 GIGAINFRA 79 759
v4
AS6939 HURRICANE 22 190
v4
AS20485 TRANSTELECOM 5 40
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS18129 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

10 adjacencies that may be an artefact of collector peering

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.