Peer1IX
Internet Exchange
Services

Interconnection

Internet ExchangeMicro PoPsEdge Data Centers

Network Services

Data Center to Data CenterVirtual Connectivity HubData Center to CloudCloud to CloudPeer1ix Cloud RouterPeer1ix Virtual EdgeNAT GatewayPeer1ix PortVirtual Cross Connect

Security Services

DDoS ProtectionPeer1ix FWaaSIPsec Tunnel

Cloud Interconnect

Cloudflare Network Interconnect
Locations
Network toolsAll-in-One Network ReportBGP Looking GlassRPKI ValidatorBGP Security & Hijack CheckIP WHOISAS WHOISBGP Route ExplorerASN InsightsBGP Hijacks & Route LeaksInternet Outage TrackerCountry Internet InsightsTop Domains RankingDNS LookupSubnet CalculatorWhat Is My IP
BlogAboutContact Get connected

Using VXCs for Temporary Projects and Events

· 1 min read · Peer1IX Team

Using VXCs for Temporary Projects and Events

Some connections are only needed for weeks. Virtual cross connects make short-term private links practical.

When you only need it for a while

A broadcaster needs a private link to a production partner for a tournament. An auditor needs access to a data room for a month. A migration needs a temporary path between two providers. None of these justify a physical cross-connect.

VXCs fit short-term work

Because a VXC runs over existing ports, setting it up is quick, and removing it afterwards leaves nothing behind.

Plan it like a project

  • Define start and end dates.
  • Agree bandwidth and security controls.
  • Test before the critical period.
  • Remove the VXC when the project ends.

Keep security tight

Temporary links should still follow your access controls. Limit which networks are reachable and log activity.

temporary connectivityeventsprojects