Evolus
AS215120
Evolus IT Solutions GmbH
Tools: Where can I peer with Evolus? · Where should Evolus peer next? · Compare Evolus 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 Evolus's PeeringDB record, from what its exchanges publish: 1 to add, 4 to correct. As of 2026-11-19 18:41 UTC.
Make the changes on Evolus'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 Evolus'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 (4)
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 Port speed differs 100G 30G - In the entry with IPv4 193.178.185.186: set Speed to 30000 (30G) (now 100000).
PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 100G 10G - In the entry with IPv4 185.0.27.84: set Speed to 10000 (10G) (now 100000).
PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 2 × 100G 100G PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 100G 12.5G - In the entry with IPv4 185.0.21.51: set Speed to 12500 (12.5G) (now 100000).
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 | 7 |
| Nov 7, 2026 | 7 |
| 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 | 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 | 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 Evolus'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.
| BCIX Berlin, Germany | 100G | Both Speed differs | |
| ERA-IX Amsterdam Amsterdam, Netherlands | Website list only | ||
| ERA-IX Frankfurt Frankfurt, Germany | 100G | Both Speed differs | |
| ERA-IX Vienna Vienna, Austria | 200G | Both | |
| GNM-IX Amsterdam, Netherlands | 2 × 100G | Both Speed differs | |
| Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia | 100G | Both Speed differs | |
| VIX Vienna, Austria | 100G | Both |
These exchanges have a switch in a facility where Evolus lists itself in PeeringDB, but don't have Evolus 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.
| NL-ixAmsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands | 672 | |
| NIX.CZPrague, Czechia | 225 | |
| NetIXSofia, Bulgaria | 204 | |
| Global-IXAmsterdam, Netherlands | 138 | |
| BIXBudapest, Hungary | 122 | |
| SIX.SKBratislava, Slovakia | 71 | |
| NIX.SKBratislava, Slovakia | 68 | |
| SOX SerbiaBelgrade/Serbia, Serbia | 46 | |
| MegaIX BerlinBerlin, Germany | 43 | |
| Community-IXBerlin, Frankfurt, Germany | 25 | |
| NIX.CZ FENIXPrague, Czechia | 8 | |
| EURASIA-IX.NETIstanbul, Türkiye | 6 | |
| Global Peer ExchangeWashington, United States | 6 |
Facilities (5)
The buildings Evolus lists in PeeringDB, and how many of the exchanges in each it's on.
| Digital Realty VIE1/2 - ViennaVienna | 4 of 13 | |
| CarrierColo Berlin Luetzow (I/P/B/ site B)Berlin | 1 of 5 | |
| Penta Infra Berlin BER01Berlin | 1 of 1 | |
| TornadoDC - FRA1Langen | 1 of 1 | |
| Penta Infra Berlin BER02Berlin | No exchange |