Incidents reported on status page for Subs https://status.subsprotocol.com/ en https://status.subsprotocol.com/ Thu, 11 Dec 2025 05:13:44 +0000 https://status.subsprotocol.com/#9025edb92fac9d0ce1928bfa1f87a39543c3477651e470765a541b3a032109c6 api.subsprotocol.com recovered https://status.subsprotocol.com/ Thu, 11 Dec 2025 04:54:05 +0000 https://status.subsprotocol.com/#6d56ab2496fd1f781c80183765545b9a5df7ff3b9132be40c0d9ae53bb41e6c9 system.subsprotocol.com/system/status recovered https://status.subsprotocol.com/ Thu, 11 Dec 2025 04:41:58 +0000 https://status.subsprotocol.com/#6d56ab2496fd1f781c80183765545b9a5df7ff3b9132be40c0d9ae53bb41e6c9 system.subsprotocol.com/system/status went down https://status.subsprotocol.com/ Thu, 11 Dec 2025 03:55:56 +0000 https://status.subsprotocol.com/#9025edb92fac9d0ce1928bfa1f87a39543c3477651e470765a541b3a032109c6 api.subsprotocol.com went down https://status.subsprotocol.com/ Thu, 11 Dec 2025 03:40:54 +0000 https://status.subsprotocol.com/#3c89585330980e37f6035fea00c15a64dd0f692efabf39841fe5df1c34f8e320 api.subsprotocol.com recovered https://status.subsprotocol.com/ Thu, 11 Dec 2025 03:28:56 +0000 https://status.subsprotocol.com/#3c89585330980e37f6035fea00c15a64dd0f692efabf39841fe5df1c34f8e320 api.subsprotocol.com went down https://status.subsprotocol.com/ Sun, 07 Dec 2025 02:02:17 +0000 https://status.subsprotocol.com/#a1929a96ace4b040abddcdbd14e23cd2a8193ca30461ffa521a054878b536522 api.subsprotocol.com recovered https://status.subsprotocol.com/ Sun, 07 Dec 2025 01:53:21 +0000 https://status.subsprotocol.com/#a1929a96ace4b040abddcdbd14e23cd2a8193ca30461ffa521a054878b536522 api.subsprotocol.com went down https://status.subsprotocol.com/ Sun, 07 Dec 2025 00:53:18 +0000 https://status.subsprotocol.com/#9d4a8f955f88fcc1a87ef01bdd778ac3ac6abdc08aabed6e1bcf143d51511594 api.subsprotocol.com recovered https://status.subsprotocol.com/ Tue, 25 Nov 2025 00:25:24 +0000 https://status.subsprotocol.com/#6785e7a58807fa7a11557edb604dbd47fb308d48eb922f73be9bd216b892ae07 system.subsprotocol.com/system/status recovered https://status.subsprotocol.com/ Tue, 25 Nov 2025 00:16:34 +0000 https://status.subsprotocol.com/#6785e7a58807fa7a11557edb604dbd47fb308d48eb922f73be9bd216b892ae07 system.subsprotocol.com/system/status went down https://status.subsprotocol.com/ Thu, 20 Nov 2025 09:28:19 +0000 https://status.subsprotocol.com/#05533a6caaa0b9a22860a865b0a1fb4fa8d51ea9fb594422fef0fd2efb845093 system.subsprotocol.com/system/status recovered https://status.subsprotocol.com/ Thu, 20 Nov 2025 09:16:10 +0000 https://status.subsprotocol.com/#05533a6caaa0b9a22860a865b0a1fb4fa8d51ea9fb594422fef0fd2efb845093 system.subsprotocol.com/system/status went down https://status.subsprotocol.com/ Fri, 14 Nov 2025 15:02:09 +0000 https://status.subsprotocol.com/#9d4a8f955f88fcc1a87ef01bdd778ac3ac6abdc08aabed6e1bcf143d51511594 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. 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.