MiraLogic Telecommunication Systems
AS12668
Tools: Where can I peer with MiraLogic Telecommunication Systems? · Where should MiraLogic Telecommunication Systems peer next? · Compare MiraLogic Telecommunication Systems with another network
This network elsewhere: its routes on BGP Report
PeeringDB fix list Printable page · CSV
3 things to fix in MiraLogic Telecommunication Systems's PeeringDB record, from what its exchanges publish: 1 to add, 2 to check. As of 2026-11-19 18:41 UTC.
Make the changes on MiraLogic Telecommunication Systems'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 MiraLogic Telecommunication Systems's PeeringDB record. Add one entry per connection with these values.
-
2 connections, so 2 entries:
IPv4 178.18.233.16 IPv6 2a03:5f80:4:1::233:16 Speed 30000 Mbps (30G) RS peer Yes IPv4 178.18.225.156 IPv6 2a03:5f80:4::225:156 Speed 30000 Mbps (30G) 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 MiraLogic Telecommunication Systems 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.247 IPv6 2001:7f8:20:401::87:247 Speed Not published -
IPv4 194.226.100.247 IPv6 2001:7f8:20:201::100:247 Speed Not published IPv4 194.226.102.247 IPv6 2001:7f8:20:202::102:247 Speed Not published
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 5 |
| Nov 18, 2026 | 5 |
| Nov 17, 2026 | 5 |
| Nov 16, 2026 | 5 |
| Nov 15, 2026 | 5 |
| Nov 14, 2026 | 5 |
| Nov 13, 2026 | 5 |
| Nov 12, 2026 | 5 |
| Nov 11, 2026 | 5 |
| Nov 10, 2026 | 5 |
| Nov 9, 2026 | 5 |
| Nov 8, 2026 | 5 |
| Nov 7, 2026 | 5 |
| Nov 6, 2026 | 5 |
| Nov 5, 2026 | 5 |
| Nov 4, 2026 | 5 |
| Nov 3, 2026 | 5 |
| Nov 2, 2026 | 5 |
| Nov 1, 2026 | 5 |
| Oct 31, 2026 | 5 |
| Oct 30, 2026 | 5 |
| Oct 29, 2026 | 5 |
| Oct 28, 2026 | 5 |
| Oct 27, 2026 | 5 |
| Oct 26, 2026 | 5 |
| Oct 25, 2026 | 5 |
| Oct 24, 2026 | 5 |
| Oct 23, 2026 | 5 |
| Oct 22, 2026 | 5 |
| Oct 21, 2026 | 5 |
| Oct 20, 2026 | 5 |
| Oct 19, 2026 | 5 |
| Oct 18, 2026 | 5 |
| Oct 17, 2026 | 5 |
| Oct 16, 2026 | 5 |
| Oct 15, 2026 | 5 |
| Oct 14, 2026 | 5 |
| Oct 13, 2026 | 5 |
| Oct 12, 2026 | 5 |
| Oct 11, 2026 | 5 |
| Oct 10, 2026 | 5 |
| Oct 9, 2026 | 5 |
| Oct 8, 2026 | 5 |
| Oct 7, 2026 | 5 |
| Oct 6, 2026 | 5 |
| Oct 5, 2026 | 5 |
| Oct 4, 2026 | 5 |
| Oct 3, 2026 | 5 |
Map
Where MiraLogic Telecommunication Systems'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 | 30G | Not in PeeringDB | |
| MSK-IX Ekaterinburg Ekaterinburg, Russia | Both | ||
| MSK-IX Moscow Moscow, Russia | PeeringDB only | ||
| MSK-IX Novosibirsk Novosibirsk, Russia | PeeringDB only | ||
| MSK-IX Saint-Petersburg St.Petersburg, Russia | PeeringDB only |
These exchanges have a switch in a facility where MiraLogic Telecommunication Systems lists itself in PeeringDB, but don't have MiraLogic Telecommunication Systems 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 (2)
The buildings MiraLogic Telecommunication Systems lists in PeeringDB, and how many of the exchanges in each it's on.
| EKB, UralcodEkaterinburg | 2 of 5 | |
| Erlang.Ekb.MS145Ekaterinburg | 2 of 5 |