Services

Bringing the cloud to the edge.

Internet Exchange

The premier, distributed Internet Exchange delivering the cloud to all major datacenters in Okinawa.

Cross Connects

Datacenter interconnections with multiple port speed options.

Internet Access

Cloud and internet service providers connect to RIX to offer services over the RIX platform.

Extra Services

Partnered with other major Internet Exchanges, extending their advantages to RIX.

Network

The RIX network's plug and play locations.

Ryukyus Internet Exchange Core

A 200 Gbps, redundant core with nodes in Naha, Urasoe, Ginowan, Uruma, Ginoza, Nago and expanding.

Distributed Internet Exchange

A flexible multi-datacenter network capable of reaching all of Okinawa.

Member List

Current RIX Collaborators.


GLBB Japan / AS 55900

Global Broadband / AS 137912

WingTec / AS 136769

Okinawa Cable Network / AS 24277

Science Information Network 5 / AS 2907

IX Policy

Rules and Governance.

Membership Policy


To become a member of RIX the following are required:

1. All members must have an Autonomous System Number (ASN) as assigned by a Regional Internet Registry.
2. New Members must agree to follow the rules in this policy.
3. Members must exchange traffic and subscribe to one port within 3 months of membership.
4. Members must exchange traffic with at least one other member.
5. Members must pay all fees, port, and carrier costs to its hosting company, GlobalBroadband KK, in a timely manner.

General Use


1. No member may hinder the peering between two other members.
2. All members must take all required steps to maintain their network traffic and all configuration steps advised by RIX on the exchange to ensure correct peering.
3. Members must monitor their network 24/7 and ensure denial-of-service and flooding attacks do not originate from their network onto RIX.
4. Members must take reasonable steps to ensure unauthorized or malicious traffic is not propagated through their network.
5. Members must not release information that would jeopardize the security of RIX or another member.
6. Violations of security are prohibited and RIX reserves the rights to release security, abuse, and network administration contact information between members for the resolution of security issues.
7. RIX reserves the right to disconnect all ports involved in malicious activities, and/or port scanning.

Technical Policy


1. Interfaces attached to RIX ports must be configured with duplex, speed and all other required configuration settings and shall not be auto-sensing.
2. Frames forwarded to RIX ports shall have one of the following ethertypes, 0x0800 – IPv4, 0x0806 – ARP, and 0x86dd – IPv6.
3. Frames forwarded to RIX ports must all have the same source MAC address.
4. Member devices must be configured not to use Proxy-Arp nor to respond to Proxy-Arp requests.
5. Member devices must not send traffic to group or multicast addresses with the following exceptions, Broadcast ARP, LACP membership MAC, and IPv6 Neighbor Discovery.
6. Link local protocols which must not be forwarded to an RIX port includes but is not limited to:
IRDP, ICMP redirects, Spanning Tree, CDP, VTP, DTP, interior routing protocols, BOOTP, DHCP, PIM, LLDP, UDLD, and L2 Keepalives.
7. Member interfaces connected to RIX ports must only use IP addresses and masks assigned to them by RIX. In particular: IPv6 addresses (link & global scope) shall be explicitly configured and not auto-configured.
8. All exchange of routes across the RIX network shall be via BGP4+.
9. AS numbers used in BGP4+ sessions across the RIX network may not be from ranges reserved for private use.
10. Multi-lateral peering members via RIX must ensure that their device support disabling of BGP enforce-first-as checking.
11. Advertising of private IP address range (RFC1918) and default-route are not allowed on RIX.
12. IP address space assigned to RIXpeering LAN shall not be advertised to other networks without explicit permission of RIX.
13. All routes advertised across the RIX network shall point to the router advertising it unless an agreement has been made in advance in writing by the two Members involved, and RIX remains informed of this by the Members involved.
14. All routes to be advertised in peering sessions across the RIX public peering network shall be registered in the RIR Routing Information Service database or other public routing registry.
15. Traffic shall only be forwarded to a Member when permission has been given by the receiving Member either by advertising the route or by explicit written communication.

Contact Us

Please fill out all items for all inquiries.