Continuing from the previous incident (https://digitalpigeon.statuspage.io/incidents/r886w5d2t611
) which was prematurely closed based on feedback from Amazon AWS. We are continuing to work with Amazon AWS to resolve the issue.
A minority of users report that uploads, download and previews are failing. Investigation suggests that the effected users are experiencing issues due to problems resolving Domain Name Server* (DNS) queries to Amazon S3 services (our hosting provider).
DNS is a core component of the internet and is usually provided and configured auto-magically by your ISP when you connect to internet. Unfortunately being such a low level part of the internet puts it completely outside of our control.
As a temporary work-around for the issue we recommend switching to either the Cloudflare or Google DNS servers which are confirmed working (and are generally faster than those provided by your ISP).
> Cloudflare MacOS: https://developers.cloudflare.com/184.108.40.206/setting-up-220.127.116.11/mac/
> Cloudflare Windows: https://developers.cloudflare.com/18.104.22.168/setting-up-22.214.171.124/windows/
> Google MacOS: https://developers.google.com/speed/public-dns/docs/using#mac_os
> Google Windows: https://developers.google.com/speed/public-dns/docs/using#windows
* DNS converts human readable host names (e.g. digitalpigeon-dp-us-west.s3.amazonaws.com) into a series of numbers that computers understand. Whenever your computer attempts to make a connection on the internet the first thing it does is contact your configured Domain Name Server and attempt to resolve its host name into an actual network address. If this step fails then, which is what's happening in this case, the connection will fail.