Wildberries
AS57073
LLC Wildberries
Tools: Where can I peer with Wildberries? · Where should Wildberries peer next? · Compare Wildberries 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 Wildberries's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-11-19 12:40 UTC.
Make the changes on Wildberries's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
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 IPv6 address missing from PeeringDB none 2a03:5f80:4::224:84 2a03:5f80:4::225:47 2a03:5f80:4::225:218 2a03:5f80:4::227:90 - In the entry with IPv4 178.18.224.84: set IPv6 to 2a03:5f80:4::224:84 (now empty).
- In the entry with IPv4 178.18.225.218: set IPv6 to 2a03:5f80:4::225:218 (now empty).
- In the entry with IPv4 178.18.225.47: set IPv6 to 2a03:5f80:4::225:47 (now empty).
- In the entry with IPv4 178.18.227.90: set IPv6 to 2a03:5f80:4::227:90 (now empty).
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 IPv6 address missing from PeeringDB 2001:7f8:20:101::208:253 2001:7f8:20:101::209:10 2001:7f8:20:101::209:127 2001:7f8:20:101::209:176 2001:7f8:20:101::209:237 2001:7f8:20:101::210:33 2001:7f8:20:101::208:253 2001:7f8:20:101::209:10 2001:7f8:20:101::209:127 2001:7f8:20:101::209:176 2001:7f8:20:101::209:237 2001:7f8:20:101::210:33 2001:7f8:20:101::211:25 2001:7f8:20:101::211:26 - In the entry with IPv4 195.208.211.25: set IPv6 to 2001:7f8:20:101::211:25 (now empty).
- In the entry with IPv4 195.208.211.26: set IPv6 to 2001:7f8:20:101::211:26 (now empty).
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.
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 6 |
| Nov 18, 2026 | 6 |
| Nov 17, 2026 | 6 |
| Nov 16, 2026 | 6 |
| Nov 15, 2026 | 6 |
| Nov 14, 2026 | 6 |
| Nov 13, 2026 | 6 |
| Nov 12, 2026 | 6 |
| Nov 11, 2026 | 6 |
| Nov 10, 2026 | 6 |
| Nov 9, 2026 | 6 |
| Nov 8, 2026 | 6 |
| Nov 7, 2026 | 6 |
| Nov 6, 2026 | 6 |
| Nov 5, 2026 | 6 |
| Nov 4, 2026 | 6 |
| Nov 3, 2026 | 6 |
| Nov 2, 2026 | 6 |
| Nov 1, 2026 | 6 |
| Oct 31, 2026 | 6 |
| Oct 30, 2026 | 6 |
| Oct 29, 2026 | 6 |
| Oct 28, 2026 | 6 |
| 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 | 6 |
| Oct 19, 2026 | 6 |
| Oct 18, 2026 | 6 |
| Oct 17, 2026 | 6 |
| Oct 16, 2026 | 6 |
| Oct 15, 2026 | 6 |
| Oct 14, 2026 | 6 |
| Oct 13, 2026 | 6 |
| Oct 12, 2026 | 6 |
| Oct 11, 2026 | 6 |
| Oct 10, 2026 | 6 |
| Oct 9, 2026 | 6 |
| Oct 8, 2026 | 6 |
| Oct 7, 2026 | 6 |
| Oct 6, 2026 | 6 |
| Oct 5, 2026 | 6 |
| Oct 4, 2026 | 6 |
| Oct 3, 2026 | 6 |
Map
Where Wildberries'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.
| Eurasia Peering IX Moscow, Russia | 10G | PeeringDB | |
| Global-IX Amsterdam, Netherlands | 3 × 200G | PeeringDB | |
| GNM-IX Amsterdam, Netherlands | 4 × 100G | Both IPv6 not in PeeringDB | |
| MSK-IX Moscow Moscow, Russia | Both IPv6 not in PeeringDB | ||
| PITER-IX Moscow Moscow, Russia | 100G | PeeringDB | |
| PITER-IX Saint-Petersburg Saint-Petersburg, Russia | 100G | PeeringDB |
Wildberries lists no facilities in PeeringDB.