Cross connects at Nikhef.

A cross connect is a physical run, fiber or copper, between two parties in the same facility: your rack to a carrier, your rack to a peer, terminated on both ends and carrying traffic. Because it's physical, it's permanent in a way logical config isn't, you can't roll one back from a console; someone has to walk to the rack and move the strand.

Nikhef, at Amsterdam Science Park, is one of Europe's densest interconnection points. If your network peers in the Netherlands, the path likely runs through here at some point. That density is exactly why a cross connect at Nikhef is so useful, and exactly why it's so easy to lose track of one once it's in.

The failure mode is rarely the install, it's everything after. A connect gets patched and turned up, the person who ordered it moves on, and a year later there's a panel full of connects nobody dares unplug. We stop that at the source: every connect is labeled to your scheme, photographed per connect, and recorded in Netbox, so it stays traceable long after turn-up.

And because we're already inside the facility, turn-up is fast, a new peer or carrier comes online when you need it, not weeks later. We handle installs, removals, migrations between suites and console sessions for kit you already have racked here.