Incidents reported on status page for Handles https://status.handles.net/ https://d1lppblt9t2x15.cloudfront.net/logos/16304b2cbcbb4b975d2cb41fa1146ce8.png https://status.handles.net/ en https://status.handles.net/ Tue, 01 Jul 2025 02:28:54 +0000 https://status.handles.net/#550e1f539814cd20868637357ce25643373617f094746f2f4d34e03c91d5d93c Handles Club's Domains DNS recovered https://status.handles.net/ Tue, 01 Jul 2025 02:08:40 +0000 https://status.handles.net/#550e1f539814cd20868637357ce25643373617f094746f2f4d34e03c91d5d93c Handles Club's Domains DNS went down https://status.handles.net/ Thu, 26 Jun 2025 11:15:20 +0000 https://status.handles.net/#756a4d4fe4ab1ad7bb4ffc0b961c3ab73d2c5417623e719757be4ac70ec75b14 Handles Club's Domains DNS recovered https://status.handles.net/ Thu, 26 Jun 2025 10:45:48 +0000 https://status.handles.net/#756a4d4fe4ab1ad7bb4ffc0b961c3ab73d2c5417623e719757be4ac70ec75b14 Handles Club's Domains DNS went down https://status.handles.net/incident/509873 Sun, 09 Feb 2025 03:45:00 -0000 https://status.handles.net/incident/509873#dd3c0bed9b097fc01393d6177ee5069132128b5c91f71ecf26937e39da583042 ZeroSSL is back online and new Bluesky handles can be verified again. We have added a second fallback SSL certificate provider for use when ZeroSSL is offline. https://status.handles.net/incident/509873 Sun, 09 Feb 2025 03:10:00 -0000 https://status.handles.net/incident/509873#065100ef6c2486974a0c8a775aaee23e4b169fb0b548c40e02cfcf85e873b98f The issue has been identified as an [outage with our SSL certificate provider, ZeroSSL](https://status.zerossl.com/7090875/2025/02). When a new handle is created, our system issues an SSL certificate which is necessary for Bluesky to verify the handle. Due to the ZeroSSL outage, new certificates were unable to be created. https://status.handles.net/incident/509873 Sun, 09 Feb 2025 03:04:00 -0000 https://status.handles.net/incident/509873#27b664df5a547744e3dba3ae9a0eff88a52f69b02704588d859b765b93eea169 New handles are failing to verify: after creating a handle, a user will see a failed to verify error in Bluesky. https://status.handles.net/incident/509121 Fri, 07 Feb 2025 17:45:00 -0000 https://status.handles.net/incident/509121#55ca2e12b8441e10acba8634c271e63b00d7bafdca446f2d79c803b9bf4a8b9d We have identified the cause as an internal firewall intermittently misidentifying verification requests as malicious. The firewall rule has been fixed. https://status.handles.net/incident/509121 Fri, 07 Feb 2025 17:30:00 -0000 https://status.handles.net/incident/509121#0d47cdc124d187b947d44fe8002d7d727eb38634aa44761c43f3ca6e1ddfe424 Requests made by Bluesky to our system are failing to verify which causes `invalid.handle` to show up on profiles. https://status.handles.net/incident/492424 Wed, 08 Jan 2025 23:59:00 -0000 https://status.handles.net/incident/492424#972788af44eca59de6377818d29d6708fbddf59ca4c1eaf63e0bdbeba01bf06c Our primary DNS provider has helped identify our configuration issue with our .cat domains: we have rectified the issue and restored the use of our primary DNS provider for the .cat domains. https://status.handles.net/incident/492424 Wed, 08 Jan 2025 12:00:00 -0000 https://status.handles.net/incident/492424#a3e9e1b65804ddf9a26d122dfdba1d648955a52b93051f1db85a0927bd7026bc The domains are now resolving correctly. We believe the issue is due to `.cat` domains being unsupported by our primary DNS provider. We will continue to use a secondary DNS provider for these domains. We have added monitoring of all domain's DNS to ensure we capture any further issues immediately. https://status.handles.net/incident/492424 Wed, 08 Jan 2025 06:30:00 -0000 https://status.handles.net/incident/492424#6b1e1c2f055ca26ce78b1f3a04fc78c1877c6ee22edbbdf526198f8786bd0c7b We have switched to an alternative DNS provider for the .cat domains (`and.cat`, `posts.cat` and `follows.cat`). We expect the domains to start resolving again soon. https://status.handles.net/incident/492424 Tue, 07 Jan 2025 12:00:00 -0000 https://status.handles.net/incident/492424#1a255db038a438698d8251cc2e30ef69e6974efdeda7037b44168644a192a398 Due to an issue with our DNS provider, 3 domains (`and.cat`, `follows.cat` and `posts.cat`) are not resolving correctly.