Incidents reported on status page for Subs https://status.subsprotocol.com/ en https://status.subsprotocol.com/ Mon, 27 Apr 2026 05:05:56 +0000 https://status.subsprotocol.com/#0795385ddf0616e3960b0fce7aea3eca6fc7f3376d5bee36e46494afa364c865 system.subsprotocol.com/system/status went down https://status.subsprotocol.com/ Wed, 18 Mar 2026 19:17:50 +0000 https://status.subsprotocol.com/#b4458926de8636f24aa3a3926f31f434a9220528e33b9a47238bc791745ccf32 system.subsprotocol.com/system/status recovered https://status.subsprotocol.com/ Wed, 18 Mar 2026 08:20:51 +0000 https://status.subsprotocol.com/#b4458926de8636f24aa3a3926f31f434a9220528e33b9a47238bc791745ccf32 system.subsprotocol.com/system/status went down https://status.subsprotocol.com/ Wed, 18 Mar 2026 06:34:55 +0000 https://status.subsprotocol.com/#f75ba81bcb335e032d653ceda4a47dc5cd4292ae1fde797edbda5a622da7d054 system.subsprotocol.com/system/status recovered https://status.subsprotocol.com/ Sun, 15 Mar 2026 03:41:53 +0000 https://status.subsprotocol.com/#f75ba81bcb335e032d653ceda4a47dc5cd4292ae1fde797edbda5a622da7d054 system.subsprotocol.com/system/status went down https://status.subsprotocol.com/ Tue, 17 Feb 2026 16:40:45 +0000 https://status.subsprotocol.com/#d2eb34336552a8917d3cad7baa0e6c6f202ec84d54a29b9e0f735c83dea38832 api.subsprotocol.com went down https://status.subsprotocol.com/incident/447688 Sun, 20 Oct 2024 16:02:00 -0000 https://status.subsprotocol.com/incident/447688#f5a113fea29364ab45e85615c747a6b1ca6907da97d969b0a32a59b8f5e2b19b The incident was caused by a DNS lookup failure, intermittently affecting Our API and System across different regions. Despite frequent reappearances of the error, monitors eventually recovered automatically in all affected areas, and the issue was resolved without manual intervention.