Incidents reported on status page for Subs https://status.subsprotocol.com/ en 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/ Sat, 21 Feb 2026 05:53:52 +0000 https://status.subsprotocol.com/#9c7607c889ba86d99bbe41cca6340b6b968bc3bec3b50ff789af2912e0dcdc7c system.subsprotocol.com/system/status recovered https://status.subsprotocol.com/ Sat, 21 Feb 2026 05:32:55 +0000 https://status.subsprotocol.com/#9c7607c889ba86d99bbe41cca6340b6b968bc3bec3b50ff789af2912e0dcdc7c system.subsprotocol.com/system/status went down https://status.subsprotocol.com/ Fri, 20 Feb 2026 18:29:52 +0000 https://status.subsprotocol.com/#10e00e2bb2674492736f078e0781022b7c42ee7d2e51125a336c9df2e20ddb8e system.subsprotocol.com/system/status recovered https://status.subsprotocol.com/ Fri, 20 Feb 2026 18:18:20 +0000 https://status.subsprotocol.com/#10e00e2bb2674492736f078e0781022b7c42ee7d2e51125a336c9df2e20ddb8e system.subsprotocol.com/system/status went down https://status.subsprotocol.com/ Thu, 19 Feb 2026 15:11:54 +0000 https://status.subsprotocol.com/#e1f63181d0809abc5cb70e5ae847b6139ef96ad7b95f4d3c170393084d8d89d7 system.subsprotocol.com/system/status recovered https://status.subsprotocol.com/ Thu, 19 Feb 2026 15:06:23 +0000 https://status.subsprotocol.com/#e1f63181d0809abc5cb70e5ae847b6139ef96ad7b95f4d3c170393084d8d89d7 system.subsprotocol.com/system/status went down https://status.subsprotocol.com/ Thu, 19 Feb 2026 14:47:48 +0000 https://status.subsprotocol.com/#9e863c059c71d561aabea74d5f1d48519d69009644389b6bcaf5b0b2cbeb2699 system.subsprotocol.com/system/status recovered https://status.subsprotocol.com/ Thu, 19 Feb 2026 14:45:40 +0000 https://status.subsprotocol.com/#9e863c059c71d561aabea74d5f1d48519d69009644389b6bcaf5b0b2cbeb2699 system.subsprotocol.com/system/status went down https://status.subsprotocol.com/ Wed, 18 Feb 2026 09:47:54 +0000 https://status.subsprotocol.com/#7ac748b533fe161f8f81faa9940d0b6125799dee37baa5efdec6a8dd31f88480 system.subsprotocol.com/system/status recovered https://status.subsprotocol.com/ Wed, 18 Feb 2026 09:42:36 +0000 https://status.subsprotocol.com/#7ac748b533fe161f8f81faa9940d0b6125799dee37baa5efdec6a8dd31f88480 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.