FAQs
- How is the SiteSpect Cloud architecture designed to handle traffic?
- How does SiteSpect ensure that there is no effect on my traffic when a Point of Presence is degraded?
- What happens if SiteSpect Cloud goes down? Will my site be affected?
- Will SiteSpect slow down our website’s performance? By how much?
How is the SiteSpect Cloud architecture designed to handle traffic?
The SiteSpect Cloud is designed with resiliency, redundancy, and efficiency in mind. Traffic is routed to several Points of Presence (POPs), currently nine (9), strategically located in different parts of the US and Europe. Site visitors are dynamically routed to the best performing POPs based on network conditions for their geographic locations.
Within each SiteSpect POP, traffic is distributed to individual Engines, which are reverse proxy devices running SiteSpect code. Each Engine serves the same function and has the same software and configuration as every other Engine. Site visitor sessions are managed via cookies. Site visits can route through any POP and any Engine and have the same customer experience.
SiteSpect uses advanced DNS technologies to ensure that site visitors are routed to the best performing entry point in the SiteSpect cloud at all times.
How does SiteSpect ensure that there is no effect on my traffic when a Point of Presence is degraded?
The SiteSpect Cloud maintains multiple high availability Points of Presence (POPs) across Europe and North America that balance and route site traffic optimally across the platform. We use a dynamic real-time traffic management system to automatically route your traffic to the best performing POP closest to your traffic.
If a POP becomes unavailable, SiteSpect automatically routes traffic to the next optimally available POP. This happens seamlessly and is designed to be invisible to site traffic. SiteSpect engineers are immediately notified of any availability issues and work to resolve them quickly and safely.
What happens if SiteSpect Cloud goes down? Will my site be affected?
SiteSpect actively monitors its systems as well as the health of client origins 24/7. If the SiteSpect Cloud were to go down, your site traffic would be routed directly to your origin; SiteSpect is automatically bypassed.
If either you or SiteSpect suspect an event that affects traffic, you can quickly put SiteSpect into Bypass by selecting: Site > Configuration > Site Settings > Bypass. This setting is available only to System Administrators. If you are not a System Administrator, you can contact the SiteSpect Help Desk for assistance at <helpdesk@sitespect.com>. Bypass causes traffic to route around SiteSpect, sending your site visitors directly to your website origin.
Will SiteSpect slow down our website’s performance? By how much?
- The SiteSpect reverse proxy service is highly optimized to perform a variety of application functions in nominal time. The SiteSpect Cloud infrastructure is a cluster of reverse proxies that have been designed with multiple, highly available, geographically diverse Points of Presence, using a blend of routing optimization and global/local load balancing approaches.
- The SiteSpect application conducts traffic segmentation, site traffic management, data sampling, and variation of web content (HTML, CSS, XML, json, etc.) All of these functions are typically performed in under 30 ms as measured by SiteSpect internal computational overhead. This is measured and provided to customers through a real-time reporting interface within the SiteSpect user interface.