Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- Northern Virginia is the second AWS Interconnect - last mile metro after New York; AWS lists Lumen as generally available and Megaport and Equinix as preview providers there.
- Lumen customers in the continental United States can connect through Northern Virginia to public AWS Regions except China, as well as AWS Local Zones; that does not verify every facility's eligibility.
- The default connection spans two physically diverse locations with four redundant links; the 99.99% availability SLA extends only to the Direct Connect port.
- Charges are hourly per interconnect based on bandwidth and its assigned tier, rounded up to whole hours; the highest path to the furthest Region on one DXGW determines one tier.
- The pricing page does not quote Northern Virginia rates; confirm the site, delivery timing, partner charges, and contract terms separately.
Start with Northern Virginia provider status
On November 5, 2026, AWS announced Northern Virginia as its second AWS Interconnect - last mile metro after New York. A metro is the physical location where the delivery partner connects into AWS. The service is intended for teams connecting a data center, branch office, or colocation facility to AWS through a managed private connection involving AWS and a delivery partner.
AWS lists Lumen as generally available (GA) in Northern Virginia and says Lumen customers anywhere in the continental United States can order through that metro. Megaport and Equinix are listed as preview providers there. Preview is not GA, and the announcement does not establish that providers share rates or contract terms.
Check destination reach separately from site eligibility
The announcement says Lumen connections can reach all public AWS Regions except those in China, plus AWS Local Zones. This describes AWS destinations; it is not a promise of access to China Regions, does not enumerate Local Zones, and does not explain their separate commercial treatment.
The statement that continental U.S. customers can order does not verify that a particular data center, branch office, or colocation site can be delivered as planned. Ask the selected partner to confirm the address, access conditions, and estimated lead time. AWS does not publish site-by-site qualification or an installation schedule in this announcement.
Understand the redundancy design and SLA boundary
AWS says each connection is provisioned by default across two physically diverse locations with four redundant links. This describes the default resilience arrangement across AWS and partner infrastructure; it does not replace an assessment of customer equipment, branch circuits, routing, or application availability.
The announced availability service-level agreement (SLA) is 99.99% up to the Direct Connect port. It is not an end-to-end SLA from a branch office through the full network path to an application. Compare that port boundary separately from commitments made by the delivery partner or the customer's own network.
Keep the MACsec boundary clear
AWS says traffic between AWS and partner edge devices is encrypted with MACsec by default. That statement defines the encryption boundary; it does not mean the same MACsec protection covers the full route from customer branch equipment to an AWS application.
If the design requires end-to-end encryption, review the customer-to-partner edge, the path beyond the AWS port, and application encryption separately. The announcement does not specify protocol coverage, key management, or customer-device requirements, so those details should not be inferred.
Read hourly charges through the highest path
AWS's pricing page says each interconnect is charged hourly based on bandwidth and an automatically assigned tier. Billing starts when the connection is created and stops when it is deleted, with hours rounded up to the next whole hour. There are no per-gigabyte data-transfer charges for this product, but that does not make partner, other networking-service, or contract charges zero.
Each connection receives one tier rather than a sum of every tier along its paths. The tier is based on the selected metro and furthest AWS Region attached through a single Direct Connect Gateway (DXGW); the highest path sets it. With Cloud WAN, review the furthest Core Network Edge (CNE) in the topology as well: its highest tier can determine the charge, rather than the CNE nearest the partner metro.
Prepare network details for a quote
Confirm the required bandwidth, destination AWS Regions, selected metro, furthest Region attached to the DXGW, and whether Cloud WAN has a more distant CNE. Then ask the delivery partner to verify the site, GA or preview status, estimated delivery time, and what the quote includes.
Keep AWS hourly billing and rounding rules, the assigned tier, the partner quote, the contract SLA, and its boundary together when comparing designs. The AWS pricing page reviewed here gives no Northern Virginia-specific rate, and its New York examples should not be used as a Northern Virginia quote. Confirm the actual rate and any partner charges against the selected design.
Sources
Frequently Asked Questions
Which AWS interfaces can create a connection?
AWS lists the AWS Management Console, AWS CLI, and AWS Interconnect API. Interface support does not qualify a particular address; first confirm provider availability, site conditions, and the contract.
Will the pricing tier update after a more distant Cloud WAN CNE is removed?
In the pricing page’s New York example, removing the Singapore CNE causes the tier to update automatically within minutes to reflect the new topology. The actual tier still depends on the highest remaining path. This example is not a Northern Virginia rate or a timing guarantee for every configuration change.