Okko
AS211609 · OKKO
OKKO LLC
Tools: Where can I peer with Okko? · Where should Okko peer next? · Compare Okko with another network
This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report
PeeringDB fix list Printable page · CSV
5 things to fix in Okko's PeeringDB record, from what its exchanges publish: 2 to add, 3 to correct. As of 2026-11-19 12:40 UTC.
Make the changes on Okko'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 Okko's PeeringDB record. Add one entry per connection with these values.
-
IPv4 194.85.107.51 IPv6 – Speed Not published 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.
-
IPv4 193.232.140.38 IPv6 – Speed Not published 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.
Correct these entries (3)
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 IPv4 address missing from PeeringDB 178.18.224.149 178.18.224.149 178.18.224.150 178.18.225.173 178.18.225.178 IPv6 address missing from PeeringDB none 2a03:5f80:4::224:149 2a03:5f80:4::224:150 2a03:5f80:4::225:173 2a03:5f80:4::225:178 Port speed differs 100G 200G + 100G - In the entry with IPv4 178.18.224.149: set IPv6 to 2a03:5f80:4::224:149 (now empty); set Speed to 200000 (200G) (now 100000).
- Add an entry: IPv4 178.18.224.150, IPv6 2a03:5f80:4::224:150, speed 200000 (200G), RS peer yes.
- Add an entry: IPv4 178.18.225.173, IPv6 2a03:5f80:4::225:173, speed 100000 (100G), RS peer yes.
- Add an entry: IPv4 178.18.225.178, IPv6 2a03:5f80:4::225:178, speed 100000 (100G), 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 IPv4 address missing from PeeringDB 195.208.208.185 195.208.209.245 195.208.208.35 195.208.208.185 195.208.209.243 195.208.209.245 195.208.210.173 - Add an entry: IPv4 195.208.208.35, IPv6 –, RS peer yes.
- Add an entry: IPv4 195.208.209.243, IPv6 –, RS peer yes.
- Add an entry: IPv4 195.208.210.173, IPv6 –, 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 IPv4 address missing from PeeringDB 193.232.87.65 193.232.87.65 193.232.87.121 - Add an entry: IPv4 193.232.87.121, IPv6 –, 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.
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 14 |
| Nov 18, 2026 | 14 |
| Nov 17, 2026 | 14 |
| Nov 16, 2026 | 14 |
| Nov 15, 2026 | 14 |
| Nov 14, 2026 | 14 |
| Nov 13, 2026 | 14 |
| Nov 12, 2026 | 14 |
| Nov 11, 2026 | 14 |
| Nov 10, 2026 | 14 |
| Nov 9, 2026 | 14 |
| Nov 8, 2026 | 14 |
| Nov 7, 2026 | 14 |
| Nov 6, 2026 | 14 |
| Nov 5, 2026 | 14 |
| Nov 4, 2026 | 14 |
| Nov 3, 2026 | 14 |
| Nov 2, 2026 | 14 |
| Nov 1, 2026 | 14 |
| Oct 31, 2026 | 14 |
| Oct 30, 2026 | 14 |
| Oct 29, 2026 | 14 |
| Oct 28, 2026 | 14 |
| Oct 27, 2026 | 14 |
| Oct 26, 2026 | 14 |
| Oct 25, 2026 | 14 |
| Oct 24, 2026 | 14 |
| Oct 23, 2026 | 14 |
| Oct 22, 2026 | 14 |
| Oct 21, 2026 | 14 |
| Oct 20, 2026 | 14 |
| Oct 19, 2026 | 14 |
| Oct 18, 2026 | 14 |
| Oct 17, 2026 | 14 |
| Oct 16, 2026 | 14 |
| Oct 15, 2026 | 14 |
| Oct 14, 2026 | 14 |
| Oct 13, 2026 | 14 |
| Oct 12, 2026 | 14 |
| Oct 11, 2026 | 14 |
| Oct 10, 2026 | 14 |
| Oct 9, 2026 | 14 |
| Oct 8, 2026 | 14 |
| Oct 7, 2026 | 14 |
| Oct 6, 2026 | 14 |
| Oct 5, 2026 | 14 |
| Oct 4, 2026 | 14 |
| Oct 3, 2026 | 14 |
Map
Where Okko'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.
| CLOUD-IX MSK Moscow, Russia | 2 × 10G | PeeringDB | |
| CLOUD-IX SPB St. Petersburg, Russia | 2 × 10G | PeeringDB | |
| Eurasia Peering IX Moscow, Russia | 2 × 10G | PeeringDB | |
| GNM-IX Amsterdam, Netherlands | 100G | Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs | |
| MSK-IX Ekaterinburg Ekaterinburg, Russia | Not in PeeringDB | ||
| MSK-IX Moscow Moscow, Russia | 2 × 40G | Both IPv4 not in PeeringDB | |
| MSK-IX Novosibirsk Novosibirsk, Russia | 10G | Both IPv4 not in PeeringDB | |
| MSK-IX Rostov-on-Don Rostov-on-Don, Russia | Not in PeeringDB | ||
| MSK-IX Saint-Petersburg St.Petersburg, Russia | 2 × 10G | Both | |
| MSK-IX Samara Samara, Russia | 10G | Both | |
| PITER-IX Saint-Petersburg Saint-Petersburg, Russia | 2 × 20G | PeeringDB | |
| Sea-IX Krasnodar, Russia | PeeringDB | ||
| SFO-IX Barnaul, Novosibirsk, Russia | 2 × 10G | PeeringDB | |
| W-IX Moscow, Russia | 2 × 40G + 2 × 20G | PeeringDB |
Okko lists no facilities in PeeringDB.
Recent changes Search them
- Nov 2, 2026 [IXF] AS211609 Okko now on MSK-IX Moscow's IX-F list
- Nov 2, 2026 [IXF] AS211609 Okko dropped from MSK-IX Moscow's IX-F list (still in PeeringDB and on its website's members list)