(Last Updated On: July 6, 2017)
Resolved: Transient access impact for some clients
July 5, 2017 8:17pm MST – Our platform monitoring shows that the small loss of traffic noticed earlier (at the time of the issue report) is no longer present, which means that all DNS servers around the world have picked up our updates at this point, and are serving the correct configuration to access our platform. Please accept our sincere apologies if you have been impacted in the last 15 minutes. We selected the time of lowest traffic to perform this update, even though we did not expect any negative impact.
July 5, 2017 7:57pm MST – We have performed a change on the platform that requires the DNS to be in sync with servers platform confirmation. The configurations have been pushed live and synchronized on our end. But some clients who are on a network with a DNS server doing aggressive caching may get a transient error while access our service over https. If you are impacted, the issue will self heal in the coming minutes once the DNS server on your network will synchronize.