Redge Technologies
AS57811 · Atende Software, redGalaxy CDN, redCDN, Redge Guardian, redGuardian
Redge Technologies sp. z o.o.
Tools: Where can I peer with Redge Technologies? · Where should Redge Technologies peer next? · Compare Redge Technologies with another network
This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report
PeeringDB fix list Printable page · CSV
3 things to fix in Redge Technologies's PeeringDB record, from what its exchanges publish: 1 to add, 2 to correct. As of 2026-11-19 12:40 UTC.
Make the changes on Redge Technologies'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 Redge Technologies'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 (2)
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 2 × 100G 25G - In the entry with IPv4 185.0.20.20: set Speed to 25000 (25G) (now 100000).
- In the entry with IPv4 185.0.21.42: set Speed to 25000 (25G) (now 100000).
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 212.91.0.40 212.91.0.41 212.91.0.132 212.91.0.192 212.91.0.40 212.91.0.41 212.91.0.44 212.91.0.132 212.91.0.192 - In the entry with IPv4 212.91.0.132: set IPv4 to (empty) (now 212.91.0.132).
- In the entry with IPv4 212.91.0.192: set IPv4 to (empty) (now 212.91.0.192).
- In the entry with IPv4 212.91.0.40: set IPv4 to (empty) (now 212.91.0.40).
- In the entry with IPv4 212.91.0.41: set IPv4 to (empty) (now 212.91.0.41).
- Add an entry: IPv4 212.91.0.40, IPv6 –, speed 400000 (400G).
- Add an entry: IPv4 212.91.0.41, IPv6 –, speed 400000 (400G).
- Add an entry: IPv4 212.91.0.44, IPv6 –, speed 400000 (400G).
- Add an entry: IPv4 212.91.0.192, IPv6 –, speed 400000 (400G).
- Add an entry: IPv4 212.91.0.132, IPv6 –, speed 400000 (400G).
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 | 8 |
| Nov 18, 2026 | 8 |
| Nov 17, 2026 | 8 |
| Nov 16, 2026 | 8 |
| Nov 15, 2026 | 8 |
| Nov 14, 2026 | 8 |
| Nov 13, 2026 | 8 |
| Nov 12, 2026 | 8 |
| Nov 11, 2026 | 9 |
| Nov 10, 2026 | 9 |
| Nov 9, 2026 | 9 |
| Nov 8, 2026 | 9 |
| Nov 7, 2026 | 9 |
| Nov 6, 2026 | 9 |
| Nov 5, 2026 | 9 |
| Nov 4, 2026 | 9 |
| Nov 3, 2026 | 9 |
| Nov 2, 2026 | 10 |
| Nov 1, 2026 | 10 |
| Oct 31, 2026 | 10 |
| Oct 30, 2026 | 10 |
| Oct 29, 2026 | 10 |
| Oct 28, 2026 | 10 |
| Oct 27, 2026 | 10 |
| Oct 26, 2026 | 10 |
| Oct 25, 2026 | 10 |
| Oct 24, 2026 | 10 |
| Oct 23, 2026 | 10 |
| Oct 22, 2026 | 10 |
| Oct 21, 2026 | 10 |
| Oct 20, 2026 | 10 |
| Oct 19, 2026 | 10 |
| Oct 18, 2026 | 10 |
| Oct 17, 2026 | 10 |
| Oct 16, 2026 | 10 |
| Oct 15, 2026 | 10 |
| Oct 14, 2026 | 10 |
| Oct 13, 2026 | 10 |
| Oct 12, 2026 | 10 |
| Oct 11, 2026 | 10 |
| Oct 10, 2026 | 10 |
| Oct 9, 2026 | 10 |
| Oct 8, 2026 | 10 |
| Oct 7, 2026 | 10 |
| Oct 6, 2026 | 10 |
| Oct 5, 2026 | 10 |
| Oct 4, 2026 | 10 |
| Oct 3, 2026 | 10 |
In the last 30 days Redge Technologies joined 0 exchanges and left 2. Growing networks
Left
Map
Where Redge Technologies'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.
| 1-IX UA Kyiv, Ukraine | Not in PeeringDB | ||
| EPIX.Katowice Katowice/Silesia, Poland | 2 × 100G | Both | |
| EPIX.Warszawa Warsaw, Poland | 2 × 100G | Both | |
| Equinix Warsaw Warsaw, Poland | 100G | PeeringDB | |
| IX.br (PTT.br) São Paulo São Paulo/SP, Brazil | 10G | Both | |
| Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia | 2 × 100G | Both Speed differs | |
| THINX Warsaw Warsaw, Poland | 4 × 100G | Both IPv4 not in PeeringDB | |
| TPIX PL Warsaw, Poland | 4 × 100G | Both |
These exchanges have a switch in a facility where Redge Technologies lists itself in PeeringDB, but don't have Redge Technologies 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.
| LINX LON1London, United Kingdom | 837 | |
| GNM-IXAmsterdam, Netherlands | 741 | |
| NL-ixAmsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands | 672 | |
| France-IX ParisParis, France | 452 | |
| LINX LON2London, United Kingdom | 315 | |
| LONAPLondon, United Kingdom | 311 | |
| 1-IX EUNew-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland | 283 | |
| Giganet IXNAmsterdam, Frankfurt am Main, Kharkiv, Kyiv, Lviv, Odesa, Warsaw, Zaporizhzhia, Zhytomyr, Ukraine | 268 | |
| INTERIXAmsterdam, Netherlands | 262 | |
| SwissIXZurich, Switzerland | 253 | |
| Equinix ParisParis, France | 239 | |
| NIX.CZPrague, Czechia | 225 | |
| NetIXSofia, Bulgaria | 204 | |
| nineAmsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France | 160 | |
| Global-IXAmsterdam, Netherlands | 138 | |
| CHIX-CHFrauenfeld, Switzerland | 66 | |
| HopusParis, Lyon, Marseille, Geneva, Zurich, Amsterdam, Frankfurt, France | 58 | |
| Equinix LondonLondon, United Kingdom | 53 | |
| Giganet IXN WarsawWarsaw, Poland | 49 | |
| Giganet IXN AmsterdamAmsterdam, Netherlands | 47 | |
| Equinix ZurichZurich, Switzerland | 40 | |
| 1-PL FREEWarsaw, Wroclaw, Katowice, Poland | 32 | |
| nine - six in ParisParis, France | 24 | |
| SFINXParis, France | 23 | |
| Giganet IXN OdesaOdessa, Ukraine | 22 | |
| 1-FR FREEParis, France | 14 | |
| ERA-IX ParisParis, France | 14 | |
| EuroRhine-IXStrasbourg, France | 14 | |
| Giganet IXN KharkіvKharkiv, Ukraine | 13 | |
| NIX.CZ FENIXPrague, Czechia | 8 | |
| 1-CZ FREEPrague, Czechia | 6 | |
| EURASIA-IX.NETIstanbul, Türkiye | 6 | |
| France-IX Paris EssentielParis, France | 6 | |
| Global Peer ExchangeWashington, United States | 6 |
Facilities (10)
The buildings Redge Technologies lists in PeeringDB, and how many of the exchanges in each it's on.
| Telehouse - Paris 2 (Voltaire - Léon Frot)Paris | 0 of 17 | |
| Equinix WA1 - Warsaw, Centrum LIMWarsaw | 4 of 13 | |
| Equinix LD8 - London, DocklandsLondon | 0 of 9 | |
| ATMAN Data Center Warsaw-2 (WAW-2, Konstruktorska 5)Warsaw | 3 of 8 | |
| CE Colo PraguePrague | 1 of 8 | |
| Equinix ZH4 - ZurichZurich | 0 of 8 | |
| ATMAN Data Center Warsaw-1 (WAW-1, Grochowska 21A)Warsaw | 2 of 6 | |
| OPCORE - DC2 / PAR2Vitry-sur-Seine | 0 of 4 | |
| OPCORE - DC3 / PAR3Vitry-sur-Seine | 0 of 4 | |
| Digital Realty Paris PAR5Paris | 0 of 1 |
Recent changes Search them
- Nov 12, 2026 [WEB] AS57811 Redge Technologies left 1-IX EU
- Nov 3, 2026 [PDB] AS57811 Redge Technologies no longer in PeeringDB at 1-IX EU (still on its website's members list)
- Nov 3, 2026 [PDB] AS57811 Redge Technologies left 1-PL FREE