Summary

  • If a customer has not selected removal despite live traffic, Equinix asks for more information when it detects traffic. With no response within ten days, it processes the removal order as requested.
  • Removing a connection, ending its charges and taking away its cable have different conditions. A saving needs an owner who stays with the work beyond submitting the request.

The cheapest way to announce a network saving is to count removal requests as completed removals. Finance gets its good news immediately. The network carries on with its ports, dependencies and inconvenient attachment to the actual sequence of events.

Equinix's cross-connect removal guide puts a precise question between those two worlds. A customer can choose to proceed even if live traffic is detected. With that option unselected, detected traffic prompts a request for additional information. No response within ten days means the deinstallation order is processed as requested.

Packets can report that a connection is being used. They cannot withdraw the customer's instruction.

That is a small operational rule with a substantial commercial consequence. Procurement may have ordered the removal while the network team is still finding out which services use the connection. Both teams can have good records. Someone must compare them and tell the supplier what to do.

The request keeps working after its author logs off

The form identifies the connection and provides technical and notification contacts, defaulting the latter to the requester's details. Having somewhere to deliver a question is useful. Having somebody there who can answer it is a separate organisational achievement.

The person closing a supplier line may know its cost but little about the application still using it. The application owner may know exactly why the move is unfinished and never see the removal query. Neither needs to neglect their assigned job for the answer to go missing. The gap can be designed into the jobs themselves.

Ten days is the response window. Physical removal is scheduled on or after the requested date, subject to operational availability. Day eleven is therefore a poor date on which to invent a universal disconnection alarm. The consequential fact is that an unanswered question leaves the original instruction actionable.

An unticked permission to proceed despite traffic can easily acquire more meaning in the customer's mind than it has in the procedure. Someone will ask before continuing; therefore someone will keep waiting. The second proposition needs an arrangement of its own. A customer that wants to change the order must complete the conversation.

Adding recipients helps only if someone acquires the decision. Otherwise the company has bought redundancy for its excuses: everybody received the message, so surely somebody else was handling it.

A short cable can carry a long obligation

Equinix describes Cross Connects as dedicated physical connections between parties in its IBX environment, supporting private connections to networks and services. The visible span inside a building can be a small part of the business relationship at either end.

That produces three useful descriptions of the same asset. Finance sees an expense. Engineering sees ports and endpoints. The service owner sees a function that must remain available. Retirement requires putting those descriptions together. Removing the expense from a forecast does little to relocate the function.

Even the expense resists a single number per cable. Equinix's billing documentation lists monthly and installation charges for Standard, Campus, Diverse Campus and Extended Cross Connects. Intra-Customer Cross Connect has an installation charge without a monthly recurring charge. Term commitments follow colocation terms, with deinstallation charges for ending a term early.

Counting connections and multiplying by a convenient monthly rate would make an admirably quick savings model. Reconciling the product, commitment and completed work makes a model that can survive the next invoice.

Keeping an unwanted connection also has a cost. The person asking to retain it should explain what it protects and what event will make it dispensable. Technical caution becomes commercially useful when it can name an exit condition. Until then, a recurring bill has found a remarkably comfortable hiding place.

A move buys a sequence, not two completion notices

A customer moving between cabinets or cages usually wants to keep a function at a new location. Removing the old end describes only part of that wish. The other end, the maintenance window and the new identity of the circuit must fit the same plan.

Equinix's interconnection migration procedure requires scheduled maintenance and the regional migration team for moving an end of a live connection within the same metro. The team confirms the scope, arranges necessary orders and coordinates with the A-side customer for a Z-side move. Circuit identifiers are updated on completion.

The economic value lies in the sequence. A new installation can be complete and an old removal complete while the transition between them has still failed to meet the customer's operating needs. Two perfectly accurate work reports cannot substitute for the business being ready to use its new connection.

A period of overlap can be a good purchase. It needs a purpose, a payer and an ending condition. The service owner explains the continuity required; the budget owner accepts its cost; the order owner conveys an executable decision. Then the company can argue usefully about how much transition it is buying.

An unanswered traffic query does none of that. It establishes neither the replacement's readiness nor the other party's availability, and it assigns no funding for an extension. It simply leaves a contradiction unresolved while an earlier, much clearer instruction remains in the supplier's hands.

The cable can stay after the service has gone

There is another trap at the end of the process: treating a visible object as proof of a continuing service. The cabling and cross-connect deinstallation policy currently linked by Equinix is dated 1 November 2021. It allows the company to prohibit physical removal and customer retention where removal could interfere with other customers, infrastructure or operations, or where access and removal present difficulties. In those cases the cable is deactivated and not returned.

An object can therefore remain in the building after its purpose has ended. A photograph of a cable tray is wonderfully tangible evidence of a cable tray. Closing a service requires a result tied to the asset and the order.

Billing runs through actual removal, according to the removal guide. The page gives two different anchors for its minimum thirty days—requested removal date and submission date—so the applicable date for a specific order needs confirmation before calculating its billing cutoff. Optional removal of the customer's patch cable also creates a separate, chargeable Smart Hands order.

The person finishing the exit has to reconcile what ended, what work remains and what each charge pays for. Otherwise procurement, operations and finance can produce three incompatible accounts of one connection. Each new invoice then sends staff back to the same unfinished argument about what they were supposed to have saved.