Our System Administrators are working hard on this issue as we speak, we hope to have it 100% corrected soon!
This is all fixed up! Our System Administrators worked hard to fix the domain issue as soon as we could. However, you may still be seeing some issues for a brief time until everything clears up on the interwebs.
DNS changes can take a few minutes to a few hours to propogate, so it’s mostly resolved now, but some users may still get a bad link.
We are so sorry that this happened, we of course are taking steps to make sure this NEVER happens again.
I’m sorry links continue to not be working in places. I have been doing further research into ways we can help you speed up or get around the issues blocking the links from working properly on your side and/or for certain respondents.
Here’s what I have found that you can try:
The core of the problem working against us here is that to solve the problem we had, we renewed the domain, sgizmo.com, that we use to serve any private domains used through SurveyGizmo and for email campaign links. When this is done, the update to tell end users clicking these links where to find the web page is cached in cases and beholden to what is called DNS Propagation.
DNS Propagation essentially is the time it takes for the changes to a domain on the internet to take effect. The DNS, Domain Name System, settings cache the information about the domain for a certain amount of time and then refresh to look for any changes to their settings. Our renewal of the domain is part of this refresh. While many DNS caches, whether they are on your private domain, our domain, a local network at an office, company, school, or elsewhere, can update within a few hours (and that’s what we have been seeing for the majority of links that have been having issue) our research shows that the common fringe of the DNS cache settings before they refresh is up to 24 hours.
The amount of time over which a DNS cache will take to be refreshed is called TTL, or “Time to Live”. Once that time passes, the changes we have made to fix the problem will propagate for that end user. So the question to ask is, can you get around this time it takes to propagate the changes we have in place to get your links back up and running. The answer is “possibly” but not totally likely depending on the situation.
You can try speeding it up by lowering the TTL number set on your private domain or on any settings on the network in your office or at your respondent’s company. Do remember that if you update your domain itself, the network you or your respondents are using to access the internet on might refresh at a slower rate. This can be a solution, but might be detrimental overall for accessing the internet from the location.
The other thing to explore is to ask your IT team or the IT team on your respondent’s end if they can clear the DNS cache. This can work, but isn’t a comprehensive solution for getting around the time to wait for propagation to occur.
A final good step is to clear the cache and cookies on your web browser and ask your respondents to do so, if you feel its appropriate to reach out to them to ask. Here’s how in case you want to provide instructions:
While that too isn’t a comprehensive solution, it has the potential to help and is a quick step to see if it will get things rolling.
So the long story as short as possible here, is this might take up to 24 hours for some respondents and locations to get back into the links correctly. Getting around that delay is difficult and not always comprehensive for all respondents depending on what DNS settings their computer or device is beholden to.
We do want to keep helping and are looking for any other avenues to keep working towards a speedier solution on.
The final key note I can make on this end is that while you might still be seeing the incorrect page from your links because the DNS cache has yet to clear on your end, a good amount of respondents around the world are not having issue now because their DNS cache has cleared on their end. Obviously if you have a survey you’re sending to a single company or single office all sharing the same DNS cache that hasn’t cleared, this is still effecting a good amount of your respondent base. That is very damaging for you and your reputation. I’m happy to work to do anything I can to work with you there on damage control.
This problem has not yet been resolved for us here in India. It’s been 2 days now. Could you give us an alternative. We have surveys running and the respondents are not able to get into the survey yet.
This is continuing to be a problem for my clients. We have more than 200 links affected by this outage. As of 7:30 in AZ (PST) the links were working for me and my clients in VA (EST). But a main end client with 27 links is still redirecting to the register page — using a new browser where cookie cleaning would not matter. That client is in CA (PST).
What are others seeing?
It has now been 24 hours since this was supposed to have been solved. What gives?
Please provide us communication or set up some sort of outage report map so we know where issues still remain.
Our clients are still seeing an issue this morning (UK time). This is embarrassing when we told them yesterday that it was fixed.
Please provide an update.
We received ZERO notification that there was an issue with this today and it resulted in a significant decrease in revenue.
Please be sure to let your customers know that things are broken, especially when they are spending money to drive traffic to your service.