Incidents reported on status page for hapara.fail https://status.hapara.fail/ https://d1lppblt9t2x15.cloudfront.net/logos/a5e1ca1480dd15d5347aa7fa65c950b2.png https://status.hapara.fail/ en https://status.hapara.fail/incident/872653 Wed, 15 Apr 2026 23:32:07 -0000 https://status.hapara.fail/incident/872653#81c1d9113aaf477b4eb33db1ef0c3d3aad42b833142b51cfa0d79b9ef69ff207 We will be performing routine maintenance DNS 2. You may not be able to resolve queries to DNS 2 for a short period of time, but we’ll have things back up and running as soon as possible to minimize disruption to you. https://status.hapara.fail/incident/871930 Wed, 15 Apr 2026 16:02:00 -0000 https://status.hapara.fail/incident/871930#1278b5262ae452393422aea7ce931c7469637a97950dc01d399e248a989a98fd DNS 1 is facing network connectivity issues. We are currently investigating the root cause. https://status.hapara.fail/incident/871930 Wed, 15 Apr 2026 15:51:15 -0000 https://status.hapara.fail/incident/871930#87d87078121d22ae26475289807a6605988a9696dafdf047601fda971a07e20f DNS 1 went down. https://status.hapara.fail/incident/871930 Wed, 15 Apr 2026 15:19:31 -0000 https://status.hapara.fail/incident/871930#211a79dcc5d355df6ca9a268a08c88a106a2adf805b191fbde95597f87aa1a05 DNS 1 recovered. https://status.hapara.fail/incident/871930 Wed, 15 Apr 2026 15:11:04 -0000 https://status.hapara.fail/incident/871930#61a7a13c1b474b9c3dd67516e2dd6110e64e804f61ab78d389d21890ad1f5982 DNS 1 went down. https://status.hapara.fail/incident/871930 Wed, 15 Apr 2026 13:19:22 -0000 https://status.hapara.fail/incident/871930#32197810694bdf0e71a333cfe266aac59baa6242aa9d941e046caf84e8f1573f DNS 1 recovered. https://status.hapara.fail/incident/871930 Wed, 15 Apr 2026 11:20:50 -0000 https://status.hapara.fail/incident/871930#dae2eb973fd3c6086934be7908943e527cce8ab43bddce8b4ba1076c3a3c73d0 DNS 1 went down. https://status.hapara.fail/incident/871930 Wed, 15 Apr 2026 09:59:13 -0000 https://status.hapara.fail/incident/871930#e27308d5d8be933b3803b12597c67218d62476aad166e723786e1c65544710d8 DNS 1 recovered. https://status.hapara.fail/incident/871930 Wed, 15 Apr 2026 03:11:09 -0000 https://status.hapara.fail/incident/871930#0f36e87e52dd10bbe9527d532184be6034f67ec6a43e53a5072710104e5b234d DNS 1 went down. https://status.hapara.fail/incident/862132 Wed, 15 Apr 2026 01:36:00 -0000 https://status.hapara.fail/incident/862132#ce3aae3a69dcbb42eaffda47324a83b3ffd88a80dd779206c7cc8f18bc6023b3 DNS 1 has been reinstated by our hosting provider and is now usable. https://status.hapara.fail/incident/862132 Mon, 13 Apr 2026 03:13:00 -0000 https://status.hapara.fail/incident/862132#9e5a0712ed0c6dc0311692ee9e4913aca92ea36d5658b22f8b610d2d047e3140 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. https://status.hapara.fail/incident/862132 Mon, 06 Apr 2026 15:51:00 -0000 https://status.hapara.fail/incident/862132#15f3c64f4f825f9fe4fe93bb4d304a6b2dd21913e06e6260ab6f10203dfab4a6 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. https://status.hapara.fail/incident/862132 Fri, 03 Apr 2026 17:13:00 -0000 https://status.hapara.fail/incident/862132#843a146f1d8fa5d3971457fd3e5378d11eceba0e30a97d8042482202e8acbcf2 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. https://status.hapara.fail/incident/862132 Thu, 02 Apr 2026 22:35:00 -0000 https://status.hapara.fail/incident/862132#032c1d5277eb7b5865ff9e7537a6eec136066f43cd3d4134f9e212b47cbfec91 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. https://status.hapara.fail/incident/862132 Wed, 01 Apr 2026 15:53:00 -0000 https://status.hapara.fail/incident/862132#02c2a975f2368a435e9e07c063176ec1150e9cc3ea7b05735bde8671e7c6ecec 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. https://status.hapara.fail/incident/862132 Wed, 01 Apr 2026 15:08:00 -0000 https://status.hapara.fail/incident/862132#a6d2ae060c62dc37c7531a896462be2518c82385bd29dd694edfe18b3f9a66f0 Migration to new hosting provider has begun. Estimated time of restoration (ETR): 12:00 PM EDT https://status.hapara.fail/incident/862132 Wed, 01 Apr 2026 04:49:00 -0000 https://status.hapara.fail/incident/862132#149eb4199ed29cc1544972388776e8de79cc38c6400d85b088505a98cf72d13c 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. https://status.hapara.fail/incident/862132 Wed, 01 Apr 2026 04:40:00 -0000 https://status.hapara.fail/incident/862132#f7f5f7c65ba44f02b3cdb9aba2536ac31989435a6e1536c90484928041838069 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. https://status.hapara.fail/incident/862132 Wed, 01 Apr 2026 04:27:00 -0000 https://status.hapara.fail/incident/862132#11d840b9bd5563dea2ad47f4b695e5ca9a864d0bf8d534fda58bd7a36d832db7 Investigation underway. https://status.hapara.fail/incident/862132 Wed, 01 Apr 2026 04:20:52 -0000 https://status.hapara.fail/incident/862132#3f273490885b1d8798522754573d7670727519ea337487bfa0a92522efd2ad7a DNS 1 went down. https://status.hapara.fail/incident/750824 Fri, 24 Oct 2025 23:30:00 -0000 https://status.hapara.fail/incident/750824#bf3d020e1ffa7b3ea8232eeb193d570af5e2dbeae735093e7896cc32a1ecc618 Maintenance completed https://status.hapara.fail/incident/750824 Fri, 24 Oct 2025 23:00:06 -0000 https://status.hapara.fail/incident/750824#d4e3bff3e7cd91f5de71515f7242be3e02eb23b986c29f64e49f64c5ec1caa07 The hapara.fail website is undergoing significant upgrades. Expect short downtime as DNS records propagate.