Due to a DNS issue with the *.nonprofitsoapbox.com domain, pages on your site, including your administrator, may currently be experiencing a period of downtime. Our engineers are currently investigating this issue and we expect full service to be restored shortly.
This does not affect any traffic going directly to *.secure.nonprofitsoapbox.com pages nor does it affect any traffic to custom URLs. It is only affecting *.nonprofitsoapbox.com pages for some visitors.
We apologize for this inconvenience. We will update this post with additional information, as it becomes available.
Best,
Tim Forbes
VP of Products and Marketing
As a further update, one of our upstream DNS providers had technical difficulties earlier this morning that has caused issues with http://*.nonprofitsoapbox.com domains and kept them from properly loading. This issue has been resolved, but it takes about 1 hour or less, as configured in our DNS setup, for internet service providers (ISPs) to update their servers to ensure they have the right DNS information for our http://*.nonprofitsoapbox.com domains.
As noted earlier, this does not affect any traffic going directly to *.secure.nonprofitsoapbox.com pages nor does it affect any traffic to custom URLs. It is only affecting *.nonprofitsoapbox.com pages for some visitors.
Currently, we can confirm that 30 minutes ago, Google's DNS (8.8.8.8) was already properly updated for http://*.nonprofitsoapbox.com domains. Other ISPs, such as Comcast, still seem to be updating their DNS cache. We will keep you posted as we learn more.
Thank you for your patience.
Best,
Tim Forbes
VP of Products and Marketing
It appears that the DNS issue is resolved across a variety of internet service providers (ISPs) and pages using the http://*.nonprofitsoapbox.com domain are loading properly for all visitors.
If you find that http://*.nonprofitsoapbox.com pages are still not loading for your organization and you are attempting to access them from within your organization's local network, we'd recommend that you contact your IT team and ask that they flush the DNS cache on your network or your computer.
Thank you for your patience as we worked to address this issue.
Best,
Tim Forbes
VP of Products and Marketing