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/ Fri, 14 Nov 2025 12:01:56 +0000 https://status.subsprotocol.com/#29c9174723998ac39cca48a4f8e78a4119b67ed312e9d07b6f92bb2f67dc9686 api.subsprotocol.com recovered https://status.subsprotocol.com/ Fri, 14 Nov 2025 04:51:54 +0000 https://status.subsprotocol.com/#29c9174723998ac39cca48a4f8e78a4119b67ed312e9d07b6f92bb2f67dc9686 api.subsprotocol.com went down https://status.subsprotocol.com/ Fri, 14 Nov 2025 01:03:56 +0000 https://status.subsprotocol.com/#4bb211cd92fe4a8a22657aa5bb21674314ae4f0af78f70b6c43ebcafda9ce76a api.subsprotocol.com recovered https://status.subsprotocol.com/ Thu, 13 Nov 2025 23:00:54 +0000 https://status.subsprotocol.com/#4bb211cd92fe4a8a22657aa5bb21674314ae4f0af78f70b6c43ebcafda9ce76a api.subsprotocol.com went down https://status.subsprotocol.com/ Wed, 12 Nov 2025 12:29:55 +0000 https://status.subsprotocol.com/#8e0bee19cafa6aa603e44074cee3cfe8a68421ad38ad32487a960edb4aa90560 system.subsprotocol.com/system/status recovered https://status.subsprotocol.com/ Wed, 12 Nov 2025 12:27:06 +0000 https://status.subsprotocol.com/#8e0bee19cafa6aa603e44074cee3cfe8a68421ad38ad32487a960edb4aa90560 system.subsprotocol.com/system/status went down https://status.subsprotocol.com/ Tue, 11 Nov 2025 21:33:45 +0000 https://status.subsprotocol.com/#d3f7a65cce84480258b1e7ff7ac6b5dfed39f4412a75d3f4b09ff8c0e229293e api.subsprotocol.com recovered https://status.subsprotocol.com/ Tue, 11 Nov 2025 21:30:42 +0000 https://status.subsprotocol.com/#d3f7a65cce84480258b1e7ff7ac6b5dfed39f4412a75d3f4b09ff8c0e229293e api.subsprotocol.com went down https://status.subsprotocol.com/ Mon, 10 Nov 2025 20:47:41 +0000 https://status.subsprotocol.com/#ba11989f6e512ae2305c6fdf50f3f8d23894c7a6a1ce65372ff0105e0cfb16ba api.subsprotocol.com recovered https://status.subsprotocol.com/ Mon, 10 Nov 2025 20:44:42 +0000 https://status.subsprotocol.com/#ba11989f6e512ae2305c6fdf50f3f8d23894c7a6a1ce65372ff0105e0cfb16ba api.subsprotocol.com went down https://status.subsprotocol.com/ Mon, 10 Nov 2025 20:38:43 +0000 https://status.subsprotocol.com/#dd21a3fc9fa49eb59a1a829c254adf55d7f5b7464b2f06ce311ad97a47dd547a api.subsprotocol.com recovered https://status.subsprotocol.com/ Mon, 10 Nov 2025 20:32:42 +0000 https://status.subsprotocol.com/#dd21a3fc9fa49eb59a1a829c254adf55d7f5b7464b2f06ce311ad97a47dd547a api.subsprotocol.com went down https://status.subsprotocol.com/ Mon, 20 Oct 2025 18:58:47 +0000 https://status.subsprotocol.com/#70815a33a594b01dd8d79aa49414dff2b6288bee4288f609c96f39bc382251f2 system.subsprotocol.com/system/status recovered https://status.subsprotocol.com/ Mon, 20 Oct 2025 18:53:52 +0000 https://status.subsprotocol.com/#45d13d9018e1c025638909b90d637da060d6d2ee874f7473909d4b2bec767aa5 api.subsprotocol.com recovered https://status.subsprotocol.com/ Mon, 20 Oct 2025 14:26:15 +0000 https://status.subsprotocol.com/#70815a33a594b01dd8d79aa49414dff2b6288bee4288f609c96f39bc382251f2 system.subsprotocol.com/system/status went down https://status.subsprotocol.com/ Mon, 20 Oct 2025 14:04:11 +0000 https://status.subsprotocol.com/#45d13d9018e1c025638909b90d637da060d6d2ee874f7473909d4b2bec767aa5 api.subsprotocol.com went down https://status.subsprotocol.com/ Thu, 16 Oct 2025 20:54:47 +0000 https://status.subsprotocol.com/#ef0738ba6af8da84a4dcd2df58fb00ef86bec7952d44454d37945f0f417d65ac system.subsprotocol.com/system/status recovered https://status.subsprotocol.com/ Thu, 16 Oct 2025 20:49:05 +0000 https://status.subsprotocol.com/#ef0738ba6af8da84a4dcd2df58fb00ef86bec7952d44454d37945f0f417d65ac system.subsprotocol.com/system/status went down https://status.subsprotocol.com/ Wed, 24 Sep 2025 17:15:05 +0000 https://status.subsprotocol.com/#ef5c2fd178541936ad144520392b7f9273c3902282e68eaa49d992be43e1802f api.subsprotocol.com recovered https://status.subsprotocol.com/ Wed, 24 Sep 2025 17:12:14 +0000 https://status.subsprotocol.com/#ef5c2fd178541936ad144520392b7f9273c3902282e68eaa49d992be43e1802f 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.