MOTIV
AS31499 · MOTIV
Ekaterinburg-2000 LLC
Tools: Where can I peer with MOTIV? · Where should MOTIV peer next? · Compare MOTIV with another network
This network elsewhere: its routes on BGP Report
PeeringDB fix list Printable page · CSV
3 things to fix in MOTIV's PeeringDB record, from what its exchanges publish: 1 to correct, 2 to check. As of 2026-11-19 12:40 UTC.
Make the changes on MOTIV's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
Correct these entries (1)
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.226.163 178.18.226.163 178.18.233.29 178.18.233.32 IPv6 address missing from PeeringDB 2a03:5f80:4::226:163 2a03:5f80:4::226:163 2a03:5f80:4:1::233:29 2a03:5f80:4:1::233:32 Port speed differs 20G 40G + 10G - In the entry with IPv4 178.18.226.163: set Speed to 40000 (40G) (now 20000).
- Add an entry: IPv4 178.18.233.29, IPv6 2a03:5f80:4:1::233:29, speed 10000 (10G), RS peer yes.
- Add an entry: IPv4 178.18.233.32, IPv6 2a03:5f80:4:1::233:32, speed 10000 (10G), 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.
Check these entries (2)
In PeeringDB, but on none of the exchange's own lists. If MOTIV has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 193.232.87.117 IPv6 2001:7f8:20:401::87:117 Speed 50000 Mbps (50G) IPv4 193.232.87.118 IPv6 2001:7f8:20:401::87:118 Speed 50000 Mbps (50G) -
IPv4 194.226.101.117 IPv6 2001:7f8:20:201::101:117 Speed 50000 Mbps (50G) IPv4 194.226.103.117 IPv6 2001:7f8:20:202::103:117 Speed 50000 Mbps (50G)
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 6 |
| Nov 18, 2026 | 6 |
| Nov 17, 2026 | 6 |
| Nov 16, 2026 | 6 |
| Nov 15, 2026 | 6 |
| Nov 14, 2026 | 6 |
| Nov 13, 2026 | 6 |
| Nov 12, 2026 | 6 |
| Nov 11, 2026 | 6 |
| Nov 10, 2026 | 6 |
| Nov 9, 2026 | 6 |
| Nov 8, 2026 | 6 |
| Nov 7, 2026 | 6 |
| Nov 6, 2026 | 6 |
| Nov 5, 2026 | 6 |
| Nov 4, 2026 | 6 |
| Nov 3, 2026 | 6 |
| Nov 2, 2026 | 6 |
| Nov 1, 2026 | 6 |
| Oct 31, 2026 | 6 |
| Oct 30, 2026 | 6 |
| Oct 29, 2026 | 6 |
| Oct 28, 2026 | 6 |
| Oct 27, 2026 | 6 |
| Oct 26, 2026 | 6 |
| Oct 25, 2026 | 6 |
| Oct 24, 2026 | 6 |
| Oct 23, 2026 | 6 |
| Oct 22, 2026 | 6 |
| Oct 21, 2026 | 6 |
| Oct 20, 2026 | 6 |
| Oct 19, 2026 | 6 |
| Oct 18, 2026 | 6 |
| Oct 17, 2026 | 6 |
| Oct 16, 2026 | 6 |
| Oct 15, 2026 | 6 |
| Oct 14, 2026 | 6 |
| Oct 13, 2026 | 6 |
| Oct 12, 2026 | 6 |
| Oct 11, 2026 | 6 |
| Oct 10, 2026 | 6 |
| Oct 9, 2026 | 6 |
| Oct 8, 2026 | 6 |
| Oct 7, 2026 | 6 |
| Oct 6, 2026 | 6 |
| Oct 5, 2026 | 6 |
| Oct 4, 2026 | 6 |
| Oct 3, 2026 | 6 |
Map
Where MOTIV'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.
| GNM-IX Amsterdam, Netherlands | 20G | Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs | |
| MSK-IX Ekaterinburg Ekaterinburg, Russia | 2 × 50G | Both | |
| MSK-IX Moscow Moscow, Russia | 2 × 50G | PeeringDB only | |
| MSK-IX Novosibirsk Novosibirsk, Russia | 2 × 50G | PeeringDB only | |
| MSK-IX Saint-Petersburg St.Petersburg, Russia | 2 × 50G | PeeringDB only | |
| W-IX Moscow, Russia | 40G + 20G | PeeringDB |
These exchanges have a switch in a facility where MOTIV lists itself in PeeringDB, but don't have MOTIV 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.
| CLOUD-IX MSKMoscow, Russia | 52 | |
| SFO-IXBarnaul, Novosibirsk, Russia | 30 | |
| CLOUD-IX EKTEkaterinburg, Russia | 6 |
Facilities (3)
The buildings MOTIV lists in PeeringDB, and how many of the exchanges in each it's on.
| Erlang.Ekb.MS145Ekaterinburg | 2 of 5 | |
| DataHouse EkaterinburgEkaterinburg | 0 of 2 | |
| Erlang.Ekb.SH10Ekaterinburg | No exchange |