Enterprise definition

Protected and Unprotected Routes

The tradeoff between a single working path and a service designed with protection, diversity, or automatic failover.

What it means

An unprotected route is usually a single active path. If that path is damaged or interrupted, traffic waits for repair or manual reroute. A protected route is designed with a second path, optical protection, routed failover, alternate entrance, or dual handoff so the service has a planned recovery model when one side fails.

Where it fits

  • Hospitals, public agencies, manufacturers, campuses, and large enterprises
  • Private backbone routes where downtime has a direct operational cost
  • High-capacity paths that need a planned restoration model
  • Sites that need physically diverse entrances or separate long-haul paths
  • Customers deciding between lower cost single-path service and higher-resilience protected service

What we'll talk through with you

  • What outage impact are you trying to reduce?
  • Do you need a protected service, a diverse second circuit, a backup Internet path, or a manual restoration plan?
  • Should protection happen at the optical layer, Ethernet layer, IP routing layer, or through BGP?
  • Do the paths need separate entrances, separate pole or conduit routes, or separate interconnection points?
  • What failover time, monitoring, testing, and support expectations should be documented?
Important context Protected does not automatically mean fully diverse. The route, building entrance, handoff equipment, power, cross-connects, and upstream path all need to be reviewed if the goal is true resilience.

How it shows up in a real project

A healthcare network orders a primary 100G path and a protected secondary path that uses a different building entrance and different transport route. Quad State Internet documents the protection model, monitors both paths, and supports failover testing before production use.

Learn the goal

We start by translating the business need into endpoints, capacity, term, resiliency, and support expectations.

Map the meet points

We identify carrier meet points, IX ports, cloud on-ramps, colocation footprints, or private handoffs that matter.

Choose the model

The answer may be DIA, IP Transit, Type II access, dark fiber, wavelength, IRU, managed transport, or a blend.

Build the path

Quad State Internet can build, coordinate, light, monitor, document, and support the route after turn-up.