Navice Communications B.V.
AS38230
Navice Consulting
Tools: Where can I peer with Navice Communications B.V.? · Where should Navice Communications B.V. peer next? · Compare Navice Communications B.V. 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 Navice Communications B.V.'s PeeringDB record, from what its exchanges publish: 1 to correct, 1 to check. As of 2026-11-19 12:40 UTC.
Make the changes on Navice Communications B.V.'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 (1)
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 1G 200G - In the entry with IPv4 185.1.170.138: set Speed to 200000 (200G) (now 1000).
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If Navice Communications B.V. has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 – IPv6 2001:7f8:11f:be00:38:230:0:1 Speed Not published This exchange only publishes a website list, and some leave out members who ask not to be listed.
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 22 |
| Nov 18, 2026 | 22 |
| Nov 17, 2026 | 22 |
| Nov 16, 2026 | 22 |
| Nov 15, 2026 | 22 |
| Nov 14, 2026 | 22 |
| Nov 13, 2026 | 22 |
| Nov 12, 2026 | 22 |
| Nov 11, 2026 | 22 |
| Nov 10, 2026 | 22 |
| Nov 9, 2026 | 22 |
| Nov 8, 2026 | 22 |
| Nov 7, 2026 | 22 |
| Nov 6, 2026 | 22 |
| Nov 5, 2026 | 22 |
| Nov 4, 2026 | 22 |
| Nov 3, 2026 | 22 |
| Nov 2, 2026 | 22 |
| Nov 1, 2026 | 22 |
| Oct 31, 2026 | 22 |
| Oct 30, 2026 | 22 |
| Oct 29, 2026 | 22 |
| Oct 28, 2026 | 22 |
| Oct 27, 2026 | 22 |
| Oct 26, 2026 | 22 |
| Oct 25, 2026 | 22 |
| Oct 24, 2026 | 22 |
| Oct 23, 2026 | 22 |
| Oct 22, 2026 | 22 |
| Oct 21, 2026 | 22 |
| Oct 20, 2026 | 22 |
| Oct 19, 2026 | 22 |
| Oct 18, 2026 | 22 |
| Oct 17, 2026 | 22 |
| Oct 16, 2026 | 22 |
| Oct 15, 2026 | 22 |
| Oct 14, 2026 | 22 |
| Oct 13, 2026 | 22 |
| Oct 12, 2026 | 22 |
| Oct 11, 2026 | 22 |
| Oct 10, 2026 | 22 |
| Oct 9, 2026 | 22 |
| Oct 8, 2026 | 22 |
| Oct 7, 2026 | 22 |
| Oct 6, 2026 | 22 |
| Oct 5, 2026 | 22 |
| Oct 4, 2026 | 22 |
| Oct 3, 2026 | 22 |
Map
Where Navice Communications B.V.'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.
| Barcelona-IX Barcelona, Spain | Both | ||
| BEE-IX Lviv, Ukraine | PeeringDB only | ||
| DE-CIX Dusseldorf Düsseldorf, Germany | 1G | Both Speed differs | |
| FogIXP Avers, Switzerland | 4 × 1G | Both | |
| FogIXP Frankfurt Frankfurt, Germany | 10G | PeeringDB | |
| ixFabric - Amsterdam Amsterdam, Netherlands | 10G | PeeringDB | |
| ixFabric - Frankfurt Frankfurt, Germany | 1G | PeeringDB | |
| ixFabric - Kansas Kansas, United States | 1G | PeeringDB | |
| ixFabric - London London, United Kingdom | 1G | PeeringDB | |
| ixFabric - PerthVIX Perth, Australia | 1G | PeeringDB | |
| ixFabric - Singapore Singapore, Singapore | 1G | PeeringDB | |
| ixFabric - Sydney Sydney, Australia | 1G | PeeringDB | |
| ixFabric - Zurich Zurich, Switzerland | 1G | PeeringDB | |
| KleyReX Frankfurt, Germany | 100M | Both | |
| LOCIX DUSSELDORF Dusseldorf, Germany | 1G | PeeringDB | |
| LOCIX NETHERLANDS Meppel, Netherlands | 1G | PeeringDB | |
| LVIV-IX Lviv, Ukraine | PeeringDB | ||
| NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands | Both | ||
| NVIX Ashburn, United States | 1G | Both | |
| ONIX Toronto, Canada | 1G | Both | |
| RUDAKI-IX Kiev, Ukraine | 1G | Both | |
| Speed-IX Dronten, Netherlands | 1G | Both |
Navice Communications B.V. lists no facilities in PeeringDB.