Data Center Cross-Connect Renewal: Match Every Port to a Live Service and Owner
A cross-connect can stay on a data center invoice long after the person who ordered it, the carrier circuit it supported, or the equipment it reached is gone.
The line item still looks official. The cable still exists. Somebody remembers that it was important.
That is not enough reason to renew it.
Before you accept another colocation or connectivity term, match every cross-connect to a live service, a physical port, a business dependency, and an owner who will defend the charge. If your team cannot complete that chain, the renewal needs more work.
The invoice is not a network map
A cross-connect is a physical link inside a data center facility. Equinix, for example, defines its Cross Connect product as dedicated physical cabling between two parties in an Equinix IBX data center. Its documentation also refers to an A-side customer, a Z-side provider, and approved demarcation points.
That sounds simple until you try to reconcile the bill.
The facility may identify the cross-connect by an order or service number. The carrier may identify the circuit by a separate circuit ID. Your router or switch may identify the connection by interface. The invoice may use an abbreviated description created years ago. The network diagram may show a carrier name but not the port. The current IT team may have inherited all of it.
Each record can be accurate on its own while the full story remains unclear.
This is why asking the facility for “a list of our cross-connects” does not finish the audit. It starts it.
Build one register that joins the physical and commercial records
Create one row for every billed cross-connect. Do not separate the carrier inventory, facility export, equipment records, and invoices into different workstreams. The point is to connect them.
| Field | What to capture |
|---|---|
| Facility record | Data center, building, room, cage, cabinet, order ID, and service ID |
| Physical path | A-side, Z-side, demarcation, patch panel, media, connector, and strand or pair |
| Equipment port | Device name, serial number, module, port, optics, speed, and link state |
| Carrier service | Provider, carrier circuit ID, product, bandwidth, and carrier account |
| Business use | Application, customer, cloud, WAN, internet, voice, replication, or partner dependency |
| Redundancy role | Primary, secondary, diverse path, migration bridge, spare, or unknown |
| Commercial record | Monthly charge, install charge, term, notice date, renewal date, and disconnect charge |
| Ownership | Network owner, application owner, contract owner, facility contact, and carrier contact |
| Evidence | Portal record, invoice, diagram, device output, ticket, test, and last verified date |
| Decision | Keep, correct, disconnect, replace, consolidate, or compare |
Start with the facility portal export and invoices. Then add carrier bills, service records, letters of authorization, rack elevations, patching records, network diagrams, device configurations, monitoring, support tickets, and change records.
Do not trust naming conventions to make the match for you. A label such as “WAN 2” or “Carrier A” may have survived three redesigns.
Trace the chain in both directions
For every cross-connect, trace from the invoice toward the equipment:
- Facility charge
- Facility service or order ID
- A-side and Z-side records
- Demarcation and patch-panel position
- Cabinet and device
- Physical interface
- Carrier circuit or other connected party
- Business service
- Accountable owner
Then trace backward from the live device port to the invoice.
The second pass catches a different problem: live connections that operations depends on but procurement cannot map to an agreement or renewal date. Those are not free. They are unmanaged commercial risk.
If the facility record ends at a demarcation point, document what happens after that point. Equinix’s current documentation says its cross-connects must be delivered through an approved demarcation point. That provider boundary matters during troubleshooting. The facility may prove its segment works while your team, carrier, or managed network provider owns the next segment.
Write down the boundary before an outage turns it into an argument.
Do not disconnect something just because traffic looks quiet
A quiet port may be unused. It may also be a backup path that should be quiet.
Check the intended role before removal. Review device state, interface counters, monitoring history, routing, failover design, change tickets, carrier records, and business-owner confirmation. If the circuit is supposed to protect a primary path, run a controlled failover test under an approved change.
This is where weak audits get expensive. A team sees little traffic, removes the charge, and discovers later that it eliminated the only working backup. Another team keeps every quiet circuit “just in case” and pays for years of abandoned migration links.
Both decisions avoid the hard work. Prove the role.
For redundant services, confirm whether the physical paths are actually diverse. Two carrier circuit IDs do not prove two building entrances, meet-me rooms, risers, demarcations, patch panels, power paths, or upstream routes. If diversity is part of the business case, make the provider show the parts it controls and clearly state what it does not guarantee.
Reconcile the facility charge with the carrier charge
A live carrier service and a live cross-connect are related, but they are not the same billing object.
You may disconnect the carrier circuit and leave the facility cross-connect billing. You may remove a cable and leave the carrier account active. You may move service to a new port while the old facility record stays open. A migration can create months of intentional overlap, then become permanent because nobody owns the cleanup.
Match both sides before renewal:
- Does every facility cross-connect point to an active carrier or connected party?
- Does every active carrier service point to the expected facility record and device port?
- Do bandwidth, media, speed, and interface settings agree?
- Do the carrier and facility service addresses match the correct building and suite?
- Were old services formally disconnected, or were they merely unplugged?
- Did a move, upgrade, or provider change create a temporary cross-connect that should now end?
The ISP service-ID inventory checklist helps reconcile the carrier side. Use it with the facility register, not instead of it.
Price removal before you approve removal
Disconnecting a cross-connect is an operational and contractual change.
Review the agreement for notice requirements, remaining term, de-installation charges, access rules, required authorization, and billing-stop conditions. Equinix’s current billing documentation, as one provider-specific example, says its Cross Connect products include a one-time installation fee, early termination requires a one-time de-installation fee, and product term commitments follow colocation terms.
Your provider’s terms may be different. Read the actual agreement and order form.
Ask what event stops billing. Is it the request date, approved disconnect date, physical removal date, or completion date in the provider’s system? Ask what evidence you receive when the work is complete. Get the final charge and the expected last invoice in writing.
If the cross-connect supports a carrier circuit, coordinate both disconnects. One ticket is not proof that the other service ended.
Put every cross-connect into a decision bucket
Keep it when the service is live, needed, documented, owned, correctly billed, and supported by evidence.
Correct it when the connection is needed but the port, carrier ID, owner, description, billing record, or diagram is wrong.
Disconnect it when the business dependency is gone and both facility and carrier termination steps are approved, scheduled, and verified.
Replace it when the physical medium, speed, demarcation, provider, or design no longer supports the requirement.
Consolidate it when duplicate services or migration overlap can end without weakening resilience.
Compare alternatives when pricing, contract structure, support boundaries, facility constraints, or path design no longer fit the business.
Do not make one decision for the entire data center. Decide row by row.
Questions to answer before renewal
Send the facility, carrier, managed provider, and internal owners the same register. Require written corrections where records conflict.
- Which facility service ID maps to each billed cross-connect?
- What are the exact A-side, Z-side, demarcation, cabinet, panel, and port details?
- Which carrier circuit or connected party sits on the other side?
- Which device interface and business service depend on it?
- Who can approve a change, test, or disconnect?
- What evidence shows the service is live and used for its intended role?
- If it is redundant, what physical and provider diversity can be proven?
- Where does the facility’s support boundary end?
- Which charges, notice periods, and term commitments apply to removal?
- What action stops billing, and what completion evidence will the provider issue?
- Which old migrations, upgrades, or provider changes left temporary links behind?
- Which unknown records need a site visit, Smart Hands order, or controlled test?
Start early enough to investigate unknowns. A port trace, carrier correction, failover test, authorization letter, or coordinated disconnect can take longer than a renewal meeting suggests.
A broader colocation renewal exit-cost review can help when the cross-connect problem is part of a facility move or contract decision. If the issue is limited to connectivity, keep the scope narrow and finish the register.
A clean spreadsheet is useful only if it leaves you with a defensible network and a bill that matches it.
If your colocation or connectivity renewal is approaching, request a Contract and Spend Risk Review. Bring the agreement, order forms, invoices, facility export, carrier inventory, rack records, diagrams, device-port data, monitoring, tickets, and notice dates. Catch Advisors will help you reconcile the physical service with the commercial record before you renew or disconnect it.