The connections that leave your building need records too
WAN documentation records every connection between your sites, the internet and the cloud: ISP circuits, SD-WAN or MPLS links, site-to-site VPN tunnels, private cloud connections and the failover design that holds them together. It is the part of IT documentation people reach for when the office is offline and every minute counts.
In many businesses this information lives in a billing portal, an old email from the installer and the memory of one person. When the circuit drops on a Saturday, nobody knows the circuit ID, which modem is which, or whether the backup link is supposed to take over. A short register fixes that.
WAN records connect to the rest of the network documentation: each circuit lands on a firewall interface, each tunnel protects subnets from the IP address plan, and each provider is a vendor record with a support contact.

What WAN documentation records for every ISP circuit
One row per circuit, per site. Keep it with the vendor record and the firewall it connects to.
| Field | What to record | Why it matters |
|---|---|---|
| Provider and account | Carrier name, account number reference, the contract holder in your company | The carrier will only talk to an authorized contact |
| Circuit ID | The provider’s circuit or service ID exactly as printed on the bill or label | The first question support asks |
| Type and bandwidth | Fiber, cable, fixed wireless, cellular; download and upload speed as contracted | Know whether slow speed is a fault or the contract |
| Handoff and demarc | Where the provider’s equipment ends (room, rack, device), handoff type and the firewall port it connects to | The on-site tech finds the right box and cable |
| IP addressing | Static block and gateway, or DHCP; which public IP maps to which service | Firewall and DNS changes after an ISP move go smoothly |
| SLA | Uptime and repair commitments as written in the contract, and how to claim credits | Hold the carrier to what you are paying for |
| Support and escalation | Support line, portal, ticket hours, and the next level when the first one stalls | Escalate instead of waiting in a queue |
| Contract dates | Start, term, renewal and notice date, monthly cost owner | Avoid auto-renewal surprises and plan upgrades |
Sample circuit register: Harborview Dental Group
Two sites, three circuits. Provider names are generic and every ID is made up.
| Circuit | Site | Provider | Circuit ID | Bandwidth | Handoff | Addressing | Role |
|---|---|---|---|---|---|---|---|
| WAN1-HQ | Irvine office | Fiber ISP A | HDG-FIB-0412 | 500/500 Mbps | Provider ONT, closet A → FW-HQ-01 port 1 | /29 static · 5 usable IPs | Primary |
| WAN2-HQ | Irvine office | Cable ISP B | HDG-CBL-0187 | 300/20 Mbps | Cable modem, closet A → FW-HQ-01 port 2 | DHCP · 1 dynamic IP | Failover |
| WAN1-S2 | Second office | Cable ISP B | HDG-CBL-0233 | 300/20 Mbps | Cable modem, front closet → FW-S2-01 port 1 | 1 static IP | Primary · VPN to HQ |
Each row links to the vendor record (support line, portal, contract renewal date) and to the firewall interface it terminates on. All names, IDs and figures are fictional.
SD-WAN, MPLS, VPN and cloud links: what to document for each
Each WAN technology has a few details that matter most when something breaks.
SD-WAN
The orchestrator or dashboard, which sites are enrolled, the underlay circuits at each site, application steering and failover policies, and who has admin access to the controller.
MPLS
Carrier, site circuit IDs, the routing between your edge and the carrier (static or BGP, with AS numbers), class-of-service settings, and the carrier’s network operations contact.
Site-to-site VPN
Both peer addresses, the protected subnets on each side, IKE version, encryption and hashing settings, the shared-secret or certificate reference in the vault, and how the tunnel is monitored.
Private cloud connections
Dedicated links to a cloud provider (for example Azure ExpressRoute or AWS Direct Connect) or cloud VPN gateways: circuit or connection ID, the cloud networks reached, routing and redundancy. Cloud-side settings are covered on the cloud documentation page.
Sample VPN tunnel table
Tunnel records show what each connection protects. Secrets stay in the vault; the table only points to them.
| Tunnel | Local peer | Remote peer | Protected subnets | Settings | Secret | Monitoring |
|---|---|---|---|---|---|---|
| VPN-HQ-S2 | FW-HQ-01 (WAN1-HQ) | FW-S2-01 (WAN1-S2) | 10.20.0.0/16 ↔ 10.21.0.0/16 | IKEv2 · AES-256-GCM | Vault entry VPN-HQ-S2-PSK | Tunnel-down alert to IT |
| VPN-HQ-CLOUD | FW-HQ-01 (WAN1-HQ) | Cloud VPN gateway | 10.20.30.0/24 ↔ 10.50.0.0/22 | IKEv2 · AES-256-GCM | Vault entry VPN-HQ-CLD-PSK | Gateway health check |
The non-overlapping prefixes (10.20, 10.21 and 10.50) come straight from the IP plan; overlapping subnets are a common reason a new tunnel will not route. All values are fictional.
Failover design and test records in four steps
Describe the design
Which circuit is primary, how failover is detected (link state, ping or SLA probe), what moves to the backup and what does not, and how traffic returns.
Plan the test
Pick a low-impact window, tell staff, list the checks: internet, phones, VPN to the second office, card terminals and cloud apps.
Record the result
Date, who tested, how long failover and failback took, what failed, and screenshots or log extracts as evidence.
Fix and repeat
Open a change record for each issue found, then retest. Keep every test record with the circuit register.
A carrier escalation path your staff can follow
Outages rarely wait for business hours. Write the path down so anyone can start it.
For each provider, record the support line and portal, the hours of each support tier, the account PIN or verification method (as a vault reference, never in the document itself), and the next level to call when a ticket stalls, such as the account manager or the carrier’s escalation desk.
Add a short checklist for the caller: circuit ID, site address, demarc location, what the modem or ONT lights show, when the outage started, and whether the backup link took over. Log each outage with the ticket number and restore time. That log becomes evidence for SLA credit claims and for the next contract renewal.
Procedures like this belong with your other recovery steps; see runbooks and disaster-recovery documentation and our business continuity and disaster recovery services.
WAN documentation, reviewed or built for you
The IT Documentation Audit reviews your existing circuit records, VPN details and failover notes against the live firewall configuration and reports what is missing. The IT Documentation Build delivers the WAN circuit register, the tunnel table and the failover record, linked to your network diagram and firewall configuration documentation. Each package is $3,500 fixed, one-time; see IT documentation pricing.
Ali works on-site across Orange County and Southern California from Irvine, and remotely with multi-site businesses nationwide. Our work is read-only. If a failover test shows something to fix, IT Perfection can make the change.

