Red Panda Network
AS212123 · Tyrasuki
Tools: Where can I peer with Red Panda Network? · Where should Red Panda Network peer next? · Compare Red Panda Network 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 Red Panda Network's PeeringDB record, from what its exchanges publish: 3 to add. As of 2026-11-19 18:41 UTC.
Make the changes on Red Panda Network'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 (3)
On the exchange's own member list, but not in Red Panda Network's PeeringDB record. Add one entry per connection with these values.
-
IPv4 206.81.104.193 IPv6 2602:fed2:fff:ffff::193 Speed 1000 Mbps (1G) 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.
-
IPv4 185.1.147.126 IPv6 2001:7f8:ca:1::126 Speed 1000 Mbps (1G) 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.
-
IPv4 193.189.82.154 IPv6 2001:7f8:33::a121:2123:1 Speed 100 Mbps (100M) 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.
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 4 |
| Nov 18, 2026 | 4 |
| Nov 17, 2026 | 4 |
| Nov 16, 2026 | 4 |
| Nov 15, 2026 | 4 |
| Nov 14, 2026 | 4 |
| Nov 13, 2026 | 4 |
| Nov 12, 2026 | 4 |
| Nov 11, 2026 | 4 |
| Nov 10, 2026 | 4 |
| Nov 9, 2026 | 4 |
| Nov 8, 2026 | 4 |
| Nov 7, 2026 | 4 |
| Nov 6, 2026 | 4 |
| Nov 5, 2026 | 4 |
| Nov 4, 2026 | 4 |
| Nov 3, 2026 | 4 |
| Nov 2, 2026 | 4 |
| Nov 1, 2026 | 4 |
| Oct 31, 2026 | 4 |
| Oct 30, 2026 | 4 |
| Oct 29, 2026 | 4 |
| Oct 28, 2026 | 4 |
| Oct 27, 2026 | 4 |
| Oct 26, 2026 | 4 |
| Oct 25, 2026 | 3 |
| Oct 24, 2026 | 3 |
| Oct 23, 2026 | 3 |
| Oct 22, 2026 | 3 |
| Oct 21, 2026 | 3 |
| Oct 20, 2026 | 4 |
| Oct 19, 2026 | 4 |
| Oct 18, 2026 | 4 |
| Oct 17, 2026 | 4 |
| Oct 16, 2026 | 4 |
| Oct 15, 2026 | 4 |
| Oct 14, 2026 | 4 |
| Oct 13, 2026 | 4 |
| Oct 12, 2026 | 4 |
| Oct 11, 2026 | 4 |
| Oct 10, 2026 | 4 |
| Oct 9, 2026 | 4 |
| Oct 8, 2026 | 4 |
| Oct 7, 2026 | 4 |
| Oct 6, 2026 | 4 |
| Oct 5, 2026 | 4 |
| Oct 4, 2026 | 4 |
| Oct 3, 2026 | 4 |
Map
Where Red Panda Network'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.
| EVIXVIX Fremont, United States | 1G | Not in PeeringDB | |
| FogIXP Avers, Switzerland | 1G | Not in PeeringDB | |
| KleyReX Frankfurt, Germany | 100M | Not in PeeringDB | |
| LOCIX FRANKFURT Frankfurt am Main, Germany | 10G | PeeringDB |
These exchanges have a switch in a facility where Red Panda Network lists itself in PeeringDB, but don't have Red Panda Network 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.
| DE-CIX New YorkNew York, United States | 281 | |
| NetIXSofia, Bulgaria | 204 | |
| NYIIX New YorkNew York, United States | 186 | |
| Community-IXBerlin, Frankfurt, Germany | 25 | |
| MegaIX New YorkNew York, United States | 22 | |
| STACIXFrankfurt, Germany | 5 |
Facilities (2)
The buildings Red Panda Network lists in PeeringDB, and how many of the exchanges in each it's on.
| MK Netzdienste DatacenterFrankfurt am Main | 2 of 4 | |
| Telehouse - New York ChelseaNew York | 0 of 4 |