--- title: Cloudflare Network Interconnect description: Cloudflare Network Interconnect (CNI) allows you to connect your network infrastructure directly to Cloudflare — rather than using the public Internet — for a more performant and secure experience. With CNI, you can bring Cloudflare's full suite of network functions to your network edge. image: https://developers.cloudflare.com/core-services-preview.png --- [Skip to content](#%5Ftop) Was this helpful? YesNo [ Edit page ](https://github.com/cloudflare/cloudflare-docs/edit/production/src/content/docs/network-interconnect/index.mdx) [ Report issue ](https://github.com/cloudflare/cloudflare-docs/issues/new/choose) Copy page # Cloudflare Network Interconnect Connect your network infrastructure directly to Cloudflare Enterprise-only Cloudflare Network Interconnect (CNI) allows you to connect your network infrastructure directly to Cloudflare — rather than using the public Internet — for a more performant and secure experience. With CNI, you can bring Cloudflare's full suite of network functions to your network edge. ## Benefits Enterprises use CNI to achieve: * **Enhanced Performance**: Gain lower latency and more consistent network throughput. * **Increased Security**: Reduce your network's attack surface by connecting privately and avoiding the public Internet. ## Connection types Choose the connection type for your infrastructure and operational needs. | Direct Interconnect | Partner Interconnect | Cloud Interconnect | | | ------------------- | ----------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | | **Port type** | A dedicated physical fiber connection between your network equipment and Cloudflare's hardware in a shared data center. | A virtual connection to Cloudflare established through one of our global connectivity partners. | A private connection between a customer's cloud environments (for example, Amazon Web Services (AWS), Google Cloud) and Cloudflare. | | **Operations** | You are responsible for procuring and managing the physical cross-connect to Cloudflare's equipment. | Your partner manages the connection logistics, often through a software-defined networking portal. | Cloudflare connects to cloud providers' dedicated services, and customers establish private virtual circuits from their virtual private clouds. | | **Ideal use case** | For customers collocated with Cloudflare who require maximum control, performance, and reliability. | For customers who are not in the same data center as Cloudflare or prefer a managed connectivity solution. | For customers with workloads in public clouds who need secure, reliable connectivity to Cloudflare services. | ## Dataplane Cloudflare's data centers may support one or more interconnect dataplanes. The dataplane is the type of equipment that terminates your direct connection: * **Dataplane v1**: A peering connection to a Cloudflare edge data center that supports Generic Routing Encapsulation (GRE) tunnels for connecting with the Cloudflare Virtual Network, with optional GRE-less delivery for Magic Transit Direct Server Return. * **Dataplane v2**: Is based on the Customer Connectivity Router (CCR), which is specifically designed for customer connectivity. It provides simplified routing without GRE tunneling and supports a 1,500-byte Maximum Transmission Unit (MTU) bidirectionally. When you review the [available locations](https://developers.cloudflare.com/network-interconnect/static/cni-locations-31-mar-2026.pdf) (PDF), you can see which dataplane version(s) are available. ## Product use cases CNI provides a private point-to-point IP connection with Cloudflare. There are two Dataplanes that come with different technical specifications. | Dataplane v1 | Dataplane v2 | | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Magic Transit Direct Server Return (DSR)** Distributed Denial of Service (DDoS) protection for all ingress traffic from the Internet to your public network. Send egress traffic via your ISP. | Supported with or without a GRE tunnel established over the interconnect circuit. | Supported. | | **Magic Transit with Egress** DDoS protection for all ingress traffic from the Internet to your public network. Send egress traffic via Cloudflare. | Supported with a GRE tunnel established over the interconnect circuit. | Supported. | | **Cloudflare WAN and Zero Trust** Build a secure, private network backbone connecting your Zero Trust users and applications with all your sites, data centers, and clouds. | Supported with a GRE tunnel established over the interconnect circuit. | Supported. | | **Peering** Exchange public routes with a single Cloudflare PoP (Point of Presence). | Supported. All customers connecting with the edge data center will exchange public routes at that PoP with AS13335\. Connectivity is established at each individual PoP. Routes for other edge locations in Cloudflare's network may not be available. Routes for customer-advertised prefixes will be available only in the connected PoP. | Not supported. | | **Application Security and Performance** Improve the performance and security of your web applications | **Supported via peering**: Customers can use Argo Smart Routing to direct origin traffic via the edge peering connection when it is determined to be the lowest latency option. Customers must maintain a direct Internet connection which will always be used for a portion of traffic and during failure scenarios. **Supported Via Magic Transit**: Customers may configure any product with an origin server IP address that is protected by Magic Transit. Magic Transit will direct this traffic via the overlay and customer can control interconnect next-hops using the Magic Transit Virtual Network routing table. | When the origin IPs are behind Magic Transit over a CNI v2, all Cloudflare services that work with public origins (like Load Balancer, WAF, Cache) will run over the CNI. | For more details refer to the [prerequisites section](https://developers.cloudflare.com/network-interconnect/get-started/#prerequisites). ### Designing for high availability To protect against a single point of failure, it is critical to design your CNI deployment for resilience. For business-critical applications, seek Cloudflare locations that support diversity on the device level. This ensures your connections terminate on physically separate hardware. Refer to [Service Expectations](https://developers.cloudflare.com/network-interconnect/get-started/#service-expectations) for more information. --- ## Related products **[Magic Transit](https://developers.cloudflare.com/magic-transit/)** Magic Transit is a network security and performance solution that offers Distributed Denial of Service (DDoS) protection, traffic acceleration, and more for on-premise, cloud-hosted, and hybrid networks. **[Cloudflare WAN](https://developers.cloudflare.com/cloudflare-wan/)** Improve security and performance for your entire corporate network, reducing cost and operation complexity. ```json {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"item":{"@id":"/directory/","name":"Directory"}},{"@type":"ListItem","position":2,"item":{"@id":"/network-interconnect/","name":"Network Interconnect"}}]} ``` --- --- title: Get started description: Connect your network privately to Cloudflare image: https://developers.cloudflare.com/core-services-preview.png --- [Skip to content](#%5Ftop) Was this helpful? YesNo [ Edit page ](https://github.com/cloudflare/cloudflare-docs/edit/production/src/content/docs/network-interconnect/get-started.mdx) [ Report issue ](https://github.com/cloudflare/cloudflare-docs/issues/new/choose) Copy page # Get started BGP architecture and resiliency CNI supports BGP peering with the Cloudflare Virtual Network routing table. BGP over CNI is in closed beta and is not currently available to new customers. If you are interested in BGP peering over CNI, contact your account team. For detailed information about BGP architecture, Edge Resiliency Mode, and route propagation behavior, refer to the BGP reference documentation in [Magic Transit](https://developers.cloudflare.com/magic-transit/reference/traffic-steering/#bgp-information) or [Cloudflare WAN](https://developers.cloudflare.com/cloudflare-wan/reference/traffic-steering/#bgp-information) depending on your use case. ## Prerequisites ### CNI port availability Your Cloudflare account team determines CNI eligibility and port availability. Notably: * CNI ports are currently offered at no charge to Enterprise customers. * Non-Enterprise customers (and any third party) may peer with Cloudflare via Internet Exchange according to our [open peering policy ↗](https://www.cloudflare.com/peering-policy/). * CNI is available at select Cloudflare data centers: * The type of Dataplane offered in that location will determine specifications of the supported connection, such as the MTU. * The diversity offered in the location will vary. * Customers must have a BGP session established for CNI v1 to be operational. ### Prefix requirements To peer with Cloudflare, advertise prefixes with a prefix length of `/24` or shorter for IPv4 and `/48` or shorter for IPv6. ## Product use cases CNI provides a private point-to-point IP connection with Cloudflare. There are two Dataplanes that come with different technical specifications. | Dataplane v1 | Dataplane v2 | | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Magic Transit Direct Server Return (DSR)** Distributed Denial of Service (DDoS) protection for all ingress traffic from the Internet to your public network. Send egress traffic via your ISP. | Supported with or without a GRE tunnel established over the interconnect circuit. | Supported. | | **Magic Transit with Egress** DDoS protection for all ingress traffic from the Internet to your public network. Send egress traffic via Cloudflare. | Supported with a GRE tunnel established over the interconnect circuit. | Supported. | | **Cloudflare WAN and Zero Trust** Build a secure, private network backbone connecting your Zero Trust users and applications with all your sites, data centers, and clouds. | Supported with a GRE tunnel established over the interconnect circuit. | Supported. | | **Peering** Exchange public routes with a single Cloudflare PoP (Point of Presence). | Supported. All customers connecting with the edge data center will exchange public routes at that PoP with AS13335\. Connectivity is established at each individual PoP. Routes for other edge locations in Cloudflare's network may not be available. Routes for customer-advertised prefixes will be available only in the connected PoP. | Not supported. | | **Application Security and Performance** Improve the performance and security of your web applications | **Supported via peering**: Customers can use Argo Smart Routing to direct origin traffic via the edge peering connection when it is determined to be the lowest latency option. Customers must maintain a direct Internet connection which will always be used for a portion of traffic and during failure scenarios. **Supported Via Magic Transit**: Customers may configure any product with an origin server IP address that is protected by Magic Transit. Magic Transit will direct this traffic via the overlay and customer can control interconnect next-hops using the Magic Transit Virtual Network routing table. | When the origin IPs are behind Magic Transit over a CNI v2, all Cloudflare services that work with public origins (like Load Balancer, WAF, Cache) will run over the CNI. | For more details refer to the [prerequisites section](https://developers.cloudflare.com/network-interconnect/get-started/#prerequisites). ## Technical specifications * **Supported port types**: * **Dataplane v1**: 10GBASE-LR (single-mode fiber) and 100GBASE-LR (single-mode fiber). * **Dataplane v2**: 10GBASE-LR (single-mode fiber) and 100GBASE-LR4 (single-mode fiber) optics are supported. * **Distance limitations:** Cloudflare does not support optical links longer than 10 km. For longer distances, you must use intermediate hardware or a third-party provider to extend the connection. * **IP addressing:** All CNI connections and Partner CNI connections use a `/31` subnet for point-to-point IP connectivity between your router and Cloudflare. * **VLAN support:** * **Dataplane v1**: CNI ports may be assigned a single 802.1Q VLAN tag. * **Dataplane v2**: VLAN tagging (802.1Q) and QinQ are not yet supported. * **MTU considerations:** * **Dataplane v1**: Supports a native 1,500-byte MTU for traffic from Cloudflare to you (ingress), but still requires a 1,476-byte MTU for traffic from you to Cloudflare (egress). * **Dataplane v2**: Supports a maximum MTU of 1,500 bytes bidirectionally with no GRE requirement. * **Bidirectional Forwarding Detection (BFD):** * **Dataplane v1**: BFD provides fast failure detection for BGP sessions and is supported on direct connections. To enable BFD, contact your account team. Note that BFD on a CNI does not impact the failover time for IPsec/GRE tunnels, which rely on separate health checks. * **Dataplane v2**: Not yet supported. * **Link Aggregation Control Protocol (LACP)**: * **Dataplane v1**: To increase bandwidth and provide link resiliency, Cloudflare supports combining multiple physical CNI ports into a single logical channel using Link Aggregation Control Protocol (LACP). You can bundle multiple connections to increase total throughput and add redundancy to your private connection with Cloudflare. * **Dataplane v2**: Not yet supported. Use ECMP instead. ## Performance characteristics The following are the maximum throughput rates supported by the CNI connection. Actual performance will depend on your specific use case and configuration. | Direction (use case) | 10G Circuit | 100G Circuit | | ----------------------------------------------- | ---------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | | From Cloudflare to Customer (all use cases) | Up to 10 Gbps | Up to 100 Gbps | | From Customer to Cloudflare (peering use case) | Up to 10 Gbps | Up to 100 Gbps | | From Customer to Cloudflare (Magic Transit/WAN) | **v1**: Up to 1 Gbps per GRE tunnel over the CNI **v2**: Up to 1 Gbps per CNI connection | **v1**: Up to 1 Gbps per GRE tunnel over the CNI **v2**: Up to 1 Gbps per CNI connection | ## Service expectations Consider the following service levels when planning your deployment: * **No Formal SLA**: * CNI is currently offered at no charge and without a formal [Service Level Agreement (SLA) ↗](https://www.cloudflare.com/service-specific-terms-network-services/#cf-network-interconnect-terms). * Cloudflare will work to restore CNI service in the event of a Cloudflare issue. In some Cloudflare data centers the recovery time could be several days. Therefore, we always recommend backup connectivity to a different device or via an Internet tunnel. * **Observability**: There is no visibility of the interconnect config/status within the Cloudflare dashboard. * **Availability**: While network-resilient locations are designed to maintain connectivity during maintenance, single-homed locations can experience full service disruption. * **Backup Connectivity**: You are required to maintain alternative Internet connectivity as a backup for all CNI implementations. * **Capacity planning**: You are responsible for capacity planning across your available links to Cloudflare, based on the topology and size of those links. ## Location alignment ### Available locations Direct connections are available at any Cloudflare data center where you are also located. Make sure to check whether the location of interest has the right dataplane version and diversity requirements for your use case. Refer to [available locations](https://developers.cloudflare.com/network-interconnect/static/cni-locations-31-mar-2026.pdf) (PDF) for details. ### Connectivity partners Cloudflare partners with leading global providers, including: Console Connect, CoreSite, Digital Realty, Equinix Fabric, Megaport, PacketFabric, and Zayo. ## End-to-end implementation workflow The process of provisioning a CNI typically takes two to four weeks, depending on the complexity of implementation and third-party provider timelines. The most common delays occur during the physical connection phase, which is outside of Cloudflare's direct control. 1. **Submit request**: Work with your account team to create a CNI request ticket, providing your desired CNI type, location, use case, and technical details. An Implementation Manager will be assigned to guide the process. 2. **Review configuration**: For the v1 Dataplane, the Implementation Manager will provide a detailed configuration document covering IP addressing, VLANs, and other technical specifications. You must review and approve this document. For the v2 Dataplane, this step is not necessary. 3. **Order connection**: * For a **Direct Interconnect**, you will receive a Letter of Authorization (LOA) from Cloudflare to order the physical cross-connect from the data center facility operator. * For a **Partner Interconnect**, you will use the provided details to order a virtual circuit from the partner's portal. 4. **Configure network**: Both Cloudflare and your network team will configure the respective network devices according to the approved document. 5. **Test and verify**: Once the connection is physically established, teams will perform basic connectivity tests (for example, ping) and, if applicable, verify that the BGP session can be established. 6. Enable tunnel health checks for [Magic Transit](https://developers.cloudflare.com/magic-transit/how-to/configure-tunnel-endpoints/#add-tunnels) and/or [Cloudflare WAN](https://developers.cloudflare.com/cloudflare-wan/configuration/manually/how-to/configure-tunnel-endpoints/#add-tunnels). 7. **Activate services**: Configure your Cloudflare products (for example, Magic Transit) to route traffic over the new CNI. The Implementation Manager will verify end-to-end traffic flow before marking the deployment as complete. 8. [Add maintenance notifications](https://developers.cloudflare.com/network-interconnect/monitoring-and-alerts/#enable-cloudflare-status-maintenance-notification). ## How-to guides ### Provision a Direct Interconnect 1. **Project Kickoff**: In an initial kickoff call, you will confirm the scope and timeline with Cloudflare. Be prepared to provide the following information: * desired colocation facility * required port speeds (10G or 100G) * BGP ASN for Peering/Magic Transit * BGP password (optional) 2. **Order Cross-Connect**: Cloudflare will issue a Letter of Authorization (LOA). This document grants you permission to order a physical cross-connect between your equipment and a specific port on Cloudflare's hardware within the data center. The end-to-end process for ordering a cross-connect can take one to two weeks or more, depending on the facility provider. Cloudflare's demarcation is the port that is specified in the LOA. You are responsible for the deployment, provisioning, and ongoing support and operation of this connection, and the commercial relationships with the facility provider and any third-party connectivity providers. ### Provision a Partner Interconnect Cloudflare partners with leading connectivity providers globally. To provision a Partner Interconnect, you will initiate a connection request from your chosen provider's administrative portal. Cloudflare will then review and accept the request to activate the virtual circuit. ### Provision a Cloud Interconnect Enterprise customers using Cloudflare WAN can get started with Cloud Interconnect by contacting their account team. #### AWS Direct Connect (beta) If you are a Cloudflare WAN customer, you can connect to [AWS Direct Connect ↗](https://docs.aws.amazon.com/directconnect/) using Cloud Interconnect. Cloud Interconnect supports AWS Dedicated Direct Connect, which provides a full physical port allocation in AWS. AWS Hosted Direct Connect is not yet supported. For your AWS Dedicated Direct Connect, you can choose between connection speeds of 10 Gbps or 1 Gbps. To connect to AWS Direct Connect: 1. Contact your account team to start the Cloud Interconnect provisioning process. Your team will let you know of available interconnect locations so you can choose the best one for you, as well as all the details involved in this process. 2. Log in to your AWS portal and order a Direct Connect. 3. AWS will provide you a Letter of Authorization (LOA) and a VLAN ID that you need to send to your account team. 4. Your account team will continue the process of provisioning your Cloud Interconnect with the AWS documents you have provided. Overall, this process should take around four weeks to finish. #### Google Cloud interconnect (beta) 1. In the Cloudflare dashboard, go to **Interconnects**. [ Go to **Interconnects** ](https://dash.cloudflare.com/?to=/:account/magic-networks/connections/cni-tunnels) 2. Select **Create an interconnect**. 3. Under **Cloud Interconnect**, select **Create new**. 4. Under **Google Integration**, select **Select integration**. 5. Give your interconnect a name and optionally a description. Make sure the MTU value matches the MTU configured on the [GCP VLAN attachment ↗](https://cloud.google.com/network-connectivity/docs/interconnect/how-to/dedicated/creating-vlan-attachments). 6. Select **Continue**. 7. From the **Interface speed** drop-down menu, select an interface speed. GCP will charge you based on the speed of the interconnect that you choose. 8. Enter your [VLAN attachment pairing key ↗](https://cloud.google.com/network-connectivity/docs/interconnect/how-to/partner/creating-vlan-attachments). 9. Select **Continue**. 10. Review the details you provided, and select **Confirm order**. Your Google Cloud Platform (GCP) interconnect will take a few minutes to be available. A BGP session will be established but no routes will be exchanged. #### GCP next steps You can now select **View interconnects** for a list of all interconnects on your account. Select the interconnect name to show the interconnect details. The interconnect has a unique **Interconnect ID**. After you have configured your Google Cloud Interconnect, you will need to add routes to use the interconnect: * To create routes in the Cloudflare Virtual Network routing table to direct traffic towards GCP: * Add [static routes](https://developers.cloudflare.com/cloudflare-wan/configuration/manually/how-to/configure-routes/#configure-static-routes) to your Cloudflare WAN routing table with [legacy bidirectional tunnel health checks](https://developers.cloudflare.com/cloudflare-wan/configuration/manually/how-to/configure-tunnel-endpoints/#legacy-bidirectional-health-checks) to detect failures and steer traffic to alternative paths. * Note that routes advertised by BGP from GCP Cloud Router will be ignored. * To create routes in GCP routing table to direct traffic towards Cloudflare, you must use the GCP Cloud Router: * Add [custom learned routes to Cloud Router ↗](https://cloud.google.com/network-connectivity/docs/router/how-to/configure-custom-learned-routes). * Use the BGP session. Reach out to your account team to request a list of one or more prefixes to advertise, and specify the interconnect ID you want to advertise over. ```json {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"item":{"@id":"/directory/","name":"Directory"}},{"@type":"ListItem","position":2,"item":{"@id":"/network-interconnect/","name":"Network Interconnect"}},{"@type":"ListItem","position":3,"item":{"@id":"/network-interconnect/get-started/","name":"Get started"}}]} ``` --- --- title: Monitoring and alerts description: Monitor CNI status and configure maintenance alerts image: https://developers.cloudflare.com/core-services-preview.png --- [Skip to content](#%5Ftop) Was this helpful? YesNo [ Edit page ](https://github.com/cloudflare/cloudflare-docs/edit/production/src/content/docs/network-interconnect/monitoring-and-alerts.mdx) [ Report issue ](https://github.com/cloudflare/cloudflare-docs/issues/new/choose) Copy page # Monitoring and alerts ## Monitoring The Cloudflare dashboard shows a list of all previously created interconnects, as well as useful information such as IP addresses, speed, type of interconnect, and status. In the Cloudflare dashboard, go to **Interconnects**. [ Go to **Interconnects** ](https://dash.cloudflare.com/?to=/:account/magic-networks/connections/cni-tunnels) The Status column displays three statuses: * **Active**: The interconnect port on the Customer Connectivity Router (CCR) is operationally up. This means that the CCR port sees sufficient light levels and has negotiated an Ethernet link. * **Unhealthy**: The link operational state at interconnect port is down. This might mean the CCR does not see light, cannot negotiate an Ethernet signal, or the light levels are below -20 dBm. You can take general troubleshooting steps to solve the issue (such as checking cables and status lights for connectivity issues). If you are unable to solve the issue in this way, contact your account team. * **Pending**: The link is not yet active. This is expected and can occur for several reasons: the customer has not received a cross-connect, the device is unresponsive, or physical adjustments may be required, such as swapping RX/TX fibers. The **Pending** status will disappear after the customer completes the cross-connect and status moves to **Active**. ## Alerts (v1 dataplane only) You can configure notifications for upcoming CNI maintenance events using the Notifications feature in the Cloudflare dashboard. It is recommended to subscribe to two types of notifications to stay fully informed. **CNI Connection Maintenance Alert (beta):** This alert informs you about maintenance events (scheduled, updated, or canceled) that directly impact your CNI circuits used with the Cloudflare Virtual Network only. * You will receive warnings up to two weeks in advance for maintenance impacting your Magic Transit/WAN CNI connections. * You will be notified if the details of a scheduled maintenance change or if it is canceled. * For recently added maintenance, notifications are sent after a six-hour delay to prevent alerting fatigue from minor adjustments. **Cloudflare Status Maintenance Notification:** This alert informs you about maintenance for an entire Cloudflare Point of Presence (PoP). While not specific to your CNI, this maintenance will impact all CNI services in that location. This includes connections used only for peering without Cloudflare Virtual Network. * You will be warned about potentially disruptive maintenance at the PoP level. * By default, you are notified for all event types (Scheduled, Changed, Canceled), but you can filter these. * By default, you are notified for all Cloudflare PoPs, but you can filter for only the specific locations where you have CNI circuits. ## How to configure alerts ### Enable CNI Connection Maintenance Alert (beta) 1. In the Cloudflare dashboard, go to the **Notifications** page. [ Go to **Notifications** ](https://dash.cloudflare.com/?to=/:account/notifications) 2. Select **Add**. 3. From the product drop-down menu, select _Cloudflare Network Interconnect_. 4. Select **Connection Maintenance Alert**. 5. Give your notification a name and an optional description. 6. Choose your preferred notification method, such as email address. 7. Select **Save**. ### Enable Cloudflare Status Maintenance Notification First, identify the PoP code for your CNI circuit: 1. In the Cloudflare dashboard, go to **Interconnects**. [ Go to **Interconnects** ](https://dash.cloudflare.com/?to=/:account/magic-networks/connections/cni-tunnels) 2. Select the CNI you want to enable notifications for. 3. In the menu that appears, note the Data Center code (for example, `gru-b`). Now, configure the alert: 1. Go to **Notifications** and select **Add**. 2. From the product drop-down menu, select _Cloudflare Status_. 3. Select **Maintenance Notification**. 4. Give your notification a name and choose your notification method. 5. Select **Next**. 6. Optionally, use the **Filter on Event Type** to select only the event types you want to be alerted for (Scheduled, Changed, Canceled). 7. In **Filter on Points of Presence**, enter the three-letter code for your PoP (for example, for `gru-b`, enter `gru`). You can add multiple PoPs, separated by commas. 8. Select **Create**. ```json {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"item":{"@id":"/directory/","name":"Directory"}},{"@type":"ListItem","position":2,"item":{"@id":"/network-interconnect/","name":"Network Interconnect"}},{"@type":"ListItem","position":3,"item":{"@id":"/network-interconnect/monitoring-and-alerts/","name":"Monitoring and alerts"}}]} ``` --- --- title: Operational guidance description: Maintenance windows and troubleshooting guidance for CNI image: https://developers.cloudflare.com/core-services-preview.png --- [Skip to content](#%5Ftop) Was this helpful? YesNo [ Edit page ](https://github.com/cloudflare/cloudflare-docs/edit/production/src/content/docs/network-interconnect/operational-guidance.mdx) [ Report issue ](https://github.com/cloudflare/cloudflare-docs/issues/new/choose) Copy page # Operational guidance ## Understanding maintenance and availability Also refer to [Monitoring and alerts](https://developers.cloudflare.com/network-interconnect/monitoring-and-alerts). Regular network maintenance may impact Cloudflare Network Interconnect (CNI) connectivity. * **Maintenance impact**: Maintenance windows average six hours. Customers who are not redundantly connected to diverse devices, for instance in single-homed PoPs, will experience a complete service disruption on CNI in that location. * **Designing for availability**: For critical applications, deploy CNI in locations that support diversity on the device level (multi-homed PoPs). Cloudflare does not guarantee coordinated maintenance between PoP locations. ## Maintenance expectations ### Notice periods * **Routine maintenance**: Minimum two business days notice. * **Emergency maintenance**: Best-effort notice, which may be less than two business days. To receive advance alerts, configure [CNI maintenance notifications](https://developers.cloudflare.com/network-interconnect/monitoring-and-alerts/). ### Scheduling patterns * Maintenance on redundant devices (for example, edge router one and edge router two) may occur on consecutive days with a minimum 16-hour gap between windows. * Cloudflare does not coordinate maintenance timing between different PoP locations. * Routine maintenance is generally not rescheduled to accommodate customer schedule preferences. ### Customer responsibility Your CNI deployment must tolerate an unplanned outage on any single circuit at any time. This means: * Traffic failover between redundant circuits must be automatic. * If your operations require manual intervention to reroute traffic during maintenance, your configuration needs review. * Contact your account team to validate your failover design. ## Troubleshooting When facing connectivity problems, your first action should be to check for broader service disruptions. Visit [Cloudflare Status ↗](https://www.cloudflarestatus.com/) to see if any scheduled maintenance or active incidents are impacting services. This helps determine if the issue originates outside your network. Refer to [Monitoring and alerts](https://developers.cloudflare.com/network-interconnect/monitoring-and-alerts/). If no system-wide problems are reported, gather the following information before submitting a support case. Providing comprehensive details facilitates a faster resolution: * **Timeline**: When the issue began and ended (if applicable), including the timezone. * **Identification**: The CNI IP address or point-to-point prefix for the impacted CNI. If your CNI is part of a Magic setup, please also provide the name of the Magic Transit/WAN interconnect as listed in your dashboard. * **Physical Layer**: Light levels of the CNI link (if applicable). * **Service Impact**: Confirmation whether Magic Transit / WAN traffic was affected. * **Problem Description**: A clear summary of the issue (for example, CNI down, Border Gateway Protocol (BGP) session down, prefixes withdrawn). ```json {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"item":{"@id":"/directory/","name":"Directory"}},{"@type":"ListItem","position":2,"item":{"@id":"/network-interconnect/","name":"Network Interconnect"}},{"@type":"ListItem","position":3,"item":{"@id":"/network-interconnect/operational-guidance/","name":"Operational guidance"}}]} ``` --- --- title: Changelog description: Review recent changes to Cloudflare Network Interconnect. image: https://developers.cloudflare.com/core-services-preview.png --- [Skip to content](#%5Ftop) Was this helpful? YesNo [ Edit page ](https://github.com/cloudflare/cloudflare-docs/edit/production/src/content/docs/network-interconnect/changelog.mdx) [ Report issue ](https://github.com/cloudflare/cloudflare-docs/issues/new/choose) Copy page # Changelog [ Subscribe to RSS ](https://developers.cloudflare.com/changelog/rss/network-interconnect.xml) ## 2026-03-24 **Interconnects moved to Connectors** The top-level **Interconnects** page in the Cloudflare dashboard has been removed. Interconnects are now located under **Connectors** \> **Interconnects**. Your existing configurations and functionality remain the same. ## 2025-06-20 **CNI maintenance alerts** Customers using Cloudflare Network Interconnect with the v1 dataplane can now subscribe to maintenance alert emails. These alerts notify you of planned maintenance windows that may affect your CNI circuits. For more information, refer to [Monitoring and alerts](https://developers.cloudflare.com/network-interconnect/monitoring-and-alerts/). ## 2024-12-17 **Establish BGP peering over Direct CNI circuits** Magic WAN and Magic Transit customers can use the Cloudflare dashboard to configure and manage BGP peering between their networks and their Magic routing table when using a Direct CNI on-ramp. Using BGP peering allows customers to: * Automate the process of adding or removing networks and subnets. * Take advantage of failure detection and session recovery features. With this functionality, customers can: * Establish an eBGP session between their devices and the Magic WAN / Magic Transit service when connected via CNI. * Secure the session by MD5 authentication to prevent misconfigurations. * Exchange routes dynamically between their devices and their Magic routing table. Refer to [Magic WAN BGP peering](https://developers.cloudflare.com/cloudflare-wan/configuration/manually/how-to/configure-routes/#configure-bgp-routes) or [Magic Transit BGP peering](https://developers.cloudflare.com/magic-transit/how-to/configure-routes/#configure-bgp-routes) to learn more about this feature and how to set it up. ## 2024-10-01 **Early access testing for BGP on Direct CNI circuits** Customers can exchange routes dynamically with their Magic virtual network overlay via Direct CNI or Cloud CNI based connectivity. ## 2024-09-02 **Interconnect portal displays all available locations in a list** Customers can now see all available Direct CNI locations when searching for a Cloudflare site in the Interconnects interface. ```json {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"item":{"@id":"/directory/","name":"Directory"}},{"@type":"ListItem","position":2,"item":{"@id":"/network-interconnect/","name":"Network Interconnect"}},{"@type":"ListItem","position":3,"item":{"@id":"/network-interconnect/changelog/","name":"Changelog"}}]} ```