Considerations and Implications
Instart can point your traffic to your origin services directly, if for any reason you make this request. However, please note that this request can have serious implications and should only be made after full consideration of the following points:
- Can your origin handle the volume of requests per second and load currently handled by Instart?
- Switching over might bring down your origin and result in a deadlock for your web traffic.
- Current traffic volume can be confirmed in the Instart portal.
- Do you currently use Instart's Web Application Firewall (WAF)?
- If you have the WAF enabled, for the period of the time your traffic is being forwarded straight to your origin, Instart will not be providing WAF functionality or associated security measures.
- Does your origin have a valid SSL certificate for all the domains that you are requesting to have bypass Instart?
- Without valid SSL certificates secure traffic will result in errors when forwarded to your origin.
- Is your origin configured to manage requests from the Instart service in a specific way (e.g. looking for a specific User Agent string, specific headers being passed by Instart, or only allowing connections from certain IPs)?
- If so, you will need to disable those checks during the period of time you will be taking traffic directly or have equivalent configuration functionality available on your origin at the time you make the request to bypass Instart services.
- Does your application use any Instart hostnames (e.g. look for occurances of insw.net in your application code)?
- This may render them unreachable.
Remember that multiple customer domains can point to the same Instart service domain as an endpoint, but will likely have a different origin service at the back end. So, for example, if for some reason you point portal.mysite.com, support.mysite.com, images.mysite.com, and www.mysite.com all to instart.mysite.com, and if support.mysite.com’s origin server is different than www.mysite.com, then updating DNS for instart.mysite.com to point to one of the domain’s origin servers will render some connections unreachable.
- Have you configured DNS using only a CNAME?
- If you have pointed to the Instart service using an A record, this process will not work. You will need to update your DNS setup to point it to your origin prior to being able to make this request.
If after reading and understanding the above you still want to go ahead with the DNS switch, please see below on how to contact Instart Support and request Instart bypass.
Requesting Instart Bypass
To request bypassing Instart services:
- Raise a request to Instart Support:
US Toll Free Number: 1-888-576-3166
Direct Dial: +1-650-919-8854
For opening support requests via email, please see Using Email with Support Requests.
- If the request for Instart bypass is urgent, (e.g. due to issues affecting production traffic or services), please let us know that your concern is urgent:
- Setting the 'Priority' to 'Urgent' in the support ticket online.
- Adding '#urgent' to your email submitted support.
- Dialing directly and indicating that a production system is being affected to your support representative.
- If this is not an urgent request, please indicate any time sensitivity in the request and your support representative can work with you on the desired timing.
- Any tool such as dig or host will show the mapping of the service domain. The service domain should be pointing to the requested origin, rather than an Instart location.