Provider

Provider · Registry · Circuits

Circuits on record.

Layout records generated from registry truth, never drawn by hand. If the record and the glass disagree, the record wins the argument and the glass gets fixed.

Circuits30all backbone layout records
Passing28clean light, clean record
Impaired2down or degraded
Operators5federated ownership
down

CLR-2416 DEN–KC (Meridian Capacity Co.) is hard down. The layout record resolves to the underlying cable; the splice case and the full light path are in fiber plant.Work order tracks the repair.

Layout records

Circuit layout records with route, operator, capacity, optical endpoints, and status
CLRRouteKindOperatorCapacityA deviceZ deviceStatus
CLR-2400ORD–JFKbackboneCorepath Networks200GunassignedunassignedUp
CLR-2401ORD–DFWbackboneMeridian Capacity Co.400Gunassigneddfw-optical2.r01Up
CLR-2402ORD–KCbackboneMeridian Capacity Co.100Gunassignedkc-optical1.r02Up
CLR-2403ORD–MSPbackboneMeridian Capacity Co.100Gunassignedmsp-optical1.r01Up
CLR-2404ORD–IADbackboneCorepath Networks100GunassignedunassignedUp
CLR-2405JFK–IADbackboneCorepath Networks200GunassignedunassignedUp
CLR-2406JFK–BOSbackboneCorepath Networks400Gunassignedbos-optical1.r01Up
CLR-2407IAD–ATLbackboneCorepath Networks100Gunassignedatl-optical2.r03Up
CLR-2408ATL–MIAbackboneNaaS Labs400Gatl-optical2.r03unassignedUp
CLR-2409ATL–DFWbackboneNaaS Labs400Gatl-optical2.r03dfw-optical2.r01Up
CLR-2410DFW–PHXbackboneMeridian Capacity Co.100Gdfw-optical2.r01phx-optical1.r02Degraded
CLR-2411DFW–KCbackboneMeridian Capacity Co.100Gdfw-optical2.r01kc-optical1.r02Up
CLR-2412PHX–LAXbackboneMeridian Capacity Co.100Gphx-optical1.r02unassignedUp
CLR-2413LAX–SJCbackboneNaaS Labs100GunassignedunassignedUp
CLR-2414SJC–SEAbackboneNaaS Labs400GunassignedunassignedUp
CLR-2415SEA–DENbackboneMeridian Capacity Co.100Gunassignedden-optical2.r01Up
CLR-2416DEN–KCbackboneMeridian Capacity Co.100Gden-optical2.r01kc-optical1.r02Down
CLR-2417JFK–LHRbackboneAurora Transit400GunassignedunassignedUp
CLR-2418IAD–LHRbackboneAurora Transit200GunassignedunassignedUp
CLR-2419LHR–AMSbackboneAurora Transit100Gunassignedams-optical2.r02Up
CLR-2420LHR–PARbackboneAurora Transit100GunassignedunassignedUp
CLR-2421AMS–FRAbackboneAurora Transit100Gams-optical2.r02fra-optical1.r01Up
CLR-2422FRA–PARbackboneAurora Transit100Gfra-optical1.r01unassignedUp
CLR-2423SJC–NRTbackboneBlue Harbor DC400Gunassignednrt-optical2.r01Up
CLR-2424NRT–SINbackboneBlue Harbor DC100Gnrt-optical2.r01sin-optical2.r01Up
CLR-2425SIN–SYDbackboneBlue Harbor DC400Gsin-optical2.r01unassignedUp
CLR-2426LAX–SYDbackboneBlue Harbor DC100GunassignedunassignedUp
CLR-2427ORD–YYZbackboneCorepath Networks200Gunassignedyyz-optical2.r04Up
CLR-2428YYZ–JFKbackboneCorepath Networks400Gyyz-optical2.r04unassignedUp
CLR-2429FRA–SINbackboneAurora Transit100Gfra-optical1.r01sin-optical2.r01Up

Every record above is assembled from device ports, patch fields, and strand assignments already in the registry. There is no separate circuit drawing to keep in sync, which is the point. The A and Z endpoints and the circuit record itself bind to the VRFs, VLANs, and ASNs that carry them in IP space bindings.