ixreport

Rain Communications

AS329451

RAIN COMMUNICATIONS LIMITED

3Exchanges
0On an exchange's list, not in PeeringDB
1In PeeringDB, not on the exchange's list
–Type
OpenPeering policy
2Using the route servers
1To fix in PeeringDB
6Facilities in PeeringDB

Tools: Where can I peer with Rain Communications? · Where should Rain Communications peer next? · Compare Rain Communications with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in Rain Communications's PeeringDB record, from what its exchanges publish: 1 to check. As of 2026-11-19 12:40 UTC.

Make the changes on Rain Communications's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If Rain Communications has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Kenya KIXP-Mombasa Mombasa, Kenya · PeeringDB 2362Not on its IX-F export
    IPv4196.60.68.69
    IPv62001:43f8:c0:1::69
    Speed10000 Mbps (10G)

Exchanges over time

0123Oct 3, 2026Nov 19, 20263
Show as a table
DateExchanges
Nov 19, 20263
Nov 18, 20263
Nov 17, 20263
Nov 16, 20263
Nov 15, 20263
Nov 14, 20263
Nov 13, 20263
Nov 12, 20263
Nov 11, 20263
Nov 10, 20263
Nov 9, 20263
Nov 8, 20263
Nov 7, 20263
Nov 6, 20263
Nov 5, 20263
Nov 4, 20263
Nov 3, 20263
Nov 2, 20263
Nov 1, 20263
Oct 31, 20263
Oct 30, 20263
Oct 29, 20263
Oct 28, 20263
Oct 27, 20263
Oct 26, 20263
Oct 25, 20263
Oct 24, 20263
Oct 23, 20263
Oct 22, 20263
Oct 21, 20263
Oct 20, 20263
Oct 19, 20263
Oct 18, 20263
Oct 17, 20263
Oct 16, 20263
Oct 15, 20263
Oct 14, 20263
Oct 13, 20263
Oct 12, 20263
Oct 11, 20263
Oct 10, 20263
Oct 9, 20263
Oct 8, 20263
Oct 7, 20263
Oct 6, 20263
Oct 5, 20263
Oct 4, 20263
Oct 3, 20263

Map

Where Rain Communications's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 120G across 3 exchanges.

Kenya KIXP - Nairobi Nairobi, Kenya 196.223.21.193 2001:43f8:60:1::193 10G Both
Kenya KIXP-Mombasa Mombasa, Kenya 196.60.68.69 2001:43f8:c0:1::69 10G Yes PeeringDB only
Kenya LINX Mombasa Mombasa, Kenya 196.60.124.13 2001:43f8:1771::5:6eb:1 100G Down Both

Exchanges in its buildings that it isn't on (1)

These exchanges have a switch in a facility where Rain Communications lists itself in PeeringDB, but don't have Rain Communications as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.

Kenya LINX NairobiNairobi, Kenya 70 Africa Data Centres, Nairobi NBO1, Kenya; icolo.io Nairobi One (NBO1); PAIX Nairobi and 1 more
Facilities (6)

The buildings Rain Communications lists in PeeringDB, and how many of the exchanges in each it's on.

Kenya Africa Data Centres, Nairobi NBO1, KenyaNairobi 1 of 2
Kenya icolo.io Mombasa One (MBA1)Miritini 2 of 2
Kenya icolo.io Mombasa Two (MBA2)Nyali 2 of 2
Kenya icolo.io Nairobi One (NBO1)Karen 1 of 2
Kenya iXAfrica NBOX1 (Nairobi X One)Nairobi 1 of 2
Kenya PAIX NairobiNairobi 1 of 2