资源
为下一次网络决策准备的细节。
面向需要运营链路的人，提供策略、维护说明和技术背景。
网络状态
Network updates will appear here when published by the operations team.
路由策略
Routing and peering policy documents are prepared for the public site.
常见问题
Bring questions about ports, routes, handoffs and operating support to engineering.
READING PATH
Use the library by the decision in front of you.
Before an order
Start with the product data sheet, facility checklist and routing policy. These define what to bring to a technical review.
Before a change
Read maintenance notes, support boundaries and the escalation path. Confirm who owns the next timestamp.
During an incident
Use network status, DDoS response guidance and the NOC contact to keep the operational conversation precise.
GLOSSARY
Words that should mean the same thing on both sides.
| Term | Plain meaning | Ask in a review |
|---|---|---|
| IP Transit | Internet reach delivered through a BGP relationship. | Which routes, filters and communities apply? |
| DIA | Managed, dedicated internet access to a site. | What is the handoff and SLA? |
| Peering | Direct exchange between networks to shorten a path. | Which IX, VLAN and policy? |
| RPKI | Cryptographic authorization for a route origin. | What validity state is accepted? |
| LOA / CFA | Documents used to request a cross-connect. | Who issues and tracks the request? |
PUBLISHING CADENCE
Useful detail stays current.
Events
Maintenance and incidents carry a timestamp and owner.
Network rules
Routing and peering documents are reviewed when policy changes.
Technical context
Product and architecture notes explain the handoff.
Field questions
Repeated operator questions become searchable guidance.
FIELD NOTES
Turn recurring questions into shared language.
What should a route review include?
Prefixes, origin, filters, communities, failure behavior and the person who owns the next change.
What should a facility review include?
Meet-me room, cross-connect, optics, port band, lead time and the latest availability check.
What should an incident update include?
Impact, start time, affected boundary, mitigation, next update and a contact for escalation.
What should a handoff include?
Acceptance test, monitoring signal, maintenance channel, NOC path and rollback expectation.