SiteSpect Cloud Overview


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 any number Points of Presence (POPs), currently nine (9), strategically located in different parts of the US and Europe. Site visitors are dynamical routed to the best performing POPs based on network conditions for their geographic locations.

Within each SiteSpect POP, traffic is directed to devices called Engines, reverse proxy devices with SiteSpect code. Each Engine has the same configuration as all other Engines. Site visitor sessions are managed via cookies. Site visitors can route from Engine to Engine and POP to POP without any impact to their customer experience.

SiteSpect uses advanced DNS technologies to ensure that site visitors are always routed to the best performing entry point into 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?  

SiteSpect Cloud maintains multiple high availability Points of Presence (POPs) across Europe and North America that provide the ability to 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 optimally available POP. This happens seamlessly and is designed to be invisible to site traffic. SiteSpect engineers are immediately notified of any unavailable POP and work to restore them safely and quickly.

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 SiteSpect Cloud goes down, your site traffic is routed to your origin directly and SiteSpect is automatically bypassed.

If either you or SiteSpect suspect an event that affects traffic, you can quickly put SiteSpect into Bypass by selecting SiteConfigurationSite SettingsBypass. This setting is available only to System Administrators. Contact the SiteSpect Help Desk for assistance at Doing so 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.

How can I (the IT stakeholder) realize the value of SiteSpect?

SiteSpect has a variety of features of particular use to our IT stakeholders:

  • We provide kibana-like log visualization of access logs. Due to SiteSpect's placement as a reverse proxy, we can provide a detailed view of your origin's performance from a site visitor’s perspective.
  • SiteSpect can also be used for release and feature testing. SiteSpect can maintain audience membership and session management to roll out new features and releases to a limited percentage of traffic. This can be used to both ensure that not all site visitors see new code until you're confident in your site’s stability and to measure the business value of those new releases and features.
  • SiteSpect can push hotfixes to all traffic or to a segment of your website traffic to quickly resolve issues.
  • SiteSpect can track JS errors in Campaigns so that you can see if changes you are trying to test are causing more client side errors than the control.