DNS 1 has been reinstated by our hosting provider and is now usable.

We still have not received word from our hosting provider, who we are told operates one of the largest cloud infrastructures on the planet and yet appears to be reviewing our appeal by hand, in pencil, on paper, in a cave. DNS 2 remains fully operational. We appreciate your continued patience, which is apparently more patience than our hosting provider has bandwidth to reciprocate.

Our cloud provider's Trust & Safety team requested additional information regarding our appeal. We have submitted a detailed follow-up response outlining the nature of our workload, corrective steps taken, and planned improvements to our rate limiting and monitoring systems. We are awaiting their final decision. DNS 2 (152.42.152.171) remains fully operational in the meantime.

Our hosting provider has still not updated us on the status of our appeal. We are leaning towards a 2-4 week period for a response, rather than the initial estimate of 2 days that our hosting provider gave us. We thank you for your patience during this time.

We are still awaiting a response in our appeal to our DNS 1 hosting provider. As a reminder, DNS 2 has been provisioned and is available for use with all the privacy functionality of hapara.fail DNS.

A secondary server (DNS 2) has been provisioned at 152.42.152.171 and is fully operational, restoring service for users. DNS 1 remains offline pending our hosting provider's response to the appeal. This incident will remain open until DNS 1 is reinstated or formally decommissioned.

Migration to new hosting provider has begun. Estimated time of restoration (ETR): 12:00 PM EDT

An appeal has been submitted to our hosting provider and is currently under review. We expect a response within two business days. In parallel, we are provisioning a replacement server to restore service sooner. Next update will follow once the new server is live or the appeal is resolved.

Our DNS resolver is currently unavailable following an unexpected suspension by our hosting provider. We have identified the cause and are in the process of migrating to a new server. Service is expected to be restored within 24 hours. We will post a further update once the migration is underway.

Investigation underway.

DNS 1 went down.