StackPath’s Private Backbone 21% Faster Than Public Internet
How much faster does content travel over a private network backbone like StackPath’s vs the public Internet?
The public Internet is a wonderful thing. It interconnects the world’s public networks together to allow fast and reliable communications between electronic devices all across the globe. But it can be made faster.
The nature of the public Internet is that each network (such as a network transit provider) can pass off traffic meant for another network. So Network A can send traffic to Network C via an intermediate network, Network B.
When a content delivery company like StackPath has a private network backbone, it can bypass any intermediary network that’s part of the public Internet to deliver that content directly over long distances. And, since time losses accrue with every network the content has to cross over, fewer networks means faster data transfer.
How much faster?
To answer this question, we made 1,000 requests over the public Internet for a 1MB object, then 1,000 requests over StackPath’s backbone for the same 1MB object.
- Path #1 (public Internet): We had a client in LA make a request to StackPath’s proxy server in LA which forwarded a request to an origin server in NYC over the public Internet.
- Path #2 (StackPath’s backbone): This time, StackPath’s proxy server in LA forwarded a request to StackPath’s proxy server in NYC over StackPath’s backbone. Once in NYC, that proxy server forwarded the request onto the origin. (Nothing here was cached.)
Based on the average total response times for 1,000 requests, we found that StackPath’s private backbone is 21% faster than the public Internet.
This was the case despite the extra proxy server sitting in New York to terminate the connection over StackPath, which could induce extra waiting time as the proxy server also has to process the request.
Want to learn more about what makes StackPath’s backbone a faster path for content delivery? You can learn about our network here.