CIRA-CLOUD1
AS55195 · CIRA
CIRA
Tools: Where can I peer with CIRA-CLOUD1? · Where should CIRA-CLOUD1 peer next? · Compare CIRA-CLOUD1 with another network
This network elsewhere: its routes on BGP Report
PeeringDB fix list Printable page · CSV
6 things to fix in CIRA-CLOUD1's PeeringDB record, from what its exchanges publish: 2 to add, 4 to correct. As of 2026-11-19 18:41 UTC.
Make the changes on CIRA-CLOUD1's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
Add these exchanges (2)
On the exchange's own member list, but not in CIRA-CLOUD1's PeeringDB record. Add one entry per connection with these values.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
Correct these entries (4)
Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.
-
Problem PeeringDB has The export has Port speed differs 1G 10G - In the entry with IPv4 195.66.226.79: set Speed to 10000 (10G) (now 1000).
-
Problem PeeringDB has The export has Port speed differs 1G 5G - In the entry with IPv4 5.57.81.125: set Speed to 5000 (5G) (now 1000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 206.72.208.6 206.72.208.6 206.72.208.9 IPv6 address missing from PeeringDB 2001:504:26::5:5195:1 2001:504:26::5:5195:1 2001:504:26::5:5195:2 - In the entry with IPv4 206.72.208.6: set IPv6 to (empty) (now 2001:504:26::5:5195:1).
- Add an entry: IPv4 –, IPv6 2001:504:26::5:5195:1, RS peer yes.
- Add an entry: IPv4 206.72.208.9, IPv6 –, RS peer yes.
- Add an entry: IPv4 –, IPv6 2001:504:26::5:5195:2, RS peer yes.
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 10G 1.25G - In the entry with IPv4 185.0.20.135: set Speed to 1250 (1.25G) (now 10000).
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 23 |
| Nov 18, 2026 | 23 |
| Nov 17, 2026 | 23 |
| Nov 16, 2026 | 23 |
| Nov 15, 2026 | 23 |
| Nov 14, 2026 | 23 |
| Nov 13, 2026 | 23 |
| Nov 12, 2026 | 23 |
| Nov 11, 2026 | 23 |
| Nov 10, 2026 | 23 |
| Nov 9, 2026 | 23 |
| Nov 8, 2026 | 22 |
| Nov 7, 2026 | 22 |
| Nov 6, 2026 | 22 |
| Nov 5, 2026 | 22 |
| Nov 4, 2026 | 22 |
| Nov 3, 2026 | 22 |
| Nov 2, 2026 | 22 |
| Nov 1, 2026 | 22 |
| Oct 31, 2026 | 22 |
| Oct 30, 2026 | 22 |
| Oct 29, 2026 | 22 |
| Oct 28, 2026 | 22 |
| Oct 27, 2026 | 22 |
| Oct 26, 2026 | 22 |
| Oct 25, 2026 | 22 |
| Oct 24, 2026 | 22 |
| Oct 23, 2026 | 22 |
| Oct 22, 2026 | 22 |
| Oct 21, 2026 | 22 |
| Oct 20, 2026 | 23 |
| Oct 19, 2026 | 23 |
| Oct 18, 2026 | 23 |
| Oct 17, 2026 | 23 |
| Oct 16, 2026 | 23 |
| Oct 15, 2026 | 23 |
| Oct 14, 2026 | 23 |
| Oct 13, 2026 | 23 |
| Oct 12, 2026 | 23 |
| Oct 11, 2026 | 23 |
| Oct 10, 2026 | 23 |
| Oct 9, 2026 | 23 |
| Oct 8, 2026 | 23 |
| Oct 7, 2026 | 23 |
| Oct 6, 2026 | 23 |
| Oct 5, 2026 | 23 |
| Oct 4, 2026 | 23 |
| Oct 3, 2026 | 23 |
Map
Where CIRA-CLOUD1'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.
| Any2West Los Angeles and Silicon Valley, United States | 10G | PeeringDB | |
| BBIX Singapore Singapore, Singapore | 10G | PeeringDB | |
| BBIX Tokyo Tokyo, Japan | Not in PeeringDB | ||
| CANIX Halifax Halifax, Canada | 1G | PeeringDB | |
| Equinix Paris Paris, France | 10G | PeeringDB | |
| Equinix Singapore Singapore, Singapore | 10G | PeeringDB | |
| Extreme IX Delhi Delhi, India | 10G | PeeringDB | |
| France-IX Paris Paris, France | 10G | PeeringDB | |
| IX Australia Melbourne (VIC-IX) Melbourne, Australia | 1G | Both | |
| IX Australia Sydney (NSW-IX) Sydney, Australia | Website list only | ||
| IX.br (PTT.br) São Paulo São Paulo/SP, Brazil | 10G | Both | |
| LINX LON1 London, United Kingdom | 1G | Both Speed differs | |
| LONAP London, United Kingdom | 1G | Both Speed differs | |
| MBIX Winnipeg, Manitoba, Canada | 1G | Both IPv4 not in PeeringDBIPv6 not in PeeringDB | |
| MegaIX Melbourne Melbourne, Australia | 1G | Both | |
| MIX-IT Milan, Italy | 10G | Both | |
| NAPAfrica IX Johannesburg Johannesburg, South Africa | 1G | Both | |
| Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia | 10G | Both Speed differs | |
| PIT - Peru - Lima Lima, Peru | 10G | PeeringDB | |
| SGIX Singapore, Singapore | 10G | Both | |
| TorIX Toronto, Canada | 1G | PeeringDB | |
| YXEIX Saskatoon, Canada | 1G | Both | |
| YYCIX Calgary, Canada | 1G | Both |
These exchanges have a switch in a facility where CIRA-CLOUD1 lists itself in PeeringDB, but don't have CIRA-CLOUD1 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.
| NL-ixAmsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands | 672 | |
| LINX LON2London, United Kingdom | 315 | |
| 1-IX EUNew-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland | 283 | |
| Equinix Hong KongHong Kong, Hong Kong | 254 | |
| JINXJohannesburg, South Africa | 215 | |
| ONIXToronto, Canada | 207 | |
| NetIXSofia, Bulgaria | 204 | |
| BBIX Hong KongHong Kong, Hong Kong | 104 | |
| BBIX US-WestWest Coast, United States | 87 | |
| Equinix LondonLondon, United Kingdom | 53 | |
| Hong Kong Global Internet ExchangeHong Kong, Hong Kong | 33 | |
| NAPAfrica MAPS JohannesburgJohannesburg, South Africa | 31 | |
| JumboIX PeruLima, Peru | 27 | |
| MegaIX Los AngelesLos Angeles, United States | 27 | |
| NYIIX Los AngelesLos Angeles, United States | 21 | |
| Equinix TorontoToronto, Canada | 16 | |
| MegaIX TorontoToronto, Canada | 16 | |
| CANIX MonctonMoncton, Canada | 10 | |
| EURASIA-IX.NETIstanbul, Türkiye | 6 | |
| Global Peer ExchangeWashington, United States | 6 | |
| JINX VoiceJohannesburg, South Africa | 4 |
Facilities (10)
The buildings CIRA-CLOUD1 lists in PeeringDB, and how many of the exchanges in each it's on.
| Equinix LD8 - London, DocklandsLondon | 2 of 9 | |
| Equinix HK1 - Hong KongTsuen Wan | 0 of 6 | |
| Teraco Johannesburg Campus, South AfricaJohannesburg | 1 of 6 | |
| CoreSite - Los Angeles (LA1) One WilshireLos Angeles | 1 of 5 | |
| Equinix TR1 - TorontoToronto | 1 of 5 | |
| Equinix PA7 - Paris, Energy ParkParis | 2 of 2 | |
| NIC-JD (João Dias)São Paulo | 1 of 2 | |
| DatahiveCalgary | 1 of 1 | |
| Fibre CentreMoncton | 0 of 1 | |
| Global Server CenterWinnipeg | 1 of 1 |