Dear Peeredge Subscribers,
2017 has been the most productive year in 46 Labs’ history. Our team has grown to over 40 people and our business has tripled since 2016. We have also made significant improvements in our infrastructure. These improvements include the acquisition of a new datacenter in the Dallas Infomart which is 8 times larger than our previous facility, an upgrade of our core routing and switching infrastructure to new Juniper MX 960 and QFX gear, and a substantial investment in a new bare metal cloud, which will house our Peeredge hosted platform. Additionally, we have added 3 new carriers in our BGP blend and established direct peering relationships with public cloud providers, such as AWS, GCE, Rackspace and Azure.
All of this effort has been made to establish a new and improved foundation in which to expand our Peeredge hosted platform, as well as to position our carrier customers to take advantage of new technologies and relationships that we have built in the large enterprise space. What this means to our Peeredge customers, is that you will see substantial improvements in Peeredge starting in 2018.
We will be migrating all customers of Peeredge to our new facility and infrastructure beginning February 1st, 2018 and concluding by the end of February. This is a minimal downtime event (Less than 2 minutes) and our client management team will be reaching out to coordinate maintenance windows in which to perform the migration. You will not need to change anything about your Peeredge configuration to make this change, and your IP addresses will remain the same. However, one thing that will change is that you will be given your own unique URLs for the Subscriber, Admin and Carrier portals. This is a transitional step in allowing you to not only custom-brand your interfaces for each of these portals, but also assign your own domain URLs from your existing domain. Effectively, this is preparing Peeredge to support full white-labeling. No other changes will be required to perform the migration and these interim URLs will be supplied to you well in advance of migration.
Architectural Changes in Peeredge
While the interface will remain the same through the migration of Peeredge to our new infrastructure, many things underneath the hood have undergone significant improvements. We have spent the last 3 months testing every aspect of these improvements to ensure a smooth and painless transition.
Peeredge Private Cloud
One of the principal changes that we have made in Peeredge is that we have migrated our entire voice switching infrastructure away from a “shared everything” infrastructure to a “shared nothing” infrastructure. What this means is that each of our customers are given their own load balancers and SBCs that are not shared by any other subscriber. These infrastructure pieces are also deployed on independent bare-metal hosts, so there is no likelihood that one customer’s traffic can impact another customer’s traffic. Effectively each of our subscribers have their own server and voice infrastructure inside of our facility and each of these infrastructures are controlled privately. We will, however, still utilize a shared OSS/BSS system, so customers can continue to realize the benefits of large clusters of available resources. These significant improvements to the resiliency, flexibility and performance of your switching infrastructure are done at no cost to our current subscribers.
Impacts to Network Flexibility
Since each of our customers, from an infrastructure perspective, are wholly separated from each other, this means we can do some very interesting things at the network level. Each of our customers are assigned their own private VLAN inside of our datacenters. This VLAN is used to provide a private network between Peeredge and other resources that you may choose to deploy including physical servers collocated in one of our datacenter racks, or VMs deployed inside of our cloud. We can also provide private point-to-point links to other datacenters or potentially directly to individual customers using either VPNs, or private physical connections. You may also utilize our direct peering into public cloud providers to privately link your Peeredge infrastructure with other workloads you may have. Additionally, you may also BYOIP (Bring your own IP) or BYOASN (Bring your own ASN) into our new infrastructure. Simply put, we can manage all aspects of your datacenter, voice switching and data connectivity needs privately and all unified into a single management element.
Impacts to Peeredge Switching
Since the switching infrastructure is entirely independent in the new architecture, this now allows us to significantly improve the per-subscriber experience. One principal benefit of this change is that it means we now control subscriber and trunk group ports and cps calculation and limits on a per-subscriber basis. We will no longer have terminating CPS or ports limits set in increments of 10 and the counting and limiting of those values will be SIGNIFICANTLY improved in the new architecture. Our distributed counting mechanisms are now discrete and thus orders of magnitude more accurate in the new architecture.
Since the SBCs, called TSs (Traffic Switches), in the new architecture are unique to the subscriber, this means that we will no longer have shared media IPs. The media IPs assigned to each traffic switch will be unique to the subscriber and can be changed at any time. We can also tailor the number of TSs we deploy for a subscriber, allowing us to match the specific workload of each subscriber independently.
Having switching separation on a per-subscriber basis also sets the new Peeredge infrastructure up to be custom tailored to the unique switching and signaling needs of each individual customer. The new architecture will mean that we can test and deploy new features or make signaling tweaks on a per-subscriber basis, greatly improving the flexibility of your voice network. It also means that we can deploy parallel independent switching infrastructures, which are controlled by the same Peeredge interface, but which are limited independently. This way customers can, for instance, deploy their conversational and short duration workloads in separate switching instances which don’t impact each other, but are controlled by a common Peeredge interface. The flexibility of our new infrastructure gives you all of the custom benefits of owning your own infrastructure and networking, without the hassle of managing it and cost of deploying it.
Peeredge 2018 Expectations
We considered 2017 a “sowing” year for Peeredge in that we spent a great deal of resources developing and preparing for the next big improvement to our Peeredge platform. Those efforts will be realized in 2018 as improvements to all aspects of Peeredge, not just in the architecture. We have gathered all feedback on what you are looking for from an interface, ratedeck, business, reporting and routing standpoint and you will notice significant improvements in all of these areas of Peeredge in 2018.
We are extremely happy to share this good news with you and look forward to a fantastic 2018.
Peeredge Client Happiness