NETGUARD
AS39251 · netguard
NETGUARD Ltd.
Tools: Where can I peer with NETGUARD? · Where should NETGUARD peer next? · Compare NETGUARD with another network
This network elsewhere: its routes on BGP Report
PeeringDB fix list Printable page · CSV
2 things to fix in NETGUARD's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-11-19 12:40 UTC.
Make the changes on NETGUARD'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 IPv4 address missing from PeeringDB 193.169.198.210 193.169.198.210 193.169.198.211 IPv6 address missing from PeeringDB 2001:7f8:58::9953:0:1 2001:7f8:58::9953:0:1 2001:7f8:58::9953:0:2 - Add an entry: IPv4 193.169.198.211, IPv6 2001:7f8:58::9953:0:2.
-
Problem PeeringDB has The export has Port speed differs 4 × 10G 10G 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 | 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 | 4 |
| Oct 24, 2026 | 4 |
| Oct 23, 2026 | 4 |
| Oct 22, 2026 | 4 |
| Oct 21, 2026 | 4 |
| 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 NETGUARD'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.
| B-IX Sofia, Bulgaria | 10G | Both | |
| BIX.BG Sofia, Bulgaria | 10G | Both IPv4 not in PeeringDBIPv6 not in PeeringDB | |
| GNM-IX Amsterdam, Netherlands | 4 × 10G | Both Speed differs | |
| NetIX Sofia, Bulgaria | 2 × 10G | Both |
These exchanges have a switch in a facility where NETGUARD lists itself in PeeringDB, but don't have NETGUARD 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.
| 1-IX EUNew-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland | 283 | |
| InterLAN-IXBucharest, Romania | 149 | |
| Global-IXAmsterdam, Netherlands | 138 | |
| TurkIX SofiaSofia, Bulgaria | 47 | |
| SOX SerbiaBelgrade/Serbia, Serbia | 46 | |
| RoNIXBucharest, Romania | 43 | |
| Balcan-IXBucharest, Romania | 29 | |
| GIBIRIXİstanbul, Türkiye | 28 | |
| 1-BG FREESofia, Bulgaria | 22 | |
| MegaIX SofiaSofia, Bulgaria | 20 | |
| RegPEXAnkara, Türkiye | 19 | |
| NVL-IXAthens, Greece | 14 | |
| T-CIXSofia, Bulgaria | 9 | |
| Global Peer ExchangeWashington, United States | 6 |
Facilities (3)
The buildings NETGUARD lists in PeeringDB, and how many of the exchanges in each it's on.
| TELEPOINT Sofia CentreSofia | 4 of 17 | |
| Sofia Data Center (SDC)Sofia | 3 of 5 | |
| Plovdiv Teleport CenterPlovdiv | 1 of 1 |