Web Gateway Cloud Service: Cloud Maintenance and Peering Benefits
As the Web Gateway Cloud Service evolves, infrastructure will be updated and maintained. Apart of this process means that we (McAfee) will be decommissioning legacy infrastructure. Is this bad? Far from it!
If you've talked with any of us on the McAfee team recently about the Web Gateway Cloud Service, you'll know we're heavily invested. So losing a few older nodes in the name of performance is a good thing.
So in December, there will be a few nodes decommissioned and as such, the counter on https://trust.mcafee.com will go down. These changes are apart of a bigger effort to roll out the new infrastructure that started on November 27th, for more information please see these KB articles:
The locations being decommissioned are listed below. They are being retired in favor of higher performance locations where peering is available.
Denver - Decommissioned, was an older data center without peering.
Amsterdam - After the change there will be one point of presence instead of two.
London - After the change there will be two points of presence instead of three.
Benefits of Peering
The new infrastructure in the Web Gateway Cloud Service is in locations where peering is available. Use of peering has many benefits, such as:
Hops are reduced if customer ISP participates in peering (a lot do)
Reduces latency between customer and the Cloud Service
Peering providers larger pipes to content providers
E.g. Connections to Google or Microsoft go over 10G pipes instead of ISP pipes
The below graphic shows how hops are eliminated on both sides of the Cloud Service -- between you and us, and between us and the content providers (which make up more than 75% of the internet). With peering, intermediate hops are no longer required.