TIS Dialog
AS31214 · TiS-Dialog
TIS Dialog LLC
Tools: Where can I peer with TIS Dialog? · Where should TIS Dialog peer next? · Compare TIS Dialog with another network
This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report
PeeringDB fix list Printable page · CSV
2 things to fix in TIS Dialog's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-11-19 12:40 UTC.
Make the changes on TIS Dialog'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 TIS Dialog'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 (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 in PeeringDB, not in the export 178.18.224.182 178.18.225.181 178.18.226.78 178.18.225.181 178.18.226.78 IPv6 address in PeeringDB, not in the export 2a03:5f80:4::224:182 2a03:5f80:4::225:181 2a03:5f80:4::226:78 2a03:5f80:4::225:181 2a03:5f80:4::226:78 Port speed differs 3 × 100G 2 × 100G - The entry with IPv4 178.18.224.182, IPv6 2a03:5f80:4::224:182 isn't in the export: delete it if that connection is gone.
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 | 7 |
| Nov 18, 2026 | 7 |
| Nov 17, 2026 | 7 |
| Nov 16, 2026 | 7 |
| Nov 15, 2026 | 7 |
| Nov 14, 2026 | 7 |
| Nov 13, 2026 | 7 |
| Nov 12, 2026 | 7 |
| Nov 11, 2026 | 7 |
| Nov 10, 2026 | 7 |
| Nov 9, 2026 | 7 |
| Nov 8, 2026 | 6 |
| Nov 7, 2026 | 6 |
| Nov 6, 2026 | 7 |
| Nov 5, 2026 | 7 |
| Nov 4, 2026 | 7 |
| Nov 3, 2026 | 7 |
| Nov 2, 2026 | 7 |
| Nov 1, 2026 | 7 |
| Oct 31, 2026 | 7 |
| Oct 30, 2026 | 7 |
| Oct 29, 2026 | 7 |
| Oct 28, 2026 | 7 |
| Oct 27, 2026 | 7 |
| Oct 26, 2026 | 7 |
| Oct 25, 2026 | 7 |
| Oct 24, 2026 | 7 |
| Oct 23, 2026 | 7 |
| Oct 22, 2026 | 7 |
| Oct 21, 2026 | 7 |
| Oct 20, 2026 | 7 |
| Oct 19, 2026 | 7 |
| Oct 18, 2026 | 7 |
| Oct 17, 2026 | 7 |
| Oct 16, 2026 | 7 |
| Oct 15, 2026 | 7 |
| Oct 14, 2026 | 7 |
| Oct 13, 2026 | 7 |
| Oct 12, 2026 | 7 |
| Oct 11, 2026 | 7 |
| Oct 10, 2026 | 7 |
| Oct 9, 2026 | 7 |
| Oct 8, 2026 | 7 |
| Oct 7, 2026 | 7 |
| Oct 6, 2026 | 7 |
| Oct 5, 2026 | 7 |
| Oct 4, 2026 | 7 |
| Oct 3, 2026 | 7 |
Map
Where TIS Dialog'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.
| Global-IX Amsterdam, Netherlands | 100G | PeeringDB | |
| GNM-IX Amsterdam, Netherlands | 3 × 100G | Both IPv4 not in exportIPv6 not in exportSpeed differs | |
| MSK-IX Moscow Moscow, Russia | 20G | Both | |
| PITER-IX Moscow Moscow, Russia | 100G | PeeringDB | |
| PITER-IX Saint-Petersburg Saint-Petersburg, Russia | 100G | PeeringDB | |
| SOLIX MTU1500 Stockholm, Sweden | Not in PeeringDB | ||
| W-IX Moscow, Russia | 30G | PeeringDB |
These exchanges have a switch in a facility where TIS Dialog lists itself in PeeringDB, but don't have TIS Dialog 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.
| Eurasia Peering IXMoscow, Russia | 136 | |
| MSK-IX Saint-PetersburgSt.Petersburg, Russia | 71 | |
| CLOUD-IX MSKMoscow, Russia | 52 | |
| SFO-IXBarnaul, Novosibirsk, Russia | 30 | |
| CLOUD-IX SPBSt. Petersburg, Russia | 25 | |
| PIRIXSt.Petersburg, Russia | 6 |
Facilities (3)
The buildings TIS Dialog lists in PeeringDB, and how many of the exchanges in each it's on.
| Bolshaya Morskaya 18St. Petersburg | 5 of 9 | |
| Moscow M9Moscow | 6 of 9 | |
| Tsvetochnaya Data CenterSt. Petersburg | 4 of 8 |