NGENIX
AS34879
OOO "Sovremennye setevye tekhnologii"
Tools: Where can I peer with NGENIX? · Where should NGENIX peer next? · Compare NGENIX with another network
This network elsewhere: its routes on BGP Report
PeeringDB fix list Printable page · CSV
4 things to fix in NGENIX's PeeringDB record, from what its exchanges publish: 1 to add, 3 to correct. As of 2026-11-19 12:40 UTC.
Make the changes on NGENIX'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 (1)
On the exchange's own member list, but not in NGENIX'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.
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 IPv6 address missing from PeeringDB none 2a03:5f80:4::224:131 2a03:5f80:4::224:223 - In the entry with IPv4 178.18.224.131: set IPv6 to 2a03:5f80:4::224:131 (now empty).
- In the entry with IPv4 178.18.224.223: set IPv6 to 2a03:5f80:4::224:223 (now empty).
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 IPv6 address missing from PeeringDB none 2001:7f8:20:101::208:37 2001:7f8:20:101::208:74 2001:7f8:20:101::209:91 - In the entry with IPv4 195.208.208.37: set IPv6 to 2001:7f8:20:101::208:37 (now empty).
- In the entry with IPv4 195.208.208.74: set IPv6 to 2001:7f8:20:101::208:74 (now empty).
- In the entry with IPv4 195.208.209.91: set IPv6 to 2001:7f8:20:101::209:91 (now empty).
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 IPv6 address missing from PeeringDB none 2001:7f8:20:201::100:48 2001:7f8:20:202::102:48 - In the entry with IPv4 194.226.100.48: set IPv6 to 2001:7f8:20:201::100:48 (now empty).
- In the entry with IPv4 194.226.102.48: set IPv6 to 2001:7f8:20:202::102:48 (now empty).
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 | 11 |
| Nov 18, 2026 | 11 |
| Nov 17, 2026 | 11 |
| Nov 16, 2026 | 11 |
| Nov 15, 2026 | 11 |
| Nov 14, 2026 | 11 |
| Nov 13, 2026 | 11 |
| Nov 12, 2026 | 11 |
| Nov 11, 2026 | 11 |
| Nov 10, 2026 | 11 |
| Nov 9, 2026 | 11 |
| Nov 8, 2026 | 11 |
| Nov 7, 2026 | 11 |
| Nov 6, 2026 | 11 |
| Nov 5, 2026 | 11 |
| Nov 4, 2026 | 11 |
| Nov 3, 2026 | 11 |
| Nov 2, 2026 | 11 |
| Nov 1, 2026 | 11 |
| Oct 31, 2026 | 11 |
| Oct 30, 2026 | 11 |
| Oct 29, 2026 | 11 |
| Oct 28, 2026 | 11 |
| Oct 27, 2026 | 11 |
| Oct 26, 2026 | 11 |
| Oct 25, 2026 | 11 |
| Oct 24, 2026 | 11 |
| Oct 23, 2026 | 11 |
| Oct 22, 2026 | 11 |
| Oct 21, 2026 | 11 |
| Oct 20, 2026 | 11 |
| Oct 19, 2026 | 11 |
| Oct 18, 2026 | 11 |
| Oct 17, 2026 | 11 |
| Oct 16, 2026 | 11 |
| Oct 15, 2026 | 11 |
| Oct 14, 2026 | 11 |
| Oct 13, 2026 | 11 |
| Oct 12, 2026 | 11 |
| Oct 11, 2026 | 11 |
| Oct 10, 2026 | 11 |
| Oct 9, 2026 | 11 |
| Oct 8, 2026 | 11 |
| Oct 7, 2026 | 11 |
| Oct 6, 2026 | 11 |
| Oct 5, 2026 | 11 |
| Oct 4, 2026 | 11 |
| Oct 3, 2026 | 11 |
Map
Where NGENIX'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 | PeeringDB | ||
| GNM-IX Amsterdam, Netherlands | Both IPv6 not in PeeringDB | ||
| KG-IX Bishkek Bishkek, Kyrgyzstan | Not in PeeringDB | ||
| MSK-IX Ekaterinburg Ekaterinburg, Russia | Both | ||
| MSK-IX Moscow Moscow, Russia | Both IPv6 not in PeeringDB | ||
| MSK-IX Novosibirsk Novosibirsk, Russia | Both | ||
| MSK-IX Saint-Petersburg St.Petersburg, Russia | Both IPv6 not in PeeringDB | ||
| MSK-IX Samara Samara, Russia | Both | ||
| MSK-IX Vladivostok Vladivostok, Russia | Both | ||
| PITER-IX Moscow Moscow, Russia | 2 × 100G | PeeringDB | |
| PITER-IX Saint-Petersburg Saint-Petersburg, Russia | 100G | PeeringDB |
These exchanges have a switch in a facility where NGENIX lists itself in PeeringDB, but don't have NGENIX 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.
| Global-IXAmsterdam, Netherlands | 138 | |
| Eurasia Peering IXMoscow, Russia | 136 | |
| W-IXMoscow, Russia | 66 | |
| SFO-IXBarnaul, Novosibirsk, Russia | 30 | |
| CLOUD-IX SPBSt. Petersburg, Russia | 25 | |
| CLOUD-IX EKTEkaterinburg, Russia | 6 | |
| PIRIXSt.Petersburg, Russia | 6 |
Facilities (8)
The buildings NGENIX lists in PeeringDB, and how many of the exchanges in each it's on.
| Moscow M9Moscow | 5 of 9 | |
| Raduga-2St. Petersburg | 5 of 8 | |
| Erlang.Ekb.MS145Ekaterinburg | 3 of 5 | |
| StoreDataMoscow | 3 of 4 | |
| Moscow TehnoGorodMoscow | 2 of 3 | |
| Moscow M10Moscow | 1 of 1 | |
| ITI-IX-T252Tashkent | No exchange | |
| Optizon KrasnoyarskKrasnoyarsk | No exchange |
Recent changes Search them
- Nov 13, 2026 [IXF] AS34879 NGENIX now on MSK-IX Novosibirsk's IX-F list
- Nov 13, 2026 [IXF] AS34879 NGENIX now on MSK-IX Vladivostok's IX-F list
- Nov 13, 2026 [IXF] AS34879 NGENIX dropped from MSK-IX Novosibirsk's IX-F list (still in PeeringDB)
- Nov 13, 2026 [IXF] AS34879 NGENIX dropped from MSK-IX Vladivostok's IX-F list (still in PeeringDB)