Abstract: What is disclosed is providing a multi-tenant virtual private network (VPN) to a plurality of tenants, wherein tenant VPNs are associated with respective private networks; identifying a first subnet that makes up a portion of a first private network associated with a first tenant of the plurality of tenants; translating the first subnet into a first multi-tenant VPN address translation (MT-NAT) subnet that is used as part of a first tenant VPN to extend the first private network across a public network; identifying a second subnet that makes up a portion of the first private network, that is not contiguous with the first subnet, and that has not been translated into the first MT-NAT; and translating the second subnet and a proper subnet of the first subnet into a second MT-NAT subnet without impacting subnet fragmentation of the first private network. Also disclosed are systems and methods for this.

Abstract: Disclosed is a cloud services exchange platform that provides for multi-tenant orchestration with a flexible underlay facilitating tenant move with minimal disruption. Multi-tenant node engines are adapted to orchestrate the instantiation, hosting, and/or provisioning of services to one or more endpoints on behalf of a customer. Multiple dataplanes are associated with the cloud services exchange platform.

Abstract: A cloud exchange platform includes policy-based routing. Labeling (or tagging) on a multi-tenant virtual private network (VPN) facilitates recognition of active routes for a flow. The tags can be implemented such that flows are treated as having active routes across a multi-tenant VPN to enable a customer to treat flows as having an identifiable active route through the multi-tenant VPN. Thus, for example, BGP can be used as a generalized signaling protocol to carry information about flows through a multi-tenant VPN.

Abstract: Disclosed is a system that includes a plurality of regional cloud exchange platforms coupled to a distributed alert triaging engine. A system can include a first regional cloud exchange platform and a second regional cloud exchange platform, each of which includes a regional cloud services monitoring engine and a cloud exchange monitoring engine, and an alert triaging engine that provides a triaged alert, or portion thereof, to an appropriate audience.

Abstract: Disclosed is a network topology visualization system comprising: branch connector instances; branch connectors, wherein each grouping of the branch connector instances has a corresponding grouping of branch microsegment edges and each node of each grouping of the branch connector instances has a corresponding edge of a corresponding grouping of branch connector edges; virtual private cloud (VPC) connectors; and a cloud exchange node. The cloud exchange node includes: a service group; applications coupled to the VPC connectors via VPC segment edges; connector groups, coupled to the branch connectors via branch segment edges, wherein each of the branch segment edges uniquely couples a branch connector to a connector group; and a visualization engine that provides a visualization facilitated by connector construct abstraction of a network topology for a network of a customer.

Abstract: Disclosed is a controller with an application-agnostic customer gateway comprising a dataplane management gateway, a dataplane management engine configured to take care of intent of platform-agnostic customer requests by onboarding on a nearest-to-customer platform and splitting requests into granular tasks to be carried out in a given region, a customer gateway for providing customer access to a customer network, a tenant management engine, a tenant provisioning engine, and a resource management engine.

Abstract: A router architecture that facilitates cloud exchange point routing is disclosed. The architecture relies upon B-nodes to connect branch network to cloud, S-nodes to connect services, and V-nodes to connect cloud to cloud. The nodes can be essentially stateless with node configuration stored outside a router, which facilitates ripping and replacement of nodes. Multiple virtual private clouds can be implemented with respective pluralities of Kubernetes pods and a master Kubernetes cluster. Consumer premises equipment is coupled to a first virtual private cloud that forms a virtual extensible local area network with a second private cloud.

Abstract: Disclosed is a system that includes a plurality of regional cloud exchange platforms coupled to a distributed alert triaging engine. A system can include a first regional cloud exchange platform and a second regional cloud exchange platform, each of which includes a regional cloud services monitoring engine and a regional cloud exchange monitoring engine, and an alert triaging engine that provides a triaged alert, or portion thereof, to an appropriate audience.

Abstract: What is disclosed is tagging a first flow of a multi-tenant virtual private network (VPN) with a first tag. Continuously tracking, based on the first tag, the first flow of the multi-tenant VPN. Capturing one or more characteristics of the first flow of the multi-tenant VPN. Categorizing the first flow of the multi-tenant VPN based on the one or more characteristics of the first flow. Providing the categorization of the first flow to a first tenant of the multi-tenant VPN. Receiving, based on input from the first tenant and the categorization of the first flow, a first policy. Enforcing the first policy on the first flow based on the first tag of the first flow and the continuous tracking of the first flow.

Abstract: Disclosed is a cloud services exchange platform that provides for multi-tenant orchestration with a flexible underlay facilitating tenant move with minimal disruption. Multi-tenant node engines are adapted to orchestrate the instantiation, hosting, and/or provisioning of services to one or more endpoints on behalf of a customer. Multiple dataplanes are associated with the cloud services exchange platform.

Abstract: A router architecture that facilitates cloud exchange point routing is disclosed. The architecture relies upon B-nodes to connect branch network to cloud, S-nodes to connect services, and V-nodes to connect cloud to cloud. The nodes can be essentially stateless with node configuration stored outside a router, which facilitates ripping and replacement of nodes. Multiple virtual private clouds can be implemented with respective pluralities of Kubernetes pods and a master Kubernetes cluster. Consumer premises equipment is coupled to a first virtual private cloud that forms a virtual extensible local area network with a second private cloud.

Abstract: What is disclosed is tagging a first flow of a multi-tenant virtual private network (VPN) with a first tag. Continuously tracking, based on the first tag, the first flow of the multi-tenant VPN. Capturing one or more characteristics of the first flow of the multi-tenant VPN. Categorizing the first flow of the multi-tenant VPN based on the one or more characteristics of the first flow. Providing the categorization of the first flow to a first tenant of the multi-tenant VPN. Receiving, based on input from the first tenant and the categorization of the first flow, a first policy. Enforcing the first policy on the first flow based on the first tag of the first flow and the continuous tracking of the first flow.

Abstract: A router architecture that facilitates cloud exchange point routing is disclosed. The architecture relies upon B-nodes to connect branch network to cloud, S-nodes to connect services, and V-nodes to connect cloud to cloud. The nodes can be essentially stateless with node configuration stored outside a router, which facilitates ripping and replacement of nodes. Multiple virtual private clouds can be implemented with respective pluralities of Kubernetes pods and a master Kubernetes cluster. Consumer premises equipment is coupled to a first virtual private cloud that forms a virtual extensible local area network with a second private cloud.

Abstract: A router architecture that facilitates cloud exchange point routing is disclosed. The architecture relies upon B-nodes to connect branch network to cloud, S-nodes to connect services, and V-nodes to connect cloud to cloud. The nodes can be essentially stateless with node configuration stored outside a router, which facilitates ripping and replacement of nodes. Multiple virtual private clouds can be implemented with respective pluralities of Kubernetes pods and a master Kubernetes cluster. Consumer premises equipment is coupled to a first virtual private cloud that forms a virtual extensible local area network with a second private cloud.