Where to go next
Firewall configuration documentation
Rule base, NAT, remote-access VPN and configuration backups, each rule with a business reason and an owner.
Runbooks and disaster recovery
Step-by-step recovery procedures, restore order and contact trees that use the circuit register.
Page 6 of 22: WAN and ISP circuit documentation
- 1. IT documentation services (hub)
- 2. Why IT documentation matters
- 3. What to include in IT documentation
- 4. Network documentation
- 5. IP address and VLAN documentation
- 6. WAN and ISP circuit documentation (this page)
- 7. Firewall and network settings documentation
- 8. Cloud documentation: Microsoft 365, Azure, AWS
- 9. Data-flow diagrams
- 10. IT asset inventory
- 11. IT password documentation
- 12. IT change management
- 13. Runbooks and disaster-recovery documentation
- 14. Securing your IT documentation
- 15. IT documentation for compliance
- 16. IT documentation software compared
- 17. Configuration backup and change tools
- 18. How to document a network
- 19. IT documentation checklist
- 20. Sample IT documentation package
- 21. IT documentation audit
- 22. IT documentation pricing

Guided by Ali Hassani, CISO
Certified CISO (C|CISO) and CISSP with 25+ years in IT, cybersecurity, compliance and infrastructure, and dozens of Microsoft and Cisco certifications, including MCSE, MCITP, MCSA Security, CCNP and CCNA. Ali verifies each circuit against the firewall interface it lands on, so the register matches the cabling and not only the bill.
Questions about WAN documentation
Where do we find our circuit ID?
It is usually on the monthly bill, the carrier’s online portal, a label on the modem or ONT, or the installation paperwork. We collect it from those sources during discovery and confirm it with the carrier record.
Should VPN shared secrets go in the WAN documentation?
No. The document should name the vault entry that holds the secret. Secrets belong in an encrypted vault with access logging, as described on our credential documentation page.
How often should we test WAN failover?
We suggest at least once a year, and after any change to circuits or firewall settings; adjust the schedule to your risk. What matters most is that each test is planned, recorded and followed up.
Do we need WAN documentation if we only have one office?
Yes. A single office still has at least one internet circuit, often a backup, and usually VPN connections to cloud services, vendors or remote staff. Those records shorten every outage.
Can you contact our carriers for us?
We gather and verify circuit details with your authorization, but your company stays the account holder. Carrier changes and repairs remain with your team, your MSP or IT Perfection.
Implementation partner
OC Security Audit documents and audits; it stays independent of the administration of your systems. If you want hands-on work, IT Perfection can fix what the documentation uncovers and keep the records current as part of managed IT.

Be ready for the next internet outage
Tell us how many sites and circuits you have. Schedule a consultation and we will scope your WAN documentation on a 30-minute call.
Irvine, Orange County and Southern California on-site; remote nationwide. Fixed one-time price: $3,500.


