◇ Open Peering Policy · Middle East & GCC

Peer with AS50475.

A Middle East network hubbed in our Kuwait datacenter, built for low latency and wide regional reach. Connect directly to AS50475 at the Kuwait IX or over a private interconnect — and shorten the path between your network and the Gulf.

AS50475
RIPE ASN · Kuwait
Kuwait IX
Public peering
RPKI
Signed IPv6
Open
No contract
// why peer with us

One shorter hop to the Gulf.

Peering with AS50475 puts your traffic a single network away from Kuwait and the wider GCC — lower latency for your users here, and a cleaner, more reliable path you control.

Low latency to the GCC

Dubai 22 ms · Riyadh 44 ms
About 20–45 ms from our Kuwait core to the Gulf's main cloud hubs, measured September 2026 — no more taking the long way around.

Regional reach

FRA 88ms · LON 95ms
A Middle East–anchored network with onward capacity to Europe — reach Gulf eyeballs and bridge beyond.

Secure & clean

RPKI · filtered
RPKI-signed IPv6 prefixes and strict route filtering — no leaks, no surprises in your table.

Open & simple

balanced ratio
An open policy with no contract and no ratio requirement. Public at the IX or private — your call.
// network at a glance

AS50475 peering, built to be verified.

Network
Point of Trade Co. · AS50475
Protocols
IPv4 + IPv6 dual-stack
Peering policy
Open · no contract
Traffic ratio
Balanced
RPKI
Signed IPv6 prefixes
Region
Middle East / GCC
4 upstream transits Direct GCC peering Kuwait IX RPKI-signed IPv6 Black Manta flood watch
// where to interconnect

Middle East peering, two ways.

Meet us on the public fabric or run a dedicated private session — either way, you reach a full-table network that is multi-homed across four upstream transits.

Kuwait IX

Public peering
Bilaterally or via the route servers, on our public-fabric presence in Kuwait City. Peering IPs shared on request.

Private interconnect

PNI · on request
A dedicated cross-connect session for higher-volume or latency-sensitive traffic.

Full-table network

4 upstreams + Kuwait IX
Behind every session sit about a million IPv4 routes from each of our four upstream transit networks, plus the Kuwait IX.
// how to peer

Turning up takes three steps.

Reach out & verify

Email our peering team or find us on PeeringDB. Share your ASN, prefixes and where you'd like to meet.

Agree & configure

We confirm the meeting point — Kuwait IX, route servers or a private session — and exchange config, with strict route filtering in place.

Turn up & monitor

Sessions come up, routes are filtered and validated, and our 24/7 NOC keeps the interconnect healthy.
  • A public ASN and your own address space.
  • Registered routes — a current IRR record.
  • RPKI ROAs for the prefixes you announce.
  • An up-to-date PeeringDB entry we can verify.
  • A 24/7 NOC contact for operational issues.
  • No static routes or default pointed at us.

Let's interconnect.

Peering with AS50475 is by agreement — a short conversation, not a checkout. Tell us your ASN and where you'd like to meet. Prefixes and IX peering IPs are shared with peers on request and via PeeringDB.