When the respondent hits the survey URL, following processes occur:
Step 1: A DNS request is made to resolve QuestionPro IP address.
Step 2: Respondents browser tries to establish connection to our servers.
Step 3: To establish a connection, a path to our servers has to be established. This is done by TCP/IP network stack as below.
Following is the path:
Client machine >> ISP GATEWAY >> Multiple Intermediate routers >> QP Datacenter ISP gateway/firewalls >> QP DATACENTER INTERNAL ROUTERS/Firewalls >>>> QP servers.
As depicted above, issues can occur anywhere in the chain, and some issues might not be even under QP's control. So we always need to work with customers for troubleshooting and getting that resolved.
In order to figure out the root cause of this issue we need the client/ respondents to run some commands on their end, that gives us the path taken by client request to our servers which helps us in debugging the issue.
Our network team would require those details in order to help you resolve/identify whether the issue is at QP end or client/customer end or somewhere in between.
For installing the MTR tool you can refer this link.
For mac and Linux:
US (QP) | US (SA) | CA | EU | AU | AE | |
---|---|---|---|---|---|---|
ping | www.questionpro.com | www.surveyanlytics.com | ca.questionpro.com | eu.questionpro.com | au.questionpro.com | ae.questionpro.com |
traceroute | www.questionpro.com | www.surveyanlytics.com | ca.questionpro.com | eu.questionpro.com | au.questionpro.com | ae.questionpro.com |
mtr -w --report -m 60 | www.questionpro.com | www.surveyanlytics.com | ca.questionpro.com | eu.questionpro.com | au.questionpro.com | ae.questionpro.com |
For Example: If you are from EU domain
ping eu.questionpro.com
traceroute eu.questionpro.com
mtr -w --report -m 60 eu.questionpro.com
For windows:
US (QP) | US (SA) | CA | EU | AU | AE | |
---|---|---|---|---|---|---|
ping -t | www.questionpro.com | www.surveyanlytics.com | ca.questionpro.com | eu.questionpro.com | au.questionpro.com | ae.questionpro.com |
tracert | www.questionpro.com | www.surveyanlytics.com | ca.questionpro.com | eu.questionpro.com | au.questionpro.com | ae.questionpro.com |
mtr -w --report -m 60 | www.questionpro.com | www.surveyanlytics.com | ca.questionpro.com | eu.questionpro.com | au.questionpro.com | ae.questionpro.com |
For Example: If you are from EU domain
ping -t eu.questionpro.com
tracert eu.questionpro.com
mtr -w --report -m 60 eu.questionpro.com
You can also use IP instead of domain name. To get the ip addresses for our site you can use tools like "nslookup" or "dig".
For example:
dig www.questionpro.com
nslookup www.questionpro.com
Output:
Non-authoritative answer:
Name: www.questionpro.com
Address: 70.42.174.124
Name: www.questionpro.com
Address: 70.42.174.125
For example:
ping 70.42.174.124
traceroute 70.42.174.124
mtr -w --report -m 60 70.42.174.124
For Windows:
ping -t 70.42.174.125
tracert 70.42.174.125
mtr -w --report -m 60 70.42.174.125
Depending on the datacenter you have signed up, the domain name/IP will change.
For US: www.questionpro.com
For EU: eu.questionpro.com
For CA: ca.questionpro.com
For AU: au.questionpro.com
For AE: ae.questionpro.com
Note: Further steps will be performed by QuestionPro's admin team, once we are provided by these details.