Incidents reported on status page for SHCKANAGAWA https://status.shc.kanagawa.jp/ en https://status.shc.kanagawa.jp/incident/797145 Thu, 01 Jan 2026 22:23:52 -0000 https://status.shc.kanagawa.jp/incident/797145#75556ac3a86d4700711c94607f83fef8768d4987ba56eb90fab418911a34867f Mastodon Daily Database Backup recovered. https://status.shc.kanagawa.jp/incident/797145 Thu, 01 Jan 2026 19:49:10 -0000 https://status.shc.kanagawa.jp/incident/797145#f8c10ba1a7018b342920eab41750b611e2d368f52f482a0acfb44b3e10634ede Mastodon Daily Database Backup went down. https://status.shc.kanagawa.jp/incident/774367 Wed, 26 Nov 2025 04:59:44 -0000 https://status.shc.kanagawa.jp/incident/774367#e46b0b37267788668b8559cc2a8eece2745c60b4974203836fede3299e923873 NextCloud Maintenance recovered. https://status.shc.kanagawa.jp/incident/774367 Wed, 26 Nov 2025 04:56:51 -0000 https://status.shc.kanagawa.jp/incident/774367#482e637d5a992ce1bcd2f03156b1aefc926abfac1f76a54dbde3df24b67a7c17 NextCloud Maintenance went down. https://status.shc.kanagawa.jp/incident/747144 Mon, 20 Oct 2025 10:10:48 -0000 https://status.shc.kanagawa.jp/incident/747144#2f3f3578c252d5e3542512636e78e2782cb793daea28758446ea3a75b4041c6c demo.shc.kanagawa.jp Initialize recovered. https://status.shc.kanagawa.jp/incident/747144 Mon, 20 Oct 2025 09:46:01 -0000 https://status.shc.kanagawa.jp/incident/747144#9b8fc036757ec7334e2c2a03739751d6d6b76a920b7bf91287db5773b201e474 demo.shc.kanagawa.jp Initialize went down. https://status.shc.kanagawa.jp/incident/731712 Thu, 25 Sep 2025 01:13:52 -0000 https://status.shc.kanagawa.jp/incident/731712#7f3ee6ba22bf58bc54cbe42fae75b7439d8fe8d9794c5a3d3d34d40469950556 demo.shc.kanagawa.jp Initialize recovered. https://status.shc.kanagawa.jp/incident/731712 Thu, 25 Sep 2025 00:31:15 -0000 https://status.shc.kanagawa.jp/incident/731712#03f2252a67ddfe99dbcd3210964d10c7b70261aea8b5b55e0bf2be81809173ac demo.shc.kanagawa.jp Initialize went down. https://status.shc.kanagawa.jp/incident/710514 Fri, 22 Aug 2025 12:14:28 -0000 https://status.shc.kanagawa.jp/incident/710514#767f791a9d772f314f18d94bfd5078521463b2eab72dc600aa5d7faee91507b6 demo.shc.kanagawa.jp Initialize recovered. https://status.shc.kanagawa.jp/incident/710514 Fri, 22 Aug 2025 10:28:22 -0000 https://status.shc.kanagawa.jp/incident/710514#39ca6859e17b87b48e558e64921d765443c969008f27cf95edd276cf9f1651bb demo.shc.kanagawa.jp Initialize went down. https://status.shc.kanagawa.jp/incident/710041 Thu, 21 Aug 2025 21:40:21 -0000 https://status.shc.kanagawa.jp/incident/710041#5cf74115bdc27d6d8ff56d02a0a3640daf8ca797849f58e0261c63de0159694e demo.shc.kanagawa.jp Initialize recovered. https://status.shc.kanagawa.jp/incident/710041 Thu, 21 Aug 2025 17:27:04 -0000 https://status.shc.kanagawa.jp/incident/710041#143355e91bb7b9150c93bda7015b22855f5958f18c20a451c9488fba245b3eca demo.shc.kanagawa.jp Initialize went down. https://status.shc.kanagawa.jp/incident/709365 Wed, 20 Aug 2025 20:07:45 -0000 https://status.shc.kanagawa.jp/incident/709365#5ddfb71ad1a60104d92ebb69596d39b8f622d7e0dc5e8562fab72d58e8718227 demo.shc.kanagawa.jp Initialize recovered. https://status.shc.kanagawa.jp/incident/709365 Wed, 20 Aug 2025 18:27:06 -0000 https://status.shc.kanagawa.jp/incident/709365#62dc75425a24494ec68f5d27275cc5844c75c8b30a5c270be13b2c79cef6ddcf demo.shc.kanagawa.jp Initialize went down. https://status.shc.kanagawa.jp/incident/625668 Fri, 25 Jul 2025 12:41:44 -0000 https://status.shc.kanagawa.jp/incident/625668#2151940c10c154c80eba43d1a4aa292c3c19aad68a03523eb0f1939a35205501 demo.shc.kanagawa.jp Initialize recovered. https://status.shc.kanagawa.jp/incident/625668 Fri, 25 Jul 2025 12:27:15 -0000 https://status.shc.kanagawa.jp/incident/625668#5e63cac385e07658254544d1fec293d9aa273433c11195c9d7caabaf38f238a8 demo.shc.kanagawa.jp Initialize went down. https://status.shc.kanagawa.jp/incident/622923 Sun, 20 Jul 2025 20:19:09 -0000 https://status.shc.kanagawa.jp/incident/622923#79056f7f8767d786a59ce5e0fc2d0d6d629cb6fef9a9869451346bf761a50535 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/622923 Sun, 20 Jul 2025 20:17:58 -0000 https://status.shc.kanagawa.jp/incident/622923#14eab9db99af709aca860cba6defc8fcb37da88194bf5b95c0426a53b823715d Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/621279 Thu, 17 Jul 2025 08:09:41 -0000 https://status.shc.kanagawa.jp/incident/621279#466be1129170bcd48e312a811455b60025b20dadfd5ec807a3b7485b054c1b17 Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/621279 Thu, 17 Jul 2025 08:08:33 -0000 https://status.shc.kanagawa.jp/incident/621279#50f1af57723fe2e4c21ecc2a446d048f2f81ac1d6ca351649bb3bc67287ee375 Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/619579 Mon, 14 Jul 2025 22:25:13 -0000 https://status.shc.kanagawa.jp/incident/619579#f7483808cebd20cfc1f3a7866c70517df655b34032343546c38107ff6180d08f NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/619579 Mon, 14 Jul 2025 22:24:04 -0000 https://status.shc.kanagawa.jp/incident/619579#c505200ba984bd7f286495300a24f81c7d3e8ae9520808cde249e674ee4f6287 Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/619579 Mon, 14 Jul 2025 22:04:00 -0000 https://status.shc.kanagawa.jp/incident/619579#4cbdd897de574bdd7272ea270e68f8b07871efc833d55252e4cd5fa3123d16da NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/619579 Mon, 14 Jul 2025 22:02:36 -0000 https://status.shc.kanagawa.jp/incident/619579#b3d4a2fd1e2780f4f9f22742593fa9dabc943950258253a0e78036ee286d3cca Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/616961 Wed, 09 Jul 2025 20:16:42 -0000 https://status.shc.kanagawa.jp/incident/616961#22d2e2fcf788b29bcdd1ef90cb58d2207de0d04dc5c40b098945d1dc5ae167ca Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/616961 Wed, 09 Jul 2025 20:15:09 -0000 https://status.shc.kanagawa.jp/incident/616961#34ea4dfd08eacef9137ec7707079394bd4cd7cf40c5edb5ea9fb48990cf6e751 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/612608 Tue, 01 Jul 2025 18:30:09 -0000 https://status.shc.kanagawa.jp/incident/612608#7cdb624779430cace8ee80765976e0ff569510b5feb7f502208ef45819ab50ca Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/612608 Tue, 01 Jul 2025 18:26:10 -0000 https://status.shc.kanagawa.jp/incident/612608#7210e725c2e426c1d3019be4537c963e3e667a90e2170db727c1f7aea7390ee5 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/608475 Tue, 24 Jun 2025 20:12:20 -0000 https://status.shc.kanagawa.jp/incident/608475#e3c3a56743f995e9071a9eb2291f8f851632ff03b20fcef88f7ce72c9149211c Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/608475 Tue, 24 Jun 2025 20:11:15 -0000 https://status.shc.kanagawa.jp/incident/608475#71939affb7e795f1cca909d21040fddc54943547161ac3cc90d0eb75342e0fd1 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/606894 Sat, 21 Jun 2025 18:16:59 -0000 https://status.shc.kanagawa.jp/incident/606894#c8a96a49bae51f0a82ffe4c0ee677789de06b244575ce52cee646c47f911e60d NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/606894 Sat, 21 Jun 2025 18:15:28 -0000 https://status.shc.kanagawa.jp/incident/606894#cd3d5620445d78d5e62b4bdb25924770430656c776cd894fc0ef30e12ba00959 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/603513 Sun, 15 Jun 2025 20:10:03 -0000 https://status.shc.kanagawa.jp/incident/603513#9ae1efbb7fad0d20c444a813a024de8f5748eda52b5aa3a8ad3549ff56491963 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/603513 Sun, 15 Jun 2025 20:08:55 -0000 https://status.shc.kanagawa.jp/incident/603513#a235c250eb32370829827326417886b974184e3655cadcfa8e66e0a1c904077b Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/602044 Thu, 12 Jun 2025 20:07:58 -0000 https://status.shc.kanagawa.jp/incident/602044#c014d8eacbb470a4b9e034f6656be4df59eda2624a56e09bd3f809952d4b3ec5 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/602044 Thu, 12 Jun 2025 20:07:32 -0000 https://status.shc.kanagawa.jp/incident/602044#60fcbb9fea386448a05476355804aee76434dd833e5bb49cdbbfab6c42ba3256 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/600630 Wed, 11 Jun 2025 04:53:03 -0000 https://status.shc.kanagawa.jp/incident/600630#106b1b72a9323a8990a50818df97d3a190f3654334cb169947a904bbecf7d2fb NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/600630 Wed, 11 Jun 2025 04:48:50 -0000 https://status.shc.kanagawa.jp/incident/600630#9ee819b713fec5bc5f69d8bf40f57e7d187a07c5c95926ff27b4b165b291d93f NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/598491 Sat, 07 Jun 2025 04:15:38 -0000 https://status.shc.kanagawa.jp/incident/598491#4b4889c0ad2116744e458ceb4c87df9f63e5f45f65959d534d16dca5ce5843e7 Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/598491 Sat, 07 Jun 2025 04:15:26 -0000 https://status.shc.kanagawa.jp/incident/598491#1092397256d24386060cf1a340201f4924ca441e45f3c5282191652f5cbcf442 Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/596891 Wed, 04 Jun 2025 11:47:30 -0000 https://status.shc.kanagawa.jp/incident/596891#9a86ff892462cb5395d78d9fd4da684369a6520a2635250b5da7e17bb9d0e51f Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/596891 Wed, 04 Jun 2025 11:46:35 -0000 https://status.shc.kanagawa.jp/incident/596891#64de86d6ee146bc1a25040f5ff7a0224be8b7ebe8334f9f79a303d7b4a5f00d9 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/595131 Sun, 01 Jun 2025 18:25:43 -0000 https://status.shc.kanagawa.jp/incident/595131#07b3c8d9a0342df83533d237cfbbb022cfebc031e2fc7e1ee2826be18a6a2984 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/595131 Sun, 01 Jun 2025 18:18:45 -0000 https://status.shc.kanagawa.jp/incident/595131#b2b8ee44fbe51b7de8ed7f9c0e3ab46d337726bd17e94452c46432acebb42058 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/581525 Tue, 27 May 2025 10:51:00 -0000 https://status.shc.kanagawa.jp/incident/581525#7242686aa5655deb973d55293e834476cdbe5519e9dc232e3565bd5cfe112f04 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/581525 Tue, 27 May 2025 10:50:00 -0000 https://status.shc.kanagawa.jp/incident/581525#dd5af4e2059e30d8eb5e9a7ad30ecd1ee62e1fdb4f46328d4acf982bd3079d89 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/579921 Mon, 26 May 2025 10:49:49 -0000 https://status.shc.kanagawa.jp/incident/579921#80f75bdf0fde895a8f7a4494d0d0dcebe5368469c07bfd8a7f138d643090a02b Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/579921 Mon, 26 May 2025 10:15:23 -0000 https://status.shc.kanagawa.jp/incident/579921#c5e503bb0e68ff146dcb778fb614d8d8cadf7c2dd526833c6c49dba900e7841b Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/579921 Mon, 26 May 2025 09:46:28 -0000 https://status.shc.kanagawa.jp/incident/579921#49f7c1787b468eb5896202ac7ef7c2346d97b0602b1104c48280aae178f1c745 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/579921 Mon, 26 May 2025 09:36:26 -0000 https://status.shc.kanagawa.jp/incident/579921#ba054c7340fb472d56e481580f9d882977522c33c898f9f37b83bbe89c1363eb Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/579921 Mon, 26 May 2025 09:22:22 -0000 https://status.shc.kanagawa.jp/incident/579921#07b821a5d18816e3f07cc19b9ca1957eb73fd0d7ed7476143c40bdce9cdd34d8 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/579921 Mon, 26 May 2025 09:12:29 -0000 https://status.shc.kanagawa.jp/incident/579921#39fcdecd64544d6f80a144accfcace5cbce6c0bc3d24a8250daecad1388dc174 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/579921 Mon, 26 May 2025 09:04:23 -0000 https://status.shc.kanagawa.jp/incident/579921#0aee75dc77470871dfdea3d09d89ac1e1a05fd11cc23acdc7cac196cfa371a50 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/579921 Mon, 26 May 2025 08:57:22 -0000 https://status.shc.kanagawa.jp/incident/579921#871b820ffef4dff7e597355f3222b386f1d04acc4cf61f5bd950fab576344313 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/579921 Mon, 26 May 2025 08:13:27 -0000 https://status.shc.kanagawa.jp/incident/579921#075033de160b687255d707b9ae362f45275f4f074b4be06369ee635771d2459e Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/579921 Mon, 26 May 2025 07:33:22 -0000 https://status.shc.kanagawa.jp/incident/579921#b55eeb292f4eef0e7c951f2299cb0e891b9fb4233b44ca0409b246853a9d2cfa Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/579921 Mon, 26 May 2025 04:10:18 -0000 https://status.shc.kanagawa.jp/incident/579921#c6b9ff7680b18386d47d20eb5a7e24ece17835b3a6996215e4d6ad6cba9e0ed8 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/579921 Mon, 26 May 2025 04:06:24 -0000 https://status.shc.kanagawa.jp/incident/579921#f7a127dbc40b3c2e79f3596621d94c1c667f819bd4c22309c28448553ef7ef1b Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/579156 Sun, 25 May 2025 22:22:19 -0000 https://status.shc.kanagawa.jp/incident/579156#fac2b29717993d798f5e17fedbb9cc61733d46bd02e821ca3140a0a515990371 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/579156 Sun, 25 May 2025 22:21:26 -0000 https://status.shc.kanagawa.jp/incident/579156#6a60f5a29efaf04c3109e2045acc1c3b05681531e139ac28a481ffbfeabc24c3 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/579156 Sun, 25 May 2025 22:07:16 -0000 https://status.shc.kanagawa.jp/incident/579156#aea74d515ec611bcb153f557f827c9e634c91683bd1bab3f51e94389f5bfbc1f Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/579156 Sun, 25 May 2025 22:06:24 -0000 https://status.shc.kanagawa.jp/incident/579156#70d5a20e0f963e5557c0da187b56e8dafd33cf86b66b6f0720bc729159833ab0 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/579156 Sun, 25 May 2025 14:40:15 -0000 https://status.shc.kanagawa.jp/incident/579156#d572578392e2ce7a999817a5c76c50bf2044a91ad9cb77caa132ea74ffb4466b Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/579156 Sun, 25 May 2025 14:15:26 -0000 https://status.shc.kanagawa.jp/incident/579156#8c557dbccccb1a4c96dcf98744b4979bae01203ff2e1c99dcdebbfc9168f895c Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/579156 Sun, 25 May 2025 13:04:15 -0000 https://status.shc.kanagawa.jp/incident/579156#2c942bf1891757358038b72fbceff3d9d881928b1c75bd8e9e24e78f4ecf8fcc Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/579156 Sun, 25 May 2025 13:00:20 -0000 https://status.shc.kanagawa.jp/incident/579156#f8795558717a4890124a9eb16428c8d274deefd6c90079160ce967e33764ff25 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/579156 Sun, 25 May 2025 12:46:22 -0000 https://status.shc.kanagawa.jp/incident/579156#e9aaccb52fbcc9bb75c0070ea058276dc02b627de8c69c8b74c86567fd4239f2 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/579156 Sun, 25 May 2025 12:12:28 -0000 https://status.shc.kanagawa.jp/incident/579156#59325aac48eac0bdd751c73e1dc320f3227a6f691359c51f207aeb4c32d7d043 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/571219 Mon, 19 May 2025 10:49:03 -0000 https://status.shc.kanagawa.jp/incident/571219#78b93b4efadf1bd1c7691ee0fd2cc182245897fcdfbc35ce62d2836722834447 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/571219 Mon, 19 May 2025 10:47:54 -0000 https://status.shc.kanagawa.jp/incident/571219#9937f540acb137e366de28760a57de84fe6ed064329aec546aab662dc43b6d2e Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/560085 Sun, 11 May 2025 10:46:57 -0000 https://status.shc.kanagawa.jp/incident/560085#e64bc96f0e42cab64365c7f4660e42b7884b73ac7e7374b8a9f208a360cbc0cc Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/560085 Sun, 11 May 2025 10:45:56 -0000 https://status.shc.kanagawa.jp/incident/560085#402754938a65e250f6784009f0f641973286f069f11b6bb4419dcab08a98e8d8 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/558021 Wed, 07 May 2025 10:45:48 -0000 https://status.shc.kanagawa.jp/incident/558021#a8ad5a19ada05b6e46a89985d28323b069674b8448dec21e9ffd4bbe001cf95a Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/558021 Wed, 07 May 2025 10:44:42 -0000 https://status.shc.kanagawa.jp/incident/558021#e8ed48eaecec7a3d96f5c6fc552d5d7342a6d75eb8d81db20ec13595cf89d516 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/557141 Tue, 06 May 2025 03:07:03 -0000 https://status.shc.kanagawa.jp/incident/557141#fa8b39065d5f394401284e915a84a508489cdf3ba6f359d1a43ae196f86bf0c2 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/557141 Tue, 06 May 2025 03:05:59 -0000 https://status.shc.kanagawa.jp/incident/557141#dd0a2a722d6cc5f6215e2c266020b7c38be258921c18bd2b100c1a70bf0313d7 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/555586 Fri, 02 May 2025 18:44:09 -0000 https://status.shc.kanagawa.jp/incident/555586#b6c5679cb6dcb01958df636c72bc78f05a4b878aad90c50dd79cda9d44a117e0 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/555586 Fri, 02 May 2025 18:36:59 -0000 https://status.shc.kanagawa.jp/incident/555586#93077fcf0baafc26c534bf53ad90227c22150d7cf51a88d8cf077fccbadffa92 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/555068 Thu, 01 May 2025 21:57:30 -0000 https://status.shc.kanagawa.jp/incident/555068#5aadfc90373b28e7d4fdc4519f1c9608a6c2a191d13d4a4b4a55d22251b4f51d demo.shc.kanagawa.jp Initialize recovered. https://status.shc.kanagawa.jp/incident/555068 Thu, 01 May 2025 21:46:37 -0000 https://status.shc.kanagawa.jp/incident/555068#fc1896d64a8265861992aa081bab9f4e78e00b55ca4f014a2b276b09a0fc683e NextCloud (cloud.shc.kanagawa.jp) and ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/555068 Thu, 01 May 2025 21:46:37 -0000 https://status.shc.kanagawa.jp/incident/555068#fc1896d64a8265861992aa081bab9f4e78e00b55ca4f014a2b276b09a0fc683e NextCloud (cloud.shc.kanagawa.jp) and ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/555068 Thu, 01 May 2025 21:46:13 -0000 https://status.shc.kanagawa.jp/incident/555068#8fb65abfea7ab5e87871f672853d452d50d5e8bdef93bc78ffcfd9666ec24d4d Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/555068 Thu, 01 May 2025 21:45:33 -0000 https://status.shc.kanagawa.jp/incident/555068#624ae8ad393f52ce41588ba4da7a2654675d642af3152d37e5779701e18cc9da Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/555068 Thu, 01 May 2025 21:45:33 -0000 https://status.shc.kanagawa.jp/incident/555068#624ae8ad393f52ce41588ba4da7a2654675d642af3152d37e5779701e18cc9da Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/555068 Thu, 01 May 2025 20:27:02 -0000 https://status.shc.kanagawa.jp/incident/555068#593325fa6353bf1a1c261b761277e345e0dfbee05acbd9caaf74bc213f7121d8 demo.shc.kanagawa.jp Initialize went down. https://status.shc.kanagawa.jp/incident/555068 Thu, 01 May 2025 18:12:38 -0000 https://status.shc.kanagawa.jp/incident/555068#295898166c0758c36af5cecc88c9781785d89831306d97f7abbed9f510d6ea34 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/555068 Thu, 01 May 2025 18:11:55 -0000 https://status.shc.kanagawa.jp/incident/555068#4cc26a6b7d820cfced78338c201c501ae7b6137676e509e9e8220ae89be6e8d7 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/555068 Thu, 01 May 2025 18:11:34 -0000 https://status.shc.kanagawa.jp/incident/555068#29a20211075fb4f48bfce5d8d374ed7709f6aed7885bb74a662d14dea7c827ec Mastodon(mt.shc.kanagawa.jp) and ownCloud (share.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/555068 Thu, 01 May 2025 18:11:34 -0000 https://status.shc.kanagawa.jp/incident/555068#29a20211075fb4f48bfce5d8d374ed7709f6aed7885bb74a662d14dea7c827ec Mastodon(mt.shc.kanagawa.jp) and ownCloud (share.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/555068 Thu, 01 May 2025 18:10:25 -0000 https://status.shc.kanagawa.jp/incident/555068#fa4ad68a04fa56f48b3093ffeb30b9250fd5d9ff828cc71b7d19e86526f42763 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/551659 Fri, 25 Apr 2025 10:42:40 -0000 https://status.shc.kanagawa.jp/incident/551659#38c2c546f30d59345140fe4bdf37e5cf6ef5ad05d895c6ecfa2ea0e8bfb5666d Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/551659 Fri, 25 Apr 2025 10:41:20 -0000 https://status.shc.kanagawa.jp/incident/551659#15dde10dfeab3f208a08b3239574bf16574ef167a5088e0ea5a38b795f19a7dc Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/544524 Sun, 13 Apr 2025 10:39:18 -0000 https://status.shc.kanagawa.jp/incident/544524#a611118c352b28d55d4cb5b2254bbf4c83c29032a5c5d78a3eec2d4841b28b1b Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/544524 Sun, 13 Apr 2025 10:38:19 -0000 https://status.shc.kanagawa.jp/incident/544524#46280d114609cbbbcabcce3860b7f0e81c61fb620681774d5bdf0031276c177a Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/541834 Tue, 08 Apr 2025 10:37:54 -0000 https://status.shc.kanagawa.jp/incident/541834#fe2a1c01d93d944ae993bcf9ba632c008d189e597534709c66bba6887eb18b9e Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/541834 Tue, 08 Apr 2025 10:36:55 -0000 https://status.shc.kanagawa.jp/incident/541834#8053a810682bfd2706a189911e1deaea499282f038ab1ca45f30367f06244315 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/541164 Mon, 07 Apr 2025 10:37:38 -0000 https://status.shc.kanagawa.jp/incident/541164#d1e9ddd8414a38103c581cd55ff9bf2545e6903a935eabbf2ce2b198c0270e74 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/541164 Mon, 07 Apr 2025 10:36:35 -0000 https://status.shc.kanagawa.jp/incident/541164#a7ec934b9311f11593c90a30dfdb8d36fc90e844cd340a16ada3d110e2c8cf92 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/540734 Sun, 06 Apr 2025 11:31:23 -0000 https://status.shc.kanagawa.jp/incident/540734#2c7f18bff3614193bea6f9158b7f44957e7ba2b08a7d2b182322164ac99ef13c Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/540734 Sun, 06 Apr 2025 11:30:26 -0000 https://status.shc.kanagawa.jp/incident/540734#8633829ecf9a3f0cfbd48fafdac8b501f30f56e2e3a07b8fbc9e716554da1fcd Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/539906 Fri, 04 Apr 2025 12:25:02 -0000 https://status.shc.kanagawa.jp/incident/539906#c8e0dee944282198466bf5f210c467aa01c80fba4576eee0997ebf6a30e2e644 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/539906 Fri, 04 Apr 2025 12:23:56 -0000 https://status.shc.kanagawa.jp/incident/539906#253c8683aaea85465cffaefc41cedae98633772d8d12b91af6ecd184fbe10fb8 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/539268 Thu, 03 Apr 2025 10:35:31 -0000 https://status.shc.kanagawa.jp/incident/539268#cfc570961db7ade95d08a3d69f37e2b41631a6fcf830595ee328b61ed32f89de Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/539268 Thu, 03 Apr 2025 10:34:28 -0000 https://status.shc.kanagawa.jp/incident/539268#75d3372b2ee4e6c820fb39169b8ccb0ffc433f8c094501cf81e2737345932c37 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/538881 Wed, 02 Apr 2025 19:19:30 -0000 https://status.shc.kanagawa.jp/incident/538881#6945d3e8bcc9406bfd83fe8ae9482eb3ffc0c8d2723079cd02462c636f7e1771 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/538881 Wed, 02 Apr 2025 19:15:19 -0000 https://status.shc.kanagawa.jp/incident/538881#47f71a1c4401a51921d113c0a6cc4eb0f1dbe5ae34a5ea1c44220946848010ec Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/537116 Mon, 31 Mar 2025 09:19:33 -0000 https://status.shc.kanagawa.jp/incident/537116#67c8878fc15b86b635c244ffa1f7b95a9cb672093c5352f530ab4fb66093774c Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/537116 Mon, 31 Mar 2025 09:18:24 -0000 https://status.shc.kanagawa.jp/incident/537116#5b33c56b7e365be39fda110fef9aea3b7c9af3ca8e57e2e09ed25dac9fa23215 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/537116 Mon, 31 Mar 2025 03:54:45 -0000 https://status.shc.kanagawa.jp/incident/537116#ab86bea33d63cca0957992f0d53be3321f1db6a890c795861b3cad13a04daff2 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/537116 Mon, 31 Mar 2025 03:53:48 -0000 https://status.shc.kanagawa.jp/incident/537116#2a25797836f455a12df70c772c52b6d080ea1f1d5d71060540332005e5177bc6 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/535370 Thu, 27 Mar 2025 09:21:20 -0000 https://status.shc.kanagawa.jp/incident/535370#400cad2d4afca7cc66b827fbd2a35939796b132a0d295f5bdbffce51049f5071 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/535370 Thu, 27 Mar 2025 09:17:24 -0000 https://status.shc.kanagawa.jp/incident/535370#ca2b11aadfbe0e252efa76c05102e1ad9a810fddece2610dc52435dc9a57d480 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/530861 Wed, 19 Mar 2025 15:35:12 -0000 https://status.shc.kanagawa.jp/incident/530861#637fcc9ece3f85a77a272b8abcc37253523b9cb57330fef9e76589dc64f45dc9 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/530861 Wed, 19 Mar 2025 15:28:18 -0000 https://status.shc.kanagawa.jp/incident/530861#0367e7b0612146887cb7da229f5789be2f832deb10ccd1d9b4eee1b5312e29da Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/530861 Wed, 19 Mar 2025 15:20:19 -0000 https://status.shc.kanagawa.jp/incident/530861#fb45797e9bdadc126fc5a29bcd52bb57dedd9d74e8e6bc9dbcf7e629ad0acd57 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/530861 Wed, 19 Mar 2025 15:19:58 -0000 https://status.shc.kanagawa.jp/incident/530861#d5e5ea8e6a92db22469582c71ee2f674523f19c36e87e27fe3c68fbd7f02ad99 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/527799 Thu, 13 Mar 2025 18:36:41 -0000 https://status.shc.kanagawa.jp/incident/527799#d3cf437708725ef31329bb35ba98b3057cc99bb7a5880cf7c83d14e641367745 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/527799 Thu, 13 Mar 2025 18:36:40 -0000 https://status.shc.kanagawa.jp/incident/527799#25d92b656184326a9835c05514c7ba2ee828bc16e1c647b2705509e36f95ec4a Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/526497 Tue, 11 Mar 2025 14:50:49 -0000 https://status.shc.kanagawa.jp/incident/526497#3cce036dfdd1c6f19867e0e5b37f580101891bd05ae92b861629198ab235060a Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/526497 Tue, 11 Mar 2025 14:49:31 -0000 https://status.shc.kanagawa.jp/incident/526497#98905798e90e84ccdf2ebd9e6cf791943b80e527d9f01341fafc8cd4fa705e09 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/525227 Sun, 09 Mar 2025 09:13:33 -0000 https://status.shc.kanagawa.jp/incident/525227#ef8825e93aaf8ba6210f236273496faf663e94bc56b266a7983ecc764aafdb21 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/525227 Sun, 09 Mar 2025 09:12:44 -0000 https://status.shc.kanagawa.jp/incident/525227#0fadb46edab4c706f7c9147f52b4e1bde2794226f044e7cbc4ddab9b5d7326e4 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/524749 Sat, 08 Mar 2025 09:13:35 -0000 https://status.shc.kanagawa.jp/incident/524749#68e12ebddae5c20bc0a4160f0f421824bba2442126d9cd927f31094cdb794fca Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/524749 Sat, 08 Mar 2025 09:12:15 -0000 https://status.shc.kanagawa.jp/incident/524749#27bee95fecb1c0fa84cc8bbe750f195b27be392111cfbda278993c443a219a63 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/522081 Mon, 03 Mar 2025 19:43:05 -0000 https://status.shc.kanagawa.jp/incident/522081#9020338480a0324bf08596ce9e87a2c9983bd1b5d71f816b945a5660360323ef Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/522081 Mon, 03 Mar 2025 19:36:05 -0000 https://status.shc.kanagawa.jp/incident/522081#aa22a574f00a688dd4d2e93e5e3c26eae7ccf92ab26ccab13ace1ed8aa164efb Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/520954 Sat, 01 Mar 2025 09:11:23 -0000 https://status.shc.kanagawa.jp/incident/520954#a5d16b7896d16b7fd0b2d6e5682fa6bd5b43744c16ed757ed1bcd49f5a384745 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/520954 Sat, 01 Mar 2025 09:10:17 -0000 https://status.shc.kanagawa.jp/incident/520954#ae57ce21bbce9d764755f711fd266ffa48a8844e1cadfb11ef6df18cc43e81e8 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/519034 Wed, 26 Feb 2025 09:17:23 -0000 https://status.shc.kanagawa.jp/incident/519034#020b8071915de9bb661f8c5554daec47ceed8832fa5c6f0e7ad3411de2372875 Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/519034 Wed, 26 Feb 2025 09:15:00 -0000 https://status.shc.kanagawa.jp/incident/519034#5867946091b4361a940cfc98c03a6fc2b9848f01d602a2311b41eff8b88d4b00 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/519034 Wed, 26 Feb 2025 09:14:21 -0000 https://status.shc.kanagawa.jp/incident/519034#8490b010826697f10be23267752c95480fcd1949b185eff50d14c5d3c43be927 Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/519034 Wed, 26 Feb 2025 09:12:29 -0000 https://status.shc.kanagawa.jp/incident/519034#08e1ff7440006b4f223a501eb985cc433997338150be176f32b0a80a10f7d9f4 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/519034 Wed, 26 Feb 2025 09:11:38 -0000 https://status.shc.kanagawa.jp/incident/519034#d8d03419f4b3784b741f295b30155790ce16a28748c02f9f7e48d98684615c2c Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/519034 Wed, 26 Feb 2025 09:04:00 -0000 https://status.shc.kanagawa.jp/incident/519034#ce8dfeeec59f9e8615f212e451121abc410336c7ce7dd09438331116ac720e90 Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/519034 Wed, 26 Feb 2025 09:02:23 -0000 https://status.shc.kanagawa.jp/incident/519034#0c8d96acf67b47987b10d0c2000620c97282f2e5c0ba7a6b3a803f2500c0d17b Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/519034 Wed, 26 Feb 2025 09:01:13 -0000 https://status.shc.kanagawa.jp/incident/519034#6670a528367c953872571451605be58db5648d5654853cf1ccea1e2e41c4c7cd Pleroma(pr.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/519034 Wed, 26 Feb 2025 09:01:13 -0000 https://status.shc.kanagawa.jp/incident/519034#6670a528367c953872571451605be58db5648d5654853cf1ccea1e2e41c4c7cd Pleroma(pr.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/519034 Wed, 26 Feb 2025 09:00:42 -0000 https://status.shc.kanagawa.jp/incident/519034#d518ec4b4b9b4c6559f4d5229fe9f82d54f5942b3a7c19e121f4f4794be5f989 Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/519034 Wed, 26 Feb 2025 07:39:23 -0000 https://status.shc.kanagawa.jp/incident/519034#c9be77639e853b4899fb73c8a1f626554dcd918afd56a96b61bcf1bfb8440e44 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/519034 Wed, 26 Feb 2025 07:35:11 -0000 https://status.shc.kanagawa.jp/incident/519034#9204965de92ad4d3c33f11d885b39443ee42df5aead9fa5e367c8318ef6f6021 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/519034 Wed, 26 Feb 2025 07:21:53 -0000 https://status.shc.kanagawa.jp/incident/519034#ba3fa2d18d9af6864f5607cdbf6b6b1dbd1fa483a8421ca0503c597ced4c3d64 Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/519034 Wed, 26 Feb 2025 07:18:48 -0000 https://status.shc.kanagawa.jp/incident/519034#e848e0a1783c48d2e58c7973aafc47e7b47ce3a77cdeded3eab6f693011868e6 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/519034 Wed, 26 Feb 2025 07:18:23 -0000 https://status.shc.kanagawa.jp/incident/519034#54fbf11ecbdd2ba9f7ce942e1bf8f04715e99c2710f542b6bcd6601bc13d3ebc Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/519034 Wed, 26 Feb 2025 07:18:04 -0000 https://status.shc.kanagawa.jp/incident/519034#97bf8a8d9970c8a0a6a72b697d65b207a67072e7297fd5ba8186fbfaa7eba1bf Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/519034 Wed, 26 Feb 2025 07:17:54 -0000 https://status.shc.kanagawa.jp/incident/519034#f303121a43ac22aef9fbbd77f848bc73fc4c2d5344eb6393a6c6ca72253ca63e Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/519034 Wed, 26 Feb 2025 07:17:54 -0000 https://status.shc.kanagawa.jp/incident/519034#f303121a43ac22aef9fbbd77f848bc73fc4c2d5344eb6393a6c6ca72253ca63e Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/519034 Wed, 26 Feb 2025 07:00:22 -0000 https://status.shc.kanagawa.jp/incident/519034#f94de09642870a9e9630bcb9c7969b3a946cb3052f19cad9c7ccdcf002bf6606 ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/519034 Wed, 26 Feb 2025 06:59:01 -0000 https://status.shc.kanagawa.jp/incident/519034#d8049fb6732b5464a506322b763ebd7d404fad2d27429bd7f55700a5b5f2ea67 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/519034 Wed, 26 Feb 2025 06:59:01 -0000 https://status.shc.kanagawa.jp/incident/519034#d8049fb6732b5464a506322b763ebd7d404fad2d27429bd7f55700a5b5f2ea67 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/519034 Wed, 26 Feb 2025 06:54:01 -0000 https://status.shc.kanagawa.jp/incident/519034#022ed546a9b8233d0e5c1ff9bae44f39079861174eb21106e57d0c29b769f426 ownCloud (share.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/519034 Wed, 26 Feb 2025 06:53:31 -0000 https://status.shc.kanagawa.jp/incident/519034#cf11ea72622faa05adbb030aa2db443b818f6be0580646616bb8eea2e4082725 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/519034 Wed, 26 Feb 2025 06:52:54 -0000 https://status.shc.kanagawa.jp/incident/519034#a90cdf0bce6cd0a22587cff2112e5702bfe755f8e4b1cd20904ecbd16caece50 Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/519034 Wed, 26 Feb 2025 06:52:32 -0000 https://status.shc.kanagawa.jp/incident/519034#544bcd1c5512f800de9d90d273176c46054c0b43a446671eacfaaa2fb1e19e6c Pleroma(pr.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/519034 Wed, 26 Feb 2025 06:52:32 -0000 https://status.shc.kanagawa.jp/incident/519034#544bcd1c5512f800de9d90d273176c46054c0b43a446671eacfaaa2fb1e19e6c Pleroma(pr.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/519034 Wed, 26 Feb 2025 03:56:03 -0000 https://status.shc.kanagawa.jp/incident/519034#ee2eb17cce1480a399526889c9305fb3cca809168177249ef773da557aa8b114 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/519034 Wed, 26 Feb 2025 03:54:02 -0000 https://status.shc.kanagawa.jp/incident/519034#6dae47c29f0749accc508a76e886740231bf46b5e7249c9bfbda8fc47c5d0072 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/519034 Wed, 26 Feb 2025 03:53:27 -0000 https://status.shc.kanagawa.jp/incident/519034#413eabc63e49d3dacdac2fc4d9bcf99de1e8c927668d89fe3a7ce94a75c3ef2f NextCloud Maintenance recovered. https://status.shc.kanagawa.jp/incident/519034 Wed, 26 Feb 2025 03:52:53 -0000 https://status.shc.kanagawa.jp/incident/519034#069908d4bbb17fe67d86a7f08053df608f40b678dcbcdbd9f23c5591080615e4 Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/519034 Wed, 26 Feb 2025 03:51:32 -0000 https://status.shc.kanagawa.jp/incident/519034#254328eca6fd7c0083b5af14f5e20cd5ae3831b347cc26bc010c4e2ac7a1b656 ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/519034 Wed, 26 Feb 2025 03:51:03 -0000 https://status.shc.kanagawa.jp/incident/519034#c1c0f4f43026110be52fc3f2460db7e53d001d489c3ff1e84d755816defe77a8 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/519034 Wed, 26 Feb 2025 03:13:55 -0000 https://status.shc.kanagawa.jp/incident/519034#2963f38105b62e6d04c7217b054bf9b43ba8514f5ed4afbd4c9c9f315bbbeffd Pleroma(pr.shc.kanagawa.jp) and ownCloud (share.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/519034 Wed, 26 Feb 2025 03:13:55 -0000 https://status.shc.kanagawa.jp/incident/519034#2963f38105b62e6d04c7217b054bf9b43ba8514f5ed4afbd4c9c9f315bbbeffd Pleroma(pr.shc.kanagawa.jp) and ownCloud (share.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/519034 Wed, 26 Feb 2025 03:10:54 -0000 https://status.shc.kanagawa.jp/incident/519034#c1043b15d624f87c2d57382bbcf611a839a83e8bc882ccd4583e73d7f18a4a75 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/519034 Wed, 26 Feb 2025 03:10:04 -0000 https://status.shc.kanagawa.jp/incident/519034#46eb40c0d3849ded0863fcc7b5d41b4b7e24e7e5cc3411457575b94f63bdbd25 NextCloud Maintenance went down. https://status.shc.kanagawa.jp/incident/519034 Wed, 26 Feb 2025 03:05:41 -0000 https://status.shc.kanagawa.jp/incident/519034#8e491f0d694713dae6de9b68f8b02d4d03948b0aa33f7b81c39e93ba4a292618 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/519034 Wed, 26 Feb 2025 03:04:31 -0000 https://status.shc.kanagawa.jp/incident/519034#44b046f5e31eb4e7da01dcf749513a75f367b8abe42f0c258c6c186e36e064c8 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/519034 Wed, 26 Feb 2025 03:03:50 -0000 https://status.shc.kanagawa.jp/incident/519034#1539a14d869d1c43743d04086335528f2d869953502db78eeebb99332baebfdf Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/519034 Wed, 26 Feb 2025 02:59:01 -0000 https://status.shc.kanagawa.jp/incident/519034#8cf99afb4e0559add674bc33c178c6c30b19e203c5d528b14948c6d56e5b62c0 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/519034 Wed, 26 Feb 2025 02:55:52 -0000 https://status.shc.kanagawa.jp/incident/519034#9725ddb0be4072cb51d69a70ecc3545518a6fba207d364d5601cd91396f6bba9 Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/519034 Wed, 26 Feb 2025 02:54:00 -0000 https://status.shc.kanagawa.jp/incident/519034#1e1bff6064712aa358baacf373963762a375361050ab4e0437a7e00e3526037b ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/519034 Wed, 26 Feb 2025 02:53:31 -0000 https://status.shc.kanagawa.jp/incident/519034#0719a21789521161a4e725fb0a2621fb1212fa0480d2ddd932c2e30d318ce9f9 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/519034 Wed, 26 Feb 2025 02:52:50 -0000 https://status.shc.kanagawa.jp/incident/519034#42d8067e3efa3bd7d61ad36067c8898b2ff40c76ce8a51b6c4343634752cbfed ownCloud (share.shc.kanagawa.jp) went down and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/519034 Wed, 26 Feb 2025 02:52:50 -0000 https://status.shc.kanagawa.jp/incident/519034#42d8067e3efa3bd7d61ad36067c8898b2ff40c76ce8a51b6c4343634752cbfed ownCloud (share.shc.kanagawa.jp) went down and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/519034 Wed, 26 Feb 2025 02:50:02 -0000 https://status.shc.kanagawa.jp/incident/519034#84d30e1519d09d8fb315a06e3dbc19e224dd306da190e8765d7069a48a6069e6 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/519034 Wed, 26 Feb 2025 02:50:02 -0000 https://status.shc.kanagawa.jp/incident/519034#84d30e1519d09d8fb315a06e3dbc19e224dd306da190e8765d7069a48a6069e6 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/519034 Wed, 26 Feb 2025 02:49:34 -0000 https://status.shc.kanagawa.jp/incident/519034#68198e166b35004a0f1711cc26371ca0a6206633047e7a1431706cb332946f32 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/516595 Fri, 21 Feb 2025 06:34:38 -0000 https://status.shc.kanagawa.jp/incident/516595#1b4640f14d2ad8656e87d6e3dd5077a7ac9ad84b4371e7bc2bc3e996945e1cea Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/516595 Fri, 21 Feb 2025 06:33:30 -0000 https://status.shc.kanagawa.jp/incident/516595#3decc51bc2ff1086fbe1da61c9ef8599cb5e7c45ccdef0d0768ed11725a6e4e1 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/514104 Mon, 17 Feb 2025 06:33:35 -0000 https://status.shc.kanagawa.jp/incident/514104#940f6384503412def2d9d4a5683375a9d3fd62bbf8957bac360064d2050ad1be Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/514104 Mon, 17 Feb 2025 06:32:33 -0000 https://status.shc.kanagawa.jp/incident/514104#3b52c462f397adc62ef44f7ae19ba34dfaed16b4bd1766100c62c13bcda46787 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/509401 Sat, 08 Feb 2025 06:31:08 -0000 https://status.shc.kanagawa.jp/incident/509401#ed382127c53d537c62992fe0bcea41995254a37c6665a04b779ee7541ed7850f Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/509401 Sat, 08 Feb 2025 06:30:12 -0000 https://status.shc.kanagawa.jp/incident/509401#d4bfab006605456c28eca7c02de65b3927b1b8ee8cf21cc16e64be0342f4d9c1 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/506091 Mon, 03 Feb 2025 18:28:27 -0000 https://status.shc.kanagawa.jp/incident/506091#5a0e7beda2a88a0cf8d7653e81c2473842879a8f7de14107c0405e9fc62e634b Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/506091 Mon, 03 Feb 2025 18:24:46 -0000 https://status.shc.kanagawa.jp/incident/506091#fe0c07e240d1a03236b6d4f22f8e312fa04807e4f7c6d9c2b93bbd679aee404a Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/506091 Mon, 03 Feb 2025 02:39:47 -0000 https://status.shc.kanagawa.jp/incident/506091#07b11900289199451f32c3ab8fb6dfce871d755afbda320f1dd21dfe46cb4b78 demo.shc.kanagawa.jp Initialize recovered. https://status.shc.kanagawa.jp/incident/506091 Sun, 02 Feb 2025 19:27:14 -0000 https://status.shc.kanagawa.jp/incident/506091#a04c722b02fe9879a9abba021b914c00d53dd0602dd551287dbad05cfd9ee251 demo.shc.kanagawa.jp Initialize went down. https://status.shc.kanagawa.jp/incident/505142 Sat, 01 Feb 2025 03:57:01 -0000 https://status.shc.kanagawa.jp/incident/505142#199a4fe84937b880302c881babd8c70a74348001c198bfef01457b61ce43466b demo.shc.kanagawa.jp Initialize recovered. https://status.shc.kanagawa.jp/incident/505142 Fri, 31 Jan 2025 17:26:59 -0000 https://status.shc.kanagawa.jp/incident/505142#a7c36e5866e6dd7d1133cfd5f352efbac28ed3a3fabdfaf1d40eeb2d5efed978 demo.shc.kanagawa.jp Initialize went down. https://status.shc.kanagawa.jp/incident/503578 Wed, 29 Jan 2025 06:07:37 -0000 https://status.shc.kanagawa.jp/incident/503578#b86b4b1011932d1aa6b45614e9efaa12f4e73f28e98b86fb4869f9d445fbc947 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/503578 Wed, 29 Jan 2025 06:07:37 -0000 https://status.shc.kanagawa.jp/incident/503578#b86b4b1011932d1aa6b45614e9efaa12f4e73f28e98b86fb4869f9d445fbc947 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/503578 Wed, 29 Jan 2025 05:19:40 -0000 https://status.shc.kanagawa.jp/incident/503578#e8cc8513b7ef952c6d9f77e68e886ac2b541fc1123816c2cb0503993650c9f61 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/503578 Wed, 29 Jan 2025 05:19:20 -0000 https://status.shc.kanagawa.jp/incident/503578#13272f4c883a967bd224522135528af0b652fb05c770d56bfb60b446b3e8ea8a Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/502959 Tue, 28 Jan 2025 06:32:40 -0000 https://status.shc.kanagawa.jp/incident/502959#d4f9c345bdf17d00a116b6863fcfba467473798bb621d80938d8ae4e1a992cbc Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/502959 Tue, 28 Jan 2025 06:32:40 -0000 https://status.shc.kanagawa.jp/incident/502959#d4f9c345bdf17d00a116b6863fcfba467473798bb621d80938d8ae4e1a992cbc Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/502959 Tue, 28 Jan 2025 06:31:40 -0000 https://status.shc.kanagawa.jp/incident/502959#9e4c0008db924ea2d39d0493dcaa703ad1ce38786d424cab5c56b4e5cd10535a Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/502959 Tue, 28 Jan 2025 06:31:40 -0000 https://status.shc.kanagawa.jp/incident/502959#9e4c0008db924ea2d39d0493dcaa703ad1ce38786d424cab5c56b4e5cd10535a Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/500016 Wed, 22 Jan 2025 13:04:13 -0000 https://status.shc.kanagawa.jp/incident/500016#d17a1905d27f179c5a941c34175858b907abc8454955de89a0f6c63a761bc51d NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/500016 Wed, 22 Jan 2025 12:54:44 -0000 https://status.shc.kanagawa.jp/incident/500016#e201ca39402fa5a53b29397dd0c9b9d57b3ff929aef538b75893522a365b5bde NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/500016 Wed, 22 Jan 2025 11:51:59 -0000 https://status.shc.kanagawa.jp/incident/500016#8e14a94e9ba0814787d0ad309d1f080166fcbe20d6a2eb40966e6f4fd77ecdb9 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/500016 Wed, 22 Jan 2025 11:51:16 -0000 https://status.shc.kanagawa.jp/incident/500016#e88c427797638471ccc753e16d6c47e9736f06c4b0114ccd5aec6c8887f8df77 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/498161 Sun, 19 Jan 2025 06:26:02 -0000 https://status.shc.kanagawa.jp/incident/498161#d8248d472b82d44ecdfbd1ca73a8328902bb9827cb9003f1fd320edcd97f305a Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/498161 Sun, 19 Jan 2025 06:24:55 -0000 https://status.shc.kanagawa.jp/incident/498161#782d1829dcec40d20b665caacbfb1c8da591891bea5e9ee4b00bfc618484e6b4 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/496207 Wed, 15 Jan 2025 10:33:31 -0000 https://status.shc.kanagawa.jp/incident/496207#6c1493cdca5e306bdc6cfd344d2c4cef7188b4244fcbcc2dac8f9a0ef7ffdbe3 ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/496207 Wed, 15 Jan 2025 10:19:51 -0000 https://status.shc.kanagawa.jp/incident/496207#bdb8284a16fc1414a4f2d2cbac298574d0c90ea622b1b2e4659c89b756a7fac6 ownCloud (share.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/495662 Tue, 14 Jan 2025 13:52:17 -0000 https://status.shc.kanagawa.jp/incident/495662#5fb044286400bf5507c817fe794820770457f55a01ae711edcfb199dfbcb192c NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/495662 Tue, 14 Jan 2025 13:28:16 -0000 https://status.shc.kanagawa.jp/incident/495662#6915f12d26622a49c75733f4e5767e886f6280117977508869cf1779cc1bb867 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/495662 Tue, 14 Jan 2025 12:39:55 -0000 https://status.shc.kanagawa.jp/incident/495662#1fc3b3ad5974f682e8ccff5ac154b43ba8ccdddff920fbdde6157c4fbc0073f6 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/495662 Tue, 14 Jan 2025 12:38:42 -0000 https://status.shc.kanagawa.jp/incident/495662#f97ffca83f687436780d8165b0405d1923c641e63e7bbc6fcc0f12d1008e8487 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/490605 Mon, 13 Jan 2025 12:41:13 -0000 https://status.shc.kanagawa.jp/incident/490605#93db8a9bfc32846cb2346ddd32a4c55f5674f29848bf8d78462809cf8393b8a8 demo.shc.kanagawa.jp Initialize recovered. https://status.shc.kanagawa.jp/incident/490605 Sun, 12 Jan 2025 01:10:16 -0000 https://status.shc.kanagawa.jp/incident/490605#23206dbeede415c4502d870d98f229599aca71ac0102fcc261abfe8b8a25302c Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/490605 Sun, 12 Jan 2025 01:09:39 -0000 https://status.shc.kanagawa.jp/incident/490605#0eb37fb66b493248c3ad86319080b0d2bc3a84669d1e690dc0a8b3dbcde0864e Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/490605 Sun, 12 Jan 2025 00:54:37 -0000 https://status.shc.kanagawa.jp/incident/490605#69d48a3a87ac42b382c792b5ab5e258f44ebe6749b19a160892e19e992483cce Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/490605 Sun, 12 Jan 2025 00:54:37 -0000 https://status.shc.kanagawa.jp/incident/490605#69d48a3a87ac42b382c792b5ab5e258f44ebe6749b19a160892e19e992483cce Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/490605 Sun, 12 Jan 2025 00:52:30 -0000 https://status.shc.kanagawa.jp/incident/490605#aebb080c3656c37cf256823565872f411baf3d6e48a4acc616e941b36a4c21c7 Pleroma(pr.shc.kanagawa.jp), NextCloud (cloud.shc.kanagawa.jp), and ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/490605 Sun, 12 Jan 2025 00:52:30 -0000 https://status.shc.kanagawa.jp/incident/490605#aebb080c3656c37cf256823565872f411baf3d6e48a4acc616e941b36a4c21c7 Pleroma(pr.shc.kanagawa.jp), NextCloud (cloud.shc.kanagawa.jp), and ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/490605 Sun, 12 Jan 2025 00:52:30 -0000 https://status.shc.kanagawa.jp/incident/490605#aebb080c3656c37cf256823565872f411baf3d6e48a4acc616e941b36a4c21c7 Pleroma(pr.shc.kanagawa.jp), NextCloud (cloud.shc.kanagawa.jp), and ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/490605 Sat, 11 Jan 2025 23:27:08 -0000 https://status.shc.kanagawa.jp/incident/490605#45a0411a9c10e0a7ee22d9cd3a03edc1b6265afd3b308642cd25c408daac2fb1 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/490605 Sat, 11 Jan 2025 23:24:27 -0000 https://status.shc.kanagawa.jp/incident/490605#3574506728e3ebf900d80715e87dffee7a3f141ca412b2c6fb31af6b07cd0e5b Mastodon(mt.shc.kanagawa.jp) and ownCloud (share.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/490605 Sat, 11 Jan 2025 23:24:27 -0000 https://status.shc.kanagawa.jp/incident/490605#3574506728e3ebf900d80715e87dffee7a3f141ca412b2c6fb31af6b07cd0e5b Mastodon(mt.shc.kanagawa.jp) and ownCloud (share.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/490605 Sat, 11 Jan 2025 23:22:40 -0000 https://status.shc.kanagawa.jp/incident/490605#9998e5bf3c9c14df50288c46831216eaef84955ad414f0b0e0ed02da687709ef NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/490605 Sat, 11 Jan 2025 23:21:10 -0000 https://status.shc.kanagawa.jp/incident/490605#1b77920738650c9f7a77c2b9a7ac2c9eb359626679bc8da970f1a5649b22c422 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/490605 Wed, 08 Jan 2025 00:47:54 -0000 https://status.shc.kanagawa.jp/incident/490605#6afbc92e58ae543aea53898cc5a8582f91500e24223d7da538b3ace0ddbb5423 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/490605 Wed, 08 Jan 2025 00:40:52 -0000 https://status.shc.kanagawa.jp/incident/490605#d9ae1bae08b18c5fab713e018f931f1e51ecbcc7dea3a57681a9630b0d2a5557 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/490605 Mon, 06 Jan 2025 18:36:44 -0000 https://status.shc.kanagawa.jp/incident/490605#1d8f6c3f8abbaaaeea69dcc9f3beafc44a22686d9850b5f58f673db5c64c1498 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/490605 Mon, 06 Jan 2025 18:32:44 -0000 https://status.shc.kanagawa.jp/incident/490605#9ae5ff957ca053e435cde6c9ffc8d8c11b3fcb0cef2d28bd5b57de8d9441aa32 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/490605 Sun, 05 Jan 2025 17:39:33 -0000 https://status.shc.kanagawa.jp/incident/490605#fcfdabda2293cedaf7b1d89612af32353c74e25410e5e9ea5b27aa480f7576cf Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/490605 Sun, 05 Jan 2025 17:38:48 -0000 https://status.shc.kanagawa.jp/incident/490605#449671df972b05e843536a9770c02686ac3dfd3be4d300a3d843eda29b5d2225 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/490605 Sun, 05 Jan 2025 10:48:08 -0000 https://status.shc.kanagawa.jp/incident/490605#0075cbcdf8d646d37efdfff7ef7c489ae68742ba2f70044440d2e4644d30e4ac Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/490605 Sun, 05 Jan 2025 10:47:26 -0000 https://status.shc.kanagawa.jp/incident/490605#7e887d30af210ec22b650f4824a8968269d32db2d3ab2e33affacc049b94c25c Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/490605 Sun, 05 Jan 2025 04:38:19 -0000 https://status.shc.kanagawa.jp/incident/490605#6e33ca6a096ef1ffc705b096ffaa50fe9bb0bf97d8b012d53550b0c83e604df8 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/490605 Sun, 05 Jan 2025 04:34:12 -0000 https://status.shc.kanagawa.jp/incident/490605#3dd88a17a82f16de771255b4293b1b201343a9fdb8bcf525aff184d9c63da99c Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/490605 Sat, 04 Jan 2025 10:28:11 -0000 https://status.shc.kanagawa.jp/incident/490605#62c8dd530400eeb02cb369aff2254db5825d7b81378a1732afd6f2c2ff7b7cdd demo.shc.kanagawa.jp Initialize went down. https://status.shc.kanagawa.jp/incident/488424 Mon, 30 Dec 2024 08:06:42 -0000 https://status.shc.kanagawa.jp/incident/488424#2d065a28ed19b07c2cbc93fb843f6eb44ddbe392e3a52810785afe47f46dab13 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/488424 Mon, 30 Dec 2024 08:05:45 -0000 https://status.shc.kanagawa.jp/incident/488424#cf63e192cb4bdec743b460251f0fda6c79a004a2263655f0e5551965ea751dd6 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/488081 Sun, 29 Dec 2024 09:34:38 -0000 https://status.shc.kanagawa.jp/incident/488081#6417be083066886e25aaa38d0fb8f32917157fbe70b1f46df72cb1ee399e843e demo.shc.kanagawa.jp Initialize recovered. https://status.shc.kanagawa.jp/incident/488081 Sun, 29 Dec 2024 09:32:19 -0000 https://status.shc.kanagawa.jp/incident/488081#6ef1bfec40302ebfc76426ad12dac43e638dec7d4b26cbc732e24dcb69a81b67 demo.shc.kanagawa.jp Initialize went down. https://status.shc.kanagawa.jp/incident/487431 Fri, 27 Dec 2024 12:11:12 -0000 https://status.shc.kanagawa.jp/incident/487431#d0e6b9090d0a80554d1cb885118b048463c5b4509d4a50a9b4ef25882b7c54e0 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/487431 Fri, 27 Dec 2024 12:10:23 -0000 https://status.shc.kanagawa.jp/incident/487431#7ae6737c1e0df38354f35966ede299c6355d785fd3e19678f2bd9a287e35977b Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/486647 Wed, 25 Dec 2024 06:19:35 -0000 https://status.shc.kanagawa.jp/incident/486647#9d1a4b71cfd7629293785f48ff21a9f795f463dde818f8cf7f8f0635fcc98b4d Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/486647 Wed, 25 Dec 2024 06:18:26 -0000 https://status.shc.kanagawa.jp/incident/486647#0a3e56d20439aeb34d3a94d660b5c638ff491b6c306d2cf699033990001235c9 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/486378 Tue, 24 Dec 2024 11:43:35 -0000 https://status.shc.kanagawa.jp/incident/486378#3d742f61aa64b4881e62a81e862d963db76f264c76ead01524c692e4fb162542 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/486378 Tue, 24 Dec 2024 11:42:56 -0000 https://status.shc.kanagawa.jp/incident/486378#f5eae4af56ef3a1caa16cbeb8d3852a47021c25b20695afb5b24d83dbd2047b6 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/485615 Sun, 22 Dec 2024 13:19:18 -0000 https://status.shc.kanagawa.jp/incident/485615#825a6f21bbc6d94acd26d9c2de44f0feeeef4cd06b7ba91f0c6fcbb7ded5a687 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/485615 Sun, 22 Dec 2024 13:18:20 -0000 https://status.shc.kanagawa.jp/incident/485615#31b4dbd8b822b0e33b47bcdfaf330313d20256b84f1770d259dab3d4804afd34 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/485166 Sat, 21 Dec 2024 06:18:18 -0000 https://status.shc.kanagawa.jp/incident/485166#204d7238976bb8fb1fc28b50d0efbccef99b7ce3445092e5c07f30278e361c64 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/485166 Sat, 21 Dec 2024 06:17:11 -0000 https://status.shc.kanagawa.jp/incident/485166#77e4f19748179a725d14d9160f70cd9b58b8b7d424c83d4ddf07a9a0d2783a12 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/484733 Fri, 20 Dec 2024 11:47:59 -0000 https://status.shc.kanagawa.jp/incident/484733#3d1974a6fc8defceeafbe79d4aa79b7494c971ed1f211c0a71b141c1e9074653 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/484733 Fri, 20 Dec 2024 11:26:10 -0000 https://status.shc.kanagawa.jp/incident/484733#cdbaa5bc931fc9b58365748572d3bbc049f312a4ee01662d8f7969990869f0e9 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/484733 Fri, 20 Dec 2024 09:06:00 -0000 https://status.shc.kanagawa.jp/incident/484733#aa34a8e35bb5c225391f2018b14a64059b28626d6519c582980b69f09773e0e6 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/484733 Fri, 20 Dec 2024 09:05:10 -0000 https://status.shc.kanagawa.jp/incident/484733#e556638ed9f2ca038ddafa664238c55d46b066c70922cf10231ee01b86ad5cbf Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/484733 Fri, 20 Dec 2024 08:59:58 -0000 https://status.shc.kanagawa.jp/incident/484733#f2815b0a5dfa566d3d7fc0e352c0ae8b875b828bc7d4e290bf7b326a2930ea90 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/484733 Fri, 20 Dec 2024 08:59:09 -0000 https://status.shc.kanagawa.jp/incident/484733#e73ff2c0be0b6fbd76039238459c1f3e720de4f42b5886dc2782c64072f258da Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/484733 Fri, 20 Dec 2024 07:23:56 -0000 https://status.shc.kanagawa.jp/incident/484733#bbe438510f61ac264ba69e081079bfbfc75fb464336f4b9e011d18c179399653 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/484733 Fri, 20 Dec 2024 07:19:47 -0000 https://status.shc.kanagawa.jp/incident/484733#658b8167dcb40abfe57a7c80698182901fea4671ced445aac8be69040c486b44 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/484733 Fri, 20 Dec 2024 06:26:57 -0000 https://status.shc.kanagawa.jp/incident/484733#b3c1a3fcc30565509499e4fda42640686f8c56ce4ddb84c0a17aa4f79830e969 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/484733 Fri, 20 Dec 2024 06:25:46 -0000 https://status.shc.kanagawa.jp/incident/484733#9665dd185752bbef84271b2b7c731aa5ba8bfedb12fb3429d79f10661050768b Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/484212 Thu, 19 Dec 2024 10:12:29 -0000 https://status.shc.kanagawa.jp/incident/484212#7ca7b165b11dfb7ec5e9604d21ee931a1ebf55711859df194505b0f5557aa563 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/484212 Thu, 19 Dec 2024 10:08:29 -0000 https://status.shc.kanagawa.jp/incident/484212#5c19b79db214a4dc808476ffc7d2e12b95babf4056739946b67fc4805d03e1df Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/484212 Thu, 19 Dec 2024 09:12:21 -0000 https://status.shc.kanagawa.jp/incident/484212#5ebfdd24551659fb83a4fcbd28b371d13425238436e5de5c131089d4a01d7a31 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/484212 Thu, 19 Dec 2024 09:08:30 -0000 https://status.shc.kanagawa.jp/incident/484212#fbc9eaee25461293c42f566bede2e07adbe399c036915975ef672dbe249446cd Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/484212 Thu, 19 Dec 2024 08:09:30 -0000 https://status.shc.kanagawa.jp/incident/484212#1a0dd14e35fbd50d00d4d1584594f0c99b33308971f5cef26bbbc480c188c659 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/484212 Thu, 19 Dec 2024 08:02:32 -0000 https://status.shc.kanagawa.jp/incident/484212#8b7f7a8d716f429b7587541ed42efe62182c23e7a0b4cd5573e73a9584eeaf5b Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/484212 Thu, 19 Dec 2024 06:27:25 -0000 https://status.shc.kanagawa.jp/incident/484212#5949ae88be2ab9fdced7b4da0effcab2fc0f583130fa658320af1678b9463a2c Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/484212 Thu, 19 Dec 2024 06:20:32 -0000 https://status.shc.kanagawa.jp/incident/484212#980df9cc788356f5f1e2197bcf53044642f6849611965a511ccda24436550aa7 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/483747 Wed, 18 Dec 2024 09:11:33 -0000 https://status.shc.kanagawa.jp/incident/483747#166ef2376463cfa862624aae33ffa6eb28a4c9c1eb34b8c10480fc99088cb717 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/483747 Wed, 18 Dec 2024 09:04:44 -0000 https://status.shc.kanagawa.jp/incident/483747#95aec9ad5f01e1b6ebba022ebe6b3533f05c6d92005d7c10e72c3c57c326bcfa Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/480461 Tue, 17 Dec 2024 11:50:49 -0000 https://status.shc.kanagawa.jp/incident/480461#0d79ec0a22e693476448e0b119cd821c9a05404be7844d7cd88b5be6542cd6db Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/480461 Tue, 17 Dec 2024 11:43:40 -0000 https://status.shc.kanagawa.jp/incident/480461#02c4a1e9806cbf1f49b6141f50225bfae99928a53394f264a2a4c47891228144 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/480461 Tue, 17 Dec 2024 10:11:31 -0000 https://status.shc.kanagawa.jp/incident/480461#e6fc7a3b87783f8815ff0f6abe544bc0b34c7d6e17c1f4dc1d1eaf6a0fac91b6 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/480461 Tue, 17 Dec 2024 10:10:25 -0000 https://status.shc.kanagawa.jp/incident/480461#299060a3bad050613031bcfa8dbb26c37b08e97be9a7f696e5f1a581d9a47617 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/477021 Fri, 13 Dec 2024 15:55:29 -0000 https://status.shc.kanagawa.jp/incident/477021#ab6e551413a4acb31fea9927454873f6540dd63f46e64d068beacdc1a722fad7 Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/477021 Fri, 13 Dec 2024 15:54:19 -0000 https://status.shc.kanagawa.jp/incident/477021#539eb77e0505059f3767a0e34f2702fffbeba504d20eb1dee7fce87e1a7d77dd Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/477021 Fri, 13 Dec 2024 06:16:23 -0000 https://status.shc.kanagawa.jp/incident/477021#21e2f39ba5f1a4791f53ddcfb7366ca6606539683a9704306dcecc0e30563116 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/477021 Fri, 13 Dec 2024 06:15:11 -0000 https://status.shc.kanagawa.jp/incident/477021#5a8a9993b01837f000e779defc718499055d7fb05f908a43c3a7205dab6b91c8 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/474180 Sun, 08 Dec 2024 12:38:27 -0000 https://status.shc.kanagawa.jp/incident/474180#f53a5174d083ab52a8f5c40d08336de100871c66975b73565e644949ca38d571 Internet Relay Chat Web (webirc.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/474180 Sun, 08 Dec 2024 03:50:16 -0000 https://status.shc.kanagawa.jp/incident/474180#64d497e061b82e117dec7b76bd2a19afb6b9535cfdc6cecbe144179a3218ae55 Internet Relay Chat Web (webirc.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/473567 Fri, 06 Dec 2024 18:49:18 -0000 https://status.shc.kanagawa.jp/incident/473567#2e2dcd1d6f0f3a9903fbd9a3a6b674c3c0e246bac5e71b2920fcb439cc932a09 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/473567 Fri, 06 Dec 2024 18:21:10 -0000 https://status.shc.kanagawa.jp/incident/473567#cd7d135c4451caffc4e8fbffbe568546026a885474b99dbeb95512125799e47f Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/472647 Thu, 05 Dec 2024 06:14:16 -0000 https://status.shc.kanagawa.jp/incident/472647#25afdcdc4397d0ceac674eebe3ae47343ea29053537238699ae5039cc151448c Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/472647 Thu, 05 Dec 2024 06:13:10 -0000 https://status.shc.kanagawa.jp/incident/472647#680a4bad9146d766d889b5af689e4608024866bb5b519900f241ea50ee78670e Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/471785 Tue, 03 Dec 2024 19:30:35 -0000 https://status.shc.kanagawa.jp/incident/471785#492863add5f5ba6879616a63078ef07f5f887257bb075e376682818ba3c1aad9 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/471785 Tue, 03 Dec 2024 19:30:35 -0000 https://status.shc.kanagawa.jp/incident/471785#492863add5f5ba6879616a63078ef07f5f887257bb075e376682818ba3c1aad9 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/471785 Tue, 03 Dec 2024 19:24:36 -0000 https://status.shc.kanagawa.jp/incident/471785#8246505944501d1b7f5fc49039d0b774a166e40d5ed342fc93ec85067cffb8e5 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/471785 Tue, 03 Dec 2024 19:24:36 -0000 https://status.shc.kanagawa.jp/incident/471785#8246505944501d1b7f5fc49039d0b774a166e40d5ed342fc93ec85067cffb8e5 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/471785 Tue, 03 Dec 2024 19:00:52 -0000 https://status.shc.kanagawa.jp/incident/471785#69e9707a2ebde321cd13ac7635ef9325c3b9fcd9f396ff3f30ce7390116e545e Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/471785 Tue, 03 Dec 2024 18:57:24 -0000 https://status.shc.kanagawa.jp/incident/471785#aac8855a6b4270c74bbdfb1a41b24ead52185ab51e054612dc39a8eea1b75315 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/471785 Tue, 03 Dec 2024 18:03:36 -0000 https://status.shc.kanagawa.jp/incident/471785#17d87c2653a7edb8a5cdc36aef47e641321eded66ed9be611c1b9ead6d420ad7 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/471785 Tue, 03 Dec 2024 18:03:22 -0000 https://status.shc.kanagawa.jp/incident/471785#c4bc9b69f54de931917898ad63db9af0dff51fa554ce515ba19798383ac2ee9e Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/471785 Tue, 03 Dec 2024 17:56:12 -0000 https://status.shc.kanagawa.jp/incident/471785#d246ca91f65f79dca9835a511b908e98e57234eab813d1a3424220ceb68a196a Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/471785 Tue, 03 Dec 2024 17:54:09 -0000 https://status.shc.kanagawa.jp/incident/471785#af178e2b5b536f40a91579f3381f3e7b8410cc43639b0c4fb50be45ccf917cb1 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/470759 Mon, 02 Dec 2024 08:10:03 -0000 https://status.shc.kanagawa.jp/incident/470759#7e0623efd967cca402c4a8be52a6b14c87923dbdfde98351055c912aadf6b460 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/470759 Mon, 02 Dec 2024 07:33:28 -0000 https://status.shc.kanagawa.jp/incident/470759#a21e6bc851991e746811374eef75728dc492cde40780ac27110effebd0b8b632 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/470759 Mon, 02 Dec 2024 07:32:09 -0000 https://status.shc.kanagawa.jp/incident/470759#9d496ad725411357119152f2ab19fd9be27d3d5c32507d10da2548b3b6d4bdab Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/470759 Mon, 02 Dec 2024 07:14:39 -0000 https://status.shc.kanagawa.jp/incident/470759#86f7debcf219aa9379d0390b43054435d1392aca7d20a340bf05f64f0eee3fb4 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/470759 Mon, 02 Dec 2024 06:42:23 -0000 https://status.shc.kanagawa.jp/incident/470759#43099368a2680c379a8d6e5ae73e5fd198689cd3434d8b2bd2940736f108dd12 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/470759 Mon, 02 Dec 2024 06:30:24 -0000 https://status.shc.kanagawa.jp/incident/470759#0769a22d4e8538d1a14df6c6be8e755bf4c5dc91dc2742d435ebc620c0559a19 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/470759 Mon, 02 Dec 2024 06:17:08 -0000 https://status.shc.kanagawa.jp/incident/470759#beeaaab13e1b1b8a51af605a44ceabcb6d8b5e23da3c8a3baaa4b1eebc1ae407 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/470759 Mon, 02 Dec 2024 06:12:27 -0000 https://status.shc.kanagawa.jp/incident/470759#cb2d3442f0eeef4e12e5494b34f06fba95823142545b3f2e7fc8f024b4a6aca0 ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/470759 Mon, 02 Dec 2024 06:12:07 -0000 https://status.shc.kanagawa.jp/incident/470759#3ecde94397d66f479f5c977e89902b6f24e3a9e2c3697bdea2ad2da6abc8240e Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/470759 Mon, 02 Dec 2024 06:11:27 -0000 https://status.shc.kanagawa.jp/incident/470759#f6d413c79931a019884cc993a5f12bd9ea783843ab29c5715cc329326cb3a002 ownCloud (share.shc.kanagawa.jp) went down and Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/470759 Mon, 02 Dec 2024 06:11:27 -0000 https://status.shc.kanagawa.jp/incident/470759#f6d413c79931a019884cc993a5f12bd9ea783843ab29c5715cc329326cb3a002 ownCloud (share.shc.kanagawa.jp) went down and Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/470759 Mon, 02 Dec 2024 06:11:27 -0000 https://status.shc.kanagawa.jp/incident/470759#f6d413c79931a019884cc993a5f12bd9ea783843ab29c5715cc329326cb3a002 ownCloud (share.shc.kanagawa.jp) went down and Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/470759 Mon, 02 Dec 2024 06:09:18 -0000 https://status.shc.kanagawa.jp/incident/470759#50e9e4c44ffb0494225f89900bdc4c56602d2f6231ecc76aad56f841f197d9a0 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/470759 Mon, 02 Dec 2024 06:08:02 -0000 https://status.shc.kanagawa.jp/incident/470759#72eb590c4251491d1965e63ddf7ea1ed101588e5f6fcbb477dba525e3fdfa883 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/470759 Mon, 02 Dec 2024 06:05:10 -0000 https://status.shc.kanagawa.jp/incident/470759#7e8db3ec5de5130a3b1ea8888047123688d8e644365a657481456019cb6182fb Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/470759 Mon, 02 Dec 2024 05:52:51 -0000 https://status.shc.kanagawa.jp/incident/470759#e1434930ebdce7b3323a5fea9bd9d63dc36d156493fdc65fb86680c03a68b076 Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/470759 Mon, 02 Dec 2024 04:09:27 -0000 https://status.shc.kanagawa.jp/incident/470759#4c3ce30e85966a82986c1d7d6637ff449f0f671e7fd6b579243c8c6be4d4b35f Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/470759 Mon, 02 Dec 2024 02:47:28 -0000 https://status.shc.kanagawa.jp/incident/470759#9b38a0c5089a57497f072cb2a336e882423c0d2aec4703763c229ff1d1f4f50c Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/470422 Sun, 01 Dec 2024 07:33:29 -0000 https://status.shc.kanagawa.jp/incident/470422#24926864effb3eec788f70989c1131be19bf0c8e5e09f6cd757be8789e5d983d Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/470422 Sun, 01 Dec 2024 07:24:28 -0000 https://status.shc.kanagawa.jp/incident/470422#bac1e114c1eee56157d5651e958c3ac8c922fd407ae8e54429f251e73aa8c5c6 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/470422 Sun, 01 Dec 2024 06:57:08 -0000 https://status.shc.kanagawa.jp/incident/470422#c7ed2aa7db36b2c52e898c5c5d13c3d942aa9caff6aad0df3c776a79e2bf7313 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/470422 Sun, 01 Dec 2024 06:54:20 -0000 https://status.shc.kanagawa.jp/incident/470422#de19f3ef4e202e82aea87f42650b2e507b0c97cc7ec110c1b662dc41f0415de5 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/470422 Sun, 01 Dec 2024 06:48:31 -0000 https://status.shc.kanagawa.jp/incident/470422#df3e86f6d2f918317d64e13df8e0f8b79362c237a1ab7ef924746d53dc05e136 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/470422 Sun, 01 Dec 2024 06:39:26 -0000 https://status.shc.kanagawa.jp/incident/470422#471684da03f3b9affdf8ab19b75acdb68c891ac400cb87aa6f5362f0d69713ef Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/469047 Sat, 30 Nov 2024 12:50:50 -0000 https://status.shc.kanagawa.jp/incident/469047#db591bf52d594dafc1e12c63902d3809a6297d8519934f288f5d56e9a47d274d Internet Relay Chat Web (webirc.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/469047 Sat, 30 Nov 2024 12:20:42 -0000 https://status.shc.kanagawa.jp/incident/469047#e4232a2c6087c4d34aec404483bda8c488e5797bb301c3ba353e46a33c836e44 Internet Relay Chat Web (webirc.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/469047 Sat, 30 Nov 2024 11:38:45 -0000 https://status.shc.kanagawa.jp/incident/469047#e5b41257020cb676d841772e83592b7421a0d55c3a2278f7eebf14090954db3d Internet Relay Chat Web (webirc.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/469047 Sat, 30 Nov 2024 10:08:27 -0000 https://status.shc.kanagawa.jp/incident/469047#4acfd8a64902be1dcf822e1e3a625535b87d49c02c7bc4fc2fc2584583258c95 Internet Relay Chat (irc.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/469047 Sat, 30 Nov 2024 05:26:47 -0000 https://status.shc.kanagawa.jp/incident/469047#f4d2f50ff10a152f6c9b1cfbceb6b6398016566fcc20df9e582d96a6b424994e Internet Relay Chat (irc.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/469047 Sat, 30 Nov 2024 05:00:36 -0000 https://status.shc.kanagawa.jp/incident/469047#000911c19f1f6e770aac8c23ad3414b5855b06da3b1ced70847464b85566fc77 demo.shc.kanagawa.jp Initialize recovered. https://status.shc.kanagawa.jp/incident/469047 Sat, 30 Nov 2024 04:29:09 -0000 https://status.shc.kanagawa.jp/incident/469047#4c2b34bce4f163e8af5261d297b3df2a807d127344f8c22d802405ca16335927 demo.shc.kanagawa.jp Initialize went down. https://status.shc.kanagawa.jp/incident/469047 Sat, 30 Nov 2024 04:02:00 -0000 https://status.shc.kanagawa.jp/incident/469047#8fba23d15df4ac588e71cd99f6bb858adfdf147367daa75d5b3e9a4db651ce75 Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/469047 Sat, 30 Nov 2024 04:01:15 -0000 https://status.shc.kanagawa.jp/incident/469047#37a01b9086a7cdbb874adb28312ebbb65cbaccee28a8cfec33d6ae6928cff4c2 Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/469047 Fri, 29 Nov 2024 15:11:46 -0000 https://status.shc.kanagawa.jp/incident/469047#3efb4920d7568390da1f3f548eb8a6993f320d2eff20edbc341e803bd4465cd6 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/469047 Fri, 29 Nov 2024 15:07:40 -0000 https://status.shc.kanagawa.jp/incident/469047#28400251409c0850a6351e212d8ed3d8aa3216871dd10bc3d8d50104992f25d3 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/469047 Fri, 29 Nov 2024 14:10:34 -0000 https://status.shc.kanagawa.jp/incident/469047#320a198b94bd331d709122803020092ab59d21779ab7397b2710c94122698b94 Internet Relay Chat (irc.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/469047 Fri, 29 Nov 2024 11:53:08 -0000 https://status.shc.kanagawa.jp/incident/469047#7faf10f5177cecb54d2493c5b63f585e0384845639834765271a30b6c52ad06e Internet Relay Chat (irc.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/469047 Thu, 28 Nov 2024 23:49:37 -0000 https://status.shc.kanagawa.jp/incident/469047#ee673ac1e4f84e0b9258bc9b75cf7aaa8192467c4299a9857f2d12a70fedbcbf Internet Relay Chat Web (webirc.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/469047 Thu, 28 Nov 2024 23:41:45 -0000 https://status.shc.kanagawa.jp/incident/469047#45e7d8539879f1125540c18bdd52fbf12c9e6c3885b8ff7ace03ef97d945028d Internet Relay Chat Web (webirc.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/469047 Thu, 28 Nov 2024 12:36:58 -0000 https://status.shc.kanagawa.jp/incident/469047#1a57455fb7e8c08b7c0ecf537e53f1fa70caffe30ce3669daadf7ae1ca0b8d65 Internet Relay Chat (irc.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/469047 Thu, 28 Nov 2024 11:57:22 -0000 https://status.shc.kanagawa.jp/incident/469047#8abbf4b38943fcc38dc3b81dd916b0604ef0f320d5dc901b2d0b43beb4fa2011 Internet Relay Chat (irc.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/469047 Thu, 28 Nov 2024 11:39:24 -0000 https://status.shc.kanagawa.jp/incident/469047#8a3c67fef50f5671097a8292b4b44cbbff86ffedda167db3f87f92a2adda3e6f Internet Relay Chat (irc.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/469047 Thu, 28 Nov 2024 11:21:23 -0000 https://status.shc.kanagawa.jp/incident/469047#814c45c3a486c07915e968796834cc0a94701e93363d0c3330a24a92b1c246f4 Internet Relay Chat (irc.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/469047 Thu, 28 Nov 2024 07:04:29 -0000 https://status.shc.kanagawa.jp/incident/469047#d58ac4dfb51ada0f557b28626023eed1643081b639524508574c275a3fe4f312 Internet Relay Chat (irc.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/469047 Thu, 28 Nov 2024 04:58:58 -0000 https://status.shc.kanagawa.jp/incident/469047#bea937ef216d15b3c32e07ce23f813799c1e721475906811afb148d1bcd3d8c7 Internet Relay Chat (irc.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/469047 Thu, 28 Nov 2024 04:37:52 -0000 https://status.shc.kanagawa.jp/incident/469047#b2267a0c42faecae09117314022a8af6a3a42a9345f28bd7022e117c31a5047f Internet Relay Chat Web (webirc.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/468647 Wed, 27 Nov 2024 23:40:56 -0000 https://status.shc.kanagawa.jp/incident/468647#ca8a1bd90ac571c273db015d42d1bee08c086c2e6779d757f643e4569d94e83f Internet Relay Chat Web (webirc.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/468647 Wed, 27 Nov 2024 13:01:44 -0000 https://status.shc.kanagawa.jp/incident/468647#511252c8eb178c59fd9379ebefc55a2438c2b7fb191172053b51050835b7d3d1 Internet Relay Chat Web (webirc.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/467790 Tue, 26 Nov 2024 18:36:41 -0000 https://status.shc.kanagawa.jp/incident/467790#5287847a9e234dc42fc0389612821ff176b07283267e7039c94812c0bf4d1d80 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/467790 Tue, 26 Nov 2024 18:35:53 -0000 https://status.shc.kanagawa.jp/incident/467790#01acd5310e2d96e2cf2791c6edb270c10bfea90836cdf97c1c9fbedcf1c5505b NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/467790 Tue, 26 Nov 2024 06:10:06 -0000 https://status.shc.kanagawa.jp/incident/467790#3778ade450a8041b98b782721b48806a979ba6deb5631ac7490d5284296d7ff3 Pleroma(pr.shc.kanagawa.jp) and ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/467790 Tue, 26 Nov 2024 06:10:06 -0000 https://status.shc.kanagawa.jp/incident/467790#3778ade450a8041b98b782721b48806a979ba6deb5631ac7490d5284296d7ff3 Pleroma(pr.shc.kanagawa.jp) and ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/467790 Tue, 26 Nov 2024 06:09:23 -0000 https://status.shc.kanagawa.jp/incident/467790#a8203dc852e9d02a8d8aa0516bfacef992fb35e9fc4d681f105f7ac08dcd7e71 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/467790 Tue, 26 Nov 2024 06:09:23 -0000 https://status.shc.kanagawa.jp/incident/467790#a8203dc852e9d02a8d8aa0516bfacef992fb35e9fc4d681f105f7ac08dcd7e71 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/467790 Tue, 26 Nov 2024 06:06:23 -0000 https://status.shc.kanagawa.jp/incident/467790#305d83011c0a0b128bba468f527c1d15c7bd12c72ee9f733f6d5bb11d71abd48 ownCloud (share.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/467790 Tue, 26 Nov 2024 06:04:03 -0000 https://status.shc.kanagawa.jp/incident/467790#bd5fa286c6229d4b7f2218a0a91c04200d5d9847cb12a90e4b6941ec2135a2fd Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/467790 Tue, 26 Nov 2024 06:03:15 -0000 https://status.shc.kanagawa.jp/incident/467790#b81d53abba99a2fe26130de12e62cfa0e72f37e2d479e6ec618ea7aa43d75e2a Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/467790 Tue, 26 Nov 2024 06:03:01 -0000 https://status.shc.kanagawa.jp/incident/467790#d45388dcdaf859d4bb74c2b3a7bd490c915bcc0aabc3e1a698534abcd9e1f3a6 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/467790 Tue, 26 Nov 2024 03:31:26 -0000 https://status.shc.kanagawa.jp/incident/467790#f746c6d888a4b6b74c80c42bc0d28c1dc0225686510945af0353d961f5e91f7b NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/467790 Tue, 26 Nov 2024 03:09:52 -0000 https://status.shc.kanagawa.jp/incident/467790#a656130d33672c080ca3892562bf8abc3fa9153ac5311c1e2cbc100c820b8b05 Pleroma(pr.shc.kanagawa.jp) and ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/467790 Tue, 26 Nov 2024 03:09:52 -0000 https://status.shc.kanagawa.jp/incident/467790#a656130d33672c080ca3892562bf8abc3fa9153ac5311c1e2cbc100c820b8b05 Pleroma(pr.shc.kanagawa.jp) and ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/467790 Tue, 26 Nov 2024 03:09:16 -0000 https://status.shc.kanagawa.jp/incident/467790#8d5a54bce02ae34041527b8b115092b327200ba69056e7ba1f8ffcbdb54cee38 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/467790 Tue, 26 Nov 2024 03:08:58 -0000 https://status.shc.kanagawa.jp/incident/467790#0cccfcd00f5cfc99b6b395ac2312ebf32eb3b09ac9931350807006c2465a9221 Pleroma(pr.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), NextCloud (cloud.shc.kanagawa.jp), and 1 other resource went down. https://status.shc.kanagawa.jp/incident/467790 Tue, 26 Nov 2024 03:08:58 -0000 https://status.shc.kanagawa.jp/incident/467790#0cccfcd00f5cfc99b6b395ac2312ebf32eb3b09ac9931350807006c2465a9221 Pleroma(pr.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), NextCloud (cloud.shc.kanagawa.jp), and 1 other resource went down. https://status.shc.kanagawa.jp/incident/467790 Tue, 26 Nov 2024 03:08:58 -0000 https://status.shc.kanagawa.jp/incident/467790#0cccfcd00f5cfc99b6b395ac2312ebf32eb3b09ac9931350807006c2465a9221 Pleroma(pr.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), NextCloud (cloud.shc.kanagawa.jp), and 1 other resource went down. https://status.shc.kanagawa.jp/incident/467790 Tue, 26 Nov 2024 03:08:58 -0000 https://status.shc.kanagawa.jp/incident/467790#0cccfcd00f5cfc99b6b395ac2312ebf32eb3b09ac9931350807006c2465a9221 Pleroma(pr.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), NextCloud (cloud.shc.kanagawa.jp), and 1 other resource went down. https://status.shc.kanagawa.jp/incident/467754 Tue, 26 Nov 2024 03:00:30 -0000 https://status.shc.kanagawa.jp/incident/467754#08121cb0b28747842091a7e0a0721ed67134646becface01fe374c07ce0bf2c7 Maintenance completed https://status.shc.kanagawa.jp/incident/467754 Tue, 26 Nov 2024 03:00:30 -0000 https://status.shc.kanagawa.jp/incident/467754#08121cb0b28747842091a7e0a0721ed67134646becface01fe374c07ce0bf2c7 Maintenance completed https://status.shc.kanagawa.jp/incident/467754 Tue, 26 Nov 2024 03:00:30 -0000 https://status.shc.kanagawa.jp/incident/467754#08121cb0b28747842091a7e0a0721ed67134646becface01fe374c07ce0bf2c7 Maintenance completed https://status.shc.kanagawa.jp/incident/467754 Tue, 26 Nov 2024 03:00:30 -0000 https://status.shc.kanagawa.jp/incident/467754#08121cb0b28747842091a7e0a0721ed67134646becface01fe374c07ce0bf2c7 Maintenance completed https://status.shc.kanagawa.jp/incident/467754 Tue, 26 Nov 2024 03:00:30 -0000 https://status.shc.kanagawa.jp/incident/467754#08121cb0b28747842091a7e0a0721ed67134646becface01fe374c07ce0bf2c7 Maintenance completed https://status.shc.kanagawa.jp/incident/467754 Tue, 26 Nov 2024 03:00:30 -0000 https://status.shc.kanagawa.jp/incident/467754#08121cb0b28747842091a7e0a0721ed67134646becface01fe374c07ce0bf2c7 Maintenance completed https://status.shc.kanagawa.jp/incident/467754 Tue, 26 Nov 2024 02:00:30 -0000 https://status.shc.kanagawa.jp/incident/467754#f0027446fc3c879b60ec4286fd400faa0c8441053718627c8dcf58fb12abb386 We plan maintenance on Tuesday, hold onto your hats! Event Type: Storage Upgrade Start Time: 2024-11-26 2:00:00 UTC 開始時刻 2024/11/26 11:00:00 日本時間 End Time: 2024-11-26 3:00:00 UTC 終了時刻 2024/11/26 12:00:00 日本時間 https://status.shc.kanagawa.jp/incident/467754 Tue, 26 Nov 2024 02:00:30 -0000 https://status.shc.kanagawa.jp/incident/467754#f0027446fc3c879b60ec4286fd400faa0c8441053718627c8dcf58fb12abb386 We plan maintenance on Tuesday, hold onto your hats! Event Type: Storage Upgrade Start Time: 2024-11-26 2:00:00 UTC 開始時刻 2024/11/26 11:00:00 日本時間 End Time: 2024-11-26 3:00:00 UTC 終了時刻 2024/11/26 12:00:00 日本時間 https://status.shc.kanagawa.jp/incident/467754 Tue, 26 Nov 2024 02:00:30 -0000 https://status.shc.kanagawa.jp/incident/467754#f0027446fc3c879b60ec4286fd400faa0c8441053718627c8dcf58fb12abb386 We plan maintenance on Tuesday, hold onto your hats! Event Type: Storage Upgrade Start Time: 2024-11-26 2:00:00 UTC 開始時刻 2024/11/26 11:00:00 日本時間 End Time: 2024-11-26 3:00:00 UTC 終了時刻 2024/11/26 12:00:00 日本時間 https://status.shc.kanagawa.jp/incident/467754 Tue, 26 Nov 2024 02:00:30 -0000 https://status.shc.kanagawa.jp/incident/467754#f0027446fc3c879b60ec4286fd400faa0c8441053718627c8dcf58fb12abb386 We plan maintenance on Tuesday, hold onto your hats! Event Type: Storage Upgrade Start Time: 2024-11-26 2:00:00 UTC 開始時刻 2024/11/26 11:00:00 日本時間 End Time: 2024-11-26 3:00:00 UTC 終了時刻 2024/11/26 12:00:00 日本時間 https://status.shc.kanagawa.jp/incident/467754 Tue, 26 Nov 2024 02:00:30 -0000 https://status.shc.kanagawa.jp/incident/467754#f0027446fc3c879b60ec4286fd400faa0c8441053718627c8dcf58fb12abb386 We plan maintenance on Tuesday, hold onto your hats! Event Type: Storage Upgrade Start Time: 2024-11-26 2:00:00 UTC 開始時刻 2024/11/26 11:00:00 日本時間 End Time: 2024-11-26 3:00:00 UTC 終了時刻 2024/11/26 12:00:00 日本時間 https://status.shc.kanagawa.jp/incident/467754 Tue, 26 Nov 2024 02:00:30 -0000 https://status.shc.kanagawa.jp/incident/467754#f0027446fc3c879b60ec4286fd400faa0c8441053718627c8dcf58fb12abb386 We plan maintenance on Tuesday, hold onto your hats! Event Type: Storage Upgrade Start Time: 2024-11-26 2:00:00 UTC 開始時刻 2024/11/26 11:00:00 日本時間 End Time: 2024-11-26 3:00:00 UTC 終了時刻 2024/11/26 12:00:00 日本時間 https://status.shc.kanagawa.jp/incident/466866 Sun, 24 Nov 2024 10:33:17 -0000 https://status.shc.kanagawa.jp/incident/466866#da288fa0a1f669c4c6010c1463851b9ecb66f3f7e4ce9643d0a5c9a143567c0f Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/466866 Sun, 24 Nov 2024 10:32:20 -0000 https://status.shc.kanagawa.jp/incident/466866#5b34a81971319c815eadaf5e40981d311c7ed46783a177c75a49e5ccb7f73464 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/466461 Sat, 23 Nov 2024 09:15:18 -0000 https://status.shc.kanagawa.jp/incident/466461#b00315de6d288a019455ac400c2fcbafa81ab8ab23b301556faeeb10e3cf65bf Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/466461 Sat, 23 Nov 2024 09:14:30 -0000 https://status.shc.kanagawa.jp/incident/466461#441f784da8fd72666940d008b2f4782008d482c4d612a38db9a7844f321f3649 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/464457 Wed, 20 Nov 2024 10:57:31 -0000 https://status.shc.kanagawa.jp/incident/464457#7b2e1292f57c1a357d97b3e2955540ade948f16b451be97de5ead515655d6fdc Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/464457 Wed, 20 Nov 2024 10:56:39 -0000 https://status.shc.kanagawa.jp/incident/464457#fa4dd720bb4ab293c0e055ebc83a54b4caa83850ffed69e996cd8b2babad51a9 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/464457 Wed, 20 Nov 2024 02:16:20 -0000 https://status.shc.kanagawa.jp/incident/464457#577075ca93740dea6593f899715058241d6b6924193f85edcf3d8a7d676ac4de Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/464457 Wed, 20 Nov 2024 02:14:20 -0000 https://status.shc.kanagawa.jp/incident/464457#f2c42d11d80c4dd3fab660009b7e81d962b3dbb10f2b0a46ef730ef2bd8d27bc NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/464457 Wed, 20 Nov 2024 02:13:49 -0000 https://status.shc.kanagawa.jp/incident/464457#b6ec0665bc5c5ae232dcbe87a7a8639230745999c33810963c2730b4079b97b9 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/464457 Wed, 20 Nov 2024 02:13:21 -0000 https://status.shc.kanagawa.jp/incident/464457#f17ecf1366d6c3f3a5ab9f220249b086f047464076addc9493dd7f0128da43a7 Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/464457 Wed, 20 Nov 2024 02:07:21 -0000 https://status.shc.kanagawa.jp/incident/464457#e2bda6459d0a04c015533a8bc59cac0d87fcc2a99f9874b710fc6164c33f5f5e Pleroma(pr.shc.kanagawa.jp) and NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/464457 Wed, 20 Nov 2024 02:07:21 -0000 https://status.shc.kanagawa.jp/incident/464457#e2bda6459d0a04c015533a8bc59cac0d87fcc2a99f9874b710fc6164c33f5f5e Pleroma(pr.shc.kanagawa.jp) and NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/464457 Wed, 20 Nov 2024 02:07:10 -0000 https://status.shc.kanagawa.jp/incident/464457#c215dee71866996e26072ef27f9a128a70e8fcf6e35d4d5e189115c33380fbda Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/464457 Wed, 20 Nov 2024 02:07:10 -0000 https://status.shc.kanagawa.jp/incident/464457#c215dee71866996e26072ef27f9a128a70e8fcf6e35d4d5e189115c33380fbda Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/463460 Mon, 18 Nov 2024 11:27:31 -0000 https://status.shc.kanagawa.jp/incident/463460#982b17ff3f07a4841df080f9fa641b48ebb27ced64fdcd21df2a55a36326fbe8 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/463460 Mon, 18 Nov 2024 11:26:44 -0000 https://status.shc.kanagawa.jp/incident/463460#51379ff40a93e2e35cb06a5d0021cb24a265d207c2d4dd7848a8b40b2b70c927 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/461903 Fri, 15 Nov 2024 07:09:33 -0000 https://status.shc.kanagawa.jp/incident/461903#e7675e0a9e1c3cd42d01fab7479420c8bad1776115157a3ac2d6d10378bc9ba1 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/461903 Fri, 15 Nov 2024 07:08:41 -0000 https://status.shc.kanagawa.jp/incident/461903#f0658ddcce895175055a5aa9c815784428b4c31928a4a76762658b86bf0025e7 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/460631 Wed, 13 Nov 2024 07:44:07 -0000 https://status.shc.kanagawa.jp/incident/460631#0bb516631ebfca957de80bc51b2942d980856b7f7bc20be43a463e5ade19c22d Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/460631 Wed, 13 Nov 2024 07:43:05 -0000 https://status.shc.kanagawa.jp/incident/460631#a944acfdbcd85a1df83e28c216192417263b37f1a1cf8978a005a5e28f2974d7 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/459960 Tue, 12 Nov 2024 10:30:05 -0000 https://status.shc.kanagawa.jp/incident/459960#bb89481c8c283b2c71c63fc06706a482b6f486139adec0ca3f5e4446b772714c Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/459960 Tue, 12 Nov 2024 10:29:06 -0000 https://status.shc.kanagawa.jp/incident/459960#3afa43c2e1ec96c7955e2712163c7e30c686a9bb4476b99c9264eff97e1b4e76 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/458099 Mon, 11 Nov 2024 21:00:00 -0000 https://status.shc.kanagawa.jp/incident/458099#af3f4c1e666889cbe68007e75669c372e243ece1f4831186f28f538ae024e8d7 Maintenance completed https://status.shc.kanagawa.jp/incident/458099 Mon, 11 Nov 2024 19:00:00 -0000 https://status.shc.kanagawa.jp/incident/458099#20941d3a90b6c47c156c5705d916e1368a1fdb414093aeda357908557ff4db84 We plan maintenance on Tuesday, hold onto your hats! Event Type: Network Upgrade Start Time: 2024-11-11 19:00:00 UTC 開始時刻 2024/11/12 4:00:00 日本時間 End Time: 2024-11-11 21:00:00 UTC 終了時刻 2024/11/12 6:00:00 日本時間 We schedule higher impact maintenance events during off-peak times to reduce impact to customer infrastructure. Our engineers make every effort to minimize system impact, however, network reachability to instances may be affected for some, or all, of the scheduled maintenance window as we perform this work. While it’s important to be aware of start and end times of the maintenance window, due to our redundant network architecture, our engineers expect that you may see little to no impact at all while the work is performed. https://status.shc.kanagawa.jp/incident/459403 Mon, 11 Nov 2024 10:29:39 -0000 https://status.shc.kanagawa.jp/incident/459403#d68cfe357db5fd326fcab44b41262d8e30e11ffb9bd67a05a25aea26860b68c1 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/459403 Mon, 11 Nov 2024 10:28:33 -0000 https://status.shc.kanagawa.jp/incident/459403#a8dd2492a0735c67effa540d8babea4298e95054652ede3d21ff3a6bdedee334 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/458939 Sun, 10 Nov 2024 09:46:29 -0000 https://status.shc.kanagawa.jp/incident/458939#b48654ea6442fbcc6c19b84e91324b34d779b0e73062b811b8820fd5845219b4 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/458939 Sun, 10 Nov 2024 09:10:21 -0000 https://status.shc.kanagawa.jp/incident/458939#1401efc57e57d0f3c87933e16a0c6545203067bc3f43b32f9b909bc5a884aaad Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/458939 Sun, 10 Nov 2024 09:09:50 -0000 https://status.shc.kanagawa.jp/incident/458939#c2289bc845f4ba4619531860a004721836095f353b4471f421bc9040b0df28f0 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/458939 Sun, 10 Nov 2024 08:09:34 -0000 https://status.shc.kanagawa.jp/incident/458939#821d6934972bcb07628ec8d3b7e54a6c7e5eac35a7e664e945a6621ea8a168d2 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/457488 Thu, 07 Nov 2024 10:28:49 -0000 https://status.shc.kanagawa.jp/incident/457488#4e64b9ab62fea76005d5984896fcef369ed7f35a95a58969727f89d2527aae9b Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/457488 Thu, 07 Nov 2024 10:27:42 -0000 https://status.shc.kanagawa.jp/incident/457488#5c6be4dec8998a982c3685e589de20bc429f0721f292fad3a73321a158674b92 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/457488 Thu, 07 Nov 2024 10:19:49 -0000 https://status.shc.kanagawa.jp/incident/457488#e19dd78e279e0093f5b409e3cdc44e47834f5a129614e8f787eded681b2691dd Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/457488 Thu, 07 Nov 2024 10:18:50 -0000 https://status.shc.kanagawa.jp/incident/457488#0a82732ec5f0da7239b573115f3172761d6e968367c0249e7af228be32914171 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/457488 Thu, 07 Nov 2024 10:13:43 -0000 https://status.shc.kanagawa.jp/incident/457488#4674d3e8119f968b0234f1cc832e0b0f5bd3f83d4a4638fb62e22f9119ec927c Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/457488 Thu, 07 Nov 2024 10:12:55 -0000 https://status.shc.kanagawa.jp/incident/457488#528ec411a74ee5d24f61f8d625a5aed9491169f90c3b69ef2063c7d5c0e0df03 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/457103 Wed, 06 Nov 2024 18:42:49 -0000 https://status.shc.kanagawa.jp/incident/457103#d83dd0f1ec6dc072998c166f83905e930dd0b8b29f735dca36492b6fdcbde368 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/457103 Wed, 06 Nov 2024 18:35:44 -0000 https://status.shc.kanagawa.jp/incident/457103#9c721f760b28b6a5868b432640e82d165938217bced2379829a9d3f521f9cde4 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/455640 Tue, 05 Nov 2024 06:00:42 -0000 https://status.shc.kanagawa.jp/incident/455640#1acd3d567ae6902fb8629aa561ffea0454c31a6a6819bdb99d07344807fc4fba Maintenance completed https://status.shc.kanagawa.jp/incident/456172 Tue, 05 Nov 2024 05:07:01 -0000 https://status.shc.kanagawa.jp/incident/456172#b582e3073ff198970c52f87b959732471ebcb0e9f48ee3449d3ca875f1737632 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/456172 Tue, 05 Nov 2024 05:06:11 -0000 https://status.shc.kanagawa.jp/incident/456172#44e3ff97f3bcbe85916cf15a0d7ebb864b074e4b5f5d3e029606a7da70add480 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/455640 Mon, 04 Nov 2024 16:00:42 -0000 https://status.shc.kanagawa.jp/incident/455640#53a2c4b6a089fedd899ad51f5565a2991ac89c975e1f6ea20f43e92271aba52c We plan maintenance on Tuesday, hold onto your hats! Our Cloud Storage team will be performing upgrades to our Object Storage infrastructure starting at 2024-11-04 16:00:00 UTC. During this maintenance window, creating, attaching, and deletion of Drive files may be temporarily unavailable. Start Time: 2024-11-04 16:00:00 UTC 開始時刻: 2024/11/05 1:00:00 日本時間 End Time: 2024-11-04 18:00:00 UTC 終了時刻: 2024/11/05 3:00:00 日本時間 https://status.shc.kanagawa.jp/incident/455349 Sun, 03 Nov 2024 21:56:58 -0000 https://status.shc.kanagawa.jp/incident/455349#b41a1a050ee21099ec4f70aad9783cb36ae8e7c7bf7c82a365ae37f73e475467 demo.shc.kanagawa.jp Initialize recovered. https://status.shc.kanagawa.jp/incident/455349 Sun, 03 Nov 2024 21:29:19 -0000 https://status.shc.kanagawa.jp/incident/455349#a249eff7b6fbc4f86dd463a22b3aa7a97edf4eae476b4038dfb4e5354399591d demo.shc.kanagawa.jp Initialize went down. https://status.shc.kanagawa.jp/incident/454758 Sat, 02 Nov 2024 05:46:17 -0000 https://status.shc.kanagawa.jp/incident/454758#02ba8c3ee81955fc7b46b05c5aa49500bdfe40b4ac1370ebf38e22518272a9c9 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/454758 Sat, 02 Nov 2024 05:45:16 -0000 https://status.shc.kanagawa.jp/incident/454758#10606f68e0cf1e9d409fa10d471c9ef049a580f3aa00ec4993105c14a19571d0 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/451469 Sun, 27 Oct 2024 18:37:33 -0000 https://status.shc.kanagawa.jp/incident/451469#160b7499bdb037e7081a4c77d0229d0160c14fe4040bd21aef705cba215a4b0f NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/451469 Sun, 27 Oct 2024 18:36:37 -0000 https://status.shc.kanagawa.jp/incident/451469#c67eb7b7e2cd007be5d99f0dfc3c7534989c0f47fab534e292bd316a2f28b813 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/449300 Wed, 23 Oct 2024 10:24:34 -0000 https://status.shc.kanagawa.jp/incident/449300#2a00eb49c6351af404e336d340a0336f3c9a4a51db90084a8ef049e7921d3bcb Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/449300 Wed, 23 Oct 2024 10:23:33 -0000 https://status.shc.kanagawa.jp/incident/449300#89e4f4caa9db545378c81e2581646d07285d9ae40fdf2df10cf3db45351a45e8 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/447482 Sun, 20 Oct 2024 05:01:42 -0000 https://status.shc.kanagawa.jp/incident/447482#ceb92ff1b0300aa3e9a41f2067193a642943dbeea279584413c3ad9ff3313538 demo.shc.kanagawa.jp Initialize recovered. https://status.shc.kanagawa.jp/incident/447482 Sun, 20 Oct 2024 02:28:24 -0000 https://status.shc.kanagawa.jp/incident/447482#a6d236b9e6e528c3d9065b87db7e0eb6991f06fad840824e802af20014925c8f demo.shc.kanagawa.jp Initialize went down. https://status.shc.kanagawa.jp/incident/446138 Thu, 17 Oct 2024 10:22:58 -0000 https://status.shc.kanagawa.jp/incident/446138#466832b2c946107cc5b8fe88057978fd1c40845cc036a2788d52259974b9b524 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/446138 Thu, 17 Oct 2024 10:21:54 -0000 https://status.shc.kanagawa.jp/incident/446138#6cfd5dc5beb5ffb59621f892c53aceedd1b2a1a22c8a8395951aa55082a36d3f Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/442147 Thu, 10 Oct 2024 01:56:49 -0000 https://status.shc.kanagawa.jp/incident/442147#1471bf67836bf2c319ad954d0e4b4b7b3493e7c89b908c2bfd422fc89a8eb25b Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/442147 Thu, 10 Oct 2024 01:56:49 -0000 https://status.shc.kanagawa.jp/incident/442147#1471bf67836bf2c319ad954d0e4b4b7b3493e7c89b908c2bfd422fc89a8eb25b Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/442147 Thu, 10 Oct 2024 01:54:49 -0000 https://status.shc.kanagawa.jp/incident/442147#4323263a58f6a9eb78ce3475b166dd72d81851f321d4d7654930daa38ac06e94 NextCloud (cloud.shc.kanagawa.jp) and ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/442147 Thu, 10 Oct 2024 01:54:49 -0000 https://status.shc.kanagawa.jp/incident/442147#4323263a58f6a9eb78ce3475b166dd72d81851f321d4d7654930daa38ac06e94 NextCloud (cloud.shc.kanagawa.jp) and ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/442147 Thu, 10 Oct 2024 01:54:29 -0000 https://status.shc.kanagawa.jp/incident/442147#887f143a3cd48759234e191e99664f710271a22c5863057820835855ffc5ddc0 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/442147 Thu, 10 Oct 2024 01:29:52 -0000 https://status.shc.kanagawa.jp/incident/442147#c838c60b295037ab10e4b8f5df3edc11dad1af3bdf8533cdbf5862e2d444fe87 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/442147 Thu, 10 Oct 2024 01:29:41 -0000 https://status.shc.kanagawa.jp/incident/442147#0d586b90c2b54c61ef70661d5f475eb1cbe76d67aacf0ad93ee5ccb1b1df92d7 Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/442147 Thu, 10 Oct 2024 01:28:59 -0000 https://status.shc.kanagawa.jp/incident/442147#dfc2aae988859379438d4457522d3b90d7297dc27d740cd3e4466fba4e00eb0b ownCloud (share.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/442147 Thu, 10 Oct 2024 01:27:51 -0000 https://status.shc.kanagawa.jp/incident/442147#2f7bfe19ad6ec7e6954420d155a0d1a0ecf1ec308a7d7ad666a8611e3f6934fe NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/442147 Thu, 10 Oct 2024 01:27:29 -0000 https://status.shc.kanagawa.jp/incident/442147#571e9bc94c9b6914c6d6f30e1562e121efe519caa2203ce2e441b1c629f103b0 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/441083 Wed, 09 Oct 2024 10:21:12 -0000 https://status.shc.kanagawa.jp/incident/441083#da78b597d4e57c435511d6cdce394a9be1e858867d9cb58ddc20220e88bb04ec Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/441083 Wed, 09 Oct 2024 09:10:40 -0000 https://status.shc.kanagawa.jp/incident/441083#8f98c2f499d2fa6b5debe028a9a8863728f79b6862669741c26c2cd7dc0df86f Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/441083 Wed, 09 Oct 2024 09:03:22 -0000 https://status.shc.kanagawa.jp/incident/441083#e2939f175a725b8ad93a74483a5c67c6a26105a3d9ccc6a1dcf404b86f1ec9a7 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/441083 Wed, 09 Oct 2024 06:21:20 -0000 https://status.shc.kanagawa.jp/incident/441083#aae1ef2fbb0ea264173c1d442e70d71e2fa22457a3327e7c43fbb9884ea0207e Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/441083 Wed, 09 Oct 2024 06:09:57 -0000 https://status.shc.kanagawa.jp/incident/441083#6a3dc58fffe0e9420b8ff15af981007f3f95aa5bfcb480dfd392769e0eaac76f Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/441083 Wed, 09 Oct 2024 05:06:45 -0000 https://status.shc.kanagawa.jp/incident/441083#6f87571e86a843bc60648158df571c7ef4e3aae6e39161400fe306e81294cf18 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/441083 Wed, 09 Oct 2024 04:40:15 -0000 https://status.shc.kanagawa.jp/incident/441083#3ae0e898e4f21b5be8accea0dde766f086d8df5a32bea17865408f023892723d Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/441083 Wed, 09 Oct 2024 04:09:44 -0000 https://status.shc.kanagawa.jp/incident/441083#1a226d4ecb2ba4e7a21caec43e67ffb0abe20cf545b48c9d929433f4d85a77d1 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/441083 Wed, 09 Oct 2024 04:04:35 -0000 https://status.shc.kanagawa.jp/incident/441083#47d6f0aed83e1151c4b129c61bd5817db081b09e5e8a12b29707c54f4a7dea2d Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/441083 Wed, 09 Oct 2024 04:03:35 -0000 https://status.shc.kanagawa.jp/incident/441083#286d0a20c20be07ff5be47f70ffac4c675e516fb8d9096d6f7f4ff55f8ce9af3 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/441083 Wed, 09 Oct 2024 03:58:29 -0000 https://status.shc.kanagawa.jp/incident/441083#abc3f3adfcd3e8c8d13b280f2c2f774f87ea172634d23a638884f997c73f863b Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/441083 Wed, 09 Oct 2024 03:09:19 -0000 https://status.shc.kanagawa.jp/incident/441083#ff231faa8325d39d52877419428b44a6728806185e4b1e7c6c2789e440e61168 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/441083 Wed, 09 Oct 2024 02:52:22 -0000 https://status.shc.kanagawa.jp/incident/441083#b55ff9dae63291aa22316fac4044e9c8195bf9e86d2d60ef90f5a787bc193d9c Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/441083 Wed, 09 Oct 2024 02:15:49 -0000 https://status.shc.kanagawa.jp/incident/441083#3a0ac5773c5a7b278eac8bfe04b5b77e8593d818280746fe3b5da05b8147261d Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/441083 Wed, 09 Oct 2024 01:55:19 -0000 https://status.shc.kanagawa.jp/incident/441083#2cd779d8f2e83a1351d844383894d48f85d488347c7310fa1ef7e8f2e514159d Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/441083 Wed, 09 Oct 2024 01:18:32 -0000 https://status.shc.kanagawa.jp/incident/441083#884f08223237860305bd1471227924360566285e2f3732ecda03122b546b3f8a Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/441083 Wed, 09 Oct 2024 01:13:13 -0000 https://status.shc.kanagawa.jp/incident/441083#309b024f679b1a0e5bfc60912738dff45f2f98963d64ed34e084f433761429cb Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/441083 Wed, 09 Oct 2024 01:09:35 -0000 https://status.shc.kanagawa.jp/incident/441083#501f092450e404d9aa4797feeb0c1df12a09de5a905aee810c14ae90c21cebed Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/441083 Wed, 09 Oct 2024 01:04:34 -0000 https://status.shc.kanagawa.jp/incident/441083#264b172e0a481c6ea589e5ca7632370074706e8eea7c8c379400a9d9bad07693 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/441083 Tue, 08 Oct 2024 21:27:32 -0000 https://status.shc.kanagawa.jp/incident/441083#e06dd4fa3cc8d2fafc1ec35b6f7ff6df91c04027855e566304785e5b1b68f1ec Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/441083 Tue, 08 Oct 2024 21:22:29 -0000 https://status.shc.kanagawa.jp/incident/441083#2ab998bc638543db310b160e671ea0bc84807889fd88bbba90530be54187ae63 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/441083 Tue, 08 Oct 2024 20:50:46 -0000 https://status.shc.kanagawa.jp/incident/441083#b4aa24801dacb92954bf0b726a08595b9dc4fc49e6d6a798a950cd32d63c155e Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/441083 Tue, 08 Oct 2024 20:40:09 -0000 https://status.shc.kanagawa.jp/incident/441083#5716ba2f01576bf9d6ca66f115ceadda8d4989e170fad5d443c5413d528763ad Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/441083 Tue, 08 Oct 2024 18:42:30 -0000 https://status.shc.kanagawa.jp/incident/441083#cb3aedf92fbd6d2c663b5aacd610449fc6874ba2072506bda092a0ebce06bc86 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/441083 Tue, 08 Oct 2024 18:37:16 -0000 https://status.shc.kanagawa.jp/incident/441083#467d1c9debfc13a924b944e26d4c0f97f871dce65ec7e8712c272b1f304ffdee Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/441083 Tue, 08 Oct 2024 18:00:27 -0000 https://status.shc.kanagawa.jp/incident/441083#4c8bd51617118cd9e9fbe74b8c01f7c7c238168b35b9db6c356ff698142425b2 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/441083 Tue, 08 Oct 2024 17:43:08 -0000 https://status.shc.kanagawa.jp/incident/441083#698dcac88e9848a5719ad1f80d9bec033e1ca292d6fc7de1b9cebb8a740823c3 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/441083 Tue, 08 Oct 2024 17:41:43 -0000 https://status.shc.kanagawa.jp/incident/441083#2fd6ec8e5de29269657b59faef02de2c47d0ccb8e439a5c839ad3cacd394fa36 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/441083 Tue, 08 Oct 2024 17:21:44 -0000 https://status.shc.kanagawa.jp/incident/441083#cbdbea3285872c3cf180ce450dab0760c3e83da48f98462a0776189b7fe26805 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/441083 Tue, 08 Oct 2024 10:03:17 -0000 https://status.shc.kanagawa.jp/incident/441083#6c229c866100a785501885698ac9c86f3e15a9acce4d4632e8764a9ea3010946 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/441083 Tue, 08 Oct 2024 09:50:10 -0000 https://status.shc.kanagawa.jp/incident/441083#f059d1be03d8b70ac3248fef8d72c0ff10b43afb99e195a63df361653f5c434c Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/441083 Tue, 08 Oct 2024 09:28:20 -0000 https://status.shc.kanagawa.jp/incident/441083#666a0b02e324963c67b318b06e23c1c7ea6aed75e431b54f05ffa1f9d0538530 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/441083 Tue, 08 Oct 2024 09:19:57 -0000 https://status.shc.kanagawa.jp/incident/441083#29028857b66ec748f48c4e725a6702dc936fea241bfc5f3048e697bc728ab473 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/441083 Tue, 08 Oct 2024 09:18:57 -0000 https://status.shc.kanagawa.jp/incident/441083#5ff19e5e0d1dada823e8f63becd0bcc6995e9b6b3a3528ec181de5e95684cb2d Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/441083 Tue, 08 Oct 2024 09:13:30 -0000 https://status.shc.kanagawa.jp/incident/441083#9d8f047ef3150fa75fccefbf31cad2604961ded808d899f962bd1388a3f7eebb Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/441083 Tue, 08 Oct 2024 09:04:07 -0000 https://status.shc.kanagawa.jp/incident/441083#ad39bb90c1bcc5e6e3cfcbb9bf82cb5ac974dc7becfa7b00678da2c6ae929fc9 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/441083 Tue, 08 Oct 2024 08:59:04 -0000 https://status.shc.kanagawa.jp/incident/441083#36d92f03b3517983893a39fea1bded88318d72b38fc7da25a3b611657def5452 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/441083 Tue, 08 Oct 2024 08:24:26 -0000 https://status.shc.kanagawa.jp/incident/441083#dadfdf734fc1409e2410ea2f3e913c1acb0a04285a9a13438ebe7f2e95be03a4 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/440768 Mon, 07 Oct 2024 19:03:03 -0000 https://status.shc.kanagawa.jp/incident/440768#dc5186d6bc2bb222de4e1fb197bdaf5fb2aeb71020c28f87ed77053511577a6e Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/440768 Mon, 07 Oct 2024 18:59:02 -0000 https://status.shc.kanagawa.jp/incident/440768#9254ce9c31e83e926d5fca5e6181533f9660f8fd03367ccd92861df7cbb4746e Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/439833 Sat, 05 Oct 2024 21:54:56 -0000 https://status.shc.kanagawa.jp/incident/439833#742bee7c43606cea1158502eadedc62faab38a8c9a309aed9a5d9eca2813d7be demo.shc.kanagawa.jp Initialize recovered. https://status.shc.kanagawa.jp/incident/439833 Sat, 05 Oct 2024 21:28:18 -0000 https://status.shc.kanagawa.jp/incident/439833#908668db2ef7e25ad8e8ed21fd8d4910b344cc67129da954e9e18ac1518586e7 demo.shc.kanagawa.jp Initialize went down. https://status.shc.kanagawa.jp/incident/436191 Sat, 28 Sep 2024 12:32:41 -0000 https://status.shc.kanagawa.jp/incident/436191#c7f39f4587857d94a05cdbdf915fe9e61f324a2e4bac7197160ac22178945453 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/436191 Sat, 28 Sep 2024 12:28:34 -0000 https://status.shc.kanagawa.jp/incident/436191#2d47a8fb1a2abf89d2722f37802744f3d0db54d3c126d6355c2da63903ecd52b Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/431187 Wed, 18 Sep 2024 17:09:50 -0000 https://status.shc.kanagawa.jp/incident/431187#f17eac4f55a9bb46658b942e246007805c15d8de3c1a4ee941f3384d49f556f9 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/431187 Wed, 18 Sep 2024 17:06:34 -0000 https://status.shc.kanagawa.jp/incident/431187#acfaef42cc0483dd35e78e94aaca6d715d42bb2e01260ecbf8f716f7649fc073 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/429613 Sun, 15 Sep 2024 22:48:26 -0000 https://status.shc.kanagawa.jp/incident/429613#8d6e6f4c7bf4220aa634b0961bf1c1129f71eee6123f3a01a37a143f96dd6625 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/429613 Sun, 15 Sep 2024 22:39:21 -0000 https://status.shc.kanagawa.jp/incident/429613#bff5339372bd8265a37cfdd316093b9c4d992bd85db99db7ab49fdbb6ea8405a Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/427035 Tue, 10 Sep 2024 11:05:57 -0000 https://status.shc.kanagawa.jp/incident/427035#d423b9264cee11fb3eafc2a513a882946ac4ea0ac7bfceaafd68f7ef7d1f44f1 NextCloud (cloud.shc.kanagawa.jp) and ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/427035 Tue, 10 Sep 2024 11:05:57 -0000 https://status.shc.kanagawa.jp/incident/427035#d423b9264cee11fb3eafc2a513a882946ac4ea0ac7bfceaafd68f7ef7d1f44f1 NextCloud (cloud.shc.kanagawa.jp) and ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/427035 Tue, 10 Sep 2024 11:05:37 -0000 https://status.shc.kanagawa.jp/incident/427035#88e370ba2b8e27875ac243f98b6d859eab76f4113d4091ce4ac63c622e07d0e9 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/427035 Tue, 10 Sep 2024 11:04:55 -0000 https://status.shc.kanagawa.jp/incident/427035#ef2b26df5e8428e6199a76dfaf7eaabd896ecfbf7dfbefec00aa1f210ff71583 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/427035 Tue, 10 Sep 2024 11:04:55 -0000 https://status.shc.kanagawa.jp/incident/427035#ef2b26df5e8428e6199a76dfaf7eaabd896ecfbf7dfbefec00aa1f210ff71583 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/427035 Tue, 10 Sep 2024 11:04:12 -0000 https://status.shc.kanagawa.jp/incident/427035#d2fa17042ab4ef88a6263f83a942ed2254830d110d4bcdb89b9afb556d0c8f84 ownCloud (share.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/427035 Tue, 10 Sep 2024 11:03:03 -0000 https://status.shc.kanagawa.jp/incident/427035#27376834ed5333c73b7b11901065e27fb65a7d9a032c44c38b53ac6a46333fe4 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/427035 Tue, 10 Sep 2024 11:02:39 -0000 https://status.shc.kanagawa.jp/incident/427035#10b412c1cf1c3b38a6e85e9dc09b06c8ae0a156ef00dc6ae510c00ee0d1b18de Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/427035 Tue, 10 Sep 2024 11:01:43 -0000 https://status.shc.kanagawa.jp/incident/427035#9d078c20057599b93d73e30050198e6c060e3895547def39ac1f9a0d11726360 Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/427035 Tue, 10 Sep 2024 10:56:56 -0000 https://status.shc.kanagawa.jp/incident/427035#9ada4fac37c5b8dee0c0abe19dbac86992b329c648c504bf6b7f2f370ac0c7ff NextCloud (cloud.shc.kanagawa.jp) and ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/427035 Tue, 10 Sep 2024 10:56:56 -0000 https://status.shc.kanagawa.jp/incident/427035#9ada4fac37c5b8dee0c0abe19dbac86992b329c648c504bf6b7f2f370ac0c7ff NextCloud (cloud.shc.kanagawa.jp) and ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/427035 Tue, 10 Sep 2024 10:56:24 -0000 https://status.shc.kanagawa.jp/incident/427035#60daa6996847b930e00622260de3f3c8864da03f2b77760665bf94119533b538 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/427035 Tue, 10 Sep 2024 10:55:45 -0000 https://status.shc.kanagawa.jp/incident/427035#83017a309c4e4497741db9327c300168a8f7f6c8f52c4fa0c218630859033a5f Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/427035 Tue, 10 Sep 2024 10:55:03 -0000 https://status.shc.kanagawa.jp/incident/427035#f033dd3fb6827128a345cf4da673c343400ee63dd1c03154fc5ea252fd329a89 ownCloud (share.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/427035 Tue, 10 Sep 2024 10:53:49 -0000 https://status.shc.kanagawa.jp/incident/427035#9d3215779b7206444c28822a2c130a005e80e9997101c7009a32810108e5b4a6 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/427035 Tue, 10 Sep 2024 10:53:25 -0000 https://status.shc.kanagawa.jp/incident/427035#d3ebafe9ad1eef927ed6849a2d53bc0ff2049738eb94069acce1d33ed7003d1b Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/427035 Tue, 10 Sep 2024 10:52:58 -0000 https://status.shc.kanagawa.jp/incident/427035#a7a4ba27e42ae4efbec2b4ddee0a4c6a90633574ff6cfb5f60be5aad0b0e1af7 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/427035 Tue, 10 Sep 2024 10:52:38 -0000 https://status.shc.kanagawa.jp/incident/427035#68ec38b46fceed14d79cd065b016e8b0244f5d2a691d6547405257a126303c67 Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/425676 Sat, 07 Sep 2024 18:39:43 -0000 https://status.shc.kanagawa.jp/incident/425676#fc058b220ee5472561f7daa5b85c1c7acce2e8523f48a7f0e7e3d2c2c416503e Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/425676 Sat, 07 Sep 2024 18:35:32 -0000 https://status.shc.kanagawa.jp/incident/425676#c19fe2708f409e6a31b657b700a4954077fb47d9307b13fd1e296ddb8ea1ebb8 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/423836 Wed, 04 Sep 2024 03:26:04 -0000 https://status.shc.kanagawa.jp/incident/423836#2c64d0c48e300f2ce05211f74fb81d87274f8b333536364d8509a86791a22706 ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/423836 Wed, 04 Sep 2024 03:25:38 -0000 https://status.shc.kanagawa.jp/incident/423836#e3d7959085baac79de495cbc47d6528b04c53be8f3ff67e2eac3088ef75cdc69 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/423836 Wed, 04 Sep 2024 03:25:05 -0000 https://status.shc.kanagawa.jp/incident/423836#203b4d83034694c5c38197baa1ee68e9996fe4ec56da9618ae9204f97083e407 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/423836 Wed, 04 Sep 2024 03:25:05 -0000 https://status.shc.kanagawa.jp/incident/423836#203b4d83034694c5c38197baa1ee68e9996fe4ec56da9618ae9204f97083e407 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/423836 Wed, 04 Sep 2024 03:24:43 -0000 https://status.shc.kanagawa.jp/incident/423836#160eb573f06d9c5a2c520bd02a13efdc89ed4ab46f91d44084b0122ff297908b NextCloud Maintenance recovered. https://status.shc.kanagawa.jp/incident/423836 Wed, 04 Sep 2024 03:23:30 -0000 https://status.shc.kanagawa.jp/incident/423836#0806f8b805d9f767bf5057e5805f02542a6c1217299c419c6936880267f77ce7 NextCloud Maintenance went down. https://status.shc.kanagawa.jp/incident/423836 Wed, 04 Sep 2024 03:23:17 -0000 https://status.shc.kanagawa.jp/incident/423836#cc16b1f597748904e124f95bfd934d4bd862f0f4d7f0844f45933ba0512d0da8 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/423836 Wed, 04 Sep 2024 03:19:05 -0000 https://status.shc.kanagawa.jp/incident/423836#9b6a8c4a3980fa892fd18265f24c447833fee3ffb7efe99ba1258405cabbeacf ownCloud (share.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/423836 Wed, 04 Sep 2024 03:13:44 -0000 https://status.shc.kanagawa.jp/incident/423836#14094b8a428179188095e8ae3f63b9673d551edd2beda4674181dc4d8bfdf321 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/423836 Wed, 04 Sep 2024 03:13:21 -0000 https://status.shc.kanagawa.jp/incident/423836#f3a8b1540c94a911513b1e83d987db086d7152d7bafac54e41774a18a7daf102 Misskey(mk.shc.kanagawa.jp) and NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/423836 Wed, 04 Sep 2024 03:13:21 -0000 https://status.shc.kanagawa.jp/incident/423836#f3a8b1540c94a911513b1e83d987db086d7152d7bafac54e41774a18a7daf102 Misskey(mk.shc.kanagawa.jp) and NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/423836 Wed, 04 Sep 2024 03:12:25 -0000 https://status.shc.kanagawa.jp/incident/423836#213f98accad20767261038a575afb8664d33e559ed40566bc60e4e777a292e8b Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/421623 Fri, 30 Aug 2024 21:56:07 -0000 https://status.shc.kanagawa.jp/incident/421623#312093180bdd4bd5b10f9f4d2675e42777d4accc4c72683d799b2cd96d2dd3f9 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/421623 Fri, 30 Aug 2024 21:55:17 -0000 https://status.shc.kanagawa.jp/incident/421623#556c06d6374e0050c37a6e7c6350f3c9631c7d06a057b4ff9e00c8009990f455 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/421623 Fri, 30 Aug 2024 21:55:17 -0000 https://status.shc.kanagawa.jp/incident/421623#556c06d6374e0050c37a6e7c6350f3c9631c7d06a057b4ff9e00c8009990f455 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/421623 Fri, 30 Aug 2024 21:54:47 -0000 https://status.shc.kanagawa.jp/incident/421623#9a2ddaaa1773f045cd00182779e3faaf9fc97b3be365509e0b6b9aa3e1fac8b8 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/421623 Fri, 30 Aug 2024 21:54:22 -0000 https://status.shc.kanagawa.jp/incident/421623#aac0731a71fd62f8282ac7eecbb7abd1b8bc05565862a340ab7323b895581070 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/421623 Fri, 30 Aug 2024 21:54:22 -0000 https://status.shc.kanagawa.jp/incident/421623#aac0731a71fd62f8282ac7eecbb7abd1b8bc05565862a340ab7323b895581070 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/421623 Fri, 30 Aug 2024 21:53:24 -0000 https://status.shc.kanagawa.jp/incident/421623#b4b2c140ffa4174d7bb60736558bbe20bd30d13d843dceddde1c35fabf60889e NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/421623 Fri, 30 Aug 2024 21:52:25 -0000 https://status.shc.kanagawa.jp/incident/421623#2e1f280a23698264722cb9eb309c5aa3f17289f25541286fb49fa117708e7a00 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/421623 Fri, 30 Aug 2024 06:04:41 -0000 https://status.shc.kanagawa.jp/incident/421623#d53e6b5a5e9a83b28f11d47e4d575815ce858dda95fb6240ee1a56c5a90aa2ef Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/421623 Fri, 30 Aug 2024 06:04:21 -0000 https://status.shc.kanagawa.jp/incident/421623#e736feff810ca3d7d6176ae13f13759d572e64ba92b9ea2b4b877f0cd323e508 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/397892 Sat, 24 Aug 2024 03:22:30 -0000 https://status.shc.kanagawa.jp/incident/397892#13a950f8ee7ab75b00ed38edc2a76517e4f916ceb96f2d6e4ee519c5873ee95a Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/397892 Sat, 24 Aug 2024 03:21:46 -0000 https://status.shc.kanagawa.jp/incident/397892#c5fd32c03980fdf861d59c0056e691347f9143bb304dbe039d4c8588fa68f9a6 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/397892 Wed, 21 Aug 2024 13:10:01 -0000 https://status.shc.kanagawa.jp/incident/397892#faffbc5bfc627f686cf177b79088bb961313c3d91ddeb8cc92b35cdeda508ffa Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/397892 Wed, 21 Aug 2024 13:00:47 -0000 https://status.shc.kanagawa.jp/incident/397892#7b7ccab697b9ca0f28abdd37748dab9de45fcc5628eab8cabb588078f85b99fa Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/397892 Wed, 21 Aug 2024 12:42:06 -0000 https://status.shc.kanagawa.jp/incident/397892#935c631debf0d9617756be6f823b8aca9f887ece00bb5fc4630ff1fd280d483d Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/397892 Wed, 21 Aug 2024 12:32:10 -0000 https://status.shc.kanagawa.jp/incident/397892#ed0a6da4ab9ca21179f1584579c8deade35c1e1f746078f0e4d421560dcf49ae Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/397892 Sat, 17 Aug 2024 05:08:29 -0000 https://status.shc.kanagawa.jp/incident/397892#3a2edb6d87bff73be30d3bcf6e797ba6ba619fb4f09b0249b6a776c938ebec24 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/397892 Sat, 17 Aug 2024 05:08:13 -0000 https://status.shc.kanagawa.jp/incident/397892#5cd7734cdb95ced44a3ebfc90cb861394ae54a593c69d20be29ed4ab165cce96 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/397892 Wed, 14 Aug 2024 21:04:33 -0000 https://status.shc.kanagawa.jp/incident/397892#ac56d1c0b6fe349432af8dde7e035c47bbab41badc865a08d81b0697e216110f Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/397892 Wed, 14 Aug 2024 21:03:49 -0000 https://status.shc.kanagawa.jp/incident/397892#ea78bfffb45882a48d812030608aa8f7742e28dee392f5e2d57a8171c7fc289d Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/397892 Wed, 14 Aug 2024 21:03:49 -0000 https://status.shc.kanagawa.jp/incident/397892#ea78bfffb45882a48d812030608aa8f7742e28dee392f5e2d57a8171c7fc289d Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/397892 Wed, 14 Aug 2024 21:01:33 -0000 https://status.shc.kanagawa.jp/incident/397892#54df43ab2b703e1e7b85ec58817f2356929def709b58251df246ce80fef577ca Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/397892 Wed, 14 Aug 2024 21:00:53 -0000 https://status.shc.kanagawa.jp/incident/397892#740e56546747e9407aadd375746e774767141d8c0cffdbd270bef06ab38d75d4 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/397892 Wed, 14 Aug 2024 21:00:53 -0000 https://status.shc.kanagawa.jp/incident/397892#740e56546747e9407aadd375746e774767141d8c0cffdbd270bef06ab38d75d4 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/397892 Tue, 13 Aug 2024 22:14:59 -0000 https://status.shc.kanagawa.jp/incident/397892#8fedc2f1a9803fe2462e6a1318fd7320bcd67232ba21f1bdca066a2211d83303 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/397892 Tue, 13 Aug 2024 22:13:53 -0000 https://status.shc.kanagawa.jp/incident/397892#7a18120d6f0d71281939f338febbdd88b61e1016a041a090d01c68a053012dc2 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/397892 Tue, 13 Aug 2024 12:42:01 -0000 https://status.shc.kanagawa.jp/incident/397892#2adcff459ae5ed5fedfdac8a5f55eec2383cf7f73f12e7423a11a95d6957582b NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/397892 Tue, 13 Aug 2024 12:41:03 -0000 https://status.shc.kanagawa.jp/incident/397892#b2d335437fe40a72bb13af142379eb82d2fd9ae2277a2b1f607a572b21c41574 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/397892 Thu, 08 Aug 2024 18:45:22 -0000 https://status.shc.kanagawa.jp/incident/397892#7037a253406370d768697e7fe516d6a0f1c406b22ebdff587f9602020fe5b243 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/397892 Thu, 08 Aug 2024 18:08:23 -0000 https://status.shc.kanagawa.jp/incident/397892#4f2624b4ce148f44e437ea8720ba1335ae2c00cee052ecf2f2024c05d1642ab4 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/397892 Sun, 04 Aug 2024 06:56:46 -0000 https://status.shc.kanagawa.jp/incident/397892#33d46abb9d3635aac45a8acf3ab417717f5fc81e77a13b5d237b7b2c6ec370ec Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/397892 Sun, 04 Aug 2024 06:56:27 -0000 https://status.shc.kanagawa.jp/incident/397892#5f8c1e859683a37d55f648a38d6e7e2f1bdb15c5251601866e1baf3ff8dc0ec9 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/397892 Thu, 01 Aug 2024 03:48:14 -0000 https://status.shc.kanagawa.jp/incident/397892#e1427fc7c74e6d013bf4718807e68f7e16c9839f4a9b28d718c662c568e33479 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/397892 Thu, 01 Aug 2024 03:47:15 -0000 https://status.shc.kanagawa.jp/incident/397892#4cf0588abce538765ece8df0f1e9abf033d359b261523a7313398c900ca887e0 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/397892 Sat, 27 Jul 2024 15:12:17 -0000 https://status.shc.kanagawa.jp/incident/397892#802fc6e2ea72b9c457c97d9171da634bce96c45c9e53c75fe3037f66bde63fce Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/397892 Sat, 27 Jul 2024 15:08:54 -0000 https://status.shc.kanagawa.jp/incident/397892#5b8262e1f85594c142bd05bf14614f1372f82f12f3687ff150c18131e57278d9 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/397892 Sat, 27 Jul 2024 08:39:11 -0000 https://status.shc.kanagawa.jp/incident/397892#1dba0d3613854e16c0e2dc6acc8c743e5b4e11dc66aec91c910189af5c0f3694 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/397892 Sat, 27 Jul 2024 08:39:00 -0000 https://status.shc.kanagawa.jp/incident/397892#ecc35bef5d7925bb1f474df1e33ff3fc47daee92286c47a7852ee5fbfaabc422 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/397892 Tue, 23 Jul 2024 07:26:08 -0000 https://status.shc.kanagawa.jp/incident/397892#d0f31a46a51ad41c9b5b7ed01a53303c6d9e116b234780c957bcd456d9ec5e54 NextCloud (cloud.shc.kanagawa.jp) and ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/397892 Tue, 23 Jul 2024 07:26:08 -0000 https://status.shc.kanagawa.jp/incident/397892#d0f31a46a51ad41c9b5b7ed01a53303c6d9e116b234780c957bcd456d9ec5e54 NextCloud (cloud.shc.kanagawa.jp) and ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/397892 Tue, 23 Jul 2024 07:25:51 -0000 https://status.shc.kanagawa.jp/incident/397892#c6954103b1422f1c03b274760bbec4dfcb661b905fe45ed9e35753897e4ea25a Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/397892 Tue, 23 Jul 2024 07:25:06 -0000 https://status.shc.kanagawa.jp/incident/397892#ee66832388d4b1f3a824bbc3f01d22e669da488c7367d28a3eafd3cdba9d72c3 ownCloud (share.shc.kanagawa.jp) went down and Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/397892 Tue, 23 Jul 2024 07:25:06 -0000 https://status.shc.kanagawa.jp/incident/397892#ee66832388d4b1f3a824bbc3f01d22e669da488c7367d28a3eafd3cdba9d72c3 ownCloud (share.shc.kanagawa.jp) went down and Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/397892 Tue, 23 Jul 2024 07:25:06 -0000 https://status.shc.kanagawa.jp/incident/397892#ee66832388d4b1f3a824bbc3f01d22e669da488c7367d28a3eafd3cdba9d72c3 ownCloud (share.shc.kanagawa.jp) went down and Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/397892 Tue, 23 Jul 2024 07:22:09 -0000 https://status.shc.kanagawa.jp/incident/397892#e9b773b83eb8309b6c69d44eeee97259838f3e4259e19495fd7a13596f65e7c0 Misskey(mk.shc.kanagawa.jp) and NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/397892 Tue, 23 Jul 2024 07:22:09 -0000 https://status.shc.kanagawa.jp/incident/397892#e9b773b83eb8309b6c69d44eeee97259838f3e4259e19495fd7a13596f65e7c0 Misskey(mk.shc.kanagawa.jp) and NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/397892 Tue, 23 Jul 2024 07:22:00 -0000 https://status.shc.kanagawa.jp/incident/397892#27098d8f9933116aa42f836a9ba1432d9494ccb1d8b4f6179ac4371461067561 Mastodon(mt.shc.kanagawa.jp) and Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/397892 Tue, 23 Jul 2024 07:22:00 -0000 https://status.shc.kanagawa.jp/incident/397892#27098d8f9933116aa42f836a9ba1432d9494ccb1d8b4f6179ac4371461067561 Mastodon(mt.shc.kanagawa.jp) and Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/397892 Mon, 22 Jul 2024 08:38:24 -0000 https://status.shc.kanagawa.jp/incident/397892#dc2cc258091bfaf4172e3c8c0c45d2b0103b6cf109addab7e812f32443b16703 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/397892 Mon, 22 Jul 2024 08:38:24 -0000 https://status.shc.kanagawa.jp/incident/397892#dc2cc258091bfaf4172e3c8c0c45d2b0103b6cf109addab7e812f32443b16703 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/397892 Mon, 22 Jul 2024 08:07:12 -0000 https://status.shc.kanagawa.jp/incident/397892#35f4913f58193c916666d2d282d67296df7e038ebe6f311c08c732b54bde8e88 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/397892 Mon, 22 Jul 2024 08:07:12 -0000 https://status.shc.kanagawa.jp/incident/397892#35f4913f58193c916666d2d282d67296df7e038ebe6f311c08c732b54bde8e88 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/397892 Mon, 22 Jul 2024 06:17:09 -0000 https://status.shc.kanagawa.jp/incident/397892#4766bdd90d3e0f89648b74b5366403b96b4c6a112bafaa67aea34243343e6f58 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/397892 Mon, 22 Jul 2024 06:13:14 -0000 https://status.shc.kanagawa.jp/incident/397892#facbcaed48995ba5cccca2c1a241c0f3b852a34c332b53b996dfff9991a66b3b Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/397892 Sun, 21 Jul 2024 12:46:07 -0000 https://status.shc.kanagawa.jp/incident/397892#b8785aa7dc92b5688d04d730a5377a1d4214b95f3d7027c8eaf909227e2fec38 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/397892 Sun, 21 Jul 2024 12:46:07 -0000 https://status.shc.kanagawa.jp/incident/397892#b8785aa7dc92b5688d04d730a5377a1d4214b95f3d7027c8eaf909227e2fec38 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/397892 Sun, 21 Jul 2024 10:03:21 -0000 https://status.shc.kanagawa.jp/incident/397892#e416ff6865b0be9dcaeb2f8eb53ebbb1c4477cd6c83032ef1a387554ebdc027c Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/397892 Sun, 21 Jul 2024 10:03:21 -0000 https://status.shc.kanagawa.jp/incident/397892#e416ff6865b0be9dcaeb2f8eb53ebbb1c4477cd6c83032ef1a387554ebdc027c Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/397892 Wed, 17 Jul 2024 07:38:45 -0000 https://status.shc.kanagawa.jp/incident/397892#4e0e03152bfe515bc71b67ecc01e574a06742a7703d6478e0a3491bfba0c640e Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/397892 Wed, 17 Jul 2024 07:35:46 -0000 https://status.shc.kanagawa.jp/incident/397892#b31139a4b80701c9bf7bc976bf26a3276661bd9048b1d64aca3c1a43c6051d80 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/397892 Wed, 17 Jul 2024 07:08:05 -0000 https://status.shc.kanagawa.jp/incident/397892#253b93766851fd13b51cff9e2d8a67f061f4cc32eea29da431c42322018d2ad1 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/397892 Wed, 17 Jul 2024 07:07:48 -0000 https://status.shc.kanagawa.jp/incident/397892#fd42a2224a78ed7fdb11d61a2e13238dff67b8439c736ca5498b6e2637b6660e Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/397892 Sun, 14 Jul 2024 11:22:04 -0000 https://status.shc.kanagawa.jp/incident/397892#e27f76b6792be7cc2a9ba6ff8d0b125331b65342f25a23a0aa968a4cf2d64133 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/397892 Sun, 14 Jul 2024 11:20:49 -0000 https://status.shc.kanagawa.jp/incident/397892#c5c0bef4774ddd949d19b24c80a95cea093a3b361d48634442448cd66711212f NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/397892 Sun, 14 Jul 2024 11:12:52 -0000 https://status.shc.kanagawa.jp/incident/397892#e75eb00187d9864dd2e9aacff8107a8a552621dbefebcefac16359b5adf1b9b7 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/397892 Sun, 14 Jul 2024 11:11:45 -0000 https://status.shc.kanagawa.jp/incident/397892#aa07f130d4bfbbc475a78b2174b7c9ed0377393f32e6ab92695181501e1a4266 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/397892 Sun, 14 Jul 2024 11:02:10 -0000 https://status.shc.kanagawa.jp/incident/397892#5b4868228b4e87e59daf5622274c03c1f0cc523de831d39c7ecb595791cbe597 NextCloud Maintenance recovered. https://status.shc.kanagawa.jp/incident/397892 Sun, 14 Jul 2024 09:51:51 -0000 https://status.shc.kanagawa.jp/incident/397892#25ed259af1bbb0b6e11559017b2d9c2f310c7f33ea4b2ce9b9a061db8bc5cda3 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/397892 Sun, 14 Jul 2024 04:36:37 -0000 https://status.shc.kanagawa.jp/incident/397892#02c2c2bb4b4d1104c95b412ad7645391ab6d4c0ba79205c5c2128f6b60b68b3c NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/397892 Sun, 14 Jul 2024 04:17:45 -0000 https://status.shc.kanagawa.jp/incident/397892#2d1bd082fef8fa414151c613c6db8e208c34797ba75ca67e2a03a1fecd3fa57a NextCloud Maintenance went down. https://status.shc.kanagawa.jp/incident/397892 Sun, 14 Jul 2024 04:15:47 -0000 https://status.shc.kanagawa.jp/incident/397892#703fd85ac14b24a7681ffdee8953984da004c10b91b8d5fb99ef54c62116f3c0 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/397892 Sun, 14 Jul 2024 04:06:37 -0000 https://status.shc.kanagawa.jp/incident/397892#a94104e7c5a28a3fcb6361b8f3b7e9de6d5eed3205c20a91f92237faf519cde4 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/397754 Sat, 13 Jul 2024 18:21:27 -0000 https://status.shc.kanagawa.jp/incident/397754#42a155ea498bd8e95937c8a053801945acc368dbbcfdc88aec68a668536d7a1d ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/397754 Sat, 13 Jul 2024 18:20:56 -0000 https://status.shc.kanagawa.jp/incident/397754#a346ba9fc7405b9b9b8cf251e69e7846956eff8ad811ddfce7504057a23bdefe Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/397754 Sat, 13 Jul 2024 18:20:35 -0000 https://status.shc.kanagawa.jp/incident/397754#e54c190988d0701d2cb35017c08d4d1a9776431a8d022c217d3612bb61d38713 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/397754 Sat, 13 Jul 2024 18:20:16 -0000 https://status.shc.kanagawa.jp/incident/397754#e68e599acff6b35d22bf3d7ce421c47460d96293a081331d65eeb6870b977ebf Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/397754 Sat, 13 Jul 2024 18:11:10 -0000 https://status.shc.kanagawa.jp/incident/397754#c2e3af41b6d77d75840bd2f9c2408e8ad578338381a8351f39437e1065cb6e5b ownCloud (share.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/397754 Sat, 13 Jul 2024 18:08:28 -0000 https://status.shc.kanagawa.jp/incident/397754#af69cb6e40022923461d2d81dfa17002d6ebe4c2933f17f59498874ee9d36163 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/397754 Sat, 13 Jul 2024 18:07:52 -0000 https://status.shc.kanagawa.jp/incident/397754#5ccf08ba6827fa008466138ea22f8cce11fd4ad391d47e0b4b18420c5f7c6ab6 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/397754 Sat, 13 Jul 2024 18:07:21 -0000 https://status.shc.kanagawa.jp/incident/397754#0772497681b219d1450ad390d4349bf2fbcd65d254a077f558a1c26244fe6736 Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/396636 Thu, 11 Jul 2024 08:15:26 -0000 https://status.shc.kanagawa.jp/incident/396636#12a30aa95f4307b2fcada6b4aebb8c089f128a3d0f5c3e3b5cab1240117c433f NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/396636 Thu, 11 Jul 2024 08:06:15 -0000 https://status.shc.kanagawa.jp/incident/396636#66ff1d11b382f3080160b5c6e2f1059cb652346d65f439f51ba181aebff842aa NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/396636 Thu, 11 Jul 2024 07:51:33 -0000 https://status.shc.kanagawa.jp/incident/396636#9e1862292886033ebb1ff9b8309cc909898cdd06adcd16c0ff3a27a67cc3081a NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/396636 Thu, 11 Jul 2024 07:45:18 -0000 https://status.shc.kanagawa.jp/incident/396636#d7342cccaf8501e9b7f405fc7060727a77ee8be386183afdd7bdcc7369c2ad0b NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/396636 Thu, 11 Jul 2024 07:24:29 -0000 https://status.shc.kanagawa.jp/incident/396636#bc60ea87921a3c5c73e7965699f9c3524f98cd8b80d551186ceff6e3ad7a9416 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/396636 Thu, 11 Jul 2024 07:12:28 -0000 https://status.shc.kanagawa.jp/incident/396636#76d72a2e25ac1b5577ac04594f9a3efffa7108487dad496b07541ce891e465c5 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/396636 Thu, 11 Jul 2024 06:21:36 -0000 https://status.shc.kanagawa.jp/incident/396636#6eafcabe6f43c0314bcc7626d96dd4f00354316b0eca0d8d3b8b559a48d019bb NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/396636 Thu, 11 Jul 2024 06:15:23 -0000 https://status.shc.kanagawa.jp/incident/396636#e2c3be35ae95c69604234d0c7fe9f8e944a89ffb4f5db5c046d6a0cd8eb1293f NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/396301 Wed, 10 Jul 2024 14:44:36 -0000 https://status.shc.kanagawa.jp/incident/396301#a12b22189819e329071f889893fdadde46010124c97e5ba2df8f120ab83452f1 ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/396301 Wed, 10 Jul 2024 14:44:18 -0000 https://status.shc.kanagawa.jp/incident/396301#e98339dd6c4d32ea27de9deafe9a390eb2e3ef535bdcd7bb52fdb270cbfc5393 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/396301 Wed, 10 Jul 2024 14:43:37 -0000 https://status.shc.kanagawa.jp/incident/396301#4f956a4b8e86cd06378fd2b102da74234909578b9197957a44f24c101139111b Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/396301 Wed, 10 Jul 2024 14:43:37 -0000 https://status.shc.kanagawa.jp/incident/396301#4f956a4b8e86cd06378fd2b102da74234909578b9197957a44f24c101139111b Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/396301 Wed, 10 Jul 2024 14:40:37 -0000 https://status.shc.kanagawa.jp/incident/396301#dfbd176087546a8e5c5f86526dfe0e9750b10fe4afd805a3a50a97b908ddadc1 ownCloud (share.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/396301 Wed, 10 Jul 2024 14:38:13 -0000 https://status.shc.kanagawa.jp/incident/396301#eef773ca7ff789df0137cd21552e8a5717bf70be79bcf4631719c274fa4bf8dc Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/396301 Wed, 10 Jul 2024 14:37:37 -0000 https://status.shc.kanagawa.jp/incident/396301#a4131b4ebb193da3b777b28d6c59386d947daf5c493d304783c3d5192ea69a49 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/396301 Wed, 10 Jul 2024 14:37:37 -0000 https://status.shc.kanagawa.jp/incident/396301#a4131b4ebb193da3b777b28d6c59386d947daf5c493d304783c3d5192ea69a49 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/395474 Tue, 09 Jul 2024 05:57:05 -0000 https://status.shc.kanagawa.jp/incident/395474#5ce1d0ed28bdb919c1ab54c570cb12b49488baa70cb2e53665c6d72e67c23b7f NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/395474 Tue, 09 Jul 2024 05:53:56 -0000 https://status.shc.kanagawa.jp/incident/395474#ad9a52dc908ec24472cc01713fa78047d56640bbe8347b10c55ccbfc064a1698 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/395275 Mon, 08 Jul 2024 22:18:06 -0000 https://status.shc.kanagawa.jp/incident/395275#9c8d9ed340894b17560b1f70f74325653068f62bc782e868adbd65a01d8bafef NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/395275 Mon, 08 Jul 2024 22:17:03 -0000 https://status.shc.kanagawa.jp/incident/395275#5b0052887fbb9cc238d417caf05c075be5326003f9fca3b5820d6aad41d0f407 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/395275 Mon, 08 Jul 2024 18:18:16 -0000 https://status.shc.kanagawa.jp/incident/395275#fc941a5757094e60b14c71591effbef8c85c55b37cfeb35fd2e84845d26f8152 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/395275 Mon, 08 Jul 2024 18:17:43 -0000 https://status.shc.kanagawa.jp/incident/395275#9a3d7d0991135b2ed3b239a10ad4730a2a0ca133829a9becb5fd2e0c1d9bade5 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/391925 Mon, 01 Jul 2024 20:42:03 -0000 https://status.shc.kanagawa.jp/incident/391925#46e69cd4c07f2569773136105e98781a0368dcd9d35b5d76e5526fc37e5c7fd5 MongoDB Repliction went down and NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/391925 Mon, 01 Jul 2024 20:38:47 -0000 https://status.shc.kanagawa.jp/incident/391925#6ba7597565d60b209677748f43abeded4168a35525c9566a0829b80a40beae0d NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/391925 Mon, 01 Jul 2024 11:50:07 -0000 https://status.shc.kanagawa.jp/incident/391925#5a1474ca398a0d185454a2de2bb513b8f165e7bd173fde5f2eb1ff265f79fb77 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/391925 Mon, 01 Jul 2024 11:50:07 -0000 https://status.shc.kanagawa.jp/incident/391925#5a1474ca398a0d185454a2de2bb513b8f165e7bd173fde5f2eb1ff265f79fb77 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/391925 Mon, 01 Jul 2024 11:42:53 -0000 https://status.shc.kanagawa.jp/incident/391925#be58d7b21e7a3ad46da2b847acb6505ef8634fd84fcab6f0d4af94ab502af7ad Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/391925 Mon, 01 Jul 2024 11:42:53 -0000 https://status.shc.kanagawa.jp/incident/391925#be58d7b21e7a3ad46da2b847acb6505ef8634fd84fcab6f0d4af94ab502af7ad Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/391371 Sun, 30 Jun 2024 11:59:50 -0000 https://status.shc.kanagawa.jp/incident/391371#3d63b00134162333a6b85e66fa1c945fd2474c8e3bf01ae79a3fb5fc7792f284 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/391371 Sun, 30 Jun 2024 11:59:30 -0000 https://status.shc.kanagawa.jp/incident/391371#cd59be1b76aaa33e68b20856e25b7899c35e2a7b5ba291f6ba6858be7e0d5e18 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/391371 Sun, 30 Jun 2024 11:31:34 -0000 https://status.shc.kanagawa.jp/incident/391371#2906c290e3e47403fdd367339068cab40248e6b5e3aea2b9326dddab94d6f092 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/391371 Sun, 30 Jun 2024 11:31:34 -0000 https://status.shc.kanagawa.jp/incident/391371#2906c290e3e47403fdd367339068cab40248e6b5e3aea2b9326dddab94d6f092 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/391371 Sun, 30 Jun 2024 04:56:42 -0000 https://status.shc.kanagawa.jp/incident/391371#84d84feb3bbfc8045b860cd83ac8ed9a22c7e1822e0dbe2180f68ae8aed83b31 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/391371 Sun, 30 Jun 2024 04:52:31 -0000 https://status.shc.kanagawa.jp/incident/391371#2c4a855eb9421f857830344f38fcb7da3ce885c826de3603b98b088dbb555376 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/391226 Sat, 29 Jun 2024 18:47:18 -0000 https://status.shc.kanagawa.jp/incident/391226#ef5f5b9197bad2e6b82b3aeee66a502048652b96c5e456380697b9bd39be2bdd Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/391226 Sat, 29 Jun 2024 18:47:03 -0000 https://status.shc.kanagawa.jp/incident/391226#522dde6588590544b6d10f1bf0d821f715aa0c13c2b1effe2da1dfd38dcdc544 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/391226 Sat, 29 Jun 2024 18:18:55 -0000 https://status.shc.kanagawa.jp/incident/391226#2572705d2b9f4527d91ea2ac60952c9fb3c9afc3a60111b39ee007ada1965a2b Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/391226 Sat, 29 Jun 2024 18:18:55 -0000 https://status.shc.kanagawa.jp/incident/391226#2572705d2b9f4527d91ea2ac60952c9fb3c9afc3a60111b39ee007ada1965a2b Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/390867 Fri, 28 Jun 2024 23:17:03 -0000 https://status.shc.kanagawa.jp/incident/390867#55c129e576839e0eddd6a763117087b0566166d27381c3e2ef72cecd31f4cab1 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/390867 Fri, 28 Jun 2024 19:45:27 -0000 https://status.shc.kanagawa.jp/incident/390867#56ec62f88216ba267d834da0f39fb9af1b3d0063315346245426ebe74215f856 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/390136 Thu, 27 Jun 2024 23:36:29 -0000 https://status.shc.kanagawa.jp/incident/390136#e69f03cd9317d012465bca6333094b08481f95e1fee010280415fa28b95c3e33 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/390136 Thu, 27 Jun 2024 23:36:02 -0000 https://status.shc.kanagawa.jp/incident/390136#abfddb347ec386dff3e15c0b8b1d12a582ff5066d2f743b192e72e5ce09eedd5 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/390136 Thu, 27 Jun 2024 23:32:40 -0000 https://status.shc.kanagawa.jp/incident/390136#435ff1484e0f401e363dc314513ac7c5bf54346aea0ebfeaa6fd70bf583e2e41 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/390136 Thu, 27 Jun 2024 23:32:02 -0000 https://status.shc.kanagawa.jp/incident/390136#5f379c6ce68373bb42f23097a68a8f6c7fad2c4a9c5684de69fdcda8304d0996 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/390136 Thu, 27 Jun 2024 22:35:26 -0000 https://status.shc.kanagawa.jp/incident/390136#cd92efdc8a24b39a55af701f0872799b034e95e49538094dd4584dbc86bacd66 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/390136 Thu, 27 Jun 2024 22:30:02 -0000 https://status.shc.kanagawa.jp/incident/390136#5282a40e349eec23559ba9f1329d9d664688f667843cce3f46bcbf130fa66fad Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/390136 Thu, 27 Jun 2024 22:29:02 -0000 https://status.shc.kanagawa.jp/incident/390136#c8b3604ef119b959348fced47f9ee526e812da42d1fc56ab2c95b30c25f41b6b Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/390136 Thu, 27 Jun 2024 22:29:02 -0000 https://status.shc.kanagawa.jp/incident/390136#c8b3604ef119b959348fced47f9ee526e812da42d1fc56ab2c95b30c25f41b6b Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/390136 Thu, 27 Jun 2024 21:33:26 -0000 https://status.shc.kanagawa.jp/incident/390136#994e7652f78765a1cd0305f02bee64828cd6755b87afde4d70a8ce541ce0ca22 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/390136 Thu, 27 Jun 2024 21:33:14 -0000 https://status.shc.kanagawa.jp/incident/390136#20715026ecfedc22d3cb461b7d48646f2d0b0abd9d76d8d49237268bb8a91f8c Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/390136 Thu, 27 Jun 2024 21:32:00 -0000 https://status.shc.kanagawa.jp/incident/390136#5af2d3ba48fe7fa8309e26f8b8aae0950f9010070368d896a0858cb80cd44da8 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/390136 Thu, 27 Jun 2024 21:32:00 -0000 https://status.shc.kanagawa.jp/incident/390136#5af2d3ba48fe7fa8309e26f8b8aae0950f9010070368d896a0858cb80cd44da8 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/390136 Thu, 27 Jun 2024 15:23:41 -0000 https://status.shc.kanagawa.jp/incident/390136#aca604f8258a75b036bb78d18a4f5766f4df47f5ec771eb992b06755ad4c1965 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/390136 Thu, 27 Jun 2024 15:23:14 -0000 https://status.shc.kanagawa.jp/incident/390136#cc45cdaddc2d0cb1dc512a973ab2419391495091fc00182b0a58057b793bb99f Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/390136 Thu, 27 Jun 2024 13:57:27 -0000 https://status.shc.kanagawa.jp/incident/390136#5c1b0f7f09fac6695c6b06cf00f6e980872e07564ba7bcf38c67cd599697fa0b Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/390136 Thu, 27 Jun 2024 13:57:27 -0000 https://status.shc.kanagawa.jp/incident/390136#5c1b0f7f09fac6695c6b06cf00f6e980872e07564ba7bcf38c67cd599697fa0b Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/390136 Thu, 27 Jun 2024 08:07:25 -0000 https://status.shc.kanagawa.jp/incident/390136#eee36c5cf534f59f8350b5c431680ac7d7b02dae003c456a45067e99056c953f Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/390136 Thu, 27 Jun 2024 08:06:27 -0000 https://status.shc.kanagawa.jp/incident/390136#95d3456fd3e690cb5389061573678b44eb9f22d4fc0f57f9235e0d78094ecbd8 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/388517 Mon, 24 Jun 2024 20:56:50 -0000 https://status.shc.kanagawa.jp/incident/388517#f140c22a42d0b721fc243f9ecf9c0acdedd46a9f5bbead6bc4636dc0d0369650 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/388517 Mon, 24 Jun 2024 20:53:11 -0000 https://status.shc.kanagawa.jp/incident/388517#c520c6412bf143272c594779b15f97389fee025b507060809d330996d6a22410 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/388517 Mon, 24 Jun 2024 14:59:10 -0000 https://status.shc.kanagawa.jp/incident/388517#893a0fceb288fa5b84845d88ef5ec0a44efc5cf81ddd9d36c47be2f207fd75de NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/388517 Mon, 24 Jun 2024 14:53:00 -0000 https://status.shc.kanagawa.jp/incident/388517#47a3936009f21357110bb30782218230c9fae70895382a937cd3fcbf311e9c9e NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/388517 Mon, 24 Jun 2024 10:58:41 -0000 https://status.shc.kanagawa.jp/incident/388517#4b4d4a1f47d97c7ea89c064233dc132003ced172b2c56a2c24bac7c527c47480 NextCloud Maintenance recovered. https://status.shc.kanagawa.jp/incident/388517 Mon, 24 Jun 2024 06:32:01 -0000 https://status.shc.kanagawa.jp/incident/388517#e933e12c66cd188656acbbf080e1435878e814a0d67145410a51601d4205b2a7 NextCloud Maintenance went down. https://status.shc.kanagawa.jp/incident/388517 Mon, 24 Jun 2024 06:13:48 -0000 https://status.shc.kanagawa.jp/incident/388517#46c6e29568ed8eaae7367bcd48891c5f5919f64dd8cbc09a59c69853d4aaa7f5 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/388517 Mon, 24 Jun 2024 06:07:51 -0000 https://status.shc.kanagawa.jp/incident/388517#6e9f2b978c19321d225d54e2e7bf1c38c630cf355f2aba463d1c704419e6515e NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/388107 Sun, 23 Jun 2024 22:37:38 -0000 https://status.shc.kanagawa.jp/incident/388107#75bac39c724e91d97188b46e8c54680008d98c56ca77fc73741eb5902c0191d7 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/388107 Sun, 23 Jun 2024 22:34:22 -0000 https://status.shc.kanagawa.jp/incident/388107#105e89583f68a271f86fca3c6931034ddd66f2d7ca4507f40746289abd5f5276 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/388107 Sun, 23 Jun 2024 22:33:20 -0000 https://status.shc.kanagawa.jp/incident/388107#b42604901af229920e87d705675516e216956b8568dceb8fd36d3672ee782b73 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/388107 Sun, 23 Jun 2024 22:33:20 -0000 https://status.shc.kanagawa.jp/incident/388107#b42604901af229920e87d705675516e216956b8568dceb8fd36d3672ee782b73 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/388107 Sun, 23 Jun 2024 21:37:33 -0000 https://status.shc.kanagawa.jp/incident/388107#0f8c4ca0112092a9d1b6a4669bc157f7a7e65543510f5f31687242d0eb7c7d9e Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/388107 Sun, 23 Jun 2024 21:34:13 -0000 https://status.shc.kanagawa.jp/incident/388107#454148fc37a16c787b7075a6c73852b4ce647ba10a428b007bfafb3cbc61b6cb Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/388107 Sun, 23 Jun 2024 13:31:19 -0000 https://status.shc.kanagawa.jp/incident/388107#ab40dd523e2cdd81406e714f6a16a0d534b926dbab3ebaa25d8edc52d539e6fd Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/388107 Sun, 23 Jun 2024 13:31:19 -0000 https://status.shc.kanagawa.jp/incident/388107#ab40dd523e2cdd81406e714f6a16a0d534b926dbab3ebaa25d8edc52d539e6fd Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/388107 Sun, 23 Jun 2024 13:30:44 -0000 https://status.shc.kanagawa.jp/incident/388107#ba831c43b0d110a47f3ed8139b13c262702f726ac0d2d19f75365aa933b3081c Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/388107 Sun, 23 Jun 2024 13:30:44 -0000 https://status.shc.kanagawa.jp/incident/388107#ba831c43b0d110a47f3ed8139b13c262702f726ac0d2d19f75365aa933b3081c Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/388107 Sun, 23 Jun 2024 12:34:30 -0000 https://status.shc.kanagawa.jp/incident/388107#981ceaf2e3e1f3fdda2badf00e90dd5a495f8e9d368bfcf292ad09656ae71d4d Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/388107 Sun, 23 Jun 2024 12:31:20 -0000 https://status.shc.kanagawa.jp/incident/388107#d9bd47184b2ec20fdc3eb052bcf90ea2be22103444611efe10267070eb4cb3cd Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/388107 Sun, 23 Jun 2024 12:30:15 -0000 https://status.shc.kanagawa.jp/incident/388107#5f720674ad43e53ee13252965d8056199b10175ef5e19c602d1a5c875a1c6d48 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/388107 Sun, 23 Jun 2024 12:30:15 -0000 https://status.shc.kanagawa.jp/incident/388107#5f720674ad43e53ee13252965d8056199b10175ef5e19c602d1a5c875a1c6d48 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/388107 Sun, 23 Jun 2024 09:33:37 -0000 https://status.shc.kanagawa.jp/incident/388107#c84de4fabc3196cdd384782365db20e7b57132a1a8655c507b67f2e95c03a2cb Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/388107 Sun, 23 Jun 2024 09:33:37 -0000 https://status.shc.kanagawa.jp/incident/388107#c84de4fabc3196cdd384782365db20e7b57132a1a8655c507b67f2e95c03a2cb Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/388107 Sun, 23 Jun 2024 09:29:28 -0000 https://status.shc.kanagawa.jp/incident/388107#460943d9c5115c1c4e2ae01ab3513705eb50ff576d891dbe2a97f4278f744d1f Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/388107 Sun, 23 Jun 2024 09:29:28 -0000 https://status.shc.kanagawa.jp/incident/388107#460943d9c5115c1c4e2ae01ab3513705eb50ff576d891dbe2a97f4278f744d1f Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/388107 Sun, 23 Jun 2024 05:36:42 -0000 https://status.shc.kanagawa.jp/incident/388107#99a35d0d9a61104c9f3173ad419f30377d97b3d3a217326648bebc0c78af55c9 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/388107 Sun, 23 Jun 2024 05:33:24 -0000 https://status.shc.kanagawa.jp/incident/388107#5300e8dbbf565ff1f07f82f81f2a38cd825b8ba67045cf531d2ad1921eb75858 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/388107 Sun, 23 Jun 2024 05:32:23 -0000 https://status.shc.kanagawa.jp/incident/388107#420d8d410af761de982262e2a2bd46cd5e839e9af33b7c07da6d3d9be21f004e Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/388107 Sun, 23 Jun 2024 05:32:23 -0000 https://status.shc.kanagawa.jp/incident/388107#420d8d410af761de982262e2a2bd46cd5e839e9af33b7c07da6d3d9be21f004e Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/388107 Sun, 23 Jun 2024 01:36:40 -0000 https://status.shc.kanagawa.jp/incident/388107#f2b1972e95ae3c1ec8781c5098385b3cbef08c0b493a7d5c315c9e7a469b54e1 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/388107 Sun, 23 Jun 2024 01:35:50 -0000 https://status.shc.kanagawa.jp/incident/388107#b420d87eb7708824faa8b77a3a36f23fc598650d52f53802b932d147be02782c Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/387809 Sat, 22 Jun 2024 22:33:39 -0000 https://status.shc.kanagawa.jp/incident/387809#8fc8ae8e833d51c86668d10a761fcfa4f5c739b46480c06c43f09c0c208276f2 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/387809 Sat, 22 Jun 2024 22:29:40 -0000 https://status.shc.kanagawa.jp/incident/387809#fba29dbacccba8a9a4c8bd5439a70b274f348f2b0d69b44c3b12ebe4c226aeaa Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/387809 Sat, 22 Jun 2024 15:33:40 -0000 https://status.shc.kanagawa.jp/incident/387809#ca745f4a286907a7bd27028f3b61a65b7e507dbcdf328cf6efe26d43f9af1c58 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/387809 Sat, 22 Jun 2024 15:32:51 -0000 https://status.shc.kanagawa.jp/incident/387809#a6f2ba9dbc4df0a8736470e090cd78f2b39f881917deebc6bf00d1da637a9223 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/387809 Sat, 22 Jun 2024 14:36:51 -0000 https://status.shc.kanagawa.jp/incident/387809#8a9f5cc33e2616f5bcd17c33738df1355a1f84b026f2b93cbb9a1ac607cd7d99 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/387809 Sat, 22 Jun 2024 14:33:43 -0000 https://status.shc.kanagawa.jp/incident/387809#cf8ccf792bb54e033aaf3fc1c8235d2afd23951c44c89730a6a3b1510820d7cc Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/387809 Sat, 22 Jun 2024 14:32:32 -0000 https://status.shc.kanagawa.jp/incident/387809#a09d8d1b9594805f21e7ab4f0bbc4025ebdd3f8bcdc544d66edb0a7bf236dbd7 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/387809 Sat, 22 Jun 2024 14:32:32 -0000 https://status.shc.kanagawa.jp/incident/387809#a09d8d1b9594805f21e7ab4f0bbc4025ebdd3f8bcdc544d66edb0a7bf236dbd7 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/387809 Sat, 22 Jun 2024 13:33:38 -0000 https://status.shc.kanagawa.jp/incident/387809#a740910b94f51a1b9227a5277151c3aa34ce4448c1185fcabb45a1d39d8b74d1 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/387809 Sat, 22 Jun 2024 13:33:38 -0000 https://status.shc.kanagawa.jp/incident/387809#a740910b94f51a1b9227a5277151c3aa34ce4448c1185fcabb45a1d39d8b74d1 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/387809 Sat, 22 Jun 2024 13:33:05 -0000 https://status.shc.kanagawa.jp/incident/387809#05aff6cf25f1ca469153c93fe8e981dffe566e9bcf55b6cdf188daf51b1b7bec Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/387809 Sat, 22 Jun 2024 13:32:33 -0000 https://status.shc.kanagawa.jp/incident/387809#7ab0d908f9498b42624171f7d7eef4a69341e7f8312620ae1a9e3c3c38f13879 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/387809 Sat, 22 Jun 2024 12:33:43 -0000 https://status.shc.kanagawa.jp/incident/387809#046868e240133334dc7e2c497b9ee4a827ec36f5b99bcebaf2289d56427fd121 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/387809 Sat, 22 Jun 2024 12:29:40 -0000 https://status.shc.kanagawa.jp/incident/387809#ccb78d4dbff8707b40f46d8be2699ff8d71d421d6334cabf5fd80669fa9c68df Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/387809 Sat, 22 Jun 2024 11:33:40 -0000 https://status.shc.kanagawa.jp/incident/387809#3d0d62eb0e2203e069f1607dc238b66c0bb8bfba651b05f97d9f3c41ad7bd7cb Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/387809 Sat, 22 Jun 2024 11:32:41 -0000 https://status.shc.kanagawa.jp/incident/387809#a34294f067285bde19813d1f4195684f5d1257e0b45e23717c518280629510fe Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/387809 Sat, 22 Jun 2024 11:30:51 -0000 https://status.shc.kanagawa.jp/incident/387809#4400e8dfb3e1233b0f6dff4e367203a43f040cfb8cb1530e014e53992fa79665 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/387809 Sat, 22 Jun 2024 11:30:35 -0000 https://status.shc.kanagawa.jp/incident/387809#a2e2a54a0fab5ab4f4951c102b598ebeb143a3f83eaeb6846a9ea6478960ce08 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/387809 Sat, 22 Jun 2024 10:34:35 -0000 https://status.shc.kanagawa.jp/incident/387809#5fd2e2da352dad0c0b9cce2a6974e10c34db1a3e25e73c9f82afbdf43de4cfc8 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/387809 Sat, 22 Jun 2024 10:33:40 -0000 https://status.shc.kanagawa.jp/incident/387809#646f92b30127d96dc6e821a17b24b1cf85d1695ca5f9c00c67fd23e22772d347 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/387809 Sat, 22 Jun 2024 10:30:18 -0000 https://status.shc.kanagawa.jp/incident/387809#2a31e845dbdc4c1f4fe9205b32d36688bdc1c94fc9064c8bc17aeb538af4b200 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/387809 Sat, 22 Jun 2024 10:30:18 -0000 https://status.shc.kanagawa.jp/incident/387809#2a31e845dbdc4c1f4fe9205b32d36688bdc1c94fc9064c8bc17aeb538af4b200 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/387809 Sat, 22 Jun 2024 07:33:25 -0000 https://status.shc.kanagawa.jp/incident/387809#11c70333d8d206ccbe65ac907380915225c305d26fde346bbb75ebaf3546248b Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/387809 Sat, 22 Jun 2024 07:33:25 -0000 https://status.shc.kanagawa.jp/incident/387809#11c70333d8d206ccbe65ac907380915225c305d26fde346bbb75ebaf3546248b Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/387809 Sat, 22 Jun 2024 07:32:51 -0000 https://status.shc.kanagawa.jp/incident/387809#195dad0daad0d00fa840817722f088ed073b9daae53bfaa8c18bb2ef445a6cdf Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/387809 Sat, 22 Jun 2024 07:29:31 -0000 https://status.shc.kanagawa.jp/incident/387809#c4fd6da1d54e35be754659246b78fb30f0e3427412cb38759561d417a4ae6268 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/387809 Sat, 22 Jun 2024 06:33:51 -0000 https://status.shc.kanagawa.jp/incident/387809#9767341aa804b5609fac4fcc92f469656c7fce9821c205aabdf03de42a3bdf9b Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/387809 Sat, 22 Jun 2024 06:33:51 -0000 https://status.shc.kanagawa.jp/incident/387809#9767341aa804b5609fac4fcc92f469656c7fce9821c205aabdf03de42a3bdf9b Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/387809 Sat, 22 Jun 2024 06:32:14 -0000 https://status.shc.kanagawa.jp/incident/387809#0a2c5624f4e003e169f8f63b71a13dfa2285c7e6db91322c60d2d67a5aab8ff1 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/387809 Sat, 22 Jun 2024 06:32:14 -0000 https://status.shc.kanagawa.jp/incident/387809#0a2c5624f4e003e169f8f63b71a13dfa2285c7e6db91322c60d2d67a5aab8ff1 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/387809 Sat, 22 Jun 2024 05:31:00 -0000 https://status.shc.kanagawa.jp/incident/387809#e2bdd4454dc35c36ced274455b96beb53e1c465fd3117ac56440e99cdd1f3b7b Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/387809 Sat, 22 Jun 2024 05:30:18 -0000 https://status.shc.kanagawa.jp/incident/387809#0a33a25ccf0b691158d9762dfa0251508ae663f6d69cd909d28733e999a3c303 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/387809 Sat, 22 Jun 2024 05:29:14 -0000 https://status.shc.kanagawa.jp/incident/387809#83fb8fe86b8a0e3d6bac3c618c7336801d2c21ea91b1358b31be940e997702ae Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/387809 Sat, 22 Jun 2024 05:29:14 -0000 https://status.shc.kanagawa.jp/incident/387809#83fb8fe86b8a0e3d6bac3c618c7336801d2c21ea91b1358b31be940e997702ae Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/387809 Sat, 22 Jun 2024 04:33:25 -0000 https://status.shc.kanagawa.jp/incident/387809#6b4679b66eec98c263f125481a31b4a8fa5a2429b0ce7065f6b0fa0eb7b2bddf Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/387809 Sat, 22 Jun 2024 04:33:25 -0000 https://status.shc.kanagawa.jp/incident/387809#6b4679b66eec98c263f125481a31b4a8fa5a2429b0ce7065f6b0fa0eb7b2bddf Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/387809 Sat, 22 Jun 2024 04:32:19 -0000 https://status.shc.kanagawa.jp/incident/387809#801041dd99722173ce102dade5b9cfc74f8b26d4effccadf8a7a1fd7f7da0cf0 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/387809 Sat, 22 Jun 2024 04:32:19 -0000 https://status.shc.kanagawa.jp/incident/387809#801041dd99722173ce102dade5b9cfc74f8b26d4effccadf8a7a1fd7f7da0cf0 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/387465 Fri, 21 Jun 2024 09:53:44 -0000 https://status.shc.kanagawa.jp/incident/387465#2c57eaf9500dba958423fc061f7149c3eba15bd6aea6870b81fa1be2d651fd72 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/387465 Fri, 21 Jun 2024 09:53:19 -0000 https://status.shc.kanagawa.jp/incident/387465#7c8095d604ac392817cd307c4ec9ce2f63dc2a64a8c8db42c77789ab188f58f5 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/387465 Fri, 21 Jun 2024 09:52:21 -0000 https://status.shc.kanagawa.jp/incident/387465#792d11538ce4b758503f3b9fd512f56b607e9c97f25fa5504320b9b974a78f7a Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/387465 Fri, 21 Jun 2024 09:52:21 -0000 https://status.shc.kanagawa.jp/incident/387465#792d11538ce4b758503f3b9fd512f56b607e9c97f25fa5504320b9b974a78f7a Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/386929 Thu, 20 Jun 2024 11:07:00 -0000 https://status.shc.kanagawa.jp/incident/386929#a8b15b410e48954fff3b4a8d5d83f1542a9c11b4a1d63a45a813d15ea5b57e61 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/386929 Thu, 20 Jun 2024 11:07:00 -0000 https://status.shc.kanagawa.jp/incident/386929#a8b15b410e48954fff3b4a8d5d83f1542a9c11b4a1d63a45a813d15ea5b57e61 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/386929 Thu, 20 Jun 2024 11:05:45 -0000 https://status.shc.kanagawa.jp/incident/386929#08dfbb9fb1a4fcd7d0c8fa8f37828c478f4b861e5d7a29cc1008186eee5d98e6 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/386929 Thu, 20 Jun 2024 11:05:45 -0000 https://status.shc.kanagawa.jp/incident/386929#08dfbb9fb1a4fcd7d0c8fa8f37828c478f4b861e5d7a29cc1008186eee5d98e6 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/385333 Mon, 17 Jun 2024 18:23:33 -0000 https://status.shc.kanagawa.jp/incident/385333#30f93bfeb5142b1cbf41ab1f8008c53d6c3e094f9ad405e5904e18ca6459ddc7 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/385333 Mon, 17 Jun 2024 18:20:12 -0000 https://status.shc.kanagawa.jp/incident/385333#bc19acf77abe95148a5779712c53aa09511791fd926a00d07a07e8ae14dabefa NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/385333 Mon, 17 Jun 2024 11:01:21 -0000 https://status.shc.kanagawa.jp/incident/385333#c8a467a5749d54b9b9fa1aa46764506571c5d0541742026740d49e6e41882c31 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/385333 Mon, 17 Jun 2024 11:00:23 -0000 https://status.shc.kanagawa.jp/incident/385333#96d11e25e5641fe260f8346a581dd01bb137f6712f657480298001c109356384 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/385333 Mon, 17 Jun 2024 10:37:18 -0000 https://status.shc.kanagawa.jp/incident/385333#e09cc8548f05e5f9f2108781228dd13b3a28826cc7ad0ed9cfcfbd0e4bdc02cb Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/385333 Mon, 17 Jun 2024 10:37:18 -0000 https://status.shc.kanagawa.jp/incident/385333#e09cc8548f05e5f9f2108781228dd13b3a28826cc7ad0ed9cfcfbd0e4bdc02cb Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/385333 Mon, 17 Jun 2024 10:36:29 -0000 https://status.shc.kanagawa.jp/incident/385333#0c05a91027914251abd5864b19a31ab3d13bfafb9fc520230c789fb4d7a9ec38 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/385333 Mon, 17 Jun 2024 10:36:11 -0000 https://status.shc.kanagawa.jp/incident/385333#56335b689836964741351d4c0d1688777f46c883b64093e2c497701ff2d8474e Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/385333 Mon, 17 Jun 2024 06:54:24 -0000 https://status.shc.kanagawa.jp/incident/385333#d54677a544626ebcc80b3e091771588f354573ff750b6df344a669a9aa54b05a Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/385333 Mon, 17 Jun 2024 06:53:42 -0000 https://status.shc.kanagawa.jp/incident/385333#db95216f400c93e9d26ddc4b186bb54b548dfdce8c3c916a9b8c68d9e1d84eaa Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/385333 Mon, 17 Jun 2024 06:41:09 -0000 https://status.shc.kanagawa.jp/incident/385333#e60322918d16055b06dab014d94afec07a9178d41eef7bdb34091d5dab47ea98 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/385333 Mon, 17 Jun 2024 06:41:09 -0000 https://status.shc.kanagawa.jp/incident/385333#e60322918d16055b06dab014d94afec07a9178d41eef7bdb34091d5dab47ea98 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/384546 Sun, 16 Jun 2024 10:17:24 -0000 https://status.shc.kanagawa.jp/incident/384546#3c59b80a632abd68a6caebe9651ac2cf8ee9f3d00338d61b1e1b9500bfc868db Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/384546 Sun, 16 Jun 2024 10:07:19 -0000 https://status.shc.kanagawa.jp/incident/384546#66f08fb453bfe0dcf0910f0d88fa838d4f37fceecb48530e05f427cac04f4e9c Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/384546 Sun, 16 Jun 2024 09:41:44 -0000 https://status.shc.kanagawa.jp/incident/384546#3579c9b48f5cc8afe8d1ecf61736ee2aa4a809ff4512fa0ca9addefb9223140f Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/384546 Sun, 16 Jun 2024 09:41:25 -0000 https://status.shc.kanagawa.jp/incident/384546#b8b040b1d53873dc9519c5dd966564485cf0c8eb7f6a89f15782e2a8e702617b Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/384546 Sun, 16 Jun 2024 09:29:58 -0000 https://status.shc.kanagawa.jp/incident/384546#05eeb52fdbe9b7989cc25a2d3c5a93464098a7ef2cda40bb6dc5592ea75e6344 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/384546 Sun, 16 Jun 2024 09:26:25 -0000 https://status.shc.kanagawa.jp/incident/384546#a3e94b2d8d886cc651ee0b9e08f56eaf454b1ed2f03b08d692700bf0f5aed70d Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/384546 Sun, 16 Jun 2024 09:20:36 -0000 https://status.shc.kanagawa.jp/incident/384546#d7fec69ae9c53c88e13bb21f009cb34fb852c573dfa435e9f0752ca9b0440fe5 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/384546 Sun, 16 Jun 2024 09:17:21 -0000 https://status.shc.kanagawa.jp/incident/384546#f08d6945b55252d6d92cbc2b7723a97b38c53fae3722fe91df2f47b0491b6d5c Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/384546 Sun, 16 Jun 2024 05:34:46 -0000 https://status.shc.kanagawa.jp/incident/384546#81befc51ed3929270de8d433f4f926290d22f776fafa051f7dd124950320aae4 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/384546 Sun, 16 Jun 2024 05:34:46 -0000 https://status.shc.kanagawa.jp/incident/384546#81befc51ed3929270de8d433f4f926290d22f776fafa051f7dd124950320aae4 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/384546 Sun, 16 Jun 2024 05:30:38 -0000 https://status.shc.kanagawa.jp/incident/384546#97d7c34d155e4f43a980a6eda1305632a4a39d73797c8d9df321c4cd88452608 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/384546 Sat, 15 Jun 2024 21:43:28 -0000 https://status.shc.kanagawa.jp/incident/384546#e30025e94e5bb006f565e432411eafe82e9cdcccb7986a3ac7f5ecd228882207 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/384546 Sat, 15 Jun 2024 21:22:41 -0000 https://status.shc.kanagawa.jp/incident/384546#8eb6b7066f1e9c430fdfc9eeb59d2b60c956461dda5f9712a879c2a040302609 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/384546 Sat, 15 Jun 2024 21:19:27 -0000 https://status.shc.kanagawa.jp/incident/384546#218de3d6da00351dcf8e213c603757c439850fe5a3f78ed987776630a5872ffe Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/384546 Sat, 15 Jun 2024 21:05:05 -0000 https://status.shc.kanagawa.jp/incident/384546#815e4e19d179799082f066d47c826879e5ee5c3ec823d01fac920931e6872481 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/384546 Sat, 15 Jun 2024 20:49:28 -0000 https://status.shc.kanagawa.jp/incident/384546#4783ecba360f905b224936379e60a3d16e376562bceeb0936320be72ff019449 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/384546 Sat, 15 Jun 2024 19:58:53 -0000 https://status.shc.kanagawa.jp/incident/384546#7c777c960ebae6cff929b6432cb77e710dbb656675a9ccd9d07ffc69d2297f3d Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/384546 Sat, 15 Jun 2024 19:49:29 -0000 https://status.shc.kanagawa.jp/incident/384546#476fee2e1ef964d95b022bd54ece6701da0d834992f26ea58cea865b20dedef3 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/384546 Sat, 15 Jun 2024 19:41:07 -0000 https://status.shc.kanagawa.jp/incident/384546#e512433ca88034e55a5c03480f3b18a28bca753b6d695a955c92feb8004e968f Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/384546 Sat, 15 Jun 2024 19:25:31 -0000 https://status.shc.kanagawa.jp/incident/384546#cc0ab05ea31b0f5ebaad0da8ac773b9082169edc5b669e5de6a083eae49949bc Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/384546 Sat, 15 Jun 2024 19:07:54 -0000 https://status.shc.kanagawa.jp/incident/384546#198c7c436fd94595be9b03e089e63b12f9d2ccde862d8dcf5b0b25303a53c51e Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/384546 Sat, 15 Jun 2024 19:07:31 -0000 https://status.shc.kanagawa.jp/incident/384546#1768a75074710cb37ce5749c7c9febb5c11555ce14d8e7dc3eb75ffc9b04e667 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/384546 Sat, 15 Jun 2024 19:01:38 -0000 https://status.shc.kanagawa.jp/incident/384546#1fd3bf2edd0b942a9dee2237d65bb78387cde3061ddca5a164ddbf3ead2dbfff Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/384546 Sat, 15 Jun 2024 17:49:28 -0000 https://status.shc.kanagawa.jp/incident/384546#06ffecd96ce50cf3d4b01f06646aa1a5887e457daa9bbd03077dd56d6973e5bd Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/384546 Sat, 15 Jun 2024 17:43:38 -0000 https://status.shc.kanagawa.jp/incident/384546#ac219cdd77c3be302942c5c44a1da0b59b8ea305fdd4e41d9e7f050db86542d0 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/384546 Sat, 15 Jun 2024 17:40:32 -0000 https://status.shc.kanagawa.jp/incident/384546#19fe4f2819d5d0e71aa5485f9f3e3de9a4a6793b6ea10e71562c006dddcb7e4d Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/384546 Sat, 15 Jun 2024 17:22:58 -0000 https://status.shc.kanagawa.jp/incident/384546#bcc475c7ebaad27320bb5b59ecbf74a6e187188180f1dc37ffb66c83f34b7813 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/384546 Sat, 15 Jun 2024 17:07:04 -0000 https://status.shc.kanagawa.jp/incident/384546#dcae948c57f742456a4050c5f94f6072b06929f0793afcfd460c0257f18967f6 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/384546 Sat, 15 Jun 2024 16:56:07 -0000 https://status.shc.kanagawa.jp/incident/384546#7e5e521091745ce08a9f23769e31b7344a36fb4e91e8b69c801ebd5b2ea633dd Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/384546 Sat, 15 Jun 2024 00:37:09 -0000 https://status.shc.kanagawa.jp/incident/384546#cd4d331a3a62cef00307df40e490b217cbb076597d63971a6fb7a72c7b4d0b27 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/384546 Sat, 15 Jun 2024 00:31:24 -0000 https://status.shc.kanagawa.jp/incident/384546#cce3381cf98290c6047e3b09bdbc1bd0e61450c58a2f3c3ffd2e692da13e260c Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/384546 Sat, 15 Jun 2024 00:16:10 -0000 https://status.shc.kanagawa.jp/incident/384546#cd63f848c6328ffaf1731c192d54e9985dd81196f17e9ac1550851eeb836ba4a Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/384236 Fri, 14 Jun 2024 23:55:35 -0000 https://status.shc.kanagawa.jp/incident/384236#e2936b03131eea05c096f8e73649273d3475cd8b22da0ed45500611c0837b418 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/384236 Fri, 14 Jun 2024 23:43:10 -0000 https://status.shc.kanagawa.jp/incident/384236#07d7a21fa234a19c93f684b46dcf2c7241bd1fb9b731117d6f535451c0906ac0 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/384236 Fri, 14 Jun 2024 23:31:17 -0000 https://status.shc.kanagawa.jp/incident/384236#10865af3712ffa05ca368d479aa9e338047fe0844cf460764dfca5e6051b051d Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/384236 Fri, 14 Jun 2024 23:16:05 -0000 https://status.shc.kanagawa.jp/incident/384236#9af98cbee07ab07292f57f5ee13c565a67569667ccaf8dd545dea956e448b9db Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/384236 Fri, 14 Jun 2024 22:46:35 -0000 https://status.shc.kanagawa.jp/incident/384236#399b2f50ea2b708b092ec60a24856123c970611cae457156d35d8ebff981c74b Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/384236 Fri, 14 Jun 2024 22:43:07 -0000 https://status.shc.kanagawa.jp/incident/384236#8f1cd834cc08345bd6aa6b9b5cfc4a9a8db6a5945050a8b38f9fbe6832470cd3 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/384236 Fri, 14 Jun 2024 22:10:16 -0000 https://status.shc.kanagawa.jp/incident/384236#395fcad5866ac919c134b4fb654d933cb8746adf67bce9469ef0665b3573dce5 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/384236 Fri, 14 Jun 2024 22:07:06 -0000 https://status.shc.kanagawa.jp/incident/384236#d78f347e135a0d9d50b6549e995b7ebbe80dc3f6eb26799e4622082355242c98 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/384236 Fri, 14 Jun 2024 21:58:20 -0000 https://status.shc.kanagawa.jp/incident/384236#181fff7ac8190c7c96e6019161a780945e09ce3398173bb89834a861ae991293 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/384236 Fri, 14 Jun 2024 21:55:14 -0000 https://status.shc.kanagawa.jp/incident/384236#0095bd398b2c98ad79fe372b32898cf3ff67b819ea7c7e4bb113faf39d327f02 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/384236 Fri, 14 Jun 2024 20:31:44 -0000 https://status.shc.kanagawa.jp/incident/384236#516c7c5509e4062ce14aa63611a3d46d982b89f6da2606692e904c6284b757a2 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/384236 Fri, 14 Jun 2024 20:28:08 -0000 https://status.shc.kanagawa.jp/incident/384236#0da946d4e315a850016b88141e92abe57e459c0296b88d8280e6ccb3186035a9 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/384236 Fri, 14 Jun 2024 20:10:08 -0000 https://status.shc.kanagawa.jp/incident/384236#b1f90e7bdcd7f87b51cb71d2fd24a7040b50350c3343b83048d0903bdce4781c Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/384236 Fri, 14 Jun 2024 20:04:13 -0000 https://status.shc.kanagawa.jp/incident/384236#bc56759f3548765a29d7dbbae7d1dc820bb77619c975574393f844e5ecae8161 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/384236 Fri, 14 Jun 2024 19:19:44 -0000 https://status.shc.kanagawa.jp/incident/384236#401e2714c440acce0dbff4241033640e6aefd58412baae7c3beeab1098d5039f Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/384236 Fri, 14 Jun 2024 11:34:23 -0000 https://status.shc.kanagawa.jp/incident/384236#daf6a6549493272d6c99c0cbe77930971c86611ae7a3a36a1a767afde1fa6a22 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/384236 Fri, 14 Jun 2024 11:14:05 -0000 https://status.shc.kanagawa.jp/incident/384236#9ed57fa9ca248dff408862b7070d5396517bc1dc9c5ff9d7b4f920061d687460 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/384236 Fri, 14 Jun 2024 11:13:27 -0000 https://status.shc.kanagawa.jp/incident/384236#315ad18ed00ed4777a51546bb48cb2cbffed2d6a903fca1ce0ef5a72a0e7f6f1 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/384236 Fri, 14 Jun 2024 10:49:55 -0000 https://status.shc.kanagawa.jp/incident/384236#b0a38f72b526cf75acbb17e677a54fce5d067c286d8b18a9255b7fe506c76600 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/384236 Fri, 14 Jun 2024 10:40:29 -0000 https://status.shc.kanagawa.jp/incident/384236#e1532dfccdefb33849352dc48bf64ea51ccc5c77ce3c03173487f55bb22472b8 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/384236 Fri, 14 Jun 2024 08:46:08 -0000 https://status.shc.kanagawa.jp/incident/384236#98651af912c8a970ae1e70afeea2260e00294875393e65e10c2f5d0de6ca1760 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/384236 Fri, 14 Jun 2024 08:42:36 -0000 https://status.shc.kanagawa.jp/incident/384236#c2026cda6fb655bd1f186f26011cebef685ddccd5d80dd034fb946f6c669f91e Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/383682 Thu, 13 Jun 2024 22:44:47 -0000 https://status.shc.kanagawa.jp/incident/383682#8920c8b89720b0130b6c9ea1afdb456fbfba5716b0c7878494831d01d828569b Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/383682 Thu, 13 Jun 2024 22:44:09 -0000 https://status.shc.kanagawa.jp/incident/383682#bd336b45e3f6911a0fb4b77d80864a005d4e430b35e01b7e9c5c71dfba5307b7 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/383682 Thu, 13 Jun 2024 16:41:47 -0000 https://status.shc.kanagawa.jp/incident/383682#4075d83b41edefd4261a7ba0c78b71239cffe28cfa69f9bd6f07114b5b928853 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/383682 Thu, 13 Jun 2024 16:40:39 -0000 https://status.shc.kanagawa.jp/incident/383682#9e364e0f58d7f9209d938c5a22e49186544c40e50edfd18465ef9300053e4fe8 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/383682 Thu, 13 Jun 2024 13:39:32 -0000 https://status.shc.kanagawa.jp/incident/383682#ff37b49bb24ee9e31b3b09a8dfc71ac82b405ad8b35b132ca95a1679cbb4d37c Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/383682 Thu, 13 Jun 2024 13:27:23 -0000 https://status.shc.kanagawa.jp/incident/383682#df9d1a82871804b684066bb3b4bf5def8c81f2fea4e0e094ab8951f03d8aceea Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/383682 Thu, 13 Jun 2024 08:01:25 -0000 https://status.shc.kanagawa.jp/incident/383682#e2a86b4c2d238095c3dae57cce68684c67efb16f35f7da4fe5c0cc9be0f15932 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/383682 Thu, 13 Jun 2024 07:48:47 -0000 https://status.shc.kanagawa.jp/incident/383682#50ecb9ee743999b2ebed1f00ba59db611e456473e9cd9bc1d2b1ca8ab95d87cf Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/383069 Wed, 12 Jun 2024 21:21:26 -0000 https://status.shc.kanagawa.jp/incident/383069#f77b78d294ef0d1edd6106df4b5cda12d2db17e196db1335391c1ef7298855d1 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/383069 Wed, 12 Jun 2024 21:21:01 -0000 https://status.shc.kanagawa.jp/incident/383069#fdba4fbb7256e987908b6c9057c02ec565e46f5fed7ab1cd698ab1cc283aeee9 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/383069 Wed, 12 Jun 2024 21:20:47 -0000 https://status.shc.kanagawa.jp/incident/383069#7fcac6353501c213852a725579107e25a467d75e427e3f2e98cc9c0706f5a433 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/383069 Wed, 12 Jun 2024 21:20:28 -0000 https://status.shc.kanagawa.jp/incident/383069#efc41459f9c3e91be5cb951a422a0d3eb336f7da92ce5964cbe3a9819482e368 Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/383069 Wed, 12 Jun 2024 21:19:39 -0000 https://status.shc.kanagawa.jp/incident/383069#0cbc70bd8f62e6bdc621308f240535e0abd5b75474e7fda6215f366b06b5e89c Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/383069 Wed, 12 Jun 2024 21:19:23 -0000 https://status.shc.kanagawa.jp/incident/383069#931a227c076c0234072a44a5b659ac5c2b4da951eb36e0040a204f57d318c078 Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/383069 Wed, 12 Jun 2024 14:41:37 -0000 https://status.shc.kanagawa.jp/incident/383069#bf5180b84e53af276f82e7889e2070243061f57790c94d60c815086cee545835 ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/383069 Wed, 12 Jun 2024 14:41:13 -0000 https://status.shc.kanagawa.jp/incident/383069#2e9247c5c5fb8ef089a88884b97463660cc972ccb9d841d62adf82e220d80458 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/383069 Wed, 12 Jun 2024 14:40:54 -0000 https://status.shc.kanagawa.jp/incident/383069#8e49214196b41723c6b1c5213bf7e4998694d91c19bd455b103328c73a2c451b Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/383069 Wed, 12 Jun 2024 14:40:27 -0000 https://status.shc.kanagawa.jp/incident/383069#c0a7882383a56e9a0c0795f2b395670e274d9e2f8ec9c920808920f97f6e44c8 ownCloud (share.shc.kanagawa.jp) went down and Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/383069 Wed, 12 Jun 2024 14:40:27 -0000 https://status.shc.kanagawa.jp/incident/383069#c0a7882383a56e9a0c0795f2b395670e274d9e2f8ec9c920808920f97f6e44c8 ownCloud (share.shc.kanagawa.jp) went down and Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/383069 Wed, 12 Jun 2024 14:38:14 -0000 https://status.shc.kanagawa.jp/incident/383069#6033dd564ceb5382c1ae1cc148c8c4f36ae0bbdcd5eb1d71b4acb3f721f1c76e Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/383069 Wed, 12 Jun 2024 14:37:35 -0000 https://status.shc.kanagawa.jp/incident/383069#4b3f3c75669b7fb69281f52c060780c8b45ec9b0f0e82eacb5e916be54e35670 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/383069 Wed, 12 Jun 2024 14:37:35 -0000 https://status.shc.kanagawa.jp/incident/383069#4b3f3c75669b7fb69281f52c060780c8b45ec9b0f0e82eacb5e916be54e35670 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/383069 Wed, 12 Jun 2024 13:46:31 -0000 https://status.shc.kanagawa.jp/incident/383069#cfdd8d55574da63a2b00c467425238bd307f4bacf806263fbc65420e4122cd34 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/383069 Wed, 12 Jun 2024 10:43:17 -0000 https://status.shc.kanagawa.jp/incident/383069#3e94f23e9a6acc1a214f17376a7434fea9b469b9851c0d06756ea3b1db520113 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/383069 Wed, 12 Jun 2024 10:39:12 -0000 https://status.shc.kanagawa.jp/incident/383069#ec977a21cc1dd5afdec0fa96258bcdcb81c12c05f17849307b23676267cc06bf Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/383069 Wed, 12 Jun 2024 05:17:20 -0000 https://status.shc.kanagawa.jp/incident/383069#0c95ecc6d861471a499752cd646bcc357ebf7e3c036d0d899b23ed6ac24805e4 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/382451 Tue, 11 Jun 2024 22:11:40 -0000 https://status.shc.kanagawa.jp/incident/382451#a94796c020412b1e19d6c1c9ecc93314a68f4d48ab8c4f121990238e3bcae9dd Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/382451 Tue, 11 Jun 2024 22:11:20 -0000 https://status.shc.kanagawa.jp/incident/382451#b0493190bb44dc7614b2a3e106d22858e156f6ab5b59daa9b1e1f037e8cc0ac0 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/382451 Tue, 11 Jun 2024 13:07:13 -0000 https://status.shc.kanagawa.jp/incident/382451#d1baf8744c13d0d3fb1dbf2492872a27a7b5cf661376344b8ed6c4b6a570fa0f Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/382451 Tue, 11 Jun 2024 13:06:58 -0000 https://status.shc.kanagawa.jp/incident/382451#d00e0243cadfaca6d912a4fd8cbefee8ce3e615496b4fca01a63c20aae0a1c07 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/382451 Tue, 11 Jun 2024 07:51:14 -0000 https://status.shc.kanagawa.jp/incident/382451#5fa3a145c836b065e42a1293a06649c1d2ec8225c9a35db2643498b705bb075d Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/382451 Tue, 11 Jun 2024 07:50:50 -0000 https://status.shc.kanagawa.jp/incident/382451#23cc4adc66a48ee984eb2d881fa20839bfceb2005d84738ad33005f032ef8bd5 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/382451 Tue, 11 Jun 2024 00:59:42 -0000 https://status.shc.kanagawa.jp/incident/382451#f7da24ec4693f5e6a37b9f9dc3e19cbc14dfdb86643fa2ebf98305c07298844f Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/382451 Tue, 11 Jun 2024 00:59:01 -0000 https://status.shc.kanagawa.jp/incident/382451#52a81808dd6d6fab7d91a7b8f99edeff462253ca82845a84988fab474351a869 Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/382451 Tue, 11 Jun 2024 00:58:35 -0000 https://status.shc.kanagawa.jp/incident/382451#79594b1fe17a8fda282b9d9701ac9906f776ebf77f753e06026185002b03c6a5 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/382451 Tue, 11 Jun 2024 00:57:55 -0000 https://status.shc.kanagawa.jp/incident/382451#7bf722bd545176eca4fff7d9206e59e19d2d56fe0e05df855630f5608690c77c Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/382220 Mon, 10 Jun 2024 23:41:18 -0000 https://status.shc.kanagawa.jp/incident/382220#80520f50f409a5e1297d991824ba6655d22a5a8acb4017b63fc794f40b6d869a Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/382220 Mon, 10 Jun 2024 23:28:52 -0000 https://status.shc.kanagawa.jp/incident/382220#0f9f7bfad237303ae873e0104a2d2cf2634b5a5c14d6b50061f8444ba5b336f3 Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/382220 Mon, 10 Jun 2024 21:21:10 -0000 https://status.shc.kanagawa.jp/incident/382220#1646ca9431d46dc091a5061692cd70df22354f5db745e52f3f3b7fff6d233690 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/382220 Mon, 10 Jun 2024 21:18:04 -0000 https://status.shc.kanagawa.jp/incident/382220#e78711b943d74f4770d043d7166abc4a3737363aff9e02c2d40099a2c7d57bd5 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/382220 Mon, 10 Jun 2024 16:50:55 -0000 https://status.shc.kanagawa.jp/incident/382220#d938d1a3c1a8d39c6e8905549afd62d9cbdd242c14f8f6aa568e5673c895af83 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/382220 Mon, 10 Jun 2024 15:44:20 -0000 https://status.shc.kanagawa.jp/incident/382220#d6a30468b87a9e674f93e1f3240a8912ca20c83d25aad94f03802dee4f215f9a Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/382220 Mon, 10 Jun 2024 15:05:54 -0000 https://status.shc.kanagawa.jp/incident/382220#b3f97e4faa6e9ce7c3a617c884e699b3d66ed81782d67222028e71daf389fdb2 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/382220 Mon, 10 Jun 2024 15:02:13 -0000 https://status.shc.kanagawa.jp/incident/382220#28f7f56fca2545ff6c79e44276a535155bc404002a3d3f5109c861b96960668d Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/382220 Mon, 10 Jun 2024 13:32:05 -0000 https://status.shc.kanagawa.jp/incident/382220#007ac8517277c6f18a21b58f9b29a4e15cfa8d5ed8a675509ba0f90240f1ae27 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/382220 Mon, 10 Jun 2024 13:31:40 -0000 https://status.shc.kanagawa.jp/incident/382220#301ccae2479ce2bcfbeceabedd3bbd06b5867f1d33fb8ab8d8da02509f838362 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/382220 Mon, 10 Jun 2024 12:31:52 -0000 https://status.shc.kanagawa.jp/incident/382220#68491b1493aef80a7f609e030e6afbe84785a3aaf1a298657dffff32994c7a62 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/382220 Mon, 10 Jun 2024 12:25:39 -0000 https://status.shc.kanagawa.jp/incident/382220#02ebb25012e962b0afa0f9a73f8b52ba8fc03f4f6a69e0dcdda69aecd6b07648 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/381804 Sun, 09 Jun 2024 16:58:24 -0000 https://status.shc.kanagawa.jp/incident/381804#7db4aa1c627ecef4dfa29104f5d638d75752966c97105a5cd680194fa5063da0 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/381804 Sun, 09 Jun 2024 16:51:55 -0000 https://status.shc.kanagawa.jp/incident/381804#51cc42eb18ca3de9314f37841244a2889ccfabe2527e2c17fe7be445a3caa595 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/381804 Sun, 09 Jun 2024 16:45:56 -0000 https://status.shc.kanagawa.jp/incident/381804#f2eac0dd47182cbe1847acb087d46b29ca74fe067eefc80b3401caf0d8ac58cd Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/381804 Sun, 09 Jun 2024 16:39:50 -0000 https://status.shc.kanagawa.jp/incident/381804#72504e59643913512ef33029904080de4e1acf341de2be94b2351e57b5bb0438 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/381804 Sun, 09 Jun 2024 16:34:02 -0000 https://status.shc.kanagawa.jp/incident/381804#c6e85a0ef9517519be8fa4af11c7f75e1a60bfcd7ff8a224cfcbce0c70d6bf7e Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/381804 Sun, 09 Jun 2024 16:24:46 -0000 https://status.shc.kanagawa.jp/incident/381804#31061e0ab03a4406335d39717bd3af979524ddc4aab620bad45df56ae24afc9a Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/381804 Sun, 09 Jun 2024 16:13:34 -0000 https://status.shc.kanagawa.jp/incident/381804#1437587a462c4be46cf10b321abd763249f1ed37f174d4307e2fc52011764125 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/381804 Sun, 09 Jun 2024 16:09:58 -0000 https://status.shc.kanagawa.jp/incident/381804#936fdeaa8bd14d4ec48149df9aedf33fd7faa0fd6a073368a448dcd1046a26fa Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/381804 Sun, 09 Jun 2024 15:52:23 -0000 https://status.shc.kanagawa.jp/incident/381804#1ebb63eadeaefeb6fecbe12fac90d110116f3bd064f456972357b9fa09b36bfe Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/381804 Sun, 09 Jun 2024 15:48:50 -0000 https://status.shc.kanagawa.jp/incident/381804#22f19a1d6a9f0539d91f9798503b716f3c3e7ed1662bd8104ed3418bc8c71b9d Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/381804 Sun, 09 Jun 2024 15:37:33 -0000 https://status.shc.kanagawa.jp/incident/381804#47ad871ae29e40528b7fac91c07392067bd8d480edc7acb2460ae9804b25bbb3 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/381804 Sun, 09 Jun 2024 14:55:03 -0000 https://status.shc.kanagawa.jp/incident/381804#41bffd8093da18f403c9fc328de4433a2cd06748e434c5c49eb6d47c9004eb97 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/381804 Sun, 09 Jun 2024 14:51:26 -0000 https://status.shc.kanagawa.jp/incident/381804#1e80e859eaa846c324b12daad960ce013fe36fbb1b8db3f453b37af6962a1843 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/381804 Sun, 09 Jun 2024 12:12:14 -0000 https://status.shc.kanagawa.jp/incident/381804#b0ec10b921b488a9c027526fe8338be78d244c7fc00e0d57c42308e5de0089ef Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/381569 Sat, 08 Jun 2024 20:55:23 -0000 https://status.shc.kanagawa.jp/incident/381569#5b9012cdf095be806ab9581d1dd4cffc9fb1dd549cad1e61cf00762e7991f9f0 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/381569 Sat, 08 Jun 2024 20:54:41 -0000 https://status.shc.kanagawa.jp/incident/381569#097931a248e8893098c489a7790fed1506b5952749c6c3dc4f0ddfa1b42b8ceb NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/381098 Fri, 07 Jun 2024 16:31:40 -0000 https://status.shc.kanagawa.jp/incident/381098#7cda75444b257bb73d9ba8fcacfb7779e65a869d7e94d0f4c6bc5d390289bd63 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/381098 Fri, 07 Jun 2024 16:31:40 -0000 https://status.shc.kanagawa.jp/incident/381098#7cda75444b257bb73d9ba8fcacfb7779e65a869d7e94d0f4c6bc5d390289bd63 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/381098 Fri, 07 Jun 2024 16:31:35 -0000 https://status.shc.kanagawa.jp/incident/381098#0d765a119089515ecc933d1c809932fd7040ccefaaa6b8884999a35993f88f2b Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/381098 Fri, 07 Jun 2024 16:31:35 -0000 https://status.shc.kanagawa.jp/incident/381098#0d765a119089515ecc933d1c809932fd7040ccefaaa6b8884999a35993f88f2b Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/380285 Thu, 06 Jun 2024 09:15:33 -0000 https://status.shc.kanagawa.jp/incident/380285#f3d89494ac4f89348138312cf75aaef27ae805e5a308c1d657bfb4baecd14bff NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/380285 Thu, 06 Jun 2024 09:12:27 -0000 https://status.shc.kanagawa.jp/incident/380285#7cfc535e632a418e569deb3b8212837d7e1b9ba4713f1b24d5b053a1b3404314 NextCloud Maintenance recovered. https://status.shc.kanagawa.jp/incident/380285 Thu, 06 Jun 2024 09:02:15 -0000 https://status.shc.kanagawa.jp/incident/380285#38bad0c1383876ba57d10d2ec0a8f064671c509a14f955de36c4e6cf5fa3e854 NextCloud Maintenance went down. https://status.shc.kanagawa.jp/incident/380285 Thu, 06 Jun 2024 08:54:33 -0000 https://status.shc.kanagawa.jp/incident/380285#99c56e73497f0c63fe9870fb136ef1f9d386f791ac980fc936e9e119cafe0ec4 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/380285 Thu, 06 Jun 2024 05:48:41 -0000 https://status.shc.kanagawa.jp/incident/380285#25fd2cd6b0c41f5dfb97f0d8517ae91549918eb9f9efd52de5c986b7b5218847 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/380285 Thu, 06 Jun 2024 05:42:20 -0000 https://status.shc.kanagawa.jp/incident/380285#f88e3c4d53ee40b3044c6c0a080c47ecc05521b94ed9602fb271d701d400105d NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/378861 Mon, 03 Jun 2024 21:17:34 -0000 https://status.shc.kanagawa.jp/incident/378861#7723ba2a0e5a3caa6a103a5be60a4cd93702af6299e4765bc89b9a1aa5d4ba83 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/378861 Mon, 03 Jun 2024 21:14:32 -0000 https://status.shc.kanagawa.jp/incident/378861#1db3c3a2f337b438f730cbe0e2183933b787fcc6913ff8ad6c34e08762657388 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/377468 Fri, 31 May 2024 13:16:03 -0000 https://status.shc.kanagawa.jp/incident/377468#571bd6eac34d54537dce01aacbc3c7f567ba946fbbe061b29f7a5119fa06ec75 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/377468 Fri, 31 May 2024 13:14:59 -0000 https://status.shc.kanagawa.jp/incident/377468#f1275b9b2f972f14048472e630c50c2c148dc60691cd3a879353edee4b0c8a7f Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/377046 Thu, 30 May 2024 16:46:20 -0000 https://status.shc.kanagawa.jp/incident/377046#c3d4b0b93c6df453f2af607052a452afae709554ed647f30773e541ca0377ea7 Pleroma Daily Database Backup recovered. https://status.shc.kanagawa.jp/incident/377046 Thu, 30 May 2024 16:30:42 -0000 https://status.shc.kanagawa.jp/incident/377046#dde572041827c7c8110add942713e0f1e4c700687bb004e4fece16600f496342 Pleroma Daily Database Backup went down. https://status.shc.kanagawa.jp/incident/377046 Thu, 30 May 2024 16:06:40 -0000 https://status.shc.kanagawa.jp/incident/377046#0c29edbb2d8f071360bd8028677e81ca0d7bcb1adca41eb60d9cdf7af3c89bae Mastodon Daily Database Backup recovered. https://status.shc.kanagawa.jp/incident/377046 Thu, 30 May 2024 15:55:49 -0000 https://status.shc.kanagawa.jp/incident/377046#c6b77aa0e847d3e9901a181a57064d4cef4b4fa2601c24b87bd213bdde1f6e55 Mastodon Daily Database Backup went down. https://status.shc.kanagawa.jp/incident/375555 Mon, 27 May 2024 23:39:49 -0000 https://status.shc.kanagawa.jp/incident/375555#206c33be70e980c1be25dfa48e012ab438cbc7c508a9df614145939f29b9a1b9 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/375555 Mon, 27 May 2024 23:37:49 -0000 https://status.shc.kanagawa.jp/incident/375555#56d27eb4c624fa940c051e77b30edcb06c558ec66ce104b2917c94038edde030 NextCloud Maintenance recovered. https://status.shc.kanagawa.jp/incident/375555 Mon, 27 May 2024 20:54:49 -0000 https://status.shc.kanagawa.jp/incident/375555#532ab86ebbd4c7789c18b465cf9af4a5e0cf56d2aee4751b4042195023b03ea0 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/375555 Mon, 27 May 2024 20:50:45 -0000 https://status.shc.kanagawa.jp/incident/375555#93092933c52fe332af6c48f57be1fee4321e4cce73832df1f9337a13458ca400 NextCloud Maintenance went down. https://status.shc.kanagawa.jp/incident/375555 Mon, 27 May 2024 20:46:11 -0000 https://status.shc.kanagawa.jp/incident/375555#48d758389a9fdd60e5755fd65fb46e74c862f929455e3912ba6cd35ea0f9769f NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/375555 Mon, 27 May 2024 20:42:38 -0000 https://status.shc.kanagawa.jp/incident/375555#6dfb9e2cadb9f0e38c4117c2a451637d45ef1492bf482a6113c055e4c3df46b6 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/374122 Fri, 24 May 2024 12:07:23 -0000 https://status.shc.kanagawa.jp/incident/374122#80e23ad11f955a38bc2d0ac43293cc75002e6bc983c37d293770006b28775de7 Pleroma(pr.shc.kanagawa.jp) and ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/374122 Fri, 24 May 2024 12:07:23 -0000 https://status.shc.kanagawa.jp/incident/374122#80e23ad11f955a38bc2d0ac43293cc75002e6bc983c37d293770006b28775de7 Pleroma(pr.shc.kanagawa.jp) and ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/374122 Fri, 24 May 2024 12:06:34 -0000 https://status.shc.kanagawa.jp/incident/374122#ca75ce4c005fadc5e2c4f9cd770e772692207b25d786f22e6ca04b78617b573f Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/374122 Fri, 24 May 2024 12:06:34 -0000 https://status.shc.kanagawa.jp/incident/374122#ca75ce4c005fadc5e2c4f9cd770e772692207b25d786f22e6ca04b78617b573f Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/374122 Fri, 24 May 2024 12:06:05 -0000 https://status.shc.kanagawa.jp/incident/374122#a3d173803b87f974aa46632fb22dc7d08177068974db5cbb3cad3db39234355d Pleroma(pr.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/374122 Fri, 24 May 2024 12:06:05 -0000 https://status.shc.kanagawa.jp/incident/374122#a3d173803b87f974aa46632fb22dc7d08177068974db5cbb3cad3db39234355d Pleroma(pr.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/374122 Fri, 24 May 2024 12:05:30 -0000 https://status.shc.kanagawa.jp/incident/374122#3afb703c805a1e969806c3cfb16e64c41cbc0e39afded58c0f887b682bc7ea4e Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/374122 Fri, 24 May 2024 12:04:32 -0000 https://status.shc.kanagawa.jp/incident/374122#444c5933fa6495a61d4ee136bf6b97412ae156436987d6561550b6f425269eed ownCloud (share.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/374122 Fri, 24 May 2024 11:25:38 -0000 https://status.shc.kanagawa.jp/incident/374122#27a22e9a7e01ef07d77742fa027f019b66768805fedb7986806ad300b85e3a11 ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/374122 Fri, 24 May 2024 11:22:07 -0000 https://status.shc.kanagawa.jp/incident/374122#98fb1654271ba02864f7b43c405aeb485cfd2d02c2f93e6cb70779742d297e28 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/374122 Fri, 24 May 2024 11:21:52 -0000 https://status.shc.kanagawa.jp/incident/374122#350d89d832e997db63b1a3ccd336ec8ccc964c6887f850436ca7be621621b405 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/374122 Fri, 24 May 2024 11:21:38 -0000 https://status.shc.kanagawa.jp/incident/374122#bec543fe05fb75606938f667498f429b7529e94b731711e6bba1da9910f8f0d2 Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/374122 Fri, 24 May 2024 11:15:15 -0000 https://status.shc.kanagawa.jp/incident/374122#06c92c5a84ffb137fabff49b76a6cfb95bd385ed8094b2c5bd44bfdd5e6ae4e5 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/374122 Fri, 24 May 2024 11:14:27 -0000 https://status.shc.kanagawa.jp/incident/374122#187d49e4b81826ae68fc5161a4fd4a2424d5a4705606fa693bf83f8ef7c1dddf Mastodon(mt.shc.kanagawa.jp) and ownCloud (share.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/374122 Fri, 24 May 2024 11:14:27 -0000 https://status.shc.kanagawa.jp/incident/374122#187d49e4b81826ae68fc5161a4fd4a2424d5a4705606fa693bf83f8ef7c1dddf Mastodon(mt.shc.kanagawa.jp) and ownCloud (share.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/374122 Fri, 24 May 2024 11:12:09 -0000 https://status.shc.kanagawa.jp/incident/374122#907e526a8950b38070d0eeb3470acd64ccd4ad1a49603e5b42855025002eeeca Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/373223 Thu, 23 May 2024 06:12:29 -0000 https://status.shc.kanagawa.jp/incident/373223#2c9397760c3b114c9af0cf4bfcf97568ed983243c9e5c75611300d3e29b8443d Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/373223 Thu, 23 May 2024 06:09:22 -0000 https://status.shc.kanagawa.jp/incident/373223#84ddb1cba6b441090aa1115d4333bcd7565d468ed1e108e0dc22f723cae47c51 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/373223 Thu, 23 May 2024 05:35:09 -0000 https://status.shc.kanagawa.jp/incident/373223#bc6a815857bc4de8d787b9f2efdae626bb840feec359f646faf18e0123354e5b Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/373223 Thu, 23 May 2024 05:06:32 -0000 https://status.shc.kanagawa.jp/incident/373223#b4426809af965264f88668865e9f7c94c61e6d7122fd915bd0d0be7fa717f459 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/373223 Thu, 23 May 2024 04:44:36 -0000 https://status.shc.kanagawa.jp/incident/373223#cc085785ffc7216a016606ad46a36bb7b5b310cb0da1511f218777f2ebd85b8f Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/373223 Thu, 23 May 2024 04:13:09 -0000 https://status.shc.kanagawa.jp/incident/373223#36496517c44105069d8dc344ed1b94871a4ca45c103ffe239f8082fb8e94c82e Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/373223 Thu, 23 May 2024 04:06:12 -0000 https://status.shc.kanagawa.jp/incident/373223#40477f6f493a3681d233dc397ed8eef11d4a5d9f5e51bb174a67c01923e5c52c Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/373223 Thu, 23 May 2024 03:59:57 -0000 https://status.shc.kanagawa.jp/incident/373223#bc303c29193c27790c8f212e0e6f1e5f98187f90e8d1b653acd5d1f96da69bcf Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/373223 Thu, 23 May 2024 03:42:43 -0000 https://status.shc.kanagawa.jp/incident/373223#0a4504ec2567866bdf3a472d6e845cbd514ab8173bf051d3e040738d59600400 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/373223 Thu, 23 May 2024 03:21:37 -0000 https://status.shc.kanagawa.jp/incident/373223#d8d85b76d62619722f7768abbdcdcf61f024b9cfcf0672817f8af40c69f2ef71 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/373223 Thu, 23 May 2024 02:53:38 -0000 https://status.shc.kanagawa.jp/incident/373223#a92950f05c2a23b9d1d23cbc199e74bfca8d2b481691b381466b9d2179a70753 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/373223 Thu, 23 May 2024 02:50:48 -0000 https://status.shc.kanagawa.jp/incident/373223#d30088afa49f2a4264cb18ce3d2f76aca2098edf45a317fa0ab4763f539acbea Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/373223 Thu, 23 May 2024 02:18:51 -0000 https://status.shc.kanagawa.jp/incident/373223#7f2e744f89dfdac8b7b269c802205b619f972a0d9e56524e86c002f7f657fbe7 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/373223 Thu, 23 May 2024 02:11:47 -0000 https://status.shc.kanagawa.jp/incident/373223#d9851d245f1c7d646046f4288f43a94daec944cb2102d116d63001d3a8f85b29 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/373223 Thu, 23 May 2024 02:03:47 -0000 https://status.shc.kanagawa.jp/incident/373223#6a84b036557e29c67f78fea0935610e434d67b53ae6145c18e3296b0b0dacffc Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/373223 Thu, 23 May 2024 01:56:48 -0000 https://status.shc.kanagawa.jp/incident/373223#84ab355f74b3ab623941e9e6a089a5cc7410a4d199b98714dc3e5c3ae82a5853 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/373223 Thu, 23 May 2024 01:45:44 -0000 https://status.shc.kanagawa.jp/incident/373223#577fb24a8880d96a4f676599201ea2211a4fdc603546cfb95b7bfb895d93c380 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/373223 Thu, 23 May 2024 00:33:16 -0000 https://status.shc.kanagawa.jp/incident/373223#7384f78d5cdb65e2067c9134653454755bd3991a1eca8df53f1d3685d2d757e2 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/373223 Thu, 23 May 2024 00:09:03 -0000 https://status.shc.kanagawa.jp/incident/373223#04268c31178a754a29951c8ad68f5782480738e83fc75633842b47b0f85eaebd Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/373223 Wed, 22 May 2024 23:33:19 -0000 https://status.shc.kanagawa.jp/incident/373223#6e336aa7c384df478bcfef0cf98ebd8f2007696f0c1880bcde5e5b989733344b Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/373223 Wed, 22 May 2024 23:27:19 -0000 https://status.shc.kanagawa.jp/incident/373223#3a4e03fa88a2484f3851988cc7894f6b7a428d6924d36b6d147ddc65875c203a Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/373223 Wed, 22 May 2024 23:20:46 -0000 https://status.shc.kanagawa.jp/incident/373223#f68d6f96096bb9a2976da39abfbf8790182f0f7bffb366a7c41ef31b71f202cb Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/373223 Wed, 22 May 2024 23:12:40 -0000 https://status.shc.kanagawa.jp/incident/373223#81c2608b5dcf4b5e3abaf56e4e37127c71dfac627dfeb9726adaa0c77706a3c2 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/373223 Wed, 22 May 2024 22:48:25 -0000 https://status.shc.kanagawa.jp/incident/373223#998fa147e9d8f7e3fb4153faafaf18da9351c4352a717fff7370c6a6a8e89f83 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/373223 Wed, 22 May 2024 22:36:46 -0000 https://status.shc.kanagawa.jp/incident/373223#e3d9b716de51592c5956d9f9bfa0c2820eb6225098a745de5079aac60d909951 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/373223 Wed, 22 May 2024 22:32:52 -0000 https://status.shc.kanagawa.jp/incident/373223#7e507f6a4c16fe76c71d12025fc201a118967b5c95c8d2f294c0d40f48cdccbd Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/373223 Wed, 22 May 2024 22:21:48 -0000 https://status.shc.kanagawa.jp/incident/373223#eb59bfbf56ddc896b58e45a72ee1806e7034ecc16a894c427de25f66126faa62 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/373223 Wed, 22 May 2024 21:36:43 -0000 https://status.shc.kanagawa.jp/incident/373223#dce5b761f7168c54aae2fda441fe8b5dff4e87a9d2dfa154256ae4dfc12606fe Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/373223 Wed, 22 May 2024 21:17:47 -0000 https://status.shc.kanagawa.jp/incident/373223#73e45e4ee10bb68d163937848c2605011fcacc5a0f5f3d0832b0761011202450 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/373223 Wed, 22 May 2024 21:11:37 -0000 https://status.shc.kanagawa.jp/incident/373223#60598caadb5cef05943979a1b19a2559c090901aab08775f93240f3d8464c3a9 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/373223 Wed, 22 May 2024 20:48:34 -0000 https://status.shc.kanagawa.jp/incident/373223#70994a7747d67a6fb4102f5b238607a9f34fa67cdc8cb0bf3a25fb17730be02e Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/373223 Wed, 22 May 2024 20:45:21 -0000 https://status.shc.kanagawa.jp/incident/373223#27a4751460389293521a2395213bc383c47e576955bde97a14b1e50fded76aff Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/373223 Wed, 22 May 2024 20:35:20 -0000 https://status.shc.kanagawa.jp/incident/373223#2ae934c6f2c5477960c281d391bb4b43b534a3af403701af01e42eab8e409e25 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/373223 Wed, 22 May 2024 20:21:07 -0000 https://status.shc.kanagawa.jp/incident/373223#34b775e68e17d226119e35fb43410b0a9ca85ede788b1cecd26006fb53244a0a Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/373223 Wed, 22 May 2024 20:12:41 -0000 https://status.shc.kanagawa.jp/incident/373223#af0f3eb1cf55b099a60ce14004e84615412adb35937873ec8d32166e897a9168 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/373223 Wed, 22 May 2024 20:06:37 -0000 https://status.shc.kanagawa.jp/incident/373223#cca6ef135d91a06171d5120ecc2716ed290e3b83c4ee9e519d8c11413ca87a34 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/373223 Wed, 22 May 2024 19:59:34 -0000 https://status.shc.kanagawa.jp/incident/373223#33b6cdbe76b21d1d692cd5a3f6da447de12738280bd94322118a30c18145a5d9 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/373223 Wed, 22 May 2024 19:17:44 -0000 https://status.shc.kanagawa.jp/incident/373223#ad7fd38ddfa5c3acef84325f89095ba8b0fb3022ce3aab7736aab1ff18225e88 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/373223 Wed, 22 May 2024 19:09:29 -0000 https://status.shc.kanagawa.jp/incident/373223#63aa9b23887c65940ea7a32b3bcda08895c206cb9bd95a9968d9b2fb0881ea67 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/373223 Wed, 22 May 2024 19:03:53 -0000 https://status.shc.kanagawa.jp/incident/373223#0046bdc6900fb8af85077b2c1d0504ccbb6b4310cfe1249acab992c8e080792a Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/373223 Wed, 22 May 2024 18:53:55 -0000 https://status.shc.kanagawa.jp/incident/373223#a14e09ec56d5257463b0035308a45e50fde970f3c2c03b2db66d08ae7d58f3e0 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/373223 Wed, 22 May 2024 18:45:50 -0000 https://status.shc.kanagawa.jp/incident/373223#38d7f4ea0e64c6a4a0eb5b39d6afcfe32d17b9ec724b031b5d4dea7208901756 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/373223 Wed, 22 May 2024 16:30:18 -0000 https://status.shc.kanagawa.jp/incident/373223#b65bea760aa9de9363d998fbc1f66b9192243f05dfb729925ae704c409d99b03 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/373223 Wed, 22 May 2024 16:30:05 -0000 https://status.shc.kanagawa.jp/incident/373223#a89a6a406284efdaccd0ed1116ddb8954e89aaa077100f0333bd8f0950861a44 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/372007 Mon, 20 May 2024 20:53:53 -0000 https://status.shc.kanagawa.jp/incident/372007#b492626092a940451a8ad6d7c324daec39e2e01146ad7bf013d33576cb798e8f NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/372007 Mon, 20 May 2024 20:53:31 -0000 https://status.shc.kanagawa.jp/incident/372007#d02a8404709e1b53ac63156c44d8a84e39aa9fc7279e433120915c7e104a03e9 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/372007 Mon, 20 May 2024 16:14:45 -0000 https://status.shc.kanagawa.jp/incident/372007#3909661a652b782b1c0fbdb6ea26ee652575a99dc7d2846f266d287339ed2a0b Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/372007 Mon, 20 May 2024 16:13:25 -0000 https://status.shc.kanagawa.jp/incident/372007#4a9e86e2846a9ace9b86709b978c03d5498663d7c756d3dde96feca34bf599e9 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/372007 Mon, 20 May 2024 15:26:30 -0000 https://status.shc.kanagawa.jp/incident/372007#0c36e42edb057d5b7f9162a069abfb230777fb8ff2a1c6cf3a7cab985e55c450 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/372007 Mon, 20 May 2024 15:25:12 -0000 https://status.shc.kanagawa.jp/incident/372007#3bae2caa4210bb2e08add21de33b3279b09b45319ae008a70c0667632dc89f66 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/372007 Mon, 20 May 2024 14:23:36 -0000 https://status.shc.kanagawa.jp/incident/372007#0d8273822e15c1f1db0f531da41bc274153e6d62b52b6e989a9c8116e1936b99 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/372007 Mon, 20 May 2024 14:22:09 -0000 https://status.shc.kanagawa.jp/incident/372007#31410d23ab30b26b25b6ef8e17799d74feb82421935509b17ee2fa0c26320a68 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/372007 Mon, 20 May 2024 14:02:15 -0000 https://status.shc.kanagawa.jp/incident/372007#fdaeeba6c37d9d0866360075292ee3ea191adc37250ede8239420f4ffcf01efc Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/372007 Mon, 20 May 2024 14:01:15 -0000 https://status.shc.kanagawa.jp/incident/372007#4cf42afd566b14848eb8707ac70acf3f4e26c7fb9b5e194f5a8f2c5731444638 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/372007 Mon, 20 May 2024 11:31:16 -0000 https://status.shc.kanagawa.jp/incident/372007#6766a0e8844c889c3a2c27d8dd8bf962e945dacafe976fd221da4a721fc0d9ff Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/372007 Mon, 20 May 2024 11:29:55 -0000 https://status.shc.kanagawa.jp/incident/372007#a8fd69c96011b6c6f4283db51ca9675524f748027a303a7516c5736691617fc0 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/372007 Mon, 20 May 2024 11:10:09 -0000 https://status.shc.kanagawa.jp/incident/372007#5603351bbb6a303965c50a0c3ae57d051ac95c217488d2b9443251051258cf39 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/372007 Mon, 20 May 2024 11:09:03 -0000 https://status.shc.kanagawa.jp/incident/372007#cf5c06ba92e17dc89e3a18bebfc34607e646d8f7d2aa32b8a5534fdfa7f78059 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/372007 Mon, 20 May 2024 09:44:32 -0000 https://status.shc.kanagawa.jp/incident/372007#cd8001d39efd262f2f747814aa904d01cd298110e3f443dbf1e42851a3bb69ac Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/372007 Mon, 20 May 2024 09:43:34 -0000 https://status.shc.kanagawa.jp/incident/372007#2215b56a37a1915b4c7c9e3aebda923d3f120ccdb27ee4694b942ddb66c9d27e Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/371482 Sun, 19 May 2024 02:01:33 -0000 https://status.shc.kanagawa.jp/incident/371482#ddd3486a701681432c60954ac9ec4f66347e66df312fa7567aa09d31bef458db Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/371482 Sun, 19 May 2024 02:01:20 -0000 https://status.shc.kanagawa.jp/incident/371482#27012433ddbbad99c3de18cb797782ccf468e2f8185e3b03e03ae7ab52f8f20a Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/370844 Fri, 17 May 2024 11:56:05 -0000 https://status.shc.kanagawa.jp/incident/370844#1903aae880558955dd30fd082aa46a211a4087dc0c6a16c0ac4ad6f89d5dccd9 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/370844 Fri, 17 May 2024 11:53:06 -0000 https://status.shc.kanagawa.jp/incident/370844#f4a0ba8f71865aeb1abac7685630d3d7871b0cb4cbc469b03df2c3748fb15659 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/369787 Wed, 15 May 2024 16:55:52 -0000 https://status.shc.kanagawa.jp/incident/369787#faa03bb781c6a049933870d730a9660d6b1966630e2e9d8544f0231f5e2ff1b0 ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/369787 Wed, 15 May 2024 16:55:32 -0000 https://status.shc.kanagawa.jp/incident/369787#aa3016bbcb8e03caf345ed9e3483780ad69bc9193d9e33f2c5a13c398f7afdeb Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/369787 Wed, 15 May 2024 16:54:47 -0000 https://status.shc.kanagawa.jp/incident/369787#58fb98a38e1198ec956647c5e6c317f7e2f56246dbd1406a539082d128362ab0 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/369787 Wed, 15 May 2024 16:54:47 -0000 https://status.shc.kanagawa.jp/incident/369787#58fb98a38e1198ec956647c5e6c317f7e2f56246dbd1406a539082d128362ab0 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/369787 Wed, 15 May 2024 16:54:24 -0000 https://status.shc.kanagawa.jp/incident/369787#3f3574d447e0275c951f8b8ac7a7f6f2b322904499a96740446d3f1093eeec96 ownCloud (share.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/369787 Wed, 15 May 2024 16:52:32 -0000 https://status.shc.kanagawa.jp/incident/369787#4d12fe4a121eb41f65cf5b45a356ec631ddc748f668d4bf56290c8d000168119 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/369787 Wed, 15 May 2024 16:51:56 -0000 https://status.shc.kanagawa.jp/incident/369787#3114013a226b17613f869726105f788dd713765caa0d31426162be9a11c1fbd8 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/369787 Wed, 15 May 2024 16:50:47 -0000 https://status.shc.kanagawa.jp/incident/369787#df9549ee977ebc3530ed2f83f8dd0840d1d000485845656d5c362c5f2fac818b Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/369787 Wed, 15 May 2024 14:42:43 -0000 https://status.shc.kanagawa.jp/incident/369787#7f3d2a21085ed75747e8e09dcd723538e8f4f923c13e2a2a0bde2d05298ebffb Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/369787 Wed, 15 May 2024 14:41:01 -0000 https://status.shc.kanagawa.jp/incident/369787#ace9fd8865852c82aea64b760ebf29f8c423e72e7aae7364a8ac1c473869599f NextCloud (cloud.shc.kanagawa.jp) and ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/369787 Wed, 15 May 2024 14:41:01 -0000 https://status.shc.kanagawa.jp/incident/369787#ace9fd8865852c82aea64b760ebf29f8c423e72e7aae7364a8ac1c473869599f NextCloud (cloud.shc.kanagawa.jp) and ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/369787 Wed, 15 May 2024 14:40:32 -0000 https://status.shc.kanagawa.jp/incident/369787#57a8a506e3e5f36fbfc52898c1ff628af44c239c350a79752a5a44e49e857b6d Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/369787 Wed, 15 May 2024 14:40:00 -0000 https://status.shc.kanagawa.jp/incident/369787#e6b8e8f1a7e511eec4031669b42e3e3ee9f40d4298873de77bbeb31feb233b42 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/369787 Wed, 15 May 2024 14:37:52 -0000 https://status.shc.kanagawa.jp/incident/369787#1424841a4890e988a8d66e7ceba5b57cea15a53c692e0cf9cc9085e9ccd29219 NextCloud (cloud.shc.kanagawa.jp) and ownCloud (share.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/369787 Wed, 15 May 2024 14:37:52 -0000 https://status.shc.kanagawa.jp/incident/369787#1424841a4890e988a8d66e7ceba5b57cea15a53c692e0cf9cc9085e9ccd29219 NextCloud (cloud.shc.kanagawa.jp) and ownCloud (share.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/369787 Wed, 15 May 2024 14:37:04 -0000 https://status.shc.kanagawa.jp/incident/369787#cdd612264c00fb430aba2ffc201d84ccb4ef00f7c4143c05fbd5ac3567e0e54c Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/369787 Wed, 15 May 2024 14:36:33 -0000 https://status.shc.kanagawa.jp/incident/369787#eaf5dfed5bc81714bf9ea3d5f2019df2c696808171ae5e8dd3f2bbd4265f4db0 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/369787 Wed, 15 May 2024 14:36:04 -0000 https://status.shc.kanagawa.jp/incident/369787#8b758f76438e19f360a410de5cddd684e3a78c974a6d658eb4db18ae24070fc5 Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/368821 Mon, 13 May 2024 20:46:07 -0000 https://status.shc.kanagawa.jp/incident/368821#3958155fdda90063e7ebd45a4f22c942a80437ff021f23b117c1c192dfa5bebb NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/368821 Mon, 13 May 2024 20:42:56 -0000 https://status.shc.kanagawa.jp/incident/368821#584cd7d4e769850cb3efaacc7ee9eeedc984bbf7269ded10b4ba950b3efef125 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/367121 Thu, 09 May 2024 20:46:04 -0000 https://status.shc.kanagawa.jp/incident/367121#ee2a30162b4ce400d420cde951cbd00bf307d772bb9887aa035bbbdaaf38fdcb NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/367121 Thu, 09 May 2024 20:45:07 -0000 https://status.shc.kanagawa.jp/incident/367121#b9d2492acae69b2cc364fa68d40edb7b456f51086a6786e72186fadedd006adc NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/367121 Thu, 09 May 2024 15:45:34 -0000 https://status.shc.kanagawa.jp/incident/367121#18410061dad5ca9e1ddfc88a4618ba0b329a8c475d5e4edc4f4782e397a30f3a Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/367121 Thu, 09 May 2024 15:44:38 -0000 https://status.shc.kanagawa.jp/incident/367121#76e57ff452794fca7d9d6dddd60342be0bc2ede2c1129375955f58326af68e96 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/365336 Mon, 06 May 2024 20:56:36 -0000 https://status.shc.kanagawa.jp/incident/365336#2d1541706b6c58592f1d9398dfa25d7a62a513119f0b27a79496a274a04754d4 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/365336 Mon, 06 May 2024 20:55:54 -0000 https://status.shc.kanagawa.jp/incident/365336#103a4ebfb078eee2c081d2de9f5c8ea6a7a177247fc437e082f5e92b105e46e3 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/365336 Mon, 06 May 2024 09:27:54 -0000 https://status.shc.kanagawa.jp/incident/365336#220e0a25c88fc422808740e28adeb94eadba18bf13050b870b77addd2f5ba557 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/365336 Mon, 06 May 2024 09:27:41 -0000 https://status.shc.kanagawa.jp/incident/365336#20778da1d0c88e9fa0de6cb906d584e7c8723b4a0cf374e96614104501623b32 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/365336 Mon, 06 May 2024 08:59:34 -0000 https://status.shc.kanagawa.jp/incident/365336#cd2ff812a2e7966c84c4da66dc9d0fcfda80f81d0a60bef1574e584af5d7db3f Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/365336 Mon, 06 May 2024 08:59:24 -0000 https://status.shc.kanagawa.jp/incident/365336#9cd30710b779bf5ac6a147cb1f79d95ec11b335a87523d378d89b9a759eedc92 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/365336 Mon, 06 May 2024 03:52:00 -0000 https://status.shc.kanagawa.jp/incident/365336#c2e160a5f3c16b87281824c28f109aa9de52bdd6d2c6431e38a6609cd5ec3433 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/365336 Mon, 06 May 2024 03:51:44 -0000 https://status.shc.kanagawa.jp/incident/365336#94d87ad8fb9e88205ca4308b1e8bea15c388c9c980b0f8c1c580b00b24658482 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/365084 Sun, 05 May 2024 15:27:48 -0000 https://status.shc.kanagawa.jp/incident/365084#68e46c5aad5c1121e2d007751cedfdf2920abd698ecda59275c29996e0189a4e Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/365084 Sun, 05 May 2024 15:27:44 -0000 https://status.shc.kanagawa.jp/incident/365084#d6def93313d70c14f348d87752754af4ed605c01c4439e2d3a379aa9fca6d0ec Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/365084 Sun, 05 May 2024 15:21:47 -0000 https://status.shc.kanagawa.jp/incident/365084#2296bf5918577b20945874b8ac60c961faa4c99e045f128bc0caa4a5b239123f Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/365084 Sun, 05 May 2024 15:20:47 -0000 https://status.shc.kanagawa.jp/incident/365084#8eacd7964a6140de294d01e3d4e727f1dc1e70ba2ed62234e5e55fb528354783 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/365084 Sun, 05 May 2024 13:55:14 -0000 https://status.shc.kanagawa.jp/incident/365084#0dde224f27d3799e35df66ca528e241b75d1d439d95bfd59516713f7dfdfeea2 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/365084 Sun, 05 May 2024 13:54:55 -0000 https://status.shc.kanagawa.jp/incident/365084#c4c369a1d33b88a71877fbc41b5e76c6e738716e24f57787adef5f46986f7059 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/365084 Sun, 05 May 2024 12:51:48 -0000 https://status.shc.kanagawa.jp/incident/365084#0279cb5af72a0a159e43a0a150a9039367d5254059618514b59ae112a94e5044 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/365084 Sun, 05 May 2024 12:51:42 -0000 https://status.shc.kanagawa.jp/incident/365084#efcc72bf0827f83db3449ee0dc475c5fe725c6519e27988fc51d108fe9ab1d8f Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/365084 Sun, 05 May 2024 11:12:50 -0000 https://status.shc.kanagawa.jp/incident/365084#2a80610c596535377a1e8608dc61fd3745f510cac2bb78e5d4b502e0947d50c9 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/365084 Sun, 05 May 2024 11:12:37 -0000 https://status.shc.kanagawa.jp/incident/365084#4e54a8a2463415b9cd11f013ee6b07df69c039db4f6173f103311ef1e3247f53 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/364676 Sat, 04 May 2024 22:42:39 -0000 https://status.shc.kanagawa.jp/incident/364676#199060e73c692bfb30c3654c47a33de201666ccda18e4faeb6d03907028186fd Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/364676 Sat, 04 May 2024 22:42:39 -0000 https://status.shc.kanagawa.jp/incident/364676#9af67cbbce59a65a10ff1e0ec50dc4e944e3c6402a01a07c3fbcca019376a5df Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/364676 Sat, 04 May 2024 10:13:02 -0000 https://status.shc.kanagawa.jp/incident/364676#924df88d25ec8ee9583ce88eabd99a62402f29ed9af043b7b54ba960f9cb4c96 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/364676 Sat, 04 May 2024 10:12:45 -0000 https://status.shc.kanagawa.jp/incident/364676#4482f148ada7525dc4be6aaf4fbf291f652a4f4a3bc4165ebda9697c4484833a Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/364212 Fri, 03 May 2024 09:10:41 -0000 https://status.shc.kanagawa.jp/incident/364212#9dc736038544072a24387942141da8b715c261694d1c5d6c7d323145a1250d9d Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/364212 Fri, 03 May 2024 09:10:26 -0000 https://status.shc.kanagawa.jp/incident/364212#e3629884f52405c76f8e029283080b3d36a4ccb8fee93fbce4bd12b49c8ff31f Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/364212 Fri, 03 May 2024 07:57:29 -0000 https://status.shc.kanagawa.jp/incident/364212#0b0862cc645b24fe026aeccabdc88d09d0227f39da36cd25c1693d2914d460a0 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/364212 Fri, 03 May 2024 07:57:18 -0000 https://status.shc.kanagawa.jp/incident/364212#60bdc50e1ed95a27fa7bb932484b411bad7cae19a6fc4f142d02c83de48fc366 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/363938 Thu, 02 May 2024 16:50:12 -0000 https://status.shc.kanagawa.jp/incident/363938#4047594edaacd90ed5c138571b54d7560e0f398c3ef74a9caac9c8d944a97e4c Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/363938 Thu, 02 May 2024 16:49:23 -0000 https://status.shc.kanagawa.jp/incident/363938#f6348d07b6efc15676ec1b9be22d108365b904b58cbd110bffb37d27d835392e Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/363202 Wed, 01 May 2024 08:20:29 -0000 https://status.shc.kanagawa.jp/incident/363202#3a601cbaf60067fbebd33460b9de6f4df14ecdb5b0158cb8151c94b7cdb85ce7 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/363202 Wed, 01 May 2024 08:17:25 -0000 https://status.shc.kanagawa.jp/incident/363202#252ecabd593f28744b29d46735dcaa3a07901102ee16af1ebe8f89c4863bf989 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/362693 Tue, 30 Apr 2024 11:04:33 -0000 https://status.shc.kanagawa.jp/incident/362693#02d9218d857c9f660049533f681bb7ee3f101fbac77d7e171437f1959135900d Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/362693 Tue, 30 Apr 2024 11:04:22 -0000 https://status.shc.kanagawa.jp/incident/362693#04b54891cb8f67785a882631e5a27f8dcbcc14753cc08feb68d505569c9985ac Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/362693 Tue, 30 Apr 2024 08:24:37 -0000 https://status.shc.kanagawa.jp/incident/362693#c1110c0f563c40d1e5c77bc05700eefa0d4fd008e4c8b65c49f320ad225ec568 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/362693 Tue, 30 Apr 2024 08:24:34 -0000 https://status.shc.kanagawa.jp/incident/362693#dc9a714bb9253af0da94d928014e90c2f148ff54e69da1dd3c7bc69bd005fcb1 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/362391 Mon, 29 Apr 2024 20:25:16 -0000 https://status.shc.kanagawa.jp/incident/362391#0dba326b5ea02adc939b9e56757de5b086bb0170106770012b2168aa6dd5a9b9 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/362391 Mon, 29 Apr 2024 20:25:02 -0000 https://status.shc.kanagawa.jp/incident/362391#9b622f4fb4faa1a66fba7f7b9acd0a53855cb220c0acbdeca122f8960b720a12 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/362391 Mon, 29 Apr 2024 16:16:56 -0000 https://status.shc.kanagawa.jp/incident/362391#df9d62c3c0fd58393fae3b2fd045a1a44684462c5e8e2b52c9008f97dacfafda Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/362391 Mon, 29 Apr 2024 16:15:57 -0000 https://status.shc.kanagawa.jp/incident/362391#842ef31597ef0c1d513dfa84a5167e00f08ede1858968b390b0b535f3013957f Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/360937 Fri, 26 Apr 2024 02:52:04 -0000 https://status.shc.kanagawa.jp/incident/360937#332f65e2d1760f1577da9b521437110cc4a7d0635f77b419f9bf5d4a6a349390 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/360937 Fri, 26 Apr 2024 02:48:37 -0000 https://status.shc.kanagawa.jp/incident/360937#16b92768538dce7a9fb327588151031fe92b87154c191bb2912a3fe59fe1f900 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/359642 Tue, 23 Apr 2024 15:45:09 -0000 https://status.shc.kanagawa.jp/incident/359642#ff9eaafeaf94345416ed21eb99cf0d684e58799723acc4c354f9f773f5dc8d8b Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/359642 Tue, 23 Apr 2024 15:44:12 -0000 https://status.shc.kanagawa.jp/incident/359642#c26341a61bdf5bc52afd86c4a7ad0bdb53d7166f1513b29798106e2b2feb6c1f Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/359642 Tue, 23 Apr 2024 13:27:31 -0000 https://status.shc.kanagawa.jp/incident/359642#a8e7c9f42360bf4a8a02a1286a8f00e3c2275fe31037020d975f2fa6ea411129 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/359642 Tue, 23 Apr 2024 13:26:57 -0000 https://status.shc.kanagawa.jp/incident/359642#9cacb2417f4caf17c0abb672d6f692399e2094d8d26d9a1b72913439bbc8eaf1 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/359642 Tue, 23 Apr 2024 13:26:26 -0000 https://status.shc.kanagawa.jp/incident/359642#8160f3c98d3c3a1710460140d7b65c3536ed93d1638e695bf168b4b017698e7a Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/359642 Tue, 23 Apr 2024 13:26:26 -0000 https://status.shc.kanagawa.jp/incident/359642#8160f3c98d3c3a1710460140d7b65c3536ed93d1638e695bf168b4b017698e7a Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/359642 Tue, 23 Apr 2024 13:26:01 -0000 https://status.shc.kanagawa.jp/incident/359642#239b1480b5fd538cf0c1864745565861d77fc7035732ddb7698e1872a724dab0 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/359642 Tue, 23 Apr 2024 13:25:23 -0000 https://status.shc.kanagawa.jp/incident/359642#ff0532bd04b85e0e7c648241b814e7bf76446d90c061d31b7debb05ab3c8a022 Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/359642 Tue, 23 Apr 2024 13:18:26 -0000 https://status.shc.kanagawa.jp/incident/359642#4ac5a9231b7bb28c1d242ea72a438747d581faf07a1831c45d054d172e661a65 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/359642 Tue, 23 Apr 2024 13:18:13 -0000 https://status.shc.kanagawa.jp/incident/359642#d06ae09cd622995b49b093d80a29e335ecec041974a6ee3929e5f9eca94a4650 Pleroma(pr.shc.kanagawa.jp) and ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/359642 Tue, 23 Apr 2024 13:18:13 -0000 https://status.shc.kanagawa.jp/incident/359642#d06ae09cd622995b49b093d80a29e335ecec041974a6ee3929e5f9eca94a4650 Pleroma(pr.shc.kanagawa.jp) and ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/359642 Tue, 23 Apr 2024 13:17:23 -0000 https://status.shc.kanagawa.jp/incident/359642#ef43080d68b3d3a6e605f39d56d93bc546305685a2690426391a9ddff7d258ea Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/359642 Tue, 23 Apr 2024 13:17:23 -0000 https://status.shc.kanagawa.jp/incident/359642#ef43080d68b3d3a6e605f39d56d93bc546305685a2690426391a9ddff7d258ea Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/359642 Tue, 23 Apr 2024 13:16:43 -0000 https://status.shc.kanagawa.jp/incident/359642#8638c5625fb4380eed681a6fb95db5714ca3e529dd77386da6d5cba9f100886b ownCloud (share.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/359642 Tue, 23 Apr 2024 13:15:30 -0000 https://status.shc.kanagawa.jp/incident/359642#2636f2bacaa7d1a8954729e98460c32bb9dea107803b5b46434dd5addfd3cff5 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/359642 Tue, 23 Apr 2024 13:15:00 -0000 https://status.shc.kanagawa.jp/incident/359642#856b990d826cbd1817d2229ff237c124cd57e99e31cbf4b77f8fcc917256dc4e Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/359642 Tue, 23 Apr 2024 13:14:21 -0000 https://status.shc.kanagawa.jp/incident/359642#6e47fdf9aa94066c39f9ed301e21ec2c20ce54f8dd245ed64264148e73fa0063 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/359642 Tue, 23 Apr 2024 13:14:21 -0000 https://status.shc.kanagawa.jp/incident/359642#6e47fdf9aa94066c39f9ed301e21ec2c20ce54f8dd245ed64264148e73fa0063 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/359056 Mon, 22 Apr 2024 20:57:01 -0000 https://status.shc.kanagawa.jp/incident/359056#75432e8c31c409b9de95800c27219cb2f4006ebb0c92258a6516e8b18f55253d NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/359056 Mon, 22 Apr 2024 20:53:51 -0000 https://status.shc.kanagawa.jp/incident/359056#87334998b9e9e22a6e1cf491f865c10be64db560dbdc18db993522376fe2582e NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/359056 Mon, 22 Apr 2024 11:06:54 -0000 https://status.shc.kanagawa.jp/incident/359056#572f9a66763b6e0b7f148d5e3f8a8bb5ec85187bf9cd9588efac541550c370f2 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/359056 Mon, 22 Apr 2024 10:53:46 -0000 https://status.shc.kanagawa.jp/incident/359056#2c3c6900695495a8c2d8eb4f70210cb96803afa7571d27905371beef8d952572 Misskey(mk.shc.kanagawa.jp) and MongoDB Repliction recovered. https://status.shc.kanagawa.jp/incident/359056 Mon, 22 Apr 2024 10:51:44 -0000 https://status.shc.kanagawa.jp/incident/359056#331bf87112d0f7a050241ea10e5c4276650da1920309ac8083c65402f998774b ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/359056 Mon, 22 Apr 2024 10:51:28 -0000 https://status.shc.kanagawa.jp/incident/359056#fcdb61ba008f9a4badcf5e0c2c98ace49370651015a86bc4574651491f8293f3 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/359056 Mon, 22 Apr 2024 10:50:46 -0000 https://status.shc.kanagawa.jp/incident/359056#a2177fabe134edd62b3b7d4451de9fe93df14daf3e9a5df0bf32dda0428585c6 Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/359056 Mon, 22 Apr 2024 10:49:06 -0000 https://status.shc.kanagawa.jp/incident/359056#81ee796191ac9f5ca6fbe53be4b95c12f48546964c159cef07a449a4d41de501 ownCloud (share.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/359056 Mon, 22 Apr 2024 10:48:03 -0000 https://status.shc.kanagawa.jp/incident/359056#ddcba1cd41be09222f9ebaa1bba56da65b648d1bb9d4174631efe9f87a6a95d2 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/359056 Mon, 22 Apr 2024 10:47:52 -0000 https://status.shc.kanagawa.jp/incident/359056#3afb6d1a21f4a79476a0563e148df3c9e1f88c0e7903020c4ac7005a7ed98b1b Pleroma(pr.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/359056 Mon, 22 Apr 2024 10:47:52 -0000 https://status.shc.kanagawa.jp/incident/359056#3afb6d1a21f4a79476a0563e148df3c9e1f88c0e7903020c4ac7005a7ed98b1b Pleroma(pr.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/359056 Mon, 22 Apr 2024 10:47:31 -0000 https://status.shc.kanagawa.jp/incident/359056#d32e864c9d160d16de587a45415360166ffb3807624832a895d3d8eb5e97ca39 Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/358785 Sun, 21 Apr 2024 20:59:59 -0000 https://status.shc.kanagawa.jp/incident/358785#923912270066d3ea76f03f9f68602101d5696d6731829c02b6f998045491577c Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/358785 Sun, 21 Apr 2024 20:50:55 -0000 https://status.shc.kanagawa.jp/incident/358785#36a935c396c0a7db8c05dfeedd3a56b3769d2b26f445d1d019a8e92a18e01e79 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/356491 Wed, 17 Apr 2024 01:30:38 -0000 https://status.shc.kanagawa.jp/incident/356491#2e822d570d30bd3627a6a581e3de6991502df96dc891618c1b4a2000565feb10 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/356491 Wed, 17 Apr 2024 01:15:59 -0000 https://status.shc.kanagawa.jp/incident/356491#c96e03f33a90a449e4c0e3800f656507a4353ee069be948c5a0f584d12b3e281 NextCloud Maintenance recovered. https://status.shc.kanagawa.jp/incident/356491 Wed, 17 Apr 2024 01:12:29 -0000 https://status.shc.kanagawa.jp/incident/356491#515d24ffe25e49e86e0f0b29dc5888621df838aeac0778f7cd7a8e9225702af2 ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/356491 Wed, 17 Apr 2024 01:12:03 -0000 https://status.shc.kanagawa.jp/incident/356491#96fa0afab34bcf12c6b1eb9e731839bd128b16c132aa508b3938df88fc8bc862 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/356491 Wed, 17 Apr 2024 01:11:23 -0000 https://status.shc.kanagawa.jp/incident/356491#bb34a0894ca14d362d994cfdacce6d1621dc7d6fffc7749b5d9390057a9cdfe1 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/356491 Wed, 17 Apr 2024 01:11:23 -0000 https://status.shc.kanagawa.jp/incident/356491#bb34a0894ca14d362d994cfdacce6d1621dc7d6fffc7749b5d9390057a9cdfe1 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/356491 Wed, 17 Apr 2024 00:44:15 -0000 https://status.shc.kanagawa.jp/incident/356491#0f79b4d35c45df35e570142b7fcc54986def6dd9a519552f28cfbb209cab8f6f NextCloud Maintenance went down. https://status.shc.kanagawa.jp/incident/356491 Wed, 17 Apr 2024 00:32:37 -0000 https://status.shc.kanagawa.jp/incident/356491#f06c6021533a9974708dcae77ce852c58911c913be7f85a00b0f9e8da00ac904 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/356491 Wed, 17 Apr 2024 00:31:46 -0000 https://status.shc.kanagawa.jp/incident/356491#f0b38aeb51823b19b60ffd8979c338ad4c6f6133f2600c3584a2e4bed97979b2 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/356491 Wed, 17 Apr 2024 00:31:31 -0000 https://status.shc.kanagawa.jp/incident/356491#e9a347f82e3b245380dea0dc040360e9a7dbf733d84329190232bdfdd7d29dca Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/356491 Wed, 17 Apr 2024 00:31:02 -0000 https://status.shc.kanagawa.jp/incident/356491#93656ed04ec3d2b4b751f32d58265932b3c58d4dc4c4171b1a030d235d3789f6 ownCloud (share.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/356491 Wed, 17 Apr 2024 00:29:00 -0000 https://status.shc.kanagawa.jp/incident/356491#5f27723c6ad1cdeba24023f661f5c2c4c97932bd27b23850f9bd889eec73c864 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/355493 Mon, 15 Apr 2024 18:13:34 -0000 https://status.shc.kanagawa.jp/incident/355493#99d637f229588f23c9456131c53d79b677514cb405012a9e7e6417e2fa7d3470 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/355493 Mon, 15 Apr 2024 18:12:47 -0000 https://status.shc.kanagawa.jp/incident/355493#d3a8fb3a5489eec59084abaf2b63e690bfc63c1e90d4406f90b548658f8aefb7 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/355493 Mon, 15 Apr 2024 02:25:58 -0000 https://status.shc.kanagawa.jp/incident/355493#fcc9412477eb4f8136586f06fb6acb99ddbb9afa5a5110de192b747d96b7a545 Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/355493 Mon, 15 Apr 2024 02:24:01 -0000 https://status.shc.kanagawa.jp/incident/355493#b348ce66669b961916e61f13a81e076d37fae65c44a4ebfccd237612fe7fc3fd NextCloud (cloud.shc.kanagawa.jp) and ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/355493 Mon, 15 Apr 2024 02:24:01 -0000 https://status.shc.kanagawa.jp/incident/355493#b348ce66669b961916e61f13a81e076d37fae65c44a4ebfccd237612fe7fc3fd NextCloud (cloud.shc.kanagawa.jp) and ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/355493 Mon, 15 Apr 2024 02:23:15 -0000 https://status.shc.kanagawa.jp/incident/355493#df9e0574c241005eee55eca811ce1ed62c74b4ba380fbf44de3112448c3a8887 Pleroma(pr.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/355493 Mon, 15 Apr 2024 02:23:15 -0000 https://status.shc.kanagawa.jp/incident/355493#df9e0574c241005eee55eca811ce1ed62c74b4ba380fbf44de3112448c3a8887 Pleroma(pr.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/355493 Mon, 15 Apr 2024 02:21:48 -0000 https://status.shc.kanagawa.jp/incident/355493#02b53de35a607d1cc066d6064e3b9d38ada7f17433f782d5f38440ebcd7f63b8 ownCloud (share.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/355493 Mon, 15 Apr 2024 02:20:57 -0000 https://status.shc.kanagawa.jp/incident/355493#24c6ac25084f11dee081bca7e8190f007605bce6125324c783ba9730ceac9c1f NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/355493 Mon, 15 Apr 2024 02:20:30 -0000 https://status.shc.kanagawa.jp/incident/355493#febeaf03c3266aaf059e2613ff84d90d75e18945dca60d892729bbecad34f4f3 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/355493 Mon, 15 Apr 2024 02:19:45 -0000 https://status.shc.kanagawa.jp/incident/355493#2bab011fef3abbb435b6afca5cf63188ea9b210f47b5e08780fa41a56e27ff28 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/355493 Mon, 15 Apr 2024 02:19:45 -0000 https://status.shc.kanagawa.jp/incident/355493#2bab011fef3abbb435b6afca5cf63188ea9b210f47b5e08780fa41a56e27ff28 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/355217 Sun, 14 Apr 2024 10:47:30 -0000 https://status.shc.kanagawa.jp/incident/355217#ca4532d520463cb690ebdca45d6c24481c88bebb79308c12fb5478399f20e0b6 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/355217 Sun, 14 Apr 2024 10:10:32 -0000 https://status.shc.kanagawa.jp/incident/355217#4dc3ce6a5d1649c2e22ae9b0f92318bbac2827c7f14f8e7c9c968c4b54cf5d2f Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/355217 Sun, 14 Apr 2024 09:35:54 -0000 https://status.shc.kanagawa.jp/incident/355217#010868915e0bff2420897acdb3aa015d9b164fc314a61c4d5a7d0f15ed61fbca NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/355217 Sun, 14 Apr 2024 09:35:31 -0000 https://status.shc.kanagawa.jp/incident/355217#cc9597509477ce655e959eefbf3f04c3c186eae9b274bb274c8ede251b7b1b08 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/355217 Sun, 14 Apr 2024 09:34:59 -0000 https://status.shc.kanagawa.jp/incident/355217#a45e484e935b20c05fbf0c9eb617aff608ebefcca2b1be656d74ff9c335b900e Pleroma(pr.shc.kanagawa.jp) and NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/355217 Sun, 14 Apr 2024 09:34:59 -0000 https://status.shc.kanagawa.jp/incident/355217#a45e484e935b20c05fbf0c9eb617aff608ebefcca2b1be656d74ff9c335b900e Pleroma(pr.shc.kanagawa.jp) and NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/355217 Sun, 14 Apr 2024 09:34:48 -0000 https://status.shc.kanagawa.jp/incident/355217#4fd1575bf0162b1ccca84212f77880ca71f1bcdbba006e9a76bcf0200964b3df Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/355217 Sun, 14 Apr 2024 09:34:48 -0000 https://status.shc.kanagawa.jp/incident/355217#4fd1575bf0162b1ccca84212f77880ca71f1bcdbba006e9a76bcf0200964b3df Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/355217 Sun, 14 Apr 2024 09:33:52 -0000 https://status.shc.kanagawa.jp/incident/355217#c1cd517119ac5621692235601bc72ca6fa27c36eb70418df55a444af3ebbc2c4 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/355217 Sun, 14 Apr 2024 09:33:52 -0000 https://status.shc.kanagawa.jp/incident/355217#c1cd517119ac5621692235601bc72ca6fa27c36eb70418df55a444af3ebbc2c4 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/355217 Sun, 14 Apr 2024 08:56:32 -0000 https://status.shc.kanagawa.jp/incident/355217#ca68132e039ec28e1634b1cb298def0ed7587f87cdd991ae0f6c2047c5bb57ad Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/355217 Sun, 14 Apr 2024 08:55:57 -0000 https://status.shc.kanagawa.jp/incident/355217#bb9a866d4653955f1e0dbf70a5cc7dd5890b9ef8d3a3d7682e6ea51e99dafb85 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/355217 Sun, 14 Apr 2024 08:55:57 -0000 https://status.shc.kanagawa.jp/incident/355217#bb9a866d4653955f1e0dbf70a5cc7dd5890b9ef8d3a3d7682e6ea51e99dafb85 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/355217 Sun, 14 Apr 2024 08:55:30 -0000 https://status.shc.kanagawa.jp/incident/355217#ba7e979ec7e843fed683374148f49f3f648e2020b6754dd24a9eeff91276266b Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/355217 Sun, 14 Apr 2024 08:54:51 -0000 https://status.shc.kanagawa.jp/incident/355217#fdc5ac8b5018e94e5620f5cf8eeab60713d9a8bc837cb3657ef86465071a8195 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/355217 Sun, 14 Apr 2024 08:54:51 -0000 https://status.shc.kanagawa.jp/incident/355217#fdc5ac8b5018e94e5620f5cf8eeab60713d9a8bc837cb3657ef86465071a8195 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/354944 Sat, 13 Apr 2024 15:20:49 -0000 https://status.shc.kanagawa.jp/incident/354944#89606d1728a4dfa92cb3cfe4fb357bcdb3ef45a17ee14131737113c5ef04133a Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/354944 Sat, 13 Apr 2024 15:17:37 -0000 https://status.shc.kanagawa.jp/incident/354944#b46914f6fb7eb6c331adf32116a4da9ad45a1123a40736948ad54fd77c2a79e1 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/354944 Sat, 13 Apr 2024 14:38:52 -0000 https://status.shc.kanagawa.jp/incident/354944#2591ee6c9fd6c6a41a8430a10c2683983167929d5ee5763bc8ba943215563c45 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/354944 Sat, 13 Apr 2024 14:26:41 -0000 https://status.shc.kanagawa.jp/incident/354944#c41ba30fec0d7323d7bef32834a1304441cbdbdd47cdec06abd308f6af6b5b00 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/354944 Sat, 13 Apr 2024 14:05:38 -0000 https://status.shc.kanagawa.jp/incident/354944#918a7b3b51850f5ff7744ca340e025461d284b26848a2e654c4cbf99a64bebf2 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/354944 Sat, 13 Apr 2024 14:05:29 -0000 https://status.shc.kanagawa.jp/incident/354944#882c192070f75db10020d63a22c8285c7be0a32e86296848ab6de7d07a1f5581 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/354516 Fri, 12 Apr 2024 11:17:46 -0000 https://status.shc.kanagawa.jp/incident/354516#4c246639b96d9c063582f0776dc110a8e6da29de7492eec2cca622f4fc573423 ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/354516 Fri, 12 Apr 2024 11:17:27 -0000 https://status.shc.kanagawa.jp/incident/354516#8bdf340032a104e157d423a9d4f7434f929c049c8473831bec155a1e668eec75 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/354516 Fri, 12 Apr 2024 11:16:45 -0000 https://status.shc.kanagawa.jp/incident/354516#eb62e24cc547c75027cb7bb951f494e394253f61bbb27625adc1e7a19f202eb2 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/354516 Fri, 12 Apr 2024 11:16:45 -0000 https://status.shc.kanagawa.jp/incident/354516#eb62e24cc547c75027cb7bb951f494e394253f61bbb27625adc1e7a19f202eb2 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/354516 Fri, 12 Apr 2024 11:15:00 -0000 https://status.shc.kanagawa.jp/incident/354516#276f0275f90f1c21db35527da7f89528cfc25c4c9078b3602dad69bebbfece8b ownCloud (share.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/354516 Fri, 12 Apr 2024 11:13:49 -0000 https://status.shc.kanagawa.jp/incident/354516#a058eb443d3100ac56cde2d2dbde7ed7ac737361297f9e5d9f8bbed55894d50d Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/354516 Fri, 12 Apr 2024 11:13:21 -0000 https://status.shc.kanagawa.jp/incident/354516#54bbec95992ffff72183513fb5c3dbff93b42d4a35d18aee457775a793771a7e Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/354516 Fri, 12 Apr 2024 11:12:53 -0000 https://status.shc.kanagawa.jp/incident/354516#37d12f970b6ae931f941127a26340c0ee336a491dc0167c52f99f038598e11dd Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/353653 Wed, 10 Apr 2024 18:11:06 -0000 https://status.shc.kanagawa.jp/incident/353653#d152d11461c233b2f099da990b2523e8283220761b175cbf256ae419b17d34cd Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/353653 Wed, 10 Apr 2024 18:10:28 -0000 https://status.shc.kanagawa.jp/incident/353653#d52d7ddeb5dec93bd738d634166a4d962201902c2b8fd5b90234a6d7a4ce0ad5 Pleroma(pr.shc.kanagawa.jp) went down and Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/353653 Wed, 10 Apr 2024 18:10:28 -0000 https://status.shc.kanagawa.jp/incident/353653#d52d7ddeb5dec93bd738d634166a4d962201902c2b8fd5b90234a6d7a4ce0ad5 Pleroma(pr.shc.kanagawa.jp) went down and Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/353653 Wed, 10 Apr 2024 18:10:28 -0000 https://status.shc.kanagawa.jp/incident/353653#d52d7ddeb5dec93bd738d634166a4d962201902c2b8fd5b90234a6d7a4ce0ad5 Pleroma(pr.shc.kanagawa.jp) went down and Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/353653 Wed, 10 Apr 2024 17:59:45 -0000 https://status.shc.kanagawa.jp/incident/353653#45e6113e9b6c1fd55535e01527cad7a704654411ce4f5d2390e2dd0d47b156a5 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/353653 Wed, 10 Apr 2024 17:59:22 -0000 https://status.shc.kanagawa.jp/incident/353653#c6276a7987a30bba28380ee43f0ae2ac9fccde9bf2e54a7c0d268918751b09c0 Pleroma(pr.shc.kanagawa.jp) and ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/353653 Wed, 10 Apr 2024 17:59:22 -0000 https://status.shc.kanagawa.jp/incident/353653#c6276a7987a30bba28380ee43f0ae2ac9fccde9bf2e54a7c0d268918751b09c0 Pleroma(pr.shc.kanagawa.jp) and ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/353653 Wed, 10 Apr 2024 17:57:26 -0000 https://status.shc.kanagawa.jp/incident/353653#fd5a80739faaec8fc6d785ce90ed6b61055808a974b31ee7b8be091dae4e6f85 ownCloud (share.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/353653 Wed, 10 Apr 2024 17:56:33 -0000 https://status.shc.kanagawa.jp/incident/353653#d18f33a9fd75f6baf2c87a0f925e71a10b7826e2b7e7d5dff1ab8c342e418110 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/353653 Wed, 10 Apr 2024 17:56:02 -0000 https://status.shc.kanagawa.jp/incident/353653#5bf0fc84c59309732b80b3026010dc9a0d5be29db0df139dc2c33b5719f4df3f Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/353653 Wed, 10 Apr 2024 17:55:32 -0000 https://status.shc.kanagawa.jp/incident/353653#cb0a2747d9b953bb09d0db89a9c5aa17042596dea30799bbbc66ea4544b907d0 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/353653 Wed, 10 Apr 2024 17:55:19 -0000 https://status.shc.kanagawa.jp/incident/353653#fb6aefb7c0aac2a46590ff0e059471af70c897fff5b26b8e202ce984cb632620 Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/353653 Wed, 10 Apr 2024 17:19:04 -0000 https://status.shc.kanagawa.jp/incident/353653#29442058861abeaddd70b7b82314bfe734a0bb7065278b8849cb8ab4caad9640 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/353653 Wed, 10 Apr 2024 17:16:47 -0000 https://status.shc.kanagawa.jp/incident/353653#65e938f04a13abdecbae889b10d67722b39489162cf21228e7f5ca2a6d884f03 NextCloud (cloud.shc.kanagawa.jp) and ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/353653 Wed, 10 Apr 2024 17:16:47 -0000 https://status.shc.kanagawa.jp/incident/353653#65e938f04a13abdecbae889b10d67722b39489162cf21228e7f5ca2a6d884f03 NextCloud (cloud.shc.kanagawa.jp) and ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/353653 Wed, 10 Apr 2024 17:16:30 -0000 https://status.shc.kanagawa.jp/incident/353653#26418d4c270ecfa2c9dea3e8f3ef844542d80eb98df8e570c52697bb3e51ecc4 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/353653 Wed, 10 Apr 2024 17:15:43 -0000 https://status.shc.kanagawa.jp/incident/353653#e622a43c89362f26dbba738de7998556860087bd303e93467eab490d4fb38bc1 Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/353653 Wed, 10 Apr 2024 16:53:10 -0000 https://status.shc.kanagawa.jp/incident/353653#4ba40ebe2ac9d8b995abae3149dc222f4c87890a48c65132b6997e51e93cb502 ownCloud (share.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/353653 Wed, 10 Apr 2024 16:52:16 -0000 https://status.shc.kanagawa.jp/incident/353653#55b4d29a98330bb998245ecf29867a3642509b5d3458e9af6616311c265501cc NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/353653 Wed, 10 Apr 2024 16:51:43 -0000 https://status.shc.kanagawa.jp/incident/353653#33ff6f351df4742156dd8b44d173f5dadfe3a360b95283d1e689c59b432dffd8 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/353653 Wed, 10 Apr 2024 16:51:13 -0000 https://status.shc.kanagawa.jp/incident/353653#d3583c217afd32b64f0cc1dc8488cf99dd96abd1354c89e8bb887baf25bedc31 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/353653 Wed, 10 Apr 2024 16:51:02 -0000 https://status.shc.kanagawa.jp/incident/353653#1a34f178b16661de08aa44e09123f72a8ae8e589797ced7e881ce026ab82e3c4 Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/353653 Wed, 10 Apr 2024 16:12:49 -0000 https://status.shc.kanagawa.jp/incident/353653#e06695c26bed7cee2593302d6f7cc3df751bd200806689f87a74ec87ac13ce98 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/353653 Wed, 10 Apr 2024 16:11:57 -0000 https://status.shc.kanagawa.jp/incident/353653#3d8ef1ba21992b1724cc08c62cd31e6be3b727f8316ae07deabb12028c69465d Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/353653 Wed, 10 Apr 2024 14:42:38 -0000 https://status.shc.kanagawa.jp/incident/353653#4935429036056937037559642401d5b4df17673891260c50266d9c40e6ec26ff ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/353653 Wed, 10 Apr 2024 14:42:15 -0000 https://status.shc.kanagawa.jp/incident/353653#7bb74d2908764fe3fc08f89b95c7be5de3cc59db93b8119848b10e23ab651a95 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/353653 Wed, 10 Apr 2024 14:41:33 -0000 https://status.shc.kanagawa.jp/incident/353653#6036c4543547e6aa35555fa648caa868395c42f757a97d319a45eb7b277fe06f Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/353653 Wed, 10 Apr 2024 14:41:33 -0000 https://status.shc.kanagawa.jp/incident/353653#6036c4543547e6aa35555fa648caa868395c42f757a97d319a45eb7b277fe06f Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/353653 Wed, 10 Apr 2024 14:37:40 -0000 https://status.shc.kanagawa.jp/incident/353653#db758f41cf5ad9b0d3309add97c7332851bcf275170f1c1e75a236327d9fccd0 Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/353653 Wed, 10 Apr 2024 14:36:50 -0000 https://status.shc.kanagawa.jp/incident/353653#cd4a7a5e981c4435f000ffe7db6cbd5a95c8ff02d6524d9258908da580812bfc ownCloud (share.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/353653 Wed, 10 Apr 2024 14:35:42 -0000 https://status.shc.kanagawa.jp/incident/353653#639ca68edbbff2c9a7e9ac9ac30b1730c8cdb5e3100cea616d9a329edad60e80 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/353653 Wed, 10 Apr 2024 14:35:12 -0000 https://status.shc.kanagawa.jp/incident/353653#a4c7b185d2a9d0b13eaf53840ab075fbc9bdbeab230ca6dc6e8668ed0c6a991c Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/353127 Tue, 09 Apr 2024 15:50:28 -0000 https://status.shc.kanagawa.jp/incident/353127#e2dfecf5eed808a48dab1ceef8b4300a4c107d2f59a86e9e1c6f12d7e7505791 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/353127 Tue, 09 Apr 2024 15:49:46 -0000 https://status.shc.kanagawa.jp/incident/353127#d696e69953ea02f4e4e6476fc22055ba46543fd1dce422b22ca4dfdfea360c4a Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/352617 Mon, 08 Apr 2024 16:43:38 -0000 https://status.shc.kanagawa.jp/incident/352617#6afc8612b608c7fa3bf52c8b72c013dd98ea94edc98993df11a97519d0d0d97a Pleroma Daily Database Backup recovered. https://status.shc.kanagawa.jp/incident/352617 Mon, 08 Apr 2024 16:08:36 -0000 https://status.shc.kanagawa.jp/incident/352617#f71bb8acc8d5d71c8290c3bf022aa430255aec6b56ae732ce7f47782c5715325 Pleroma Daily Database Backup went down. https://status.shc.kanagawa.jp/incident/351945 Sun, 07 Apr 2024 16:39:50 -0000 https://status.shc.kanagawa.jp/incident/351945#eb3c0aac40e13337ac809f28eccb6d97d0b531cb8a8d5051c2e9e8a0f6767fbe ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/351945 Sun, 07 Apr 2024 16:39:33 -0000 https://status.shc.kanagawa.jp/incident/351945#d3d7a0b3e2860901d86c473eabae7d739a88d24958f73ff74589e59b5f65f480 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/351945 Sun, 07 Apr 2024 16:38:50 -0000 https://status.shc.kanagawa.jp/incident/351945#9d97db0fc5a2c8d9d5df434194791bf7e3e11f0b49650205bd15694e804c671c Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/351945 Sun, 07 Apr 2024 16:38:50 -0000 https://status.shc.kanagawa.jp/incident/351945#9d97db0fc5a2c8d9d5df434194791bf7e3e11f0b49650205bd15694e804c671c Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/351945 Sun, 07 Apr 2024 16:38:34 -0000 https://status.shc.kanagawa.jp/incident/351945#cd0ec294083f026d93b18f5802e36f5d0328dda434f1c9d71b967679ad7623f9 ownCloud (share.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/351945 Sun, 07 Apr 2024 16:36:27 -0000 https://status.shc.kanagawa.jp/incident/351945#c5c123cadf20637035804a96928d09a73dd569d9d0e03c3705f9a9609e4f0d04 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/351945 Sun, 07 Apr 2024 16:36:05 -0000 https://status.shc.kanagawa.jp/incident/351945#b8a3980f8bae18388600f49c8c28943efd33bd0903bc6985271ce617ac426b4b Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/351945 Sun, 07 Apr 2024 16:34:49 -0000 https://status.shc.kanagawa.jp/incident/351945#93aa78db94b026b133876e1b10808d788a469d68f488bd9f4df479c83c5a001d Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/351945 Sun, 07 Apr 2024 04:35:52 -0000 https://status.shc.kanagawa.jp/incident/351945#2dc5865b8abd7f9411fa4635a29036aaa24f7db2a544c40322e036ccad39caa3 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/351945 Sun, 07 Apr 2024 04:35:52 -0000 https://status.shc.kanagawa.jp/incident/351945#2dc5865b8abd7f9411fa4635a29036aaa24f7db2a544c40322e036ccad39caa3 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/351945 Sun, 07 Apr 2024 04:33:54 -0000 https://status.shc.kanagawa.jp/incident/351945#b99a20be82f2efee04b634716d8f5d46155c56305d2cd57ce5d30015b6b7deff ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/351945 Sun, 07 Apr 2024 04:33:28 -0000 https://status.shc.kanagawa.jp/incident/351945#9aa60d08e85a7b86238d843d71a5e70afdab61a26318ed0cf4984908ff70873c Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/351945 Sun, 07 Apr 2024 04:32:44 -0000 https://status.shc.kanagawa.jp/incident/351945#2ecfc754b6d0cfaa25deaa97170a2938233e73ef4530440d629ab5f558187242 ownCloud (share.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/351945 Sun, 07 Apr 2024 04:30:25 -0000 https://status.shc.kanagawa.jp/incident/351945#f3b8072e236e356bde1e5ba2de723696d8a5fedc3641c72d73f71a1517d1b2d3 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/351945 Sun, 07 Apr 2024 04:29:41 -0000 https://status.shc.kanagawa.jp/incident/351945#439fd586618c021f8745eaeaa2a83568ee884a292bf0a3aa838fa15f11ef9657 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/351945 Sun, 07 Apr 2024 04:29:41 -0000 https://status.shc.kanagawa.jp/incident/351945#439fd586618c021f8745eaeaa2a83568ee884a292bf0a3aa838fa15f11ef9657 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/351390 Fri, 05 Apr 2024 22:30:12 -0000 https://status.shc.kanagawa.jp/incident/351390#ce4e493d77c73df786a2c543dda09f83fcc956b541e806d5059ff23ed0ab4a21 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/351390 Fri, 05 Apr 2024 22:29:55 -0000 https://status.shc.kanagawa.jp/incident/351390#010180a5b1cb3beadf7569ae70cafc6186779cb46b933ff5548d9ba9d57212d4 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/351390 Fri, 05 Apr 2024 22:29:36 -0000 https://status.shc.kanagawa.jp/incident/351390#d588e923874bab68acbca00ad9d71d336b3fd8cd04a94a816c90377dea8cc649 Pleroma(pr.shc.kanagawa.jp) and NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/351390 Fri, 05 Apr 2024 22:29:36 -0000 https://status.shc.kanagawa.jp/incident/351390#d588e923874bab68acbca00ad9d71d336b3fd8cd04a94a816c90377dea8cc649 Pleroma(pr.shc.kanagawa.jp) and NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/351390 Fri, 05 Apr 2024 22:29:19 -0000 https://status.shc.kanagawa.jp/incident/351390#3819d9a5fb57a61d23de6b0a96c1b5ece8921a53040e4fc5a6d6acb787831d9c Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/351390 Fri, 05 Apr 2024 22:29:08 -0000 https://status.shc.kanagawa.jp/incident/351390#4e4da104f5c07458b1f4abecf3a002d0827c29715b0eee7e3f8b73e34bcc0aa6 Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/351390 Fri, 05 Apr 2024 22:28:22 -0000 https://status.shc.kanagawa.jp/incident/351390#05d6050279aab1bbae2b5d9db59045ddb71b438aa3fa56d4ea7e32331b8dfb07 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/351390 Fri, 05 Apr 2024 22:28:22 -0000 https://status.shc.kanagawa.jp/incident/351390#05d6050279aab1bbae2b5d9db59045ddb71b438aa3fa56d4ea7e32331b8dfb07 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/351390 Fri, 05 Apr 2024 15:41:52 -0000 https://status.shc.kanagawa.jp/incident/351390#05889ac0cb1b43fc8561732c3ac8e5ef4243ea7c60295b2c5b5424b0f3ecbe35 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/351390 Fri, 05 Apr 2024 15:37:56 -0000 https://status.shc.kanagawa.jp/incident/351390#ef2766dc40aff724b3b95e5b6a60d5ed2de099fcfeb59e05568f9fbeb7877200 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/349779 Tue, 02 Apr 2024 18:19:39 -0000 https://status.shc.kanagawa.jp/incident/349779#18f5e877350366a382b36e9e905eedb3a7216b29231b6fb768422d8525c07a64 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/349779 Tue, 02 Apr 2024 18:18:41 -0000 https://status.shc.kanagawa.jp/incident/349779#e2cbda614e269aa803ca76e498cad443a8d85d69ca6f3eb4a0320af531e57e5c Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/349235 Mon, 01 Apr 2024 20:48:35 -0000 https://status.shc.kanagawa.jp/incident/349235#63e35f90b0d44b8a366beadd89ffacb5a851a936ced6d831a7b4d20e60c778af NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/349235 Mon, 01 Apr 2024 20:45:33 -0000 https://status.shc.kanagawa.jp/incident/349235#a00c07c63e404943b1202ff32529959fa483012b079928b0335d5ff91af2a252 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/348330 Sun, 31 Mar 2024 03:04:10 -0000 https://status.shc.kanagawa.jp/incident/348330#2002f11260aced417b17d0e280a70df38370cf38a831580efccf1601f7fdcbbc NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/348330 Sat, 30 Mar 2024 18:18:10 -0000 https://status.shc.kanagawa.jp/incident/348330#727f89ef6eae2922a05de8b8a8e25e06c2e77149d659f83f4b5961d40d9c3582 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/347481 Thu, 28 Mar 2024 16:09:20 -0000 https://status.shc.kanagawa.jp/incident/347481#71cc6c09695c83103f2426ca31d3d8f9e830790333833a26eefaff52d1b784ab Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/347481 Thu, 28 Mar 2024 16:02:25 -0000 https://status.shc.kanagawa.jp/incident/347481#4ed7dfa5b398d602d5e30e2f1759f994fe3c8163d6e5cbf6cb06798fa50b0299 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/345904 Mon, 25 Mar 2024 18:18:29 -0000 https://status.shc.kanagawa.jp/incident/345904#a762ef5c2ad807f31ecac173068d6d5d0bdd68625af451ddc1c33746faaa9af3 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/345904 Mon, 25 Mar 2024 18:15:17 -0000 https://status.shc.kanagawa.jp/incident/345904#7209c1d65355f0e603ac946a578051ee0dc24c33aad63c1a2ec472a135dc6658 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/344973 Sat, 23 Mar 2024 16:08:50 -0000 https://status.shc.kanagawa.jp/incident/344973#045659b6715a805210abaaedfa8f9ea0d8f68c9abe036c58f11ac2b773612218 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/344973 Sat, 23 Mar 2024 16:07:50 -0000 https://status.shc.kanagawa.jp/incident/344973#8823120c145c138ae311a0c65719eea9d65d9863ea0c2a3b90ac201b50a273de Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/344973 Sat, 23 Mar 2024 12:02:42 -0000 https://status.shc.kanagawa.jp/incident/344973#252f013e1c10e8df7b323e4231662e2c9a5724d9afab24c2f8c6d6f03545b7a5 Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/344973 Sat, 23 Mar 2024 11:50:40 -0000 https://status.shc.kanagawa.jp/incident/344973#74456375c10b2b7ccbc08c7ab74a2ff0fd4efcc373ec3377d5a10248b9340f7a Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/344589 Fri, 22 Mar 2024 16:12:16 -0000 https://status.shc.kanagawa.jp/incident/344589#fc72693117094f045ec373440a1b76fb8e15e562d3cd04d2e3bde7403c8af25f Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/344589 Fri, 22 Mar 2024 16:11:21 -0000 https://status.shc.kanagawa.jp/incident/344589#c4983d4f5aacbec3161a5f39d01ef140f2a21f50fed020c47e49147415a81e48 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/344589 Fri, 22 Mar 2024 13:45:17 -0000 https://status.shc.kanagawa.jp/incident/344589#0f327f57636253c2616e337e9509b4ff005deb5a90d28296af07f9a7f7a0276f Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/344589 Fri, 22 Mar 2024 13:38:19 -0000 https://status.shc.kanagawa.jp/incident/344589#d74dfab6bc317c7b3dfca7a6d42a3e374c58b364430a27a6d2aea0f46685d847 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/343094 Tue, 19 Mar 2024 16:13:07 -0000 https://status.shc.kanagawa.jp/incident/343094#08dbe185cb656c56b7bed57007e1898d1d3f8eb4f13ddf7c179c95745237e705 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/343094 Tue, 19 Mar 2024 16:12:04 -0000 https://status.shc.kanagawa.jp/incident/343094#c770d6515e92c616c3e4008f67825ea8ca0b2f4f910c5518072d8c327631eeca Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/342394 Mon, 18 Mar 2024 11:39:48 -0000 https://status.shc.kanagawa.jp/incident/342394#269b9dc1961e16082fce1526e08858bca3029e81ecc202e816af8ff38373dbdb Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/342394 Mon, 18 Mar 2024 11:38:48 -0000 https://status.shc.kanagawa.jp/incident/342394#482cdb7d3d45a97c5d15e08ed545bbb8be630fb66cb19d3aa0dcfe88a8741ecf Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/341290 Fri, 15 Mar 2024 14:53:21 -0000 https://status.shc.kanagawa.jp/incident/341290#e9d26f0605ab46d9b69d1e9e9a3aa3619c4a4dacda3f6e40181519b891d19ec3 demo.shc.kanagawa.jp Initialize recovered. https://status.shc.kanagawa.jp/incident/341290 Fri, 15 Mar 2024 14:28:39 -0000 https://status.shc.kanagawa.jp/incident/341290#13e51aafbf621e9aa0fde6beb2d80e60aa7ee291d5fa9a2fa004412d24ba082e demo.shc.kanagawa.jp Initialize went down. https://status.shc.kanagawa.jp/incident/340334 Wed, 13 Mar 2024 14:41:02 -0000 https://status.shc.kanagawa.jp/incident/340334#581293a536cae3f8a254092d14b1d15f6048d696b30f72ffff74446d301b9c5b ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/340334 Wed, 13 Mar 2024 14:41:00 -0000 https://status.shc.kanagawa.jp/incident/340334#53a3c436f707e9f04dc1569e756b94e300dea0b4c5ff72b6ac4258d9c0ec9afc Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/340334 Wed, 13 Mar 2024 14:40:04 -0000 https://status.shc.kanagawa.jp/incident/340334#cf3479397f407dbcc217689ddceab7c7bad74faec2b4966ae24a15c661729c08 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/340334 Wed, 13 Mar 2024 14:40:00 -0000 https://status.shc.kanagawa.jp/incident/340334#d464c21632ff168fe2324c52148475a1ca21a1919f12588c8993e71e9fee2058 ownCloud (share.shc.kanagawa.jp) went down and Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/340334 Wed, 13 Mar 2024 14:40:00 -0000 https://status.shc.kanagawa.jp/incident/340334#d464c21632ff168fe2324c52148475a1ca21a1919f12588c8993e71e9fee2058 ownCloud (share.shc.kanagawa.jp) went down and Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/340334 Wed, 13 Mar 2024 14:37:39 -0000 https://status.shc.kanagawa.jp/incident/340334#8533812677b8af79d135bf58b1acac4e44878da88b5e8e3f791437901095695c Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/340334 Wed, 13 Mar 2024 14:37:05 -0000 https://status.shc.kanagawa.jp/incident/340334#da81b61d5f80ac66ea2f070b909b8bb5791dfb33c7ecf83ae145efea86365a46 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/340334 Wed, 13 Mar 2024 14:37:05 -0000 https://status.shc.kanagawa.jp/incident/340334#da81b61d5f80ac66ea2f070b909b8bb5791dfb33c7ecf83ae145efea86365a46 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/339465 Mon, 11 Mar 2024 20:55:45 -0000 https://status.shc.kanagawa.jp/incident/339465#5cd5ced829930f08af694f79959af4fb3a74e7a1c68b20e3ed1c4e3930dbf0ca NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/339465 Mon, 11 Mar 2024 20:55:28 -0000 https://status.shc.kanagawa.jp/incident/339465#36ffe29358816304341568aa2527dd8b7fdf657422f29ccdbea38e9a7dbbf69c NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/337748 Thu, 07 Mar 2024 21:06:09 -0000 https://status.shc.kanagawa.jp/incident/337748#3eda8d136071d316bacac5f36cf91024cb5e98e28dcaacfe9902cd7b7c7f6e47 demo.shc.kanagawa.jp Initialize recovered. https://status.shc.kanagawa.jp/incident/337748 Thu, 07 Mar 2024 20:28:56 -0000 https://status.shc.kanagawa.jp/incident/337748#9d768b3b48452b3b946befa989919e0fbd37f520e4f0b87392debbeeb785e492 demo.shc.kanagawa.jp Initialize went down. https://status.shc.kanagawa.jp/incident/336189 Mon, 04 Mar 2024 20:46:33 -0000 https://status.shc.kanagawa.jp/incident/336189#ec86101e3026c10e928b2502e42c1d941a242b35eb8ed65bbea73fc3f39da7ca NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/336189 Mon, 04 Mar 2024 20:43:19 -0000 https://status.shc.kanagawa.jp/incident/336189#d470e7cf1a4cf0f11cba2cae7bd4b6d291bf7eeefcf9e238f3b529f0a044ae47 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/334051 Fri, 01 Mar 2024 10:11:51 -0000 https://status.shc.kanagawa.jp/incident/334051#a3df21cc52c0b5bb949a1212a1a0f309754da4081145165d5a6ee4cc42a56ece Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/334051 Fri, 01 Mar 2024 10:11:08 -0000 https://status.shc.kanagawa.jp/incident/334051#f8bf8b931a0d2a5193b91a384f9c61e1de7898da09346c06da545f96a0ee2ce0 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/334051 Fri, 01 Mar 2024 07:18:17 -0000 https://status.shc.kanagawa.jp/incident/334051#1d43153ca2061f181d84a229aeacb522848394d388de956eda1c40de665b9f74 demo.shc.kanagawa.jp Initialize recovered. https://status.shc.kanagawa.jp/incident/334051 Fri, 01 Mar 2024 06:28:06 -0000 https://status.shc.kanagawa.jp/incident/334051#7c3e8baa5ed59b8443eac0413d2fa1693392349cff213c79a31434e93defd3b6 demo.shc.kanagawa.jp Initialize went down. https://status.shc.kanagawa.jp/incident/333484 Thu, 29 Feb 2024 10:22:35 -0000 https://status.shc.kanagawa.jp/incident/333484#c32069eb4e931a08aa64a9d9627340e8a0928a3e67e63d9a0cb8e97f3c936665 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/333484 Thu, 29 Feb 2024 10:01:00 -0000 https://status.shc.kanagawa.jp/incident/333484#a92f352a60cc4199d7b73d6ac25a4ffcccdd5f32e29c0c9e789abdcbe6efc6f6 Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/333484 Thu, 29 Feb 2024 09:46:02 -0000 https://status.shc.kanagawa.jp/incident/333484#649f6619d0305765bd7f26ef5de50f5bc11f95fb2ba6e2b153498f7fadac7a8a Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/333484 Thu, 29 Feb 2024 09:35:24 -0000 https://status.shc.kanagawa.jp/incident/333484#f58bcad1ea11a3250d0ab6d661a11f2727d4c24f0e236d2b9a677fbb2247b5f5 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/333484 Thu, 29 Feb 2024 09:34:48 -0000 https://status.shc.kanagawa.jp/incident/333484#e1da39d94e356531fff3b9500a35be0b3b08ff85c4f6ee170be75971d27c2be6 Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/333484 Thu, 29 Feb 2024 09:32:19 -0000 https://status.shc.kanagawa.jp/incident/333484#09ecd07365a594d4b13c46c2548d39322ebf3f7f77a82fec88f7fd42d76209fd Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/333484 Thu, 29 Feb 2024 09:31:57 -0000 https://status.shc.kanagawa.jp/incident/333484#accac2a5b853e0e7c0ceb4fbf44e959ba45a4c6d01816d5501cf5964715f4aa9 Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/333484 Thu, 29 Feb 2024 09:07:02 -0000 https://status.shc.kanagawa.jp/incident/333484#152b6438c2f3c83b92bbe3707f9823917550e0503302876ac934187a2fb13bfb ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/333484 Thu, 29 Feb 2024 09:06:00 -0000 https://status.shc.kanagawa.jp/incident/333484#2e61c2fa88b1a85e1bfc41aed2ba8f17e0251a87ccf25ddba64ff8f3090fe5a9 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/333484 Thu, 29 Feb 2024 09:06:00 -0000 https://status.shc.kanagawa.jp/incident/333484#2e61c2fa88b1a85e1bfc41aed2ba8f17e0251a87ccf25ddba64ff8f3090fe5a9 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/333484 Thu, 29 Feb 2024 08:46:29 -0000 https://status.shc.kanagawa.jp/incident/333484#699fc714e9fedc3cc3fd9715a5b92aa0e237ff1c0d73b9a145c18a584cefa8c0 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/333484 Thu, 29 Feb 2024 08:45:42 -0000 https://status.shc.kanagawa.jp/incident/333484#5b69dad56ae7db8b995a60a0dddf6a7c0034ac3f6428cd28991d317db063c388 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/333484 Thu, 29 Feb 2024 07:41:52 -0000 https://status.shc.kanagawa.jp/incident/333484#230e19e3800d2a79ffec2e2c2a43c3ba27ccecb75e2fde652e8485ee2541a24f ownCloud (share.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/333484 Thu, 29 Feb 2024 07:39:53 -0000 https://status.shc.kanagawa.jp/incident/333484#92ae830276c25e9c4022320e63ec310fe5f411dbbee5a1d9a3889178161d7e4c Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/333484 Thu, 29 Feb 2024 07:37:30 -0000 https://status.shc.kanagawa.jp/incident/333484#34c5ee191dff527c5eaaaefd183cd49bc7e012efde53d3fa52486c08fc996042 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/333484 Thu, 29 Feb 2024 07:36:04 -0000 https://status.shc.kanagawa.jp/incident/333484#23f2f838417c7c66b55a870b43f1d2987d956f0026708e89a9cffe31384d676a Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/333484 Thu, 29 Feb 2024 04:33:55 -0000 https://status.shc.kanagawa.jp/incident/333484#5f8a17a001d968c6dcd7f4fd549a4a18ee6075fed22410962814e81e805b37a3 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/333484 Thu, 29 Feb 2024 04:32:44 -0000 https://status.shc.kanagawa.jp/incident/333484#1d092c84799c247ca060e3c6a268daba4b58a0000465d10d1ee5069ee9395c52 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/333484 Thu, 29 Feb 2024 02:06:44 -0000 https://status.shc.kanagawa.jp/incident/333484#d0519e7cdd5e3e7cae15a239d7b434b1a0cdaa56df9337fe6f8ca52ee374205a Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/333484 Thu, 29 Feb 2024 02:05:40 -0000 https://status.shc.kanagawa.jp/incident/333484#9c942d72a09a4ec372297c1fa3b4369d81c2d5f5195a609a0f25f5e3e7fb1bcd Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/333249 Wed, 28 Feb 2024 18:04:07 -0000 https://status.shc.kanagawa.jp/incident/333249#b0e663d7f1416d209eaa2960bf7fb40ac6e02169cf87f468c32367af94c4fd50 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/333249 Wed, 28 Feb 2024 18:03:26 -0000 https://status.shc.kanagawa.jp/incident/333249#419402786e3caf56d4822b5fb6f2fdd5efe351c796e6ad6a5404f74a54f138fe Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/333249 Wed, 28 Feb 2024 16:43:04 -0000 https://status.shc.kanagawa.jp/incident/333249#7c4d516e2508b8b0f4ede774235157b12c99509b6bf3fccaa343451d3cc22fa6 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/333249 Wed, 28 Feb 2024 16:42:00 -0000 https://status.shc.kanagawa.jp/incident/333249#f42c796400b64051594f361e0cc67b122a4cb6eb805bfd38b6085de873b3d5f5 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/332710 Tue, 27 Feb 2024 16:14:31 -0000 https://status.shc.kanagawa.jp/incident/332710#194a02435bb44d2be776843bac77f168660d02e42417ce651abdd203d2c85415 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/332710 Tue, 27 Feb 2024 16:10:28 -0000 https://status.shc.kanagawa.jp/incident/332710#4035706b95e4a5f99a4f16102724d78500a5d6834fce72ff803035ed5cd955cd Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/332710 Tue, 27 Feb 2024 16:04:52 -0000 https://status.shc.kanagawa.jp/incident/332710#217ff99021f725e22baca5bf300d6bcabcfcae3912d8426324d2c49663422158 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/332710 Tue, 27 Feb 2024 15:59:03 -0000 https://status.shc.kanagawa.jp/incident/332710#969b30c487c550b39d6eb725892ef053a9c1e6b760f7b258f7cd523eab65267f Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/332295 Mon, 26 Feb 2024 20:54:47 -0000 https://status.shc.kanagawa.jp/incident/332295#bff6ff9bd5e56ecbd90ef28d152d76fa19c22c39b50605c21df3a75e533e5963 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/332295 Mon, 26 Feb 2024 20:53:08 -0000 https://status.shc.kanagawa.jp/incident/332295#5559807710bdc949b5ec0fe828fb9f8f25eb59ad32ec4a727d3d0b3c3fd94c40 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/331645 Sun, 25 Feb 2024 07:30:57 -0000 https://status.shc.kanagawa.jp/incident/331645#792a43720605267085de50c4272265a3656bc0acef79a8c7762194c83dd96bf3 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/331645 Sun, 25 Feb 2024 07:30:07 -0000 https://status.shc.kanagawa.jp/incident/331645#09c484c2bcef73bbcb1fb85911ef2c911765bce16106f2a0edd8fa0be03ed184 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/331233 Sat, 24 Feb 2024 05:09:55 -0000 https://status.shc.kanagawa.jp/incident/331233#365d87cde6851c4c77a7e5e913453c909133ae4843ee1c8433ceaec95a101305 Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/331233 Sat, 24 Feb 2024 05:00:44 -0000 https://status.shc.kanagawa.jp/incident/331233#b670080af246c9db7aa729d822aae72c7fc0214dbd4d3a32f24c4e4cc1b9beb0 Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/331233 Sat, 24 Feb 2024 03:44:40 -0000 https://status.shc.kanagawa.jp/incident/331233#8ef98e405ea80b5c479b3dec37371b4d5b3761f49d8ea552a06f9fcc573b135f demo.shc.kanagawa.jp Initialize recovered. https://status.shc.kanagawa.jp/incident/331233 Sat, 24 Feb 2024 03:37:58 -0000 https://status.shc.kanagawa.jp/incident/331233#09d20680cdaac77e434ab5229d1d14d8f00bc13a4f770f53c96b9c271ced6cb9 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/331233 Sat, 24 Feb 2024 03:33:52 -0000 https://status.shc.kanagawa.jp/incident/331233#42f19d42016aaa0f10ea0a7534867096fc841f70fab6cc71f0bc1e0b449d6889 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/331233 Sat, 24 Feb 2024 03:31:44 -0000 https://status.shc.kanagawa.jp/incident/331233#b7c1152486206066c1657567b42c5acb3b8daabcea5a355a3d3265b90bd19dfa NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/331233 Sat, 24 Feb 2024 03:30:37 -0000 https://status.shc.kanagawa.jp/incident/331233#17ea4132b69fa4b2c805b9b41d3c545bb431ff5ca49330c24c69b26e1122c611 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/331233 Sat, 24 Feb 2024 03:28:12 -0000 https://status.shc.kanagawa.jp/incident/331233#a198775f9d85117c866fae3346cae3b728862839248c9b51ca9c27433c13aad9 demo.shc.kanagawa.jp Initialize went down. https://status.shc.kanagawa.jp/incident/331036 Fri, 23 Feb 2024 16:09:39 -0000 https://status.shc.kanagawa.jp/incident/331036#ab61f8c33a0d207686c905fc00783e2bf8a76dfa1623199f2c08794cdfb2a62b Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/331036 Fri, 23 Feb 2024 16:08:30 -0000 https://status.shc.kanagawa.jp/incident/331036#6a565ffeb9d5a53642422794c6c4d50b2d24c370b8c455a1ca812cdabf571d23 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/329126 Mon, 19 Feb 2024 18:24:16 -0000 https://status.shc.kanagawa.jp/incident/329126#42dbfb94911b55884d6c3d10781cf603febab10b15b6515a55c21abe0e7ffd2a NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/329126 Mon, 19 Feb 2024 18:20:17 -0000 https://status.shc.kanagawa.jp/incident/329126#76f178da2c36af771b0bdf46b40b6144756af32768b708f9c6e5d0776a58b8c0 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/328600 Sun, 18 Feb 2024 16:43:50 -0000 https://status.shc.kanagawa.jp/incident/328600#2bd89c65e699abf4619af423084989cd1f8b0b30d3fb9d4afdf00bf64e18c9fd Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/328600 Sun, 18 Feb 2024 16:42:47 -0000 https://status.shc.kanagawa.jp/incident/328600#a9fc7e9239d1979fe794fc40ab4c7aa9f08ab9ac434904027a9e3a1f30649274 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/325443 Wed, 14 Feb 2024 14:42:38 -0000 https://status.shc.kanagawa.jp/incident/325443#7edd3b9f7bb35a80333318b873fda15a9c8f47ba81eafedad5f5c2ecdc5fa06b ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/325443 Wed, 14 Feb 2024 14:42:23 -0000 https://status.shc.kanagawa.jp/incident/325443#533a32d28413c4d8bb3cabacc0a0801d4f4333a48bff0e3f25438e94bc9e0a79 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/325443 Wed, 14 Feb 2024 14:41:53 -0000 https://status.shc.kanagawa.jp/incident/325443#a28d6842e0a0a59322206b74ffabdb446fff93e2dfedeab42d7a9fcfe75f3c2f Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/325443 Wed, 14 Feb 2024 14:41:53 -0000 https://status.shc.kanagawa.jp/incident/325443#a28d6842e0a0a59322206b74ffabdb446fff93e2dfedeab42d7a9fcfe75f3c2f Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/325443 Wed, 14 Feb 2024 14:39:14 -0000 https://status.shc.kanagawa.jp/incident/325443#bf8e07d6e9a140b24be2da98cdece43ac4413b7efe224837c9ffba0214cd33a4 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/325443 Wed, 14 Feb 2024 14:38:38 -0000 https://status.shc.kanagawa.jp/incident/325443#99aee647eea52ad098a1883b7dccc535d2aef06bffea1f4b32c1bed843c343d8 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/325443 Wed, 14 Feb 2024 14:38:38 -0000 https://status.shc.kanagawa.jp/incident/325443#99aee647eea52ad098a1883b7dccc535d2aef06bffea1f4b32c1bed843c343d8 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/325443 Wed, 14 Feb 2024 14:37:41 -0000 https://status.shc.kanagawa.jp/incident/325443#0c0e96177b501f71ea62b110b22b7de279be9dc25484ab7a9a56ab7b8a075d95 ownCloud (share.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/325443 Mon, 12 Feb 2024 20:46:47 -0000 https://status.shc.kanagawa.jp/incident/325443#3e09ede86b3fd5b00511b730950007c6996e2290238563ebd45431d92847cb77 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/325443 Mon, 12 Feb 2024 20:43:46 -0000 https://status.shc.kanagawa.jp/incident/325443#33971547da29e07419d935693ce3f04e0fcf87f2447c40871a6b12db99f86351 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/325443 Mon, 12 Feb 2024 00:02:52 -0000 https://status.shc.kanagawa.jp/incident/325443#77b05bd697a80a1bab4bfb67ffd9af53ccb8f17c2b8f007bed6ba58287bc2751 Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/325443 Mon, 12 Feb 2024 00:02:49 -0000 https://status.shc.kanagawa.jp/incident/325443#7f1b35b60bcbca175aaf6f667913c2f99127c9d0dc63393ad5078bd7409f3793 Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/324668 Sat, 10 Feb 2024 18:30:52 -0000 https://status.shc.kanagawa.jp/incident/324668#ae212e270d0fc326510c61fc02f4ef92d3d4936730fa1d957322a4c395d12e33 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/324668 Sat, 10 Feb 2024 18:30:25 -0000 https://status.shc.kanagawa.jp/incident/324668#53f6e260f2291050ef09299c904a0eb127fcd8ca3c43b33a22f3ef36a68abba9 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/324668 Sat, 10 Feb 2024 15:41:23 -0000 https://status.shc.kanagawa.jp/incident/324668#16cf1a832d5a4eb8cee8ace3b72eac549739037378ef8913c4c663fa22751007 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/324668 Sat, 10 Feb 2024 15:34:45 -0000 https://status.shc.kanagawa.jp/incident/324668#8b977872cc954bec5c732c64646bc166c8aacf975b45a9c8565c038d36f0e252 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/324668 Sat, 10 Feb 2024 11:56:46 -0000 https://status.shc.kanagawa.jp/incident/324668#346b73378b9a7574263fe2e57bbce9961fee76ec6b9dfe3f40e339cc1b28f1b2 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/324668 Sat, 10 Feb 2024 11:47:22 -0000 https://status.shc.kanagawa.jp/incident/324668#20c5fe2e7989c506ebc45d4c9164e7d4561a0965e0b51a8a8d18fb85474334c8 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/324668 Fri, 09 Feb 2024 21:34:54 -0000 https://status.shc.kanagawa.jp/incident/324668#95a7574155e002675ece7296ed190c3f1907dfbd0c3de287cb523bc996179b98 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/324668 Fri, 09 Feb 2024 21:34:21 -0000 https://status.shc.kanagawa.jp/incident/324668#cfdbe64c3cd04513e00104915a59486a14df391d8257cdd7ef4c449508a2babb NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/324668 Fri, 09 Feb 2024 18:31:43 -0000 https://status.shc.kanagawa.jp/incident/324668#bcaadededb87b40884083181982bc5b6a3692640695306fed4d567326b53b54e NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/324668 Fri, 09 Feb 2024 18:31:00 -0000 https://status.shc.kanagawa.jp/incident/324668#cd0723510d2dcd64b656b0da2ae8843d198a0899173099c3bb86bf25f80bd0b6 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/323871 Thu, 08 Feb 2024 21:32:38 -0000 https://status.shc.kanagawa.jp/incident/323871#b517fb7602f7e368f9e9d9bb59f0692db4b9da3deadbe3ae259bf48b74fe2780 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/323871 Thu, 08 Feb 2024 21:31:13 -0000 https://status.shc.kanagawa.jp/incident/323871#77d052de183833100c837e54a60063773f8d28314c86aa6152ad073fe906c957 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/323871 Thu, 08 Feb 2024 03:52:44 -0000 https://status.shc.kanagawa.jp/incident/323871#6e6e2713aaa950118989481eb824749fdd27692b52cb7dfd573f805de37c059d Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/323871 Thu, 08 Feb 2024 03:51:20 -0000 https://status.shc.kanagawa.jp/incident/323871#f673ea92f6b7df7c77c38deb422adc1e0826850a81c23e66cf365eb95465e9e0 Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/323398 Wed, 07 Feb 2024 21:19:39 -0000 https://status.shc.kanagawa.jp/incident/323398#c04db03c4450b678ee68e63ccfe1055ba7fc80cbb3ab64186c3868c5868f173b NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/323398 Wed, 07 Feb 2024 21:19:14 -0000 https://status.shc.kanagawa.jp/incident/323398#6e8ab29b3c4039fbf9e2959d6d91e13749d7855bc5c3039007b657660934fac7 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/323398 Wed, 07 Feb 2024 21:06:55 -0000 https://status.shc.kanagawa.jp/incident/323398#73a504ae515e0fd85195efdcbf8f55b0277b36b730f554aa3bd17b3cae4aab4f Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/323398 Wed, 07 Feb 2024 21:06:01 -0000 https://status.shc.kanagawa.jp/incident/323398#a8df7e37c1321b73dcff31e550bd4e17a76264343c2fc8f017bd6ab3b054dfe2 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/323398 Wed, 07 Feb 2024 18:27:52 -0000 https://status.shc.kanagawa.jp/incident/323398#005e26c3922cf357fc9996bfb7a2c35d86a08f0d21bf850d40a64386400564dd NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/323398 Wed, 07 Feb 2024 18:27:30 -0000 https://status.shc.kanagawa.jp/incident/323398#ff00fb597950e7810634da71bc5cce97938640cca5d4d5ab9c53e1ba8f968f97 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/323398 Wed, 07 Feb 2024 11:26:23 -0000 https://status.shc.kanagawa.jp/incident/323398#00970d13107750b01f6a59fb1c90e3f5bda90cdea0d8007d7d84435dd02f005b Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/323398 Wed, 07 Feb 2024 11:26:23 -0000 https://status.shc.kanagawa.jp/incident/323398#00970d13107750b01f6a59fb1c90e3f5bda90cdea0d8007d7d84435dd02f005b Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/323398 Wed, 07 Feb 2024 11:26:14 -0000 https://status.shc.kanagawa.jp/incident/323398#5034f29efc2cc9c4950feca35588478a811b8cfb3382bf293e697b96fdb39cc4 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/323398 Wed, 07 Feb 2024 11:26:14 -0000 https://status.shc.kanagawa.jp/incident/323398#5034f29efc2cc9c4950feca35588478a811b8cfb3382bf293e697b96fdb39cc4 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/322758 Tue, 06 Feb 2024 21:50:04 -0000 https://status.shc.kanagawa.jp/incident/322758#abcee5d15ff948eacc415b8d1da9dfde43b8661256c209025d005a889b48528d Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/322758 Tue, 06 Feb 2024 21:49:39 -0000 https://status.shc.kanagawa.jp/incident/322758#73c515943eff547a18b0979cfed072f8e47bef44d0a1fa5d71a4fb345170732d Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/322758 Tue, 06 Feb 2024 20:53:54 -0000 https://status.shc.kanagawa.jp/incident/322758#83e958645c8abfbd6d84ca87118d3266f9cd47c482a4b958c69500073c66682f NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/322758 Tue, 06 Feb 2024 20:53:28 -0000 https://status.shc.kanagawa.jp/incident/322758#9ea4d1778b02dcf4abd9050b443604cef57d053b0afa82205814221735e98f8e NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/322636 Mon, 05 Feb 2024 21:24:45 -0000 https://status.shc.kanagawa.jp/incident/322636#4aa2f58ac3294fb4fe34f0663da1a572d12753311f8bc6ee709cca3feb3bf720 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/322636 Mon, 05 Feb 2024 21:23:46 -0000 https://status.shc.kanagawa.jp/incident/322636#31928cba982e274af3974a243b6c073ae83280a2f12f08fe2ae1530cd676d803 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/322636 Mon, 05 Feb 2024 18:24:22 -0000 https://status.shc.kanagawa.jp/incident/322636#0b4ffe7dd0111b4fad0ab1cdb56e7a796e15804531c10d55f6cff0ab6bb258c1 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/322636 Mon, 05 Feb 2024 18:23:47 -0000 https://status.shc.kanagawa.jp/incident/322636#5b2cebcf5be99cd654eb7f13f9a9ee004590655bf0a4d3e63e228163ebcad605 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/322046 Sun, 04 Feb 2024 20:29:20 -0000 https://status.shc.kanagawa.jp/incident/322046#2b7b51b471798fdc7679c66f31417818f06fba1ccbb2011ac39f5c5ee73a9c26 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/322046 Sun, 04 Feb 2024 20:28:33 -0000 https://status.shc.kanagawa.jp/incident/322046#4807eca18b44a56e9d9925ffd86071b4fcf00a7344d967bdfbbdc6b855478246 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/321689 Sat, 03 Feb 2024 20:22:50 -0000 https://status.shc.kanagawa.jp/incident/321689#0ba793cf5d9a843e0c0d3d546d8f9d62aa30dcf67a83c060b5bfe6b38df0d5cd NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/321689 Sat, 03 Feb 2024 20:21:46 -0000 https://status.shc.kanagawa.jp/incident/321689#409a9bc4d0d926972405bfa71f423bad1280e5b9c83c0e8ebc85d8f1a4d0f843 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/321689 Sat, 03 Feb 2024 11:32:47 -0000 https://status.shc.kanagawa.jp/incident/321689#4ae4afc071ad338c907ed57ad1c71279a7acbecf5482cea4a6cb8c95e092e90e Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/321689 Sat, 03 Feb 2024 11:31:43 -0000 https://status.shc.kanagawa.jp/incident/321689#9a4a06d6cffbffa24b52e6cbde3a1e8d350cf6e13c152a17d6c853c4210d2e63 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/321314 Fri, 02 Feb 2024 20:27:25 -0000 https://status.shc.kanagawa.jp/incident/321314#d8dd24a22fb8e57220e05e63ff672086ef3aa75bca6abd1459b485d4f0145e59 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/321314 Fri, 02 Feb 2024 20:27:11 -0000 https://status.shc.kanagawa.jp/incident/321314#ab321580a5177a87f0cfee52b23bd5abfed0a0c79cd36412e4693fc96c306c63 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/320566 Thu, 01 Feb 2024 20:51:44 -0000 https://status.shc.kanagawa.jp/incident/320566#7b84a7a2bcd4a5a5555d9e1e452d9f0167e187413fca9234923d083644828d1b NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/320566 Thu, 01 Feb 2024 20:48:44 -0000 https://status.shc.kanagawa.jp/incident/320566#304b770e2bb8ff2635182bc01bcc7fbd16fe2e3f2abf2c7b2c88d8a56a2d5ba4 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/320517 Wed, 31 Jan 2024 20:56:19 -0000 https://status.shc.kanagawa.jp/incident/320517#1f2e731914e0c3ecfb0259aa20e3df23704486adc5155d763f7ff4275c668ff4 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/320517 Wed, 31 Jan 2024 20:55:52 -0000 https://status.shc.kanagawa.jp/incident/320517#0274bfe91ebc1301a79424f15e84e2778cc0da0ddf223d787c19a35e956c7c25 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Tue, 30 Jan 2024 21:45:17 -0000 https://status.shc.kanagawa.jp/incident/306963#778dba3df08ca4ddd206bd3ee7a71f36131591767d04a0b529f97dae98032307 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Tue, 30 Jan 2024 21:44:23 -0000 https://status.shc.kanagawa.jp/incident/306963#df726bb39eec8b819c44703821cc5de6747f597497dbad5df8396d8fef098ba9 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Tue, 30 Jan 2024 18:26:42 -0000 https://status.shc.kanagawa.jp/incident/306963#020dcc2a68f37be3b35b4727b0fc4778e93a1287e0653fe14dca9fae7ef36502 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Tue, 30 Jan 2024 18:25:35 -0000 https://status.shc.kanagawa.jp/incident/306963#7851cb195bffbf7d7c2bfbd824559eb29bbd94d93ffd4e060e9238fcdb64ee7b NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Tue, 30 Jan 2024 14:21:31 -0000 https://status.shc.kanagawa.jp/incident/306963#5b20cf92240aee4fb934d5f08789f576585ea60d55c9f15af58d31326b246b90 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Tue, 30 Jan 2024 14:21:31 -0000 https://status.shc.kanagawa.jp/incident/306963#5b20cf92240aee4fb934d5f08789f576585ea60d55c9f15af58d31326b246b90 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Tue, 30 Jan 2024 09:08:49 -0000 https://status.shc.kanagawa.jp/incident/306963#fa775bd586ec9e05b3edff92041cb56d498373d816650334eea56d3c0ab8e6ad Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Tue, 30 Jan 2024 09:08:49 -0000 https://status.shc.kanagawa.jp/incident/306963#fa775bd586ec9e05b3edff92041cb56d498373d816650334eea56d3c0ab8e6ad Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Mon, 29 Jan 2024 21:12:20 -0000 https://status.shc.kanagawa.jp/incident/306963#6e52d9bd597c5afd963ec8abdcd82c6c0a1534aad412ee01071159c8df25089b NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Mon, 29 Jan 2024 21:11:19 -0000 https://status.shc.kanagawa.jp/incident/306963#c4532fbc48ce4199865de72c75bde7a5f88f0af3bc76381c9be873c43e3ba7d5 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Mon, 29 Jan 2024 18:23:38 -0000 https://status.shc.kanagawa.jp/incident/306963#f2930d465745a22e4bf1974146d5da7c0bfe299671e457c21fc62983a8ad3189 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Mon, 29 Jan 2024 18:23:03 -0000 https://status.shc.kanagawa.jp/incident/306963#f2fd451de76e65cb90297e4a9d574879528eb912154088b857462a5cd0a6c627 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Mon, 29 Jan 2024 01:31:21 -0000 https://status.shc.kanagawa.jp/incident/306963#51036974628ffc0657132f059b1124c1151afc299d5c8940fdaac7f595d938ab NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Mon, 29 Jan 2024 01:30:35 -0000 https://status.shc.kanagawa.jp/incident/306963#f88e10f942c72c9bb4032d3991e1d456dc94e90f2bdcbcaf35ab1f8941ae1e30 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Sun, 28 Jan 2024 22:00:50 -0000 https://status.shc.kanagawa.jp/incident/306963#f94682cb2716dd3586bcfdfe5f2fbd8644f923a32b58f0294d22fc2e92d05ecf NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Sun, 28 Jan 2024 21:56:42 -0000 https://status.shc.kanagawa.jp/incident/306963#b557af5ac8475ce9ea986c7f3b47419002a704a9cbaf19e6e854a47a8d1be671 NextCloud Maintenance recovered. https://status.shc.kanagawa.jp/incident/306963 Sun, 28 Jan 2024 19:42:05 -0000 https://status.shc.kanagawa.jp/incident/306963#599f05c6a3fe461ad29b1df9eef23335df98aa1fe10eacd0874e62bdcb93e20d NextCloud Maintenance went down. https://status.shc.kanagawa.jp/incident/306963 Sun, 28 Jan 2024 19:21:25 -0000 https://status.shc.kanagawa.jp/incident/306963#22e3a97eede99a3badffd637d872d9579c4008cb462496479238391ea95b512a NextCloud Maintenance recovered. https://status.shc.kanagawa.jp/incident/306963 Sun, 28 Jan 2024 18:44:09 -0000 https://status.shc.kanagawa.jp/incident/306963#7d07e7f3f9397b87795b87676b4016b846612271a9ef1deafb4f9ea5a6c897a1 NextCloud Maintenance went down. https://status.shc.kanagawa.jp/incident/306963 Sun, 28 Jan 2024 18:32:14 -0000 https://status.shc.kanagawa.jp/incident/306963#813add342ce90129cbcf4d569960d8d92cce0f00d2551aaf14a39fcc0b3bfa73 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Sun, 28 Jan 2024 16:23:16 -0000 https://status.shc.kanagawa.jp/incident/306963#86311efc15839ea23466813388479c25b2c32aa73fa30110c71b322a55437276 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Sun, 28 Jan 2024 16:23:16 -0000 https://status.shc.kanagawa.jp/incident/306963#86311efc15839ea23466813388479c25b2c32aa73fa30110c71b322a55437276 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Sun, 28 Jan 2024 06:17:36 -0000 https://status.shc.kanagawa.jp/incident/306963#3e3476b184dfacbeae74c689317d2ea827d7015d4b766aca4bcedd5190a5968e demo.shc.kanagawa.jp Initialize recovered. https://status.shc.kanagawa.jp/incident/306963 Sun, 28 Jan 2024 06:05:41 -0000 https://status.shc.kanagawa.jp/incident/306963#4b7e72a868cc96ef9fcacb55a85b1725bad9e22de8206188e085c7c5c50f9ca0 Activity Relay(relay.shc.kanagawa.jp), Pub-Relay(pub-relay.shc.kanagawa.jp), and demo.shc.kanagawa.jp Initialize went down. https://status.shc.kanagawa.jp/incident/306963 Sun, 28 Jan 2024 06:05:41 -0000 https://status.shc.kanagawa.jp/incident/306963#4b7e72a868cc96ef9fcacb55a85b1725bad9e22de8206188e085c7c5c50f9ca0 Activity Relay(relay.shc.kanagawa.jp), Pub-Relay(pub-relay.shc.kanagawa.jp), and demo.shc.kanagawa.jp Initialize went down. https://status.shc.kanagawa.jp/incident/306963 Sun, 28 Jan 2024 06:05:41 -0000 https://status.shc.kanagawa.jp/incident/306963#4b7e72a868cc96ef9fcacb55a85b1725bad9e22de8206188e085c7c5c50f9ca0 Activity Relay(relay.shc.kanagawa.jp), Pub-Relay(pub-relay.shc.kanagawa.jp), and demo.shc.kanagawa.jp Initialize went down. https://status.shc.kanagawa.jp/incident/306963 Sat, 27 Jan 2024 20:45:20 -0000 https://status.shc.kanagawa.jp/incident/306963#180228724f31e54392b063eb8327abe9cf4e0f5ae065bf19030015831a4904a0 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Sat, 27 Jan 2024 20:41:33 -0000 https://status.shc.kanagawa.jp/incident/306963#e436fd3b51810786a51521cca1f93a4590398b59606eba7b09c5f6c5fa0b59a1 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Fri, 26 Jan 2024 22:06:10 -0000 https://status.shc.kanagawa.jp/incident/306963#7bf4a27d54ae95d4fc717b315f02c85e3cd3c0b56168617c9dd056ec7bab3bda Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Fri, 26 Jan 2024 22:06:10 -0000 https://status.shc.kanagawa.jp/incident/306963#7bf4a27d54ae95d4fc717b315f02c85e3cd3c0b56168617c9dd056ec7bab3bda Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Fri, 26 Jan 2024 21:47:46 -0000 https://status.shc.kanagawa.jp/incident/306963#c442e004aec338d3fb1984d3f09645a4d46fbc10b7dbefcd8b88a02fd6e1abbd NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Fri, 26 Jan 2024 21:46:18 -0000 https://status.shc.kanagawa.jp/incident/306963#fa80de0c3825d7ade09f81c804edaadf71134278e8b870e9f6d0a276354f9fd8 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Fri, 26 Jan 2024 18:21:52 -0000 https://status.shc.kanagawa.jp/incident/306963#25c3294bd0d505b3cfb63b4c72d97987010d0472f9c4fdf18fc96bf6702217ec NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Fri, 26 Jan 2024 18:19:41 -0000 https://status.shc.kanagawa.jp/incident/306963#c366098b5f901e52d102b1eb847f6239b8a61a4daa8aadb55cdc986aa8bca6de NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Fri, 26 Jan 2024 16:10:10 -0000 https://status.shc.kanagawa.jp/incident/306963#3bc6e59814815c29cac6493ffece7cb4c01c1c16e7bb641abf61324986c1635e Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Fri, 26 Jan 2024 16:05:45 -0000 https://status.shc.kanagawa.jp/incident/306963#1b063e202b9f6c3f2be1ed903317f1efc835d9c8d1463c97a6d09d2a925cb865 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Fri, 26 Jan 2024 15:00:35 -0000 https://status.shc.kanagawa.jp/incident/306963#92da74eff0cc1a08803e77a7f08d619cb93e610c5c48ccdb7b00f64524c66e44 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Fri, 26 Jan 2024 15:00:35 -0000 https://status.shc.kanagawa.jp/incident/306963#92da74eff0cc1a08803e77a7f08d619cb93e610c5c48ccdb7b00f64524c66e44 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Thu, 25 Jan 2024 21:36:16 -0000 https://status.shc.kanagawa.jp/incident/306963#4cf2182da00fd90b0dcaa41ee934e8c5c53e7c14c7b52fa14677acc04e7b6d7f NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Thu, 25 Jan 2024 21:35:44 -0000 https://status.shc.kanagawa.jp/incident/306963#57c349f9ae1dc99267b18f201055c308c4290104f78c7e3b22cb5e54c46816fc NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Thu, 25 Jan 2024 18:21:09 -0000 https://status.shc.kanagawa.jp/incident/306963#7cebfee1736d3bb4f826801d07548e7e8b12f46db3d438c296120f7d8b13534c NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Thu, 25 Jan 2024 18:20:36 -0000 https://status.shc.kanagawa.jp/incident/306963#8e9acbf5ecaa5a287e210285c7c18cc0a7646a1424ce3dff54da1d843c81752d NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Wed, 24 Jan 2024 18:23:39 -0000 https://status.shc.kanagawa.jp/incident/306963#142803b141c488177228ca2151d32cb59c002493ab70061c3f98d3922df6e482 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Wed, 24 Jan 2024 18:22:09 -0000 https://status.shc.kanagawa.jp/incident/306963#2071e4d87d3bc05a0631bd3895e180bfae75d31709d7431d4528550cc21161e9 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Tue, 23 Jan 2024 21:30:57 -0000 https://status.shc.kanagawa.jp/incident/306963#27fc70b2fad6a8f89338bc5fc24de7ba7497b3077fe530781681fa1a4ea5dfd9 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Tue, 23 Jan 2024 21:28:08 -0000 https://status.shc.kanagawa.jp/incident/306963#19336a2390c5d56a1a61993c8e05a5b789ce02ac4dab3565af54f8d9868b60ea NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Tue, 23 Jan 2024 18:28:08 -0000 https://status.shc.kanagawa.jp/incident/306963#52025f5ec6d3d11297f647a13ab9003c3ddd4b9c67a0327e14e0602fef831cdf NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Tue, 23 Jan 2024 18:27:29 -0000 https://status.shc.kanagawa.jp/incident/306963#4482be6dd3dbdd0ff858a1454e2498fa10b03983797d32a8e59e5f32b5ee7fb8 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Mon, 22 Jan 2024 21:13:23 -0000 https://status.shc.kanagawa.jp/incident/306963#62b4bdfe9f1a80756de2179f0e4095f967e93f2f17fe11d5b7959e97a71e5860 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Mon, 22 Jan 2024 21:12:24 -0000 https://status.shc.kanagawa.jp/incident/306963#06ce025cb1da07830887f741f93f143d82eb15689228f76b66031453583bb85a NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Mon, 22 Jan 2024 18:13:26 -0000 https://status.shc.kanagawa.jp/incident/306963#bbee89599cb3d2143fc47c0f1ad25d7d3c222d473063f3aafec375faf8e76839 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Mon, 22 Jan 2024 18:12:24 -0000 https://status.shc.kanagawa.jp/incident/306963#a61b23991248ae25ade53ebabc9722f4042925cfa6ce837ee9479b434ea75773 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Sun, 21 Jan 2024 21:11:39 -0000 https://status.shc.kanagawa.jp/incident/306963#ec7c35e1445daaf153c7c1efc7064bb7a69ab36c4e719744e703d6c8c9266ff5 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Sun, 21 Jan 2024 21:06:44 -0000 https://status.shc.kanagawa.jp/incident/306963#b2c88939f98d0931204d1e864d0d9a6d18f62ef31a30a49377539ae4110f8794 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Sun, 21 Jan 2024 18:26:25 -0000 https://status.shc.kanagawa.jp/incident/306963#6d35e8ff61148d4f0f042826c21d1664defda5818b9af2b2a2575f8baf5fe0d4 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Sun, 21 Jan 2024 18:24:45 -0000 https://status.shc.kanagawa.jp/incident/306963#195b9299266d7a85244ae0fb893e619809dd360b9ecd00625676956cc7f0ae03 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Sat, 20 Jan 2024 20:09:20 -0000 https://status.shc.kanagawa.jp/incident/306963#f1617b1625287e1d07830223d0b4e5fda83922fd67e38d743750bacd51165c4e NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Sat, 20 Jan 2024 20:08:47 -0000 https://status.shc.kanagawa.jp/incident/306963#02defb84816fe46668ddeffc4a3b921d8d1bf04077fb7509f5d47f0b8f7d8726 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Fri, 19 Jan 2024 21:18:56 -0000 https://status.shc.kanagawa.jp/incident/306963#fa98ee9176c7dd73a54d1857ae281774c830cdfe00a86ce1da9fb960a12cbea2 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Fri, 19 Jan 2024 21:16:07 -0000 https://status.shc.kanagawa.jp/incident/306963#f5d10af8bf75627dc22548c23d23acf15fa73920e7f3748b61bb8dc983c5d2fa NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Thu, 18 Jan 2024 21:14:28 -0000 https://status.shc.kanagawa.jp/incident/306963#9782450e75384cd490cc11659b25309762707afa2662c0d3982415578c8762cf NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Thu, 18 Jan 2024 21:13:10 -0000 https://status.shc.kanagawa.jp/incident/306963#2624d8801942321f83a6e9b0968cd447c92db7dbaf77adfae1848858bf39070d NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Thu, 18 Jan 2024 18:34:51 -0000 https://status.shc.kanagawa.jp/incident/306963#212631aaf218bd66535d6a24c8d040761f8d46e0d914938eb506879040dbe9ee NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Thu, 18 Jan 2024 18:33:46 -0000 https://status.shc.kanagawa.jp/incident/306963#924fb99428c58e9dd1495dc33f812ac57d907c509684147b75c192f1f39a382f NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Thu, 18 Jan 2024 13:35:05 -0000 https://status.shc.kanagawa.jp/incident/306963#5b4982eba1c876452c5f50865dc3a157514b426262f6bb819441c41dd4a78101 Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Thu, 18 Jan 2024 13:33:36 -0000 https://status.shc.kanagawa.jp/incident/306963#7f78e48b40ecf1f8225d6db45d3344e94cbe4f7f65e30f4fa802417f788069e1 Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Thu, 18 Jan 2024 03:18:40 -0000 https://status.shc.kanagawa.jp/incident/306963#190d04d52edfe891c5215a84e5247eaf280a300bdcf9386ffb8413d35a481a85 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Thu, 18 Jan 2024 03:08:23 -0000 https://status.shc.kanagawa.jp/incident/306963#9c6a43c8a8d5438b6aa24c4a6e223a5c4797092102f8585f660a58608ee47ce9 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Wed, 17 Jan 2024 22:23:31 -0000 https://status.shc.kanagawa.jp/incident/306963#dfb4e2f5141e84896fb43e69cb695d275478da9e528a31a12cb4bdc0624ac32b NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Wed, 17 Jan 2024 22:17:42 -0000 https://status.shc.kanagawa.jp/incident/306963#3772497147b88fc9e850e384d303ef1374c177ba298686173efb0f001f28f36d NextCloud Maintenance recovered. https://status.shc.kanagawa.jp/incident/306963 Wed, 17 Jan 2024 22:16:14 -0000 https://status.shc.kanagawa.jp/incident/306963#aeed6d7cd9e21f000604215561cd96ef3d19c4b0836d36b2a9e0e6278db43010 NextCloud Maintenance went down. https://status.shc.kanagawa.jp/incident/306963 Wed, 17 Jan 2024 22:05:07 -0000 https://status.shc.kanagawa.jp/incident/306963#863b7a7dd5c989cd75fdff564511753c8a45010d875bdcf647872680cb62e09c NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Wed, 17 Jan 2024 21:08:11 -0000 https://status.shc.kanagawa.jp/incident/306963#e9d08fe9678a051593caec7b94db6b0d9a20b109dfed9399aec302af4524114c NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Wed, 17 Jan 2024 21:07:15 -0000 https://status.shc.kanagawa.jp/incident/306963#38f7c78c18c5128ed35dbd7f3cd5dda1411539ebeffab54db38586a7ece85d8b NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Wed, 17 Jan 2024 18:22:24 -0000 https://status.shc.kanagawa.jp/incident/306963#7c6e7950205ae85d4911c1359a869753dbe68bb365e154ad8e8e1e54a0ef1e08 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Wed, 17 Jan 2024 18:21:52 -0000 https://status.shc.kanagawa.jp/incident/306963#7717fe29589df06ed83369cffae3ce873053595c915a22d33a4156d2181eb542 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Tue, 16 Jan 2024 21:14:35 -0000 https://status.shc.kanagawa.jp/incident/306963#9528118c4a1abbc599574465569522dfa65569ad4c94cff293c27208f0d9e6b4 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Tue, 16 Jan 2024 21:13:52 -0000 https://status.shc.kanagawa.jp/incident/306963#c0ee90d2ed82336f3897a8a11b837f4806a9ba0a836789d36e8cf93b4f1cc53e NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Tue, 16 Jan 2024 18:10:03 -0000 https://status.shc.kanagawa.jp/incident/306963#cedf42ed5377b766e562f89fffc7f967075ed7d91874bdb44eb4393cdfc3d9b5 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Tue, 16 Jan 2024 18:09:12 -0000 https://status.shc.kanagawa.jp/incident/306963#a3b30f15fd2ce60434a117e2f4ef0aa720173271ffe99ba75b4189b4bc859b79 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Mon, 15 Jan 2024 18:22:12 -0000 https://status.shc.kanagawa.jp/incident/306963#3450d04d7bf84126bdf959812e1772b5537d0f6a24476724e901e341dc6f286c NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Mon, 15 Jan 2024 18:21:45 -0000 https://status.shc.kanagawa.jp/incident/306963#c8897c0ca48be58a2261a3acb36d5321d05b4fa6024c6a3f786d62a51b26dfbd NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Sun, 14 Jan 2024 21:03:35 -0000 https://status.shc.kanagawa.jp/incident/306963#6f980093e3ce4ac5d57fc17e44d35850f9dde549b34553eafc63ca34dec6a189 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Sun, 14 Jan 2024 21:02:11 -0000 https://status.shc.kanagawa.jp/incident/306963#4aaaa989a9a32383ef249f7245c8bd1aef36287106a601d0bd0385838aa157a9 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Sun, 14 Jan 2024 18:17:20 -0000 https://status.shc.kanagawa.jp/incident/306963#156eded882debc137a02aa0d148e4be6beb5be4efd2b527bec62062b5bc53fe8 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Sun, 14 Jan 2024 18:16:54 -0000 https://status.shc.kanagawa.jp/incident/306963#3dde9ae927f1710d913c00f359a1279a8d37f4eb32c63d904c1b0a7791605a37 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Sat, 13 Jan 2024 21:37:24 -0000 https://status.shc.kanagawa.jp/incident/306963#e8e1704fe32659c08247acf79338103212c52636cdc31a9a94dd7f55a8bc7e5f NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Sat, 13 Jan 2024 21:36:20 -0000 https://status.shc.kanagawa.jp/incident/306963#9b7818e23cc66d5e917c63f355b1ea6fc9d11ec3b3c859aa8b64a4f6c2921630 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Sat, 13 Jan 2024 18:18:53 -0000 https://status.shc.kanagawa.jp/incident/306963#6e0c6c4c5af5aebd71d2511185e363e459d4e98e9fb4738753391bfed687822d NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Sat, 13 Jan 2024 18:18:22 -0000 https://status.shc.kanagawa.jp/incident/306963#5072c16ada1d3ee40a8fe7d84554c31c699e859082ad06518e952aac966c04f8 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Sat, 13 Jan 2024 17:14:03 -0000 https://status.shc.kanagawa.jp/incident/306963#a422a70d32b56d7fb166a7313011b53e25934d67c6d38bfa87541dd5f64ff667 Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Sat, 13 Jan 2024 17:11:51 -0000 https://status.shc.kanagawa.jp/incident/306963#7615166a85407659498f3ff5da212f09cc0a8ff84d41fae6cc111ce7088bc82b Pleroma(pr.shc.kanagawa.jp) and ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Sat, 13 Jan 2024 17:11:51 -0000 https://status.shc.kanagawa.jp/incident/306963#7615166a85407659498f3ff5da212f09cc0a8ff84d41fae6cc111ce7088bc82b Pleroma(pr.shc.kanagawa.jp) and ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Sat, 13 Jan 2024 17:11:18 -0000 https://status.shc.kanagawa.jp/incident/306963#2f7fefe65fbf82fe1019e6bb789fc214df6e9d39bb91a6b2ed6343113f16b69d Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Sat, 13 Jan 2024 17:10:45 -0000 https://status.shc.kanagawa.jp/incident/306963#f8e34943ffb5fb3014af21d55979207140a105bed74f8eab559b0da3379e9924 ownCloud (share.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Sat, 13 Jan 2024 17:08:38 -0000 https://status.shc.kanagawa.jp/incident/306963#13107bb0e355877a40aae3d71f399c4f638d5a6ff38966ea847d4c55c1ea3b35 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Sat, 13 Jan 2024 17:08:09 -0000 https://status.shc.kanagawa.jp/incident/306963#822291f4d2f7b2f508858bd7480b2699a307a35362031e7fba6ab5bf055caa26 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Sat, 13 Jan 2024 17:07:53 -0000 https://status.shc.kanagawa.jp/incident/306963#63d972564c1338ece7d8e4fc8d18630d741e03791a73a74ed1e1d5d23c2a9d7c Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Sat, 13 Jan 2024 15:04:29 -0000 https://status.shc.kanagawa.jp/incident/306963#452a62825e40bfebb76bbbe11dbee57665133be9e333da42316acc8548720080 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Sat, 13 Jan 2024 15:04:29 -0000 https://status.shc.kanagawa.jp/incident/306963#452a62825e40bfebb76bbbe11dbee57665133be9e333da42316acc8548720080 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Sat, 13 Jan 2024 15:02:34 -0000 https://status.shc.kanagawa.jp/incident/306963#6c27224802e24c94c9a00faee64a1357231404bffb2f789168b15c8757cc81e9 ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Sat, 13 Jan 2024 15:02:07 -0000 https://status.shc.kanagawa.jp/incident/306963#ff8da88bace3c339d62f4b3ee4666baa5512fea41c43a3ed94ef43e42ba55bef Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Sat, 13 Jan 2024 14:41:26 -0000 https://status.shc.kanagawa.jp/incident/306963#10f343835af0da148f859ea999a743ae0849b17819380bc85fbb668d469f322f ownCloud (share.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Sat, 13 Jan 2024 14:40:30 -0000 https://status.shc.kanagawa.jp/incident/306963#6c92d4ebccbf36301ca35bbacd7717ca11c782fc3238afc73a181df199fe1e08 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Sat, 13 Jan 2024 14:40:00 -0000 https://status.shc.kanagawa.jp/incident/306963#906523fdc22a6062e60ee90d03c3c74ccc43e7b1e1a09631cc23d3b0d09e0b60 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Sat, 13 Jan 2024 14:39:13 -0000 https://status.shc.kanagawa.jp/incident/306963#e06126e772e411d968d74100b380a3edc8c22729557f50781a4e6a2c19b34255 Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Sat, 13 Jan 2024 10:25:05 -0000 https://status.shc.kanagawa.jp/incident/306963#86d3568b93f7746cdaad04f1bdb20bb6dc7271a5f1ab2479dd17882fe3a6e896 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Sat, 13 Jan 2024 10:23:56 -0000 https://status.shc.kanagawa.jp/incident/306963#08a35fe3cae15f03b035afca24900d03d429eb788980fd0546a6d36cfdae3526 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Fri, 12 Jan 2024 18:23:42 -0000 https://status.shc.kanagawa.jp/incident/306963#83fb64530fc19827b8b96175df89a25cd6a0f986aded250cbb9393ed575c51e6 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Fri, 12 Jan 2024 18:23:09 -0000 https://status.shc.kanagawa.jp/incident/306963#9d953db28436f3289098853b56b60a0b84002a13e20e9be10e0149383fa2d542 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Fri, 12 Jan 2024 10:53:43 -0000 https://status.shc.kanagawa.jp/incident/306963#4ff9ce120fe1dfd2eac9b95cf9bc2326211cdd72dd21fdaead614a8bfffd4995 ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Fri, 12 Jan 2024 10:53:18 -0000 https://status.shc.kanagawa.jp/incident/306963#6bb497e8523e7030f87b93813c007a8f6e65472c8af93eff20cdea9db7b69ce9 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Fri, 12 Jan 2024 10:52:50 -0000 https://status.shc.kanagawa.jp/incident/306963#79e9cbfbe4a08dd6ad79514b70ac4c62a158aa44a42e9b9c8ab34fe61ccaa969 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Fri, 12 Jan 2024 10:52:30 -0000 https://status.shc.kanagawa.jp/incident/306963#6f522e0c8e9206d5625da753f6c0953285cb201f61b1425d6bf1cedc07c21eec Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Fri, 12 Jan 2024 10:34:35 -0000 https://status.shc.kanagawa.jp/incident/306963#49522a6520edf6d0f41294e01ff30f1a387bf67613bb6860521fe32e1d4977ef Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Fri, 12 Jan 2024 10:33:26 -0000 https://status.shc.kanagawa.jp/incident/306963#38f9fa18a8b2e232f01dd012f37cd1016967a8dc7369a3038ad0fc4558cfc3ef Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Fri, 12 Jan 2024 10:33:02 -0000 https://status.shc.kanagawa.jp/incident/306963#b0bda1d51257ed24938f1752094eca050bcead1ddc380d84ed0231f577e019b2 ownCloud (share.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Fri, 12 Jan 2024 10:31:42 -0000 https://status.shc.kanagawa.jp/incident/306963#169eb6883fe6b508faa2b6437e454b738dcd72f2b64ef70f0176ccaafaeb7398 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Fri, 12 Jan 2024 06:24:55 -0000 https://status.shc.kanagawa.jp/incident/306963#75b53b3a9da30aca978520b7998b376024a63d886b1c96b45d6dc75ed69e51ae Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Fri, 12 Jan 2024 06:23:51 -0000 https://status.shc.kanagawa.jp/incident/306963#6e0688e3a77f5187c56a2336e0cd2baabe42fb5ef1c7f9c9399c3b3cdd2fbcd8 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Thu, 11 Jan 2024 21:19:19 -0000 https://status.shc.kanagawa.jp/incident/306963#4985fa0c62ef70173e7432e7b0f790e06d4a35b9cd78d51880538a2d14a72492 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Thu, 11 Jan 2024 21:18:24 -0000 https://status.shc.kanagawa.jp/incident/306963#81f89afd378f53eba4f69611ecf4fdd95efe6790a809421f1c1c09953b5e9f15 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Thu, 11 Jan 2024 18:16:01 -0000 https://status.shc.kanagawa.jp/incident/306963#4246b4ddafa577592c1992d3d56046393f16147afafadb75b05d1590688b9781 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Thu, 11 Jan 2024 18:11:54 -0000 https://status.shc.kanagawa.jp/incident/306963#2f461873fb9c6bd796f8a3e86844ad4bee34f121420f4e8272a493b46b58ba13 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Thu, 11 Jan 2024 04:24:53 -0000 https://status.shc.kanagawa.jp/incident/306963#e9a9e6fa1842a6790306a38dfe4b73919f863c73dda2e5f88a188de83ebc600f Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Thu, 11 Jan 2024 04:23:58 -0000 https://status.shc.kanagawa.jp/incident/306963#db629add63271f33a555879ff180411a2c796a92439912fe4bacb35897b70696 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Wed, 10 Jan 2024 21:17:30 -0000 https://status.shc.kanagawa.jp/incident/306963#293fa61adb50753bef8b1aa2600902de73a46c71bb10d65774af69f110d9d528 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Wed, 10 Jan 2024 21:13:21 -0000 https://status.shc.kanagawa.jp/incident/306963#796f6e21327395354b7a07801b4480631dc85d553d452cc2ea110cef051d591d NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Wed, 10 Jan 2024 18:22:47 -0000 https://status.shc.kanagawa.jp/incident/306963#5360bfea2187e164f676cca035479eac95ac9f4bf7cecb83cbbd51a57a95dbe4 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Wed, 10 Jan 2024 18:22:00 -0000 https://status.shc.kanagawa.jp/incident/306963#30272c7c9938fed55f14a8e482ea077503a8adec676256aececb50f25fe7a7a7 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Wed, 10 Jan 2024 03:24:55 -0000 https://status.shc.kanagawa.jp/incident/306963#35a0f13a00d7c5fc50fb628f72d725a9767b2f71ef7f8e5bf6da27d233894a90 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Wed, 10 Jan 2024 03:23:56 -0000 https://status.shc.kanagawa.jp/incident/306963#6f2431ba61f1c66f7963042efa47ffad3cd9327a8748ac97d4eb149bcd1ffd45 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Tue, 09 Jan 2024 20:26:12 -0000 https://status.shc.kanagawa.jp/incident/306963#b78fe1f9f4fc679ec8ee5ba919de56805d0744fa8a4119637f8db6906a86e021 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Tue, 09 Jan 2024 20:25:34 -0000 https://status.shc.kanagawa.jp/incident/306963#8867043b7d8319ee931c0c168a353d014f0e8ebcabd0fa7d59b437240e050742 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Mon, 08 Jan 2024 20:21:44 -0000 https://status.shc.kanagawa.jp/incident/306963#642e88c67e05b4bdddba97a397c01d5d7728ebc9f4f3747ac019746b6fddf4ba NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Mon, 08 Jan 2024 20:20:33 -0000 https://status.shc.kanagawa.jp/incident/306963#9054b84ed385f6dd63254537591c7fcd8ff69e623200ea84298d5e3559b0b04f NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Mon, 08 Jan 2024 03:06:26 -0000 https://status.shc.kanagawa.jp/incident/306963#be5f74eb7ee45f78d9a3792ee6b7b4c7ae9370c5f792e8e661c7524d37d4053d NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Mon, 08 Jan 2024 03:02:57 -0000 https://status.shc.kanagawa.jp/incident/306963#65fb4b0e62675b7ffe5363f844683262f4a435cce23efc6ea677f3ac9072b40c NextCloud Maintenance recovered. https://status.shc.kanagawa.jp/incident/306963 Mon, 08 Jan 2024 02:59:07 -0000 https://status.shc.kanagawa.jp/incident/306963#7b644935a3439b196a53f6cd750fd390fac8d465c0c54d6dc463112f68fc128a Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Mon, 08 Jan 2024 02:59:07 -0000 https://status.shc.kanagawa.jp/incident/306963#7b644935a3439b196a53f6cd750fd390fac8d465c0c54d6dc463112f68fc128a Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Mon, 08 Jan 2024 02:57:03 -0000 https://status.shc.kanagawa.jp/incident/306963#e0de6e4492e4e19576fece3607dffb04d271cb25198dd0682c39a98652ac10b5 Pleroma(pr.shc.kanagawa.jp) and ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Mon, 08 Jan 2024 02:57:03 -0000 https://status.shc.kanagawa.jp/incident/306963#e0de6e4492e4e19576fece3607dffb04d271cb25198dd0682c39a98652ac10b5 Pleroma(pr.shc.kanagawa.jp) and ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Mon, 08 Jan 2024 02:53:41 -0000 https://status.shc.kanagawa.jp/incident/306963#d63c0c493d6de56119c93db80c07cf8bfafa51e5c0ea1441c89ec53a067e8a35 NextCloud Maintenance went down. https://status.shc.kanagawa.jp/incident/306963 Mon, 08 Jan 2024 02:44:59 -0000 https://status.shc.kanagawa.jp/incident/306963#0dabe79d01571a0eb6ec363bebc3be232a0e76a87346c0feddb9408a962ce3d0 ownCloud (share.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Mon, 08 Jan 2024 02:44:03 -0000 https://status.shc.kanagawa.jp/incident/306963#ef0c50ba7c2b25d386105d52aa7bb02539b42df3ffeda607d40ea31935ffa082 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Mon, 08 Jan 2024 02:43:37 -0000 https://status.shc.kanagawa.jp/incident/306963#eb81ae78dc197c6c6a54625c751a0ee4417abee2321bb92fd233627ddd2486b8 Pleroma(pr.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Mon, 08 Jan 2024 02:43:37 -0000 https://status.shc.kanagawa.jp/incident/306963#eb81ae78dc197c6c6a54625c751a0ee4417abee2321bb92fd233627ddd2486b8 Pleroma(pr.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Mon, 08 Jan 2024 02:43:09 -0000 https://status.shc.kanagawa.jp/incident/306963#435788dc5dac16c907ffa35c60c53999627a3017022540ff3969551f83ff227c Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Sun, 07 Jan 2024 20:10:26 -0000 https://status.shc.kanagawa.jp/incident/306963#498624aaacc5b9c50f02e4797eb7bc45bba4c8c88626908c8157b05ab96ce236 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Sun, 07 Jan 2024 20:10:00 -0000 https://status.shc.kanagawa.jp/incident/306963#50a5ec3f39f9e8251c7103b15d36b9d6ffe070e9cc7e48e55fa88294d583958c NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Sat, 06 Jan 2024 21:05:57 -0000 https://status.shc.kanagawa.jp/incident/306963#986329432d05ab5f9faa8a48fa182fceaed5e7260be197b74604da4a7a2f4f6e NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Sat, 06 Jan 2024 21:05:04 -0000 https://status.shc.kanagawa.jp/incident/306963#d7ecb2e26b25bdfd752bb7e38aee95824e9920c5ff1f4db5313fc0a14b80448f NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Sat, 06 Jan 2024 16:24:57 -0000 https://status.shc.kanagawa.jp/incident/306963#7f31788e88cd8ac5ed4393a87612c9476aaf684c51e46e3bc482772826a990c4 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Sat, 06 Jan 2024 16:23:58 -0000 https://status.shc.kanagawa.jp/incident/306963#db85db18bcb0e5d2b89953affbccea5f58582a6df894c2178f2d27bd502c7fd2 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Fri, 05 Jan 2024 18:30:33 -0000 https://status.shc.kanagawa.jp/incident/306963#a95d9dcc7b2f209161f95d56f48eeb2c771a5ca71e2de7032a243f112317e4ca NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Fri, 05 Jan 2024 18:29:56 -0000 https://status.shc.kanagawa.jp/incident/306963#475b22b32afc3755285338d284aba8e569872a6e562a000c384f3bc7389c80de NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Fri, 05 Jan 2024 03:25:31 -0000 https://status.shc.kanagawa.jp/incident/306963#2291959feeeaa1274586781122596970682d80492cf490d663218f9c34547a7f Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Fri, 05 Jan 2024 03:23:50 -0000 https://status.shc.kanagawa.jp/incident/306963#595cea59e695af47de6a7b0d2303f2727470653f1f1265d983788726f059fcec Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Thu, 04 Jan 2024 20:02:56 -0000 https://status.shc.kanagawa.jp/incident/306963#5f71597cec23112ce0537c45d3caf466763633adcbb9cb181b58f52c4a7ec55e NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Thu, 04 Jan 2024 20:02:29 -0000 https://status.shc.kanagawa.jp/incident/306963#66724c10e527eaf624c1920de4bc4f223228cedf0feea0c41313c558f8f31675 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Wed, 03 Jan 2024 18:24:52 -0000 https://status.shc.kanagawa.jp/incident/306963#2241d7b089e5428a5f82ae8de6a308aff442cfb302d5148397bb64bbe4cf2c96 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Wed, 03 Jan 2024 18:23:54 -0000 https://status.shc.kanagawa.jp/incident/306963#0b94653577fc99a8e6090ee1f92ba3d4b4fcb4202bde0a4868eb19c77d054ae7 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Tue, 02 Jan 2024 18:31:37 -0000 https://status.shc.kanagawa.jp/incident/306963#c6be91a702d49d8ece7afc2eadc402168f25ec86066579ad5868bda60f86a7cf NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Tue, 02 Jan 2024 18:31:16 -0000 https://status.shc.kanagawa.jp/incident/306963#2af1cfcb18689d7d8f5e4e43f2ca4d3d87b307881d845c6589494ac9428239c8 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Tue, 02 Jan 2024 09:39:18 -0000 https://status.shc.kanagawa.jp/incident/306963#5f42df19637381458a7566d896fc5004815bdb5e4cd7fb6123472a5585f88f74 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Tue, 02 Jan 2024 09:38:18 -0000 https://status.shc.kanagawa.jp/incident/306963#10de24e3bd982c6461c50656e96edf563fb886aa68c4afd23ca3b04b96dca4ee Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Tue, 02 Jan 2024 09:38:15 -0000 https://status.shc.kanagawa.jp/incident/306963#9071f7c431711c04323e49dd95162a479363d487bb618d957671b2b80a10bc29 NextCloud (cloud.shc.kanagawa.jp) went down and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Tue, 02 Jan 2024 09:38:15 -0000 https://status.shc.kanagawa.jp/incident/306963#9071f7c431711c04323e49dd95162a479363d487bb618d957671b2b80a10bc29 NextCloud (cloud.shc.kanagawa.jp) went down and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Tue, 02 Jan 2024 09:37:41 -0000 https://status.shc.kanagawa.jp/incident/306963#8ca2803aced34da6b24a020cbeb2e4e8da48afc90cabcdd1ca9e920ca9a8eefa Pleroma(pr.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down and Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Tue, 02 Jan 2024 09:37:41 -0000 https://status.shc.kanagawa.jp/incident/306963#8ca2803aced34da6b24a020cbeb2e4e8da48afc90cabcdd1ca9e920ca9a8eefa Pleroma(pr.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down and Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Tue, 02 Jan 2024 09:37:41 -0000 https://status.shc.kanagawa.jp/incident/306963#8ca2803aced34da6b24a020cbeb2e4e8da48afc90cabcdd1ca9e920ca9a8eefa Pleroma(pr.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down and Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Tue, 02 Jan 2024 09:36:59 -0000 https://status.shc.kanagawa.jp/incident/306963#d11623c04fcd509e4e0b239b0540f4773218658c1a080313ea4c35d3d138ac94 Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Tue, 02 Jan 2024 01:40:20 -0000 https://status.shc.kanagawa.jp/incident/306963#80aaf1fc458339fbc149fdd8a0bc845bc657a3d60f154350d227270b1eb5afea NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306963 Tue, 02 Jan 2024 00:01:56 -0000 https://status.shc.kanagawa.jp/incident/306963#5f816ee0f751d547b7c60f7b4d0ef759e466de77192f9c072129b621e468d9c5 demo.shc.kanagawa.jp Initialize recovered. https://status.shc.kanagawa.jp/incident/306963 Mon, 01 Jan 2024 19:32:51 -0000 https://status.shc.kanagawa.jp/incident/306963#307d54c48489a4bb3b92baa4fccd529576518790f116bc428e18c2e00bfad4cc NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306963 Mon, 01 Jan 2024 14:28:41 -0000 https://status.shc.kanagawa.jp/incident/306963#378e83de9f789e9a09413c69310b30c66095a5efe0d209bf5df56d639cbc536a demo.shc.kanagawa.jp Initialize went down. https://status.shc.kanagawa.jp/incident/306523 Sat, 30 Dec 2023 20:25:58 -0000 https://status.shc.kanagawa.jp/incident/306523#1928641eecd07adb2221624005b676f6356993c51393ed76dfc491f8525b2ae6 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306523 Sat, 30 Dec 2023 20:25:34 -0000 https://status.shc.kanagawa.jp/incident/306523#1de4a144edbe02e1fe9f78b19a98eea328831e918a38362971451463a3f11513 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306523 Sat, 30 Dec 2023 11:24:56 -0000 https://status.shc.kanagawa.jp/incident/306523#c74287598db7ac844a496e1ede17e942ac6e248a91317ce04485f234238f4c1b Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306523 Sat, 30 Dec 2023 11:23:56 -0000 https://status.shc.kanagawa.jp/incident/306523#aed7f2089e67cb49357306caa627e541389ac8fada61d8933ec8f3d4f9d01bf6 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306285 Fri, 29 Dec 2023 21:27:20 -0000 https://status.shc.kanagawa.jp/incident/306285#73d51c90416533be8764fa1bbcb1dcd02daa0c49e8e68270ccf28db705ca0bad NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306285 Fri, 29 Dec 2023 21:26:56 -0000 https://status.shc.kanagawa.jp/incident/306285#923f62e4a219c8f4e811562d568fef254c00b0c6bd50eb91893f37ac9c46f888 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/306285 Fri, 29 Dec 2023 18:08:51 -0000 https://status.shc.kanagawa.jp/incident/306285#fb06dd9534c0fa223373a74d2e79d70c35fe66e408c209a45ed40407a2f150d3 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/306285 Fri, 29 Dec 2023 18:08:16 -0000 https://status.shc.kanagawa.jp/incident/306285#09afadea10b218fc02f36d3632156e5ee5781487267454be4e6629e21c1c3d5e NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/305653 Thu, 28 Dec 2023 21:22:45 -0000 https://status.shc.kanagawa.jp/incident/305653#dd0c65e1776c3351e9c19034b47a5f9343f52f7c6191f03edd4c08d287095d1c NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/305653 Thu, 28 Dec 2023 21:21:55 -0000 https://status.shc.kanagawa.jp/incident/305653#9e5ce17efae5181b1d5f01efa4e76f3da09ac5d04038f212d6b3c693c4f444ba NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/305653 Thu, 28 Dec 2023 18:31:13 -0000 https://status.shc.kanagawa.jp/incident/305653#9435524c3518d80d41a49b4b915279b3017b1274e8e49c6f35038619cffdc10f NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/305653 Thu, 28 Dec 2023 18:28:12 -0000 https://status.shc.kanagawa.jp/incident/305653#eb2178f442a4781695828e6496031fff257621b3ad33c40b22951199059e9155 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/304646 Wed, 27 Dec 2023 20:19:28 -0000 https://status.shc.kanagawa.jp/incident/304646#475c2113dd4e54072607ae68dabcdb3ec08b424f040d8a8257554ad1433c8706 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/304646 Wed, 27 Dec 2023 20:18:51 -0000 https://status.shc.kanagawa.jp/incident/304646#136b7b7dafadc288bbd0d4bf9a748ec2bc36ffa30c1d8fb4f7b2ea21a980f704 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/304646 Wed, 27 Dec 2023 11:14:32 -0000 https://status.shc.kanagawa.jp/incident/304646#8b330a9477e0e2c0ac0a0bae3d08adfc96ff7deb46b00ec59f51d2d555947729 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/304646 Wed, 27 Dec 2023 11:10:34 -0000 https://status.shc.kanagawa.jp/incident/304646#4b1f2331f9abecd949a7bc69543d93db591a16807cdc3632984ee52b5106ce2f Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/304646 Wed, 27 Dec 2023 11:09:41 -0000 https://status.shc.kanagawa.jp/incident/304646#0f61e76056f8c351e6115c24867186baa2fd097d3ad18a3d0b82227ad9d6ce7d NextCloud (cloud.shc.kanagawa.jp) and MongoDB Repliction recovered. https://status.shc.kanagawa.jp/incident/304646 Wed, 27 Dec 2023 11:06:13 -0000 https://status.shc.kanagawa.jp/incident/304646#aab9546bbe4e4014a255fca17e7c1e0c587f4b7830f36f2d041013ecbb9aecfe NextCloud Maintenance recovered. https://status.shc.kanagawa.jp/incident/304646 Wed, 27 Dec 2023 01:41:27 -0000 https://status.shc.kanagawa.jp/incident/304646#aeb5795cfe84998be4d5210f65530cd1f9892c0f6a2437b677b5054de0ddf989 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/304646 Wed, 27 Dec 2023 01:24:32 -0000 https://status.shc.kanagawa.jp/incident/304646#b0d326f8d5fe27839b46854661caf3f5305f7452fd196d2d13319cb5071b4608 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/304646 Tue, 26 Dec 2023 23:11:50 -0000 https://status.shc.kanagawa.jp/incident/304646#f8704debe19f7c32c7c8fa79882a22034e3691774cf8348722f92f9c134287f5 NextCloud Maintenance went down. https://status.shc.kanagawa.jp/incident/304646 Tue, 26 Dec 2023 22:53:38 -0000 https://status.shc.kanagawa.jp/incident/304646#281944e5367d40bfdedb673c86f2ad4146fc99bd772cbe4778507b79ce9fa451 NextCloud (cloud.shc.kanagawa.jp) and MongoDB Repliction went down. https://status.shc.kanagawa.jp/incident/304646 Tue, 26 Dec 2023 22:05:30 -0000 https://status.shc.kanagawa.jp/incident/304646#c18d35b8af0d482b420cd98b3f43f5d0c00dce6ddff571b73af07ddafd633ef6 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/304646 Tue, 26 Dec 2023 22:02:28 -0000 https://status.shc.kanagawa.jp/incident/304646#4a002ae9d5d980a432fe9cbd042aec8f8689534e2ccf2253981d78a95353e1bc NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/304646 Tue, 26 Dec 2023 18:32:41 -0000 https://status.shc.kanagawa.jp/incident/304646#aa3750d675546c1cdb53c6ddb52f56a9e813b6a377dd2a8793b42027d6142681 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/304646 Tue, 26 Dec 2023 18:32:07 -0000 https://status.shc.kanagawa.jp/incident/304646#a77b49298d4d6615b1537ae4788688a045644bce25d4c16d6b0e3d41c4d51fb9 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/304646 Mon, 25 Dec 2023 21:15:11 -0000 https://status.shc.kanagawa.jp/incident/304646#8bcf6ee407e370a9ddbca12a6d420967ca1846ffe4ed1a5d8c773e3051a0b7fe NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/304646 Mon, 25 Dec 2023 21:11:32 -0000 https://status.shc.kanagawa.jp/incident/304646#3e5d8916abfb3d52d905f6ef34302b2bcb80dd64eaad148910674bca3ac02609 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/304646 Mon, 25 Dec 2023 08:24:57 -0000 https://status.shc.kanagawa.jp/incident/304646#0792a7e0753c3f85de2c25d2f3eb244c55eee961eb9eb70b8a68d8061f1d1272 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/304646 Mon, 25 Dec 2023 08:23:51 -0000 https://status.shc.kanagawa.jp/incident/304646#bc2cf2f5679a548c3038e9ca2b53a1751d361325b8da21bac03aca3defb9902a Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/304577 Sun, 24 Dec 2023 20:43:54 -0000 https://status.shc.kanagawa.jp/incident/304577#81eddc1118de693b761058b9f38e45e26f2603659591192296609cd6cb01eb63 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/304577 Sun, 24 Dec 2023 20:43:13 -0000 https://status.shc.kanagawa.jp/incident/304577#171285ccf2a1d4ddbcdebba69e433e173ebc18cd527601e09e33473f2da34d39 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/304008 Sat, 23 Dec 2023 21:29:52 -0000 https://status.shc.kanagawa.jp/incident/304008#306cd3f5fd756af2ea6427dff31580df2410d6e1245aa4675fd66d6f4bec7e39 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/304008 Sat, 23 Dec 2023 21:25:47 -0000 https://status.shc.kanagawa.jp/incident/304008#3826ae2c04af5ddd2793c95b64e19c63ac718bb90de744f73ac9a4c663dd8bdf NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/304008 Sat, 23 Dec 2023 18:17:41 -0000 https://status.shc.kanagawa.jp/incident/304008#f5a2759af0fdfbd502d4e253d30be1e14cfbc30ba263a1d0d4b41aa17fa2d65b NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/304008 Sat, 23 Dec 2023 18:16:51 -0000 https://status.shc.kanagawa.jp/incident/304008#f17080681b4b8216febe9252de27f6238f8eef40740e09b1420f5c5566cd760c NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/304008 Sat, 23 Dec 2023 16:10:53 -0000 https://status.shc.kanagawa.jp/incident/304008#118c18ad9283f7ded10195e0c7f0ffd922ce73dbc10d0c57c3d16b98d14335f7 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/304008 Sat, 23 Dec 2023 16:10:06 -0000 https://status.shc.kanagawa.jp/incident/304008#b6019d363a55d6484e75abb3ba15deef42ff2aa70c4dc3c66e27d68eac1731c8 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/303578 Fri, 22 Dec 2023 21:00:27 -0000 https://status.shc.kanagawa.jp/incident/303578#05b5aac6b853b54fc5f53c4bc4f2b35ae500e9ba3e6e84b179f1c59a8974442e NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/303578 Fri, 22 Dec 2023 20:56:28 -0000 https://status.shc.kanagawa.jp/incident/303578#226d1303e2e01f290d1c630ba2533040e7e818162d5ebcffa61bb6de184c7c14 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/303436 Thu, 21 Dec 2023 21:22:59 -0000 https://status.shc.kanagawa.jp/incident/303436#f316b58378cde839cd4d426fa77288807bdb86a3bd63691738277aac990d4db8 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/303436 Thu, 21 Dec 2023 21:21:41 -0000 https://status.shc.kanagawa.jp/incident/303436#31df8c4071bc1095c683dfe585271717efa8bb299724cb12ca9f2beab21d153f NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/303436 Thu, 21 Dec 2023 18:10:25 -0000 https://status.shc.kanagawa.jp/incident/303436#b0590a9b7e5423ac720a4591c71c4157897d450a0010fe495a71b82d8a4971bf NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/303436 Thu, 21 Dec 2023 18:09:21 -0000 https://status.shc.kanagawa.jp/incident/303436#22d74220d743e12e18b3122b68c981db80470208789b3397899098fb044c1416 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/303014 Wed, 20 Dec 2023 20:20:09 -0000 https://status.shc.kanagawa.jp/incident/303014#6548456151ccbdb030ac5567de3e7ae7223ec4bdd44ec2eebbffc1661cca4d9e NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/303014 Wed, 20 Dec 2023 20:19:50 -0000 https://status.shc.kanagawa.jp/incident/303014#56bf74c42f2d80ff50fc4289052b6b2091ca46b7306e95b95bec2620f5e7bf24 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/302467 Tue, 19 Dec 2023 20:05:45 -0000 https://status.shc.kanagawa.jp/incident/302467#36a4a5a5696a7b7171eedfc46644cdcd7d86131ff125f0efc7a782cca2755b17 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/302467 Tue, 19 Dec 2023 20:04:43 -0000 https://status.shc.kanagawa.jp/incident/302467#39144fb3443537735ed60f5e3e911889c65dd1686a4d711706387057f7c97b1d NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/302159 Mon, 18 Dec 2023 21:29:29 -0000 https://status.shc.kanagawa.jp/incident/302159#acbc8993bc99aa1e64af2103fa23ab6a29f26055d153753a904e041c091497ca NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/302159 Mon, 18 Dec 2023 21:29:02 -0000 https://status.shc.kanagawa.jp/incident/302159#bf6f7bb0c4179ad56b19a5b13c4bf0d2ae4790f0396cd3775ddd53bbc82f87d3 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/302159 Mon, 18 Dec 2023 18:23:36 -0000 https://status.shc.kanagawa.jp/incident/302159#2c533e000c773a166aa79fc7ceda677dbc41506748acf6a0ede2d03bcd28ccc5 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/302159 Mon, 18 Dec 2023 18:22:16 -0000 https://status.shc.kanagawa.jp/incident/302159#958991dbbda19e9ad85d7f3dd4cb77d4b190d1870f92c28f3a4ce37cadbb62d9 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/301496 Sun, 17 Dec 2023 18:25:20 -0000 https://status.shc.kanagawa.jp/incident/301496#48eeb3946896b85723aee2e1b01b9f5f832d2b8ad4828fddfc98fe5293d8b017 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/301496 Sun, 17 Dec 2023 18:24:07 -0000 https://status.shc.kanagawa.jp/incident/301496#703161ceef62e64a8c04e484a7977227e481daa1f03a58a38a3107eda0867c01 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/301496 Sun, 17 Dec 2023 18:16:24 -0000 https://status.shc.kanagawa.jp/incident/301496#98e7ca347dd3ec2c11a2f59ec49d6c0675b3cec784fc97964914fcda0cf8695b NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/301496 Sun, 17 Dec 2023 18:15:33 -0000 https://status.shc.kanagawa.jp/incident/301496#97d03acb398ab545d2ca84c911cad25a5622c4bb16ee64173c7b54b587e7405a NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/301345 Sat, 16 Dec 2023 21:19:18 -0000 https://status.shc.kanagawa.jp/incident/301345#b28a1a6a7374ef6984a1decb71e981046992f54bdecc5d7a23307cd9508a8342 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/301345 Sat, 16 Dec 2023 21:18:32 -0000 https://status.shc.kanagawa.jp/incident/301345#4ff4f4b475ee5b19903512e75503310a5c4dbee75354c747c954689e0d87f043 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/301345 Sat, 16 Dec 2023 18:12:46 -0000 https://status.shc.kanagawa.jp/incident/301345#327fb6acf01447619b792d393dcab65467ba509995ab770a69ef1679c9f230f6 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/301345 Sat, 16 Dec 2023 18:12:06 -0000 https://status.shc.kanagawa.jp/incident/301345#2226c5a648b7a2d3baa48af4835e9ea54f73078cb47b609d8f7588d8641ff514 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/300737 Fri, 15 Dec 2023 20:36:04 -0000 https://status.shc.kanagawa.jp/incident/300737#5aec8470a10e6868db61d35babaff9a2af774383eb0dcd9f2462254aa10d449b NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/300737 Fri, 15 Dec 2023 20:35:35 -0000 https://status.shc.kanagawa.jp/incident/300737#2c8793a3cada1727d51e9c99817b05653cabce7f70f17ebc507006f917937c50 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/300521 Thu, 14 Dec 2023 20:57:49 -0000 https://status.shc.kanagawa.jp/incident/300521#5863175f65c3fd7155c463a2ca9776ebced448427379eb8ccea07d35caefd3ef NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/300521 Thu, 14 Dec 2023 20:56:50 -0000 https://status.shc.kanagawa.jp/incident/300521#95a25aef5c93ca8b444761f17882f40bed787a6d2731f51a0c47a48f593f5fa9 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/300521 Thu, 14 Dec 2023 18:35:59 -0000 https://status.shc.kanagawa.jp/incident/300521#d3ab5068df43f06d797defcf3001399af91ef33902464213245905f98470e8e2 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/300521 Thu, 14 Dec 2023 18:35:43 -0000 https://status.shc.kanagawa.jp/incident/300521#53adea93e553218dc863da94113279cce6fdf5045855ee5505936ed2774b0779 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/300023 Wed, 13 Dec 2023 20:12:40 -0000 https://status.shc.kanagawa.jp/incident/300023#c88be9d80e6874d666e77266853b01e9ea2b9d1b3723b0d601539861609b50e7 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/300023 Wed, 13 Dec 2023 20:12:09 -0000 https://status.shc.kanagawa.jp/incident/300023#0032ecde1276c43806bc72335c955232e520f2976caa3ec00803c60d5f49d25b NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/300023 Wed, 13 Dec 2023 14:38:04 -0000 https://status.shc.kanagawa.jp/incident/300023#30439d9452f68f9d5c63e281e669adebd14b645e2bc6e283d3d14b033770894d Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/300023 Wed, 13 Dec 2023 14:38:02 -0000 https://status.shc.kanagawa.jp/incident/300023#d888848f3c3f986358adadeecfcd614838e7c3269d0c88cf0ddceccd1a709ce0 Misskey(mk.shc.kanagawa.jp) went down and Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/300023 Wed, 13 Dec 2023 14:38:02 -0000 https://status.shc.kanagawa.jp/incident/300023#d888848f3c3f986358adadeecfcd614838e7c3269d0c88cf0ddceccd1a709ce0 Misskey(mk.shc.kanagawa.jp) went down and Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/300023 Wed, 13 Dec 2023 14:37:24 -0000 https://status.shc.kanagawa.jp/incident/300023#3c083576c7762c726696ba65d87b81b13e01d623eca15f5f0f6c1350740376cb Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/299644 Tue, 12 Dec 2023 20:31:33 -0000 https://status.shc.kanagawa.jp/incident/299644#3c64aa0352bd6857e27e7adb62ac5767b5eb369d0f4b9bd899d70ea5d81f5e68 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/299644 Tue, 12 Dec 2023 20:30:24 -0000 https://status.shc.kanagawa.jp/incident/299644#c35ca7358e0b10e2cbf2af74d77f9c0b1a2d9928214fd744c698205193b9c21c NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/298890 Mon, 11 Dec 2023 21:13:56 -0000 https://status.shc.kanagawa.jp/incident/298890#4db1596e98f8b25a356c31cb59fd9d23a7fe4bec8b07ace40a535af3c0013f9a NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/298890 Mon, 11 Dec 2023 21:13:40 -0000 https://status.shc.kanagawa.jp/incident/298890#be702ad77acf2975e7535ae0b706cb536b83b20073532ad352e791d5ad84f2d7 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/298313 Sun, 10 Dec 2023 20:04:43 -0000 https://status.shc.kanagawa.jp/incident/298313#059a47e1f16902c40b6004b6a8a2b5db822e91d0c3f7b9363902d464bf07866e NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/298313 Sun, 10 Dec 2023 20:01:17 -0000 https://status.shc.kanagawa.jp/incident/298313#46151db7fae77d7ec611e4646d27013ff782801c2aff3afd11c971816a3662db NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/297846 Sat, 09 Dec 2023 20:42:26 -0000 https://status.shc.kanagawa.jp/incident/297846#33bb74567fe0306fa2b20974cefb094a845a793afe21f063348be899c8bddd9c NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/297846 Sat, 09 Dec 2023 20:41:25 -0000 https://status.shc.kanagawa.jp/incident/297846#2c648a480c7a0d6da3f624efcd17c179e0368904862e7856e041746ded5e33c5 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/297770 Fri, 08 Dec 2023 20:55:53 -0000 https://status.shc.kanagawa.jp/incident/297770#0c65f12ad3e223d90fcfc604d52059bdaa59c9d2cd862a1981b080700a2b962f NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/297770 Fri, 08 Dec 2023 20:54:41 -0000 https://status.shc.kanagawa.jp/incident/297770#142e7da96893c05d82e5be584d7cec2e2b2da6566c8122c15a31ec99d46486bb NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/297770 Fri, 08 Dec 2023 18:26:06 -0000 https://status.shc.kanagawa.jp/incident/297770#7229002144a0352f620e87c50b064b7dfe6cac9e5408280f27506925fe266434 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/297770 Fri, 08 Dec 2023 18:25:43 -0000 https://status.shc.kanagawa.jp/incident/297770#9fc581ea211481985b57614c12ae9f5a2ebe52457c12cead0b73b2b7405348c9 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/296994 Thu, 07 Dec 2023 21:03:06 -0000 https://status.shc.kanagawa.jp/incident/296994#782e8d8bedfc9a99a75941845df93f5fa2b36a05f11f834daa6a3a060af10b7b NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/296994 Thu, 07 Dec 2023 21:02:32 -0000 https://status.shc.kanagawa.jp/incident/296994#77619c010363b2072e139944191060301b4483eabd0d12abbc8c915d038a56cd NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/296994 Thu, 07 Dec 2023 18:36:00 -0000 https://status.shc.kanagawa.jp/incident/296994#284259ea3f7c57c54fb10abd1ceea077532654a52de5622349c0c1213852c865 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/296994 Thu, 07 Dec 2023 18:35:10 -0000 https://status.shc.kanagawa.jp/incident/296994#30eebd55f4b706041935b58a721a8024ab1fabcbee2a7e23cfb75fbb2bd30312 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/296857 Wed, 06 Dec 2023 16:24:51 -0000 https://status.shc.kanagawa.jp/incident/296857#057534aa00626e084fe50f5832da88175f48258f9eb0759b4de465f81ba14416 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/296857 Wed, 06 Dec 2023 16:23:56 -0000 https://status.shc.kanagawa.jp/incident/296857#3ea1e3c288b174b54dac55c44355d8172f4ac1a75807c487baf2c57c154cf670 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/296461 Tue, 05 Dec 2023 21:29:20 -0000 https://status.shc.kanagawa.jp/incident/296461#1d4f41800435308e4334f683635195a06d19e5074ca596a77601beabd43e6e0b NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/296461 Tue, 05 Dec 2023 21:28:08 -0000 https://status.shc.kanagawa.jp/incident/296461#8ceb46a33dbdfa4291286c04236b1d4a30e4a4c38f92c6a313ab82cfca82198c NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/295879 Mon, 04 Dec 2023 20:54:01 -0000 https://status.shc.kanagawa.jp/incident/295879#eb0439d2452a5739ad394a7e1470baa7484efa87ba77ed2cff79e71b80739b48 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/295879 Mon, 04 Dec 2023 20:50:46 -0000 https://status.shc.kanagawa.jp/incident/295879#115c0e648dd818b12ba58885992bb6a93d504ed60f3cc24306543d3e49fcbfd5 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/295375 Sun, 03 Dec 2023 21:05:16 -0000 https://status.shc.kanagawa.jp/incident/295375#9e68d7a43d8f7e87f78cb25841686d69b98308c3ca8acc9c4d8ea55dd7e2f004 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/295375 Sun, 03 Dec 2023 21:01:12 -0000 https://status.shc.kanagawa.jp/incident/295375#892f1ea2cfff882cc287b02b917ff62c5ffa50fdf7e80cb36539d34974c805bf NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/295375 Sun, 03 Dec 2023 18:11:15 -0000 https://status.shc.kanagawa.jp/incident/295375#00d3cd3ab50929036f6eb1cfc9f74ba69ad4547ca59926060eb95a4a5e8a9fa0 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/295375 Sun, 03 Dec 2023 18:10:51 -0000 https://status.shc.kanagawa.jp/incident/295375#aaaecab652b0b17ad75146bd568f05eb1b7687dd0cd5e7c01ef8b73ca85c3292 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/295011 Sat, 02 Dec 2023 21:04:32 -0000 https://status.shc.kanagawa.jp/incident/295011#221851f2b7d7b32c2bf016539c40f059f455c9a5a743b1a8a198bd37a2336433 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/295011 Sat, 02 Dec 2023 21:00:51 -0000 https://status.shc.kanagawa.jp/incident/295011#f8e2ca92181fe39cea7132505e653dc61470f0bf54f85eeff6da9d775926880b NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/295011 Sat, 02 Dec 2023 18:28:19 -0000 https://status.shc.kanagawa.jp/incident/295011#cc84f0c66b3205e1b59dd566a342603e2fe84c4ace24c275986ddbb6b865c031 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/295011 Sat, 02 Dec 2023 18:27:09 -0000 https://status.shc.kanagawa.jp/incident/295011#e1d7c425940cf9412177665649b56cba855e6fb2bdfdbc2fc9558f8568f33ba3 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/295011 Sat, 02 Dec 2023 11:25:06 -0000 https://status.shc.kanagawa.jp/incident/295011#379013ebbb38899c437bfeade8cf21b0767fcc82b2acde8675b5fdae83161e80 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/295011 Sat, 02 Dec 2023 11:23:54 -0000 https://status.shc.kanagawa.jp/incident/295011#0be8d96285c6528f2324047076052c1f5eb342a19964016cd532255c82ecb203 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/295011 Sat, 02 Dec 2023 10:24:52 -0000 https://status.shc.kanagawa.jp/incident/295011#2f2694a37f5e713f99b1cb5313412c041c3a400da1fb24f837db600be4400833 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/295011 Sat, 02 Dec 2023 10:24:07 -0000 https://status.shc.kanagawa.jp/incident/295011#c09583fb08632d9e8f3850dc07b850f02fc66d91dc58733bb2594857903911b0 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/295011 Sat, 02 Dec 2023 07:54:53 -0000 https://status.shc.kanagawa.jp/incident/295011#eff77918bcf0115408a3a9720ff4902c395784837e6ca4b3733e977d5d176f49 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/295011 Sat, 02 Dec 2023 07:54:53 -0000 https://status.shc.kanagawa.jp/incident/295011#eff77918bcf0115408a3a9720ff4902c395784837e6ca4b3733e977d5d176f49 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/295011 Sat, 02 Dec 2023 07:47:57 -0000 https://status.shc.kanagawa.jp/incident/295011#b942b487531930ea8273f4f4154b800dae61be3ff273a061d85786c440feb37e Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/295011 Sat, 02 Dec 2023 07:47:57 -0000 https://status.shc.kanagawa.jp/incident/295011#b942b487531930ea8273f4f4154b800dae61be3ff273a061d85786c440feb37e Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/294687 Fri, 01 Dec 2023 20:19:39 -0000 https://status.shc.kanagawa.jp/incident/294687#cba740d363ba4cea4a0749762faaa8141a8bf41f2a452b6fb975b8ecce7b76e5 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/294687 Fri, 01 Dec 2023 20:19:00 -0000 https://status.shc.kanagawa.jp/incident/294687#fd806c7b36f611e1330c6d27cf48485f5aab2dd549d9cf99a82dd83b563b39d8 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/294375 Thu, 30 Nov 2023 21:02:34 -0000 https://status.shc.kanagawa.jp/incident/294375#04b9078bb704f3a56da5af82cd5cdd6e8ced8fff459de3c153ac727a0f303f08 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/294375 Thu, 30 Nov 2023 21:02:10 -0000 https://status.shc.kanagawa.jp/incident/294375#ee6ed2a0aabd700f3a0fab27951e472ad172281a039ffe79536a7e6d756d924f NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/294375 Thu, 30 Nov 2023 18:26:44 -0000 https://status.shc.kanagawa.jp/incident/294375#ac68e88565c8b8e8fed8c6d738b91cccd44c50930255b79536219f095e2c18e0 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/294375 Thu, 30 Nov 2023 18:23:43 -0000 https://status.shc.kanagawa.jp/incident/294375#72224cce346556ab1db48d04a167a56b7ad0e323f82845f8fac0b8a23dc1224f NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/293890 Wed, 29 Nov 2023 20:28:40 -0000 https://status.shc.kanagawa.jp/incident/293890#af7639cb2bf96d79fb9a01d1622ca039bc5bbdae14c880a46ebee5a9568ad48c NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/293890 Wed, 29 Nov 2023 20:22:37 -0000 https://status.shc.kanagawa.jp/incident/293890#190733acf599477eb77da199b43e6cb744b244348b79b0d8888c595e22be1d3c NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/293105 Tue, 28 Nov 2023 21:24:28 -0000 https://status.shc.kanagawa.jp/incident/293105#046b2e3176a0a0d91a8d1f23253990123d766fe127337e2191fe1b16e7c67d6c NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/293105 Tue, 28 Nov 2023 21:21:29 -0000 https://status.shc.kanagawa.jp/incident/293105#cc8327ef7406b48582126fea1b161c0b5e6f0affdb38bb8a9cfd8596846df90d NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/293105 Tue, 28 Nov 2023 18:42:19 -0000 https://status.shc.kanagawa.jp/incident/293105#dac4c2e472daecd542b797a51c55d70c2f210d94ee2a370473b1e8dd0684debf NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/293105 Tue, 28 Nov 2023 18:38:23 -0000 https://status.shc.kanagawa.jp/incident/293105#3791d69ffc689af4039daf72f01525d6ec86677d32ba7c22c7df9c27da420fbb NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/292895 Mon, 27 Nov 2023 21:14:58 -0000 https://status.shc.kanagawa.jp/incident/292895#79a6a6126a92ed0a988380437f3cfc094383f40b8ca5f48fe19c9c8ae5fd8453 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/292895 Mon, 27 Nov 2023 21:11:42 -0000 https://status.shc.kanagawa.jp/incident/292895#475e51ba791319bb30cf3d610a8e31298e65e807678619060b9fccd69be0796a NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/292895 Mon, 27 Nov 2023 18:23:39 -0000 https://status.shc.kanagawa.jp/incident/292895#c2300534b70d32d119b950556bfa90da0e471ad39d0dadc0c2a065a757956cf5 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/292895 Mon, 27 Nov 2023 18:23:06 -0000 https://status.shc.kanagawa.jp/incident/292895#39f65222fe871e48a0960bf7c0344dddfb83eb73de191970a630781491e4e5fb NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/292453 Sun, 26 Nov 2023 21:33:38 -0000 https://status.shc.kanagawa.jp/incident/292453#f44b8df387ccb46e460cf2d79d07a6de8665245550cc68de011a596366068fa5 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/292453 Sun, 26 Nov 2023 21:30:36 -0000 https://status.shc.kanagawa.jp/incident/292453#0bab6dde2ba960539888691ecda051832e353181c79f93f4c43126698fbfd559 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/292453 Sun, 26 Nov 2023 18:18:38 -0000 https://status.shc.kanagawa.jp/incident/292453#2d5719a84fe05c1145fc2d583716ab7ee12f7a1110f083ba7d56eb3110fbbc2f NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/292453 Sun, 26 Nov 2023 18:18:21 -0000 https://status.shc.kanagawa.jp/incident/292453#e69167d97b8b438360c29377404260c589580a0030bc349eca8c8a0d4ae9d6b8 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/292133 Sat, 25 Nov 2023 21:02:48 -0000 https://status.shc.kanagawa.jp/incident/292133#ea073d212102be14d8a312c530b6db14bbf499453ce8b6bd8dd5f8add41874dc NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/292133 Sat, 25 Nov 2023 20:58:38 -0000 https://status.shc.kanagawa.jp/incident/292133#92ffee664747c0fc9c718d2d702ef689e0dc7283da77a8a8902e62084d80884e NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/292133 Sat, 25 Nov 2023 18:35:55 -0000 https://status.shc.kanagawa.jp/incident/292133#50e059eca79fbd436176feddc7891f3a8e8b6cedaf5921f71e7f562eca5051c8 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/292133 Sat, 25 Nov 2023 18:31:42 -0000 https://status.shc.kanagawa.jp/incident/292133#ba92b34844f237cd53c4a958a5ae61bacedfdd9d463853322e50fab1ed94e4b8 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/291414 Fri, 24 Nov 2023 18:22:14 -0000 https://status.shc.kanagawa.jp/incident/291414#0851fd440ee880fb1344ee2831dcded836f6f2a48f41e7993b8a9d4821299944 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/291414 Fri, 24 Nov 2023 18:21:26 -0000 https://status.shc.kanagawa.jp/incident/291414#a17eea0daf6621ff7aec5480b97d81ede0e46908f0cae719eae207f9fcdd9127 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/291170 Thu, 23 Nov 2023 20:49:57 -0000 https://status.shc.kanagawa.jp/incident/291170#d063250ff2c2ade8aaffbe03af75ac75ad54d213d9ba8777eeda50aa10d9c9c8 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/291170 Thu, 23 Nov 2023 20:49:43 -0000 https://status.shc.kanagawa.jp/incident/291170#d2839f6acec72f1a34a6147c92ddd7c23261ddcddab8a88f78ce9aec7f5ae2ae NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/291170 Thu, 23 Nov 2023 18:10:49 -0000 https://status.shc.kanagawa.jp/incident/291170#24b2575bc098a00321769983d3f11354e92f9af985591d6d2d57133855ca16af NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/291170 Thu, 23 Nov 2023 18:10:17 -0000 https://status.shc.kanagawa.jp/incident/291170#73bd463169f5c99b145f101637e3c7c98f236dc3270ae990552865b11a2f22e4 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/291170 Thu, 23 Nov 2023 16:04:13 -0000 https://status.shc.kanagawa.jp/incident/291170#e8b838d9e437bd73c5a49cb00b97a5a129e3c40abcc06821f16c80f969c63a96 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/291170 Thu, 23 Nov 2023 16:03:29 -0000 https://status.shc.kanagawa.jp/incident/291170#1adbdd7445f69f53ab975c8bc7dd7bec862715062f93228d00faeeb994c9ba5a Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/291170 Thu, 23 Nov 2023 12:25:13 -0000 https://status.shc.kanagawa.jp/incident/291170#4628d18786bda09cac1505ea609e847e0a35f0e2a89e0083d200475fef85792c Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/291170 Thu, 23 Nov 2023 12:23:55 -0000 https://status.shc.kanagawa.jp/incident/291170#97e9a09f9ff53194c184ce8c8e8c44d5d14899859541737e0e961c00cea5eb0c Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/291170 Thu, 23 Nov 2023 11:24:59 -0000 https://status.shc.kanagawa.jp/incident/291170#0895cd36cd38d6ff01386329d8442a3800f24127fd0b17a93da68b1f6a9ff043 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/291170 Thu, 23 Nov 2023 11:23:47 -0000 https://status.shc.kanagawa.jp/incident/291170#89406eb9615d8870783926c96f1e1f9e69fdd0ce730136501f99d7552e633122 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/290703 Wed, 22 Nov 2023 20:02:40 -0000 https://status.shc.kanagawa.jp/incident/290703#a4db52435fe3a3acbfa90a3e2d7cf11c28522f72c1b7810176da0c7ad165f133 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/290703 Wed, 22 Nov 2023 20:02:09 -0000 https://status.shc.kanagawa.jp/incident/290703#7b95845262a8e0bfe424de6cd9128b93b4ebe2341f41652a5d6f77ad27da0b69 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/290403 Tue, 21 Nov 2023 20:20:15 -0000 https://status.shc.kanagawa.jp/incident/290403#4b146f014e702eb0785b0480add7b9d72729bf50c7349e6d39318adf15fe3e15 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/290403 Tue, 21 Nov 2023 20:17:09 -0000 https://status.shc.kanagawa.jp/incident/290403#28ee9a616fc5fc0d2aa69a636536ad29f294392ba2cd425f473b418cbad5acf1 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/289653 Mon, 20 Nov 2023 20:11:06 -0000 https://status.shc.kanagawa.jp/incident/289653#c896ebe9fd51ec367dbd5a5b6fd1a04901c4f08e702808c0f298325c489b8c28 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/289653 Mon, 20 Nov 2023 20:10:19 -0000 https://status.shc.kanagawa.jp/incident/289653#5973d9d1a38b1f6d41dbb881fd339e14b1567dacc18fc5989fda433a3a3cc636 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/289653 Mon, 20 Nov 2023 14:37:22 -0000 https://status.shc.kanagawa.jp/incident/289653#2a9c7178b5afe532db4a51b812c4d94c6cd9a5e3423e125a9804025f8aa2160b Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/289653 Mon, 20 Nov 2023 14:36:29 -0000 https://status.shc.kanagawa.jp/incident/289653#c053a69fae68a2b58b05b41a319b7f2cf55bc719fea231573305744dff3f3fd8 Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/289653 Mon, 20 Nov 2023 14:36:03 -0000 https://status.shc.kanagawa.jp/incident/289653#6781caa39861263601e18a842fbf57ce3cc1ca5eb9a2e19887f9c6bb83779226 Mastodon(mt.shc.kanagawa.jp) and Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/289653 Mon, 20 Nov 2023 14:36:03 -0000 https://status.shc.kanagawa.jp/incident/289653#6781caa39861263601e18a842fbf57ce3cc1ca5eb9a2e19887f9c6bb83779226 Mastodon(mt.shc.kanagawa.jp) and Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/289442 Sun, 19 Nov 2023 21:10:20 -0000 https://status.shc.kanagawa.jp/incident/289442#3f4dbe4c6102c81442db972da59b15e460ea8cfc6df4f18f787448431709b548 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/289442 Sun, 19 Nov 2023 21:09:51 -0000 https://status.shc.kanagawa.jp/incident/289442#a3e3ad145f45fadc80b02a8e7ca2f888be2d3a16cff2de7fda80d94b11ebb6cd NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/289442 Sun, 19 Nov 2023 18:09:57 -0000 https://status.shc.kanagawa.jp/incident/289442#509ad7a97772dd11d0c51413be107284e8f41a512e21dc6b220014b13c2a4ca0 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/289442 Sun, 19 Nov 2023 18:06:56 -0000 https://status.shc.kanagawa.jp/incident/289442#fe85aae36a8643107966126fc6606cd0bae84f533cc23d8ecad27586fd4c0ae1 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/289064 Sat, 18 Nov 2023 21:03:52 -0000 https://status.shc.kanagawa.jp/incident/289064#69968542434533abb1c37685541efa24da0216a6d2bd36db6c26516e3bc5dde0 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/289064 Sat, 18 Nov 2023 21:00:52 -0000 https://status.shc.kanagawa.jp/incident/289064#b17b5c0b7a015b28d965cad07eb2a9cbc66c4fd7075c20c7e311db8d5ee2435b NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/289064 Sat, 18 Nov 2023 18:24:24 -0000 https://status.shc.kanagawa.jp/incident/289064#33b09d665192dddd2ea4a6d8dc84d011b790b9335f2ed87d52934b03c3a31da2 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/289064 Sat, 18 Nov 2023 18:23:32 -0000 https://status.shc.kanagawa.jp/incident/289064#23c8393ef03c77fff5069520dcd03e0c6fa9a8d8f075983e280620732174a8f2 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/288679 Fri, 17 Nov 2023 20:47:32 -0000 https://status.shc.kanagawa.jp/incident/288679#0dadce16db37ad270802837415caba1574d6ccd876b9961bade3998fc771770c NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/288679 Fri, 17 Nov 2023 20:44:27 -0000 https://status.shc.kanagawa.jp/incident/288679#dd5013941d06af64907b121394fe72aaed24cde3d9b06e78b5d8c253b1117047 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/288679 Fri, 17 Nov 2023 18:08:27 -0000 https://status.shc.kanagawa.jp/incident/288679#50ec10d6a05298de8bb12ef82d41cb82e366e17b3d89e5d1a4ae396dd0dd95e1 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/288679 Fri, 17 Nov 2023 18:07:37 -0000 https://status.shc.kanagawa.jp/incident/288679#e4809d7ba938d9d99fc010b52b8df487760ec6314c55582606ab0c89be51a7a5 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/288047 Thu, 16 Nov 2023 20:25:17 -0000 https://status.shc.kanagawa.jp/incident/288047#63a1b4c6452e823c3d292f3901e4bddf30acf19279836e8f679ccfcd673289e2 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/288047 Thu, 16 Nov 2023 20:21:13 -0000 https://status.shc.kanagawa.jp/incident/288047#ee3d76b3a177b40e98b7a50aa107d33f669215004dac0495f4836c7d8845eaff NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/287589 Wed, 15 Nov 2023 20:46:41 -0000 https://status.shc.kanagawa.jp/incident/287589#a266eb36833c0469a645d71d4774e015a09ccb83681813c789b7b3409a501a9f NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/287589 Wed, 15 Nov 2023 20:43:34 -0000 https://status.shc.kanagawa.jp/incident/287589#5853da799b110536d72d7006a606dbc85060c33d940060f4d7f54062b9e6f45c NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/287589 Wed, 15 Nov 2023 18:16:32 -0000 https://status.shc.kanagawa.jp/incident/287589#9e1cfb3717739bdb771267618a516d48881f175ec216ef0063fa095e2e7ae539 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/287589 Wed, 15 Nov 2023 18:16:12 -0000 https://status.shc.kanagawa.jp/incident/287589#5f876b442dbccc5367c6ff4b282d452178026aa323419936177078e95284e4fc NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/287589 Wed, 15 Nov 2023 14:39:55 -0000 https://status.shc.kanagawa.jp/incident/287589#87d391766226f41df2f6a7507ce85bf5576bdae61ccf7df9cadd243d8907da91 ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/287589 Wed, 15 Nov 2023 14:39:36 -0000 https://status.shc.kanagawa.jp/incident/287589#2f7916c4b0de57e5b832782711c0d449c64e243f7f8b9e3e93a73889e7699c75 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/287589 Wed, 15 Nov 2023 14:39:10 -0000 https://status.shc.kanagawa.jp/incident/287589#fac3dfce7c82be4b4b74f6ab03d14f0abbf5349de88484d648758d6c7478b4b9 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/287589 Wed, 15 Nov 2023 14:38:53 -0000 https://status.shc.kanagawa.jp/incident/287589#4af9d06f464db2c119f7cc386e3d3b96cb541de4f3f4a34748631d8d5d357185 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/287589 Wed, 15 Nov 2023 14:38:51 -0000 https://status.shc.kanagawa.jp/incident/287589#7e4b8f2213bb73a72969ef7ed016248f8d92111ed870c3f48eea98c458ded406 ownCloud (share.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/287589 Wed, 15 Nov 2023 14:36:37 -0000 https://status.shc.kanagawa.jp/incident/287589#17d7097e6e83db7947a2a59b1ff37c156188848e16fefd57ffad1e4a111a361e Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/286397 Tue, 14 Nov 2023 20:53:13 -0000 https://status.shc.kanagawa.jp/incident/286397#b07da0106b0b9e698dc2f688338f1b5629e4b734fc411f93c9b027b89881a34f NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/286397 Tue, 14 Nov 2023 20:50:00 -0000 https://status.shc.kanagawa.jp/incident/286397#e37d64e1451bd332ebc074aff7a74a1af3a4f2fa03d1216dd89755f682e14b27 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/286397 Tue, 14 Nov 2023 18:17:08 -0000 https://status.shc.kanagawa.jp/incident/286397#1f2f298c294c29ac006d1f225a6ba029d9ff1a292f6b5b35f47eb39335b6d141 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/286397 Tue, 14 Nov 2023 18:16:40 -0000 https://status.shc.kanagawa.jp/incident/286397#4000b1dd0de7f63951381e52680aac0792e879c6ee4175c79adb8f42a180a4a4 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/286397 Tue, 14 Nov 2023 10:49:27 -0000 https://status.shc.kanagawa.jp/incident/286397#ab7a1e1f7409e5192ca42d2c6dfe7012f3e2c5219e06402ceec85e2845cbdd5e NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/286397 Tue, 14 Nov 2023 10:46:31 -0000 https://status.shc.kanagawa.jp/incident/286397#f14ade5972fcf92bf03ea758248a999ee6626d339552ce5122435962fd261a28 NextCloud Maintenance recovered. https://status.shc.kanagawa.jp/incident/286397 Tue, 14 Nov 2023 02:29:37 -0000 https://status.shc.kanagawa.jp/incident/286397#9816e9f120bf5f93cccd6d36537fe0538f08a2c55ec4f4e8a02ea90b9cef364b NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/286397 Tue, 14 Nov 2023 02:15:59 -0000 https://status.shc.kanagawa.jp/incident/286397#30caac99ae4ee30955ca590051f252aeaa4eb3452f568a948000b3443badb4f4 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/286397 Mon, 13 Nov 2023 21:47:26 -0000 https://status.shc.kanagawa.jp/incident/286397#0236af806d0d27f9db92c65c7d870b78f97a9b99e66e788d361fb32f52271af2 NextCloud Maintenance went down. https://status.shc.kanagawa.jp/incident/286397 Mon, 13 Nov 2023 21:44:35 -0000 https://status.shc.kanagawa.jp/incident/286397#e6c1853addd80587a2c961c73daf074934c758f4ac97b7386b11a6695ef46671 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/286397 Mon, 13 Nov 2023 21:39:29 -0000 https://status.shc.kanagawa.jp/incident/286397#ebd5ce2905cfdc4f7d798ffb9cd3cd14bd87e117c63751c89fbf13e21888d76c NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/286397 Mon, 13 Nov 2023 21:32:37 -0000 https://status.shc.kanagawa.jp/incident/286397#c9befad87c3f983a48a91eed27a7c4e0e59a6e6c2576912dddd053d1799d71f4 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/286397 Mon, 13 Nov 2023 20:29:35 -0000 https://status.shc.kanagawa.jp/incident/286397#9ffbbdfa3cc11e8c3a8556178ecd221ffc2a5c0031adf95676b2f3ac0352613f NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/286397 Mon, 13 Nov 2023 20:25:39 -0000 https://status.shc.kanagawa.jp/incident/286397#58b92135b6152f46b3c0f0d6d5d057f30743ff69aa798aa2bfc54aae91512df4 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/286397 Mon, 13 Nov 2023 10:24:56 -0000 https://status.shc.kanagawa.jp/incident/286397#251fe195e1af1c114e4162b720f7da3103acdfb64a2014aaaa3d25b6a5ee4ae4 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/286397 Mon, 13 Nov 2023 10:23:45 -0000 https://status.shc.kanagawa.jp/incident/286397#d04feb99667c25ae1fa79ce3449658b9e1b4e2972fb5388561600bbcedbf7fe0 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/285892 Sun, 12 Nov 2023 21:26:50 -0000 https://status.shc.kanagawa.jp/incident/285892#631163d035057bb81d957cbe1f120678d83be6c7c5c3acdb3ff1284fad0a08dd NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/285892 Sun, 12 Nov 2023 21:26:29 -0000 https://status.shc.kanagawa.jp/incident/285892#5160e2e182f01f1199838e0273b8c7c6b13f4f4225f6f7fc9833879064a58da8 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/285892 Sun, 12 Nov 2023 18:14:38 -0000 https://status.shc.kanagawa.jp/incident/285892#8fa0927dcea11a95c8d4c085825abb71c853b87932e17fb6a1e56e10cb1ebfb3 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/285892 Sun, 12 Nov 2023 18:14:07 -0000 https://status.shc.kanagawa.jp/incident/285892#79f5e00df71c6f7957cf35b443f9ce2781c6140875cb76a12d7755aab65a97e1 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/285503 Sat, 11 Nov 2023 20:16:50 -0000 https://status.shc.kanagawa.jp/incident/285503#7e6be993579812467f3a47900fd2695768a521db3a80fc48036a417ee72f857a NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/285503 Sat, 11 Nov 2023 20:16:23 -0000 https://status.shc.kanagawa.jp/incident/285503#6074dae1c8798159a3ec26e7614d1c3532ef459e29e899598d79d473ccb7f9ef NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/285503 Sat, 11 Nov 2023 07:04:16 -0000 https://status.shc.kanagawa.jp/incident/285503#6f78baa323e2a229983b1bd4f27fa6a178a98eef8c9ff3f4fbe89844c74e50e2 NextCloud (cloud.shc.kanagawa.jp) and ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/285503 Sat, 11 Nov 2023 07:04:16 -0000 https://status.shc.kanagawa.jp/incident/285503#6f78baa323e2a229983b1bd4f27fa6a178a98eef8c9ff3f4fbe89844c74e50e2 NextCloud (cloud.shc.kanagawa.jp) and ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/285503 Sat, 11 Nov 2023 06:59:01 -0000 https://status.shc.kanagawa.jp/incident/285503#89b3c7c471592056686115a80052be9c07290e3ae69654cdc9fb29122b0bbdad ownCloud (share.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/285503 Sat, 11 Nov 2023 06:58:06 -0000 https://status.shc.kanagawa.jp/incident/285503#f28ca7bcf6f6d1614d66fd8d5cb8f2c127c4a33bc3d0c6f623e1fb8dc582f5fb NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/285503 Sat, 11 Nov 2023 06:42:05 -0000 https://status.shc.kanagawa.jp/incident/285503#35077d96c8fa1eb6f244eaf929542cadbe8b941d39582f577a6384c29edf8d0e Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/285503 Sat, 11 Nov 2023 06:41:47 -0000 https://status.shc.kanagawa.jp/incident/285503#6b91a347359200977f82f00e2676a23d1817fabca5274870502a1e5703121ced Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/285503 Sat, 11 Nov 2023 06:34:06 -0000 https://status.shc.kanagawa.jp/incident/285503#31ae3572567471b8bd207b2863734e4f4b6deaa72c37755e3629a55c28f132a3 NextCloud (cloud.shc.kanagawa.jp) and ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/285503 Sat, 11 Nov 2023 06:34:06 -0000 https://status.shc.kanagawa.jp/incident/285503#31ae3572567471b8bd207b2863734e4f4b6deaa72c37755e3629a55c28f132a3 NextCloud (cloud.shc.kanagawa.jp) and ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/285503 Sat, 11 Nov 2023 06:33:36 -0000 https://status.shc.kanagawa.jp/incident/285503#43e29bc854dada65fbb4c4ce3226ed830229568647034506c26a541ce453e9ac Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/285503 Sat, 11 Nov 2023 06:33:07 -0000 https://status.shc.kanagawa.jp/incident/285503#0c46ef35008ff50f1ec26145fcc4f2d57579b02f70a808fef751f476748cbc25 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/285503 Sat, 11 Nov 2023 06:33:07 -0000 https://status.shc.kanagawa.jp/incident/285503#0c46ef35008ff50f1ec26145fcc4f2d57579b02f70a808fef751f476748cbc25 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/285503 Sat, 11 Nov 2023 06:32:06 -0000 https://status.shc.kanagawa.jp/incident/285503#ca6547d7aa3e87dcd7902d0b6d76607d8c87b8851395ca29c37e03eb074f1f82 ownCloud (share.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/285503 Sat, 11 Nov 2023 06:31:04 -0000 https://status.shc.kanagawa.jp/incident/285503#6ea483c7e3a7cac8526a87ceed77129aa14c0042747266564f25f0cc9f7a4e84 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/285503 Sat, 11 Nov 2023 06:30:33 -0000 https://status.shc.kanagawa.jp/incident/285503#8e9e61504f53ecc1ded91ce73210b638a4f80a52b2b5253143d0a5b552e71e53 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/285503 Sat, 11 Nov 2023 06:29:59 -0000 https://status.shc.kanagawa.jp/incident/285503#1ea166346fe811395b0e14c78e3502f0f8460b252525d9d3e1958dac6df755f6 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/285503 Sat, 11 Nov 2023 06:29:39 -0000 https://status.shc.kanagawa.jp/incident/285503#0d8b8a91d70e98131797f7b7f43664f216662197023a21f2f30677537e8fa1b1 Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/285410 Fri, 10 Nov 2023 21:06:17 -0000 https://status.shc.kanagawa.jp/incident/285410#552b6855c8b35310bd4564f4f7ddda4fc874df6b2fe9d995ea578dc43e9d96f2 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/285410 Fri, 10 Nov 2023 21:02:19 -0000 https://status.shc.kanagawa.jp/incident/285410#049ff00774fcbf5dda6c5515cda4c61002f98ec173719f6bf456b015d031736d NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/285410 Fri, 10 Nov 2023 18:21:23 -0000 https://status.shc.kanagawa.jp/incident/285410#aaac0763a97e304377fc7228d6328f70ce86c52bdc5f5de369345718824d211f NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/285410 Fri, 10 Nov 2023 18:20:58 -0000 https://status.shc.kanagawa.jp/incident/285410#12227edee9cd8d4098b0923442ef2d0f400006c51fec5c49fd275979da426bac NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/284898 Thu, 09 Nov 2023 21:18:23 -0000 https://status.shc.kanagawa.jp/incident/284898#83ce63fdcd7e0c1eac171e95aa8b5349abb2d8ee560db67f5c537c828ebd1464 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/284898 Thu, 09 Nov 2023 21:17:46 -0000 https://status.shc.kanagawa.jp/incident/284898#2bd20a96f603dcf2e2b9dfd034d999e86b6c380ca57111817a49be06a1c3f3cf NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/284898 Thu, 09 Nov 2023 18:30:24 -0000 https://status.shc.kanagawa.jp/incident/284898#1e394a5c2db990484154defc0ccb42713300e9a54b5381a439f225bf3ed9554d NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/284898 Thu, 09 Nov 2023 18:30:04 -0000 https://status.shc.kanagawa.jp/incident/284898#c803d2e7c8022af501b892551803251ab8b79b9cabdd4cc6bb4d39fabde0a2f4 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/284396 Wed, 08 Nov 2023 21:30:24 -0000 https://status.shc.kanagawa.jp/incident/284396#4d631b80a38fb5f8fd472abcb7fc661ea410105f1cc2ae904a7d8359740d7773 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/284396 Wed, 08 Nov 2023 21:26:10 -0000 https://status.shc.kanagawa.jp/incident/284396#16c66f065477c8dbedbab060149acba66500cc83a271d262c0cc155e7d363a07 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/284396 Wed, 08 Nov 2023 18:23:49 -0000 https://status.shc.kanagawa.jp/incident/284396#0409dcc8ee0ec2763eb9494478dd8f889bb488019386f96c2638727a0b3ae69e NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/284396 Wed, 08 Nov 2023 18:23:02 -0000 https://status.shc.kanagawa.jp/incident/284396#36fb8083c1fa0df479b2ef1b168f546b81afae9fc4e72e8db187c62beb0c427c NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/283833 Tue, 07 Nov 2023 20:20:28 -0000 https://status.shc.kanagawa.jp/incident/283833#0c44d522bde9b82ef282c360ed1169f724295cb77f5625d87bda885ff328ae8f NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/283833 Tue, 07 Nov 2023 20:19:38 -0000 https://status.shc.kanagawa.jp/incident/283833#10b2e079c49c4456935e1d074a3fec1ca8e04b0f159abb989db46d2686995b86 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/283225 Mon, 06 Nov 2023 21:32:46 -0000 https://status.shc.kanagawa.jp/incident/283225#67287ea5b10d285a3eb9e883eba3e998241f33febf6ba81bcee99ff6daecc94c NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/283225 Mon, 06 Nov 2023 21:31:59 -0000 https://status.shc.kanagawa.jp/incident/283225#48ddfd3c05e895a573c58f2194003e768572e34bce28dbd936e538e0ba853234 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/283225 Mon, 06 Nov 2023 18:11:03 -0000 https://status.shc.kanagawa.jp/incident/283225#03795ef9d0ead7005aaa58adc144ece183c4fd3558e839a83a2e0cc4de50e0fb NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/283225 Mon, 06 Nov 2023 18:07:52 -0000 https://status.shc.kanagawa.jp/incident/283225#4e678e1b32b1d5d37dddfe1394aa1623c7e1fe74ace9dee364600264b4263888 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/282626 Sun, 05 Nov 2023 20:44:28 -0000 https://status.shc.kanagawa.jp/incident/282626#1311d1055b10bb912054943b95e4bfb11db907f0879fe44c4e9005d621ba6e3f NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/282626 Sun, 05 Nov 2023 20:43:36 -0000 https://status.shc.kanagawa.jp/incident/282626#419d6158e7c7749b7355bed0f9d62ce01a2a48a0353d5bc04ed0937a59da4e9b NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/282626 Sun, 05 Nov 2023 18:17:28 -0000 https://status.shc.kanagawa.jp/incident/282626#5f86b740232044d9b312cfbde87212d677c3d2e05e81e845e28fd4df7ea0c498 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/282626 Sun, 05 Nov 2023 18:17:15 -0000 https://status.shc.kanagawa.jp/incident/282626#a2dce6e27c4e0d5b61237064c00bfca01f3fb775aefbbb28ee4c562ed2f91409 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/282626 Sun, 05 Nov 2023 11:11:10 -0000 https://status.shc.kanagawa.jp/incident/282626#1fe066dd78b3f8e2081da653c1babac31658f8a27abddc93aaad9022c4d939a8 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/282626 Sun, 05 Nov 2023 11:07:48 -0000 https://status.shc.kanagawa.jp/incident/282626#8a4c942757ec6af95488e18e05db6c51ecaef006167fff8d036f219273f9b13d Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/282626 Sun, 05 Nov 2023 08:37:55 -0000 https://status.shc.kanagawa.jp/incident/282626#a28f53673509fc0196b919ae6b460286bc4d9aeab564eec4fa48dcfdee4a2a1e Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/282626 Sun, 05 Nov 2023 08:37:44 -0000 https://status.shc.kanagawa.jp/incident/282626#0601cf22bcdcf0b2fa1337a7ac40ce8814b5edc1e898416436afc8407fd138e5 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/282626 Sun, 05 Nov 2023 08:34:35 -0000 https://status.shc.kanagawa.jp/incident/282626#6436cdd25eb3f58c249c3fa58d72ccb66b4520308572d9479a803e69d690a3b4 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/282626 Sun, 05 Nov 2023 08:30:57 -0000 https://status.shc.kanagawa.jp/incident/282626#1c794739a2c30a84d5623aee6332ade9839cd4a1d9a8d9d21415d9b71e95bd64 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/282453 Sat, 04 Nov 2023 20:52:48 -0000 https://status.shc.kanagawa.jp/incident/282453#cc4a0d4c92a4902011c314d93f5a2444add79f67074bfd05f59f29cdbd1a51be NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/282453 Sat, 04 Nov 2023 20:52:28 -0000 https://status.shc.kanagawa.jp/incident/282453#f029bce890599ac0e2391e8fd4abf71e02b8ad30c628d400489ee444a6ff19cc NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/282054 Fri, 03 Nov 2023 21:30:49 -0000 https://status.shc.kanagawa.jp/incident/282054#0fae64216e4df9bbdf23b23a85d6a66e79f0c01b2e8ea9a999a99bd0af169ba4 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/282054 Fri, 03 Nov 2023 21:26:51 -0000 https://status.shc.kanagawa.jp/incident/282054#b4296ab08dc3939b90945292bd666e562111c9d308e7b94b63a1734a9f69fe62 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/282054 Fri, 03 Nov 2023 18:21:50 -0000 https://status.shc.kanagawa.jp/incident/282054#9f25432347748984a96b10f29cd5c0a58f4aec2e0c9fbefd7f054482fb495820 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/282054 Fri, 03 Nov 2023 18:21:15 -0000 https://status.shc.kanagawa.jp/incident/282054#84707506073faa7e05d467d1763d705adeecceff0754ea8f7be624ae75bfa5e7 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/281382 Thu, 02 Nov 2023 21:15:48 -0000 https://status.shc.kanagawa.jp/incident/281382#d48afe4c80f7dfca2fbe2d05db6859ac58c2371d616d082af0caae93696ff019 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/281382 Thu, 02 Nov 2023 21:14:57 -0000 https://status.shc.kanagawa.jp/incident/281382#cf1e6230bd6734d397d9c59046011493b860121bf825b18072af5a66567f52f7 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/281382 Thu, 02 Nov 2023 19:42:35 -0000 https://status.shc.kanagawa.jp/incident/281382#627a5963a7fcf0af4452025e204606929bac3d409efb1c712aec4032e493a664 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/281382 Thu, 02 Nov 2023 19:42:22 -0000 https://status.shc.kanagawa.jp/incident/281382#231ae0e3a5cefce013e7413b119f58fdc9c383bc8b2741cb42dd943e0733e42c Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/281382 Thu, 02 Nov 2023 19:36:19 -0000 https://status.shc.kanagawa.jp/incident/281382#ffcb1f00febe6ea696e571309e875170134bd072493f86f4a5daf05256aeb103 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/281382 Thu, 02 Nov 2023 19:36:06 -0000 https://status.shc.kanagawa.jp/incident/281382#7d000619d1583f18f013528019efde189a2c3e272cf67b1853cbe6582e1291f6 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/281382 Thu, 02 Nov 2023 18:37:01 -0000 https://status.shc.kanagawa.jp/incident/281382#942b4473c3b4492d05afa7a31ee794316eff61ec0a401383823540698a543ec9 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/281382 Thu, 02 Nov 2023 18:36:37 -0000 https://status.shc.kanagawa.jp/incident/281382#da3134a63c50a9be76848794eff51860fc27f878b21cd4d4c61aa9230057d7a5 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/281382 Thu, 02 Nov 2023 18:30:31 -0000 https://status.shc.kanagawa.jp/incident/281382#52c2037ee76478b7afa193204a4094bc142aa58d569cea89c23c161f9fccc314 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/281382 Thu, 02 Nov 2023 18:30:06 -0000 https://status.shc.kanagawa.jp/incident/281382#e6c550f69335116d2890f501399ee6106b2bdf945af5c8a6296153936428fac6 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/281382 Thu, 02 Nov 2023 18:29:58 -0000 https://status.shc.kanagawa.jp/incident/281382#38f42406106055fc64ca2559faff68a46e9d8b75874a5058dea833c1385332e3 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/281382 Thu, 02 Nov 2023 18:29:58 -0000 https://status.shc.kanagawa.jp/incident/281382#38f42406106055fc64ca2559faff68a46e9d8b75874a5058dea833c1385332e3 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/281051 Wed, 01 Nov 2023 21:16:04 -0000 https://status.shc.kanagawa.jp/incident/281051#78043e254bdba88c824cfae19bcca32d6a9e47937ee0065c80003de289cb117a NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/281051 Wed, 01 Nov 2023 21:15:28 -0000 https://status.shc.kanagawa.jp/incident/281051#96fca058ead4026e8fd4e8a87d42eccb637caeebc4fcabd4bae72dce9b099ccc NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/280543 Tue, 31 Oct 2023 20:54:47 -0000 https://status.shc.kanagawa.jp/incident/280543#2657e21591ce63c08bc410ece11e6ff724500fab3a9dc92a53e9d5f6f341a8cc NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/280543 Tue, 31 Oct 2023 20:47:58 -0000 https://status.shc.kanagawa.jp/incident/280543#1cfece1b77403c02bb216aaa3f11df7f768bc2b0235252a9ad46caac69833799 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/278983 Mon, 30 Oct 2023 18:29:26 -0000 https://status.shc.kanagawa.jp/incident/278983#39c3232674d8534b8d7b373c606348d5ceae63584089f8e53e16d8fc3a601e5e NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/278983 Mon, 30 Oct 2023 18:28:58 -0000 https://status.shc.kanagawa.jp/incident/278983#c7a04f77762d7c0a25f3add8123779ead756140b65d6e3eeb85087c9b06501da NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/278983 Mon, 30 Oct 2023 05:26:23 -0000 https://status.shc.kanagawa.jp/incident/278983#aba0c2d24510aceef02116de2600388a9d1e9de6035d4f2551b65bec0fa0e781 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/278983 Mon, 30 Oct 2023 05:25:16 -0000 https://status.shc.kanagawa.jp/incident/278983#8bc55f94e567aac4c16dfd9ea99417cfbae2348823d9330f4c070e7358fff1b0 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/278983 Mon, 30 Oct 2023 05:17:21 -0000 https://status.shc.kanagawa.jp/incident/278983#c7dc969035205b553aaf8fb05dde3136a6373ecfa9a295ee780dcf62bddaf214 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/278983 Mon, 30 Oct 2023 05:16:15 -0000 https://status.shc.kanagawa.jp/incident/278983#73897ef4a5a8396934ced08f9ee54af738719412afb9da2f0025f5f84d4391c6 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/278983 Mon, 30 Oct 2023 05:08:27 -0000 https://status.shc.kanagawa.jp/incident/278983#eb536c83c80791bb02cbe0a3d0c9dd47bac72999f3e5f882835992d3918865ba Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/278983 Mon, 30 Oct 2023 05:01:19 -0000 https://status.shc.kanagawa.jp/incident/278983#12609dbec6a12bc530aec5ec641f8dfc2298af7f70c8cf818a9006e054f37de7 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/278983 Mon, 30 Oct 2023 04:32:16 -0000 https://status.shc.kanagawa.jp/incident/278983#2e5a9646547f20b2d959b186653476ffbdccd70a8ae9dcb9f4ff75f18209f015 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/278983 Mon, 30 Oct 2023 04:25:09 -0000 https://status.shc.kanagawa.jp/incident/278983#62a043afec946fd7aac6742b37cd132b7b529a58ec8c36b2a68f22d28ebb7940 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/278983 Sun, 29 Oct 2023 20:38:34 -0000 https://status.shc.kanagawa.jp/incident/278983#8b0e1ce4d6daa861703108e8dab5c53ed00bc3aa4276d04ca41e9a3abc527167 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/278983 Sun, 29 Oct 2023 20:34:22 -0000 https://status.shc.kanagawa.jp/incident/278983#c50f105f4febc761d81b570e3aee506cb78c8b3d10fd153cd24c0fbc8425244d NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/278983 Sun, 29 Oct 2023 16:50:42 -0000 https://status.shc.kanagawa.jp/incident/278983#91f94f258775aca930c47e31bab27c7e3c88aac555c45030b2d8b39ae7cfa2b4 Pleroma Daily Database Backup recovered. https://status.shc.kanagawa.jp/incident/278983 Sun, 29 Oct 2023 16:09:47 -0000 https://status.shc.kanagawa.jp/incident/278983#64abc659d0a573ef3240589a5839131e1e04fe69d021c07e78e8f78c10092d2f Pleroma Daily Database Backup went down. https://status.shc.kanagawa.jp/incident/278983 Sun, 29 Oct 2023 10:20:14 -0000 https://status.shc.kanagawa.jp/incident/278983#1b341232100702e826dfada7fc5480dca1eca5f4efc3f88e2e4582b832043376 ownCloud (share.shc.kanagawa.jp) and MongoDB Repliction recovered. https://status.shc.kanagawa.jp/incident/278983 Sun, 29 Oct 2023 10:19:04 -0000 https://status.shc.kanagawa.jp/incident/278983#f35cf765efdbcdf420fbebbe913fc4d743a32554acc4341fe4ebb95f11105ff5 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/278983 Sun, 29 Oct 2023 10:19:04 -0000 https://status.shc.kanagawa.jp/incident/278983#f35cf765efdbcdf420fbebbe913fc4d743a32554acc4341fe4ebb95f11105ff5 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/278983 Sun, 29 Oct 2023 10:16:40 -0000 https://status.shc.kanagawa.jp/incident/278983#51deafdff75a0fee79ffee093a21d30bc01641c81c26a1d73a3057133ca94b74 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/278983 Sat, 28 Oct 2023 20:34:57 -0000 https://status.shc.kanagawa.jp/incident/278983#4b0c12f5eb91f1053b8434b892e83f1446f0081e9fc0d2695ae3e750df7573e8 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/278983 Sat, 28 Oct 2023 20:28:15 -0000 https://status.shc.kanagawa.jp/incident/278983#14c82e121e76bfb4205b72ea73bf33ac979b03f2d1df71a02737949118fbf602 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/278983 Sat, 28 Oct 2023 17:03:48 -0000 https://status.shc.kanagawa.jp/incident/278983#7da0c76fc12f13da35b91e35fe93f006ad1f6a26cde2ebac08d481ff5705c8c8 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/278983 Sat, 28 Oct 2023 17:03:31 -0000 https://status.shc.kanagawa.jp/incident/278983#17dece567e96e54f06bf5fb6fb480f5867bdd1d1915a97cf69aadfeda0e0ecc5 ownCloud (share.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/278983 Sat, 28 Oct 2023 17:02:37 -0000 https://status.shc.kanagawa.jp/incident/278983#2e80b113ac67d6ac66a564f545e5f28698ba685aa7ef40493dd06f3a9d9a2eee Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/278983 Sat, 28 Oct 2023 17:01:21 -0000 https://status.shc.kanagawa.jp/incident/278983#405aeb7871aa161bbcf02a5224c0ae0af459d3e91f7831e02632369caf0ac10e Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/278650 Fri, 27 Oct 2023 21:28:34 -0000 https://status.shc.kanagawa.jp/incident/278650#314cf5fcdb07c86837c391ebb53aedc46dd497b8b11d0f0d3bb7ad19c14caa95 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/278650 Fri, 27 Oct 2023 21:28:05 -0000 https://status.shc.kanagawa.jp/incident/278650#9afd7c64afbd07b0711b96996097241146ffa2a535d6a7ea72f5305bb2856860 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/278650 Fri, 27 Oct 2023 18:19:39 -0000 https://status.shc.kanagawa.jp/incident/278650#02b70e7921a36ee61f019a57b3ec5b467a330bb46b310d4e21c66fd0bc48141b NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/278650 Fri, 27 Oct 2023 18:19:05 -0000 https://status.shc.kanagawa.jp/incident/278650#5d719bcd7ed6a2895fde016d3785d76078814914ef2ec474bd9b0a9640398975 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/278171 Thu, 26 Oct 2023 21:20:43 -0000 https://status.shc.kanagawa.jp/incident/278171#f8719cd11e48864781d9ba6c7884f918e235074df1e618c8afe0eb2b279986e7 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/278171 Thu, 26 Oct 2023 21:17:33 -0000 https://status.shc.kanagawa.jp/incident/278171#694f459d52ece21007cfa710a4b2e019a476964b2966cc4ce44790379a11a3eb NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/278171 Thu, 26 Oct 2023 18:26:21 -0000 https://status.shc.kanagawa.jp/incident/278171#29909027c4465c04f386707c70f84161693411c778a11802f68d4f891b42422e NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/278171 Thu, 26 Oct 2023 18:25:09 -0000 https://status.shc.kanagawa.jp/incident/278171#3543fdaabd5aef3def756fd74c578f379e06edf92b2154246adae7fcc0b5aed3 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/277494 Wed, 25 Oct 2023 21:32:43 -0000 https://status.shc.kanagawa.jp/incident/277494#e917c1f20cfc311b76c5042731dbebdea8faed56bf9c2cf3227f37bc97ea0a85 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/277494 Wed, 25 Oct 2023 21:32:17 -0000 https://status.shc.kanagawa.jp/incident/277494#a3fd26fa526d1556e81991c259907a4ba6312f842de11927880e10114cd6765f NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/277494 Wed, 25 Oct 2023 18:35:17 -0000 https://status.shc.kanagawa.jp/incident/277494#4437a2495b5690e53c1332a61faeb1f94a6c0dd95086f000b1c9a5e356b5c57a NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/277494 Wed, 25 Oct 2023 18:35:04 -0000 https://status.shc.kanagawa.jp/incident/277494#cfebd0374cd187f797a67c60d80da41a8171977676401d5daf9a7c68bac4d37a NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/277094 Tue, 24 Oct 2023 22:56:14 -0000 https://status.shc.kanagawa.jp/incident/277094#a92ab41fed3324e6b49dda0ff82139d58496d6b74e04c5cf8e12fb35d8f00af4 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/277094 Tue, 24 Oct 2023 22:55:46 -0000 https://status.shc.kanagawa.jp/incident/277094#b271a2acd69bed553c001a617e42349c2d359f4b24f8ea26b58c2e0124b2c497 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/277094 Tue, 24 Oct 2023 21:18:33 -0000 https://status.shc.kanagawa.jp/incident/277094#7232e650773e17fc86ced1cf360515e26203bcde8b33edf3c365c937a5413da6 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/277094 Tue, 24 Oct 2023 21:18:09 -0000 https://status.shc.kanagawa.jp/incident/277094#ecefcb5581283d0ec577c436434cbf96feb8bc4897120dcad539eebd301fdc3b NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/277094 Tue, 24 Oct 2023 18:33:05 -0000 https://status.shc.kanagawa.jp/incident/277094#b498dd70ca403612e68425ee0e17ea0c14b4bf075fd83cb6644f3873d561ec8f NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/277094 Tue, 24 Oct 2023 18:31:58 -0000 https://status.shc.kanagawa.jp/incident/277094#8a289cd5d35441211a65f225f68b7cee60a2366ea56375444fd912a2e79c8f95 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/277094 Tue, 24 Oct 2023 15:56:11 -0000 https://status.shc.kanagawa.jp/incident/277094#54ced916baed3e3bf0a03beaef39e6797e786e7bc68ece4f053d8534414d8957 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/277094 Tue, 24 Oct 2023 15:55:20 -0000 https://status.shc.kanagawa.jp/incident/277094#8c182779a912255344bc6e853798735958efaa561c08603718b8ad5775765d6e Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/276272 Mon, 23 Oct 2023 18:36:27 -0000 https://status.shc.kanagawa.jp/incident/276272#8c1a6abf1c432afd75fe28cbe613624a92f432f97368f47c8f36aae35f2ee391 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/276272 Mon, 23 Oct 2023 18:35:58 -0000 https://status.shc.kanagawa.jp/incident/276272#9a0df4e47e907cf2c9e2a67d02a29205430dc8cd50fcb78cdbc7edcb1eff840c NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/276158 Sun, 22 Oct 2023 21:14:13 -0000 https://status.shc.kanagawa.jp/incident/276158#f2cff5019e60f9cdbb06252af21e672898865017c5a2fbb80ddf01e5b4874795 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/276158 Sun, 22 Oct 2023 21:11:06 -0000 https://status.shc.kanagawa.jp/incident/276158#e4dfa700e5d2b3879e63b96e741c037b69522d839ebec787295863b312de68eb NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/276158 Sun, 22 Oct 2023 18:11:11 -0000 https://status.shc.kanagawa.jp/incident/276158#f8519a24ab127d3acb01c04a544b69d0bcb1a02558974df58143cdee997eb702 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/276158 Sun, 22 Oct 2023 18:10:38 -0000 https://status.shc.kanagawa.jp/incident/276158#ef0b6e9fd017c92b76b1db6ab83bc3ca9e04cbc38e226478733e5d0abbba02ea NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/275718 Sat, 21 Oct 2023 20:08:20 -0000 https://status.shc.kanagawa.jp/incident/275718#d83e04493e3cb5bcdc608d3e0b991c28243452fe38b6f85b789840ee83285a54 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/275718 Sat, 21 Oct 2023 20:04:29 -0000 https://status.shc.kanagawa.jp/incident/275718#57dbe78bf8c358df0592f588a72aeab33accd8f00ed49fdf96728ba6c427cb77 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/275718 Sat, 21 Oct 2023 18:08:25 -0000 https://status.shc.kanagawa.jp/incident/275718#b290749827bdd0fb396fc84e6ad51d9bec34a857e705b1a034d6b787905dc58c NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/275718 Sat, 21 Oct 2023 18:07:19 -0000 https://status.shc.kanagawa.jp/incident/275718#daea944818ee93f4c6b215c62f2cf612c73a9b5884dc6457429e02ed338896d4 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/275718 Sat, 21 Oct 2023 08:10:41 -0000 https://status.shc.kanagawa.jp/incident/275718#07f1c03813dacebd95eec428e6dbb7786c7fb409282bfc43ea6cbeefccc179e8 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/275718 Sat, 21 Oct 2023 08:09:49 -0000 https://status.shc.kanagawa.jp/incident/275718#d66e0f0db38a7ac1f1f9d14bf4f6c262392dee27c8df766728263c0c97171b48 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/275134 Fri, 20 Oct 2023 20:58:42 -0000 https://status.shc.kanagawa.jp/incident/275134#11b09bfc59f4d465260b34c1396f5a1d9cd1a2fefcdbb5f677eacd11b11253c5 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/275134 Fri, 20 Oct 2023 20:54:39 -0000 https://status.shc.kanagawa.jp/incident/275134#1295d39dc68050cea9570b778232e7c5bbca267952b457ca36da9b2fce7b772d NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/275134 Fri, 20 Oct 2023 18:13:58 -0000 https://status.shc.kanagawa.jp/incident/275134#e196785207d7a3934ca422fc244790e2448169c1ca68615b06bfeaf75dc4c1f7 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/275134 Fri, 20 Oct 2023 18:13:20 -0000 https://status.shc.kanagawa.jp/incident/275134#559005023dd37f6dff00a5b434384ba0229431065b47c1e23e55ed3974145e92 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/274654 Thu, 19 Oct 2023 21:36:23 -0000 https://status.shc.kanagawa.jp/incident/274654#a07a6896061f509f07c82ff7cc844077486120032a56104e46b896ea04e2c907 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/274654 Thu, 19 Oct 2023 21:35:49 -0000 https://status.shc.kanagawa.jp/incident/274654#4404389198d320f6d74f5f6d91f259e5e3d4d8a18f80c0b9539981fbcaacb63e NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/274654 Thu, 19 Oct 2023 18:30:24 -0000 https://status.shc.kanagawa.jp/incident/274654#6e8ed3a35d65387242d08ee7123bc90fdd31c818d4dc31d1f0e116c13dcda1e6 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/274654 Thu, 19 Oct 2023 18:29:37 -0000 https://status.shc.kanagawa.jp/incident/274654#019177c09f9789afc645ea703e93b6d3a1aef10622238aeda46e885f4460e4cd NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/274654 Thu, 19 Oct 2023 00:40:10 -0000 https://status.shc.kanagawa.jp/incident/274654#a5b1d688592b81d36a1a129ec08bae1fd6ca7d0016c8aac7232d208b12fa6ff3 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/274654 Thu, 19 Oct 2023 00:32:05 -0000 https://status.shc.kanagawa.jp/incident/274654#d310d3d065488b310c1a015cae8c825676a49cb290b6d462d1d0a2478d832a49 NextCloud (cloud.shc.kanagawa.jp) and labo.wovs.tk Streaming Replication Monitor recovered. https://status.shc.kanagawa.jp/incident/274654 Thu, 19 Oct 2023 00:21:06 -0000 https://status.shc.kanagawa.jp/incident/274654#3d691c5adcb4d73886761cabb21e9db228a5a275de11ca521f2b6de40fdb9226 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/274654 Thu, 19 Oct 2023 00:20:06 -0000 https://status.shc.kanagawa.jp/incident/274654#6f147a27bf9499529fce283f36f21c84d0df1af2573e36e0638a0e5d029be501 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/274189 Wed, 18 Oct 2023 20:01:53 -0000 https://status.shc.kanagawa.jp/incident/274189#8c6cfe5dc03086ce6ac6edb2308998b2c5f71a4a9439b99b1eba6eaddc2b3e1c NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/274189 Wed, 18 Oct 2023 19:57:45 -0000 https://status.shc.kanagawa.jp/incident/274189#61bed1c2481b38ea97456c59e378051649b159f4086233e47e511acc52dca2d8 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/274189 Wed, 18 Oct 2023 17:15:40 -0000 https://status.shc.kanagawa.jp/incident/274189#92bc78c598e28d41bea522fb68b8d9d267f76639f9152eaa4e7fb9aa65fd4d29 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/274189 Wed, 18 Oct 2023 17:15:02 -0000 https://status.shc.kanagawa.jp/incident/274189#a30d01f4c58e66a0f77b5b775e79ac58ef7c190fb3c9dd01e8f69b98f0e82854 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/274189 Wed, 18 Oct 2023 11:30:16 -0000 https://status.shc.kanagawa.jp/incident/274189#0abd985af405a480460b4d01246b5d9328343e1d613f88566d21d59548d5b06e Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/274189 Wed, 18 Oct 2023 11:20:29 -0000 https://status.shc.kanagawa.jp/incident/274189#9f0c8680ef136e9f08364cc16a7a0903b4115a6c64c6ad42e5a18ff1e9afb6e6 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/274189 Wed, 18 Oct 2023 08:53:45 -0000 https://status.shc.kanagawa.jp/incident/274189#32bbdb3f6ea9fa26f5703cb4cb80c06444e427ebcb6ea29b04aa04ccd52e9e6c Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/274189 Wed, 18 Oct 2023 08:53:11 -0000 https://status.shc.kanagawa.jp/incident/274189#072ca0f42989e31782cb02a1c356baa2f7871df5ec93b835b1956c863f968bf5 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/274189 Wed, 18 Oct 2023 04:47:30 -0000 https://status.shc.kanagawa.jp/incident/274189#b641135ffe9a09f4b4302ed314eb56199ad19b4a6c5bc8f413533e622d9b7b86 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/274189 Wed, 18 Oct 2023 04:41:36 -0000 https://status.shc.kanagawa.jp/incident/274189#f8e1ab8372a906c5cd960c28612369e6f366081b4a3c20e737901f3357235b4c Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/273566 Tue, 17 Oct 2023 23:38:51 -0000 https://status.shc.kanagawa.jp/incident/273566#553df3e3d1ebeb7827cb8bda9717f5104bf87ec7d4b5d1b6051bdc5d822132bb demo.shc.kanagawa.jp Initialize recovered. https://status.shc.kanagawa.jp/incident/273566 Tue, 17 Oct 2023 21:06:31 -0000 https://status.shc.kanagawa.jp/incident/273566#8fa9e73699e9345b4c9b2241b93615d2d0e308c7c162ed238fa12593509c2f5d NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/273566 Tue, 17 Oct 2023 21:05:49 -0000 https://status.shc.kanagawa.jp/incident/273566#305851786c02c4e0a2fb99316f36fa5db48ea24638e7ede5bc33edf94411453b NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/273566 Tue, 17 Oct 2023 21:05:27 -0000 https://status.shc.kanagawa.jp/incident/273566#ecb96f5d97ec1fab064f8f4fa8b677bd9cd1b5897f69f469d87f87aef9b1c795 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/273566 Tue, 17 Oct 2023 21:04:36 -0000 https://status.shc.kanagawa.jp/incident/273566#08f82926621db9ea3591540a37527304e4566b6196c82bed053c9793986bc882 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/273566 Tue, 17 Oct 2023 20:05:45 -0000 https://status.shc.kanagawa.jp/incident/273566#2eacb79a4f4ced9a2eba51c8512e068b970db7bcdbac013d70a8d5e1d823784d Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/273566 Tue, 17 Oct 2023 20:01:36 -0000 https://status.shc.kanagawa.jp/incident/273566#1face098c7f9fd4e16d4e3da25262b80abb0271abeb94885fd935671c9ea7d97 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/273566 Tue, 17 Oct 2023 18:12:27 -0000 https://status.shc.kanagawa.jp/incident/273566#d8dd037ab97aa72223df35ba655479fbdc877904f93714ab3b1ecd1543e7d1e0 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/273566 Tue, 17 Oct 2023 18:12:09 -0000 https://status.shc.kanagawa.jp/incident/273566#a9bd9ea537355b0416b747303c92731ab44188f3ef81e3a207e3fae5cd45fe77 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/273566 Tue, 17 Oct 2023 16:28:48 -0000 https://status.shc.kanagawa.jp/incident/273566#352d9e459ce813d1763c4ae4ea5f3fa3eb348da118f2b05658ecde45017e22f9 demo.shc.kanagawa.jp Initialize went down. https://status.shc.kanagawa.jp/incident/273566 Mon, 16 Oct 2023 20:52:31 -0000 https://status.shc.kanagawa.jp/incident/273566#f95820d5f797d3fa9e7498cb11ad76d85313417eaca585847270eb83458658a4 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/273566 Mon, 16 Oct 2023 20:48:13 -0000 https://status.shc.kanagawa.jp/incident/273566#4dbdd20e727bf3c8efd3c32d002ecbd7a97f499c6289ef3c8904fc3e39cd6e1f NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/273566 Mon, 16 Oct 2023 18:10:14 -0000 https://status.shc.kanagawa.jp/incident/273566#0d861c5c2744645a8c150d2bd4dcee4f02f827fd1f2153c6da36aef9fce433b7 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/273566 Mon, 16 Oct 2023 18:10:03 -0000 https://status.shc.kanagawa.jp/incident/273566#9ace42ba6dc29f4583ea0452f008405ffe73769d15c195183341a531ee71d654 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/273021 Sun, 15 Oct 2023 21:08:03 -0000 https://status.shc.kanagawa.jp/incident/273021#a9e9ceb5ef32f30201837e3ac17bc6ca7a4b46f937cdfd54c7c5794f44672194 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/273021 Sun, 15 Oct 2023 21:07:42 -0000 https://status.shc.kanagawa.jp/incident/273021#4a5cc783f8ead04fc34a54d1a66d8f880f58d0cf4bbffc8f60e3f23ac94cbbc4 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/273021 Sun, 15 Oct 2023 18:37:56 -0000 https://status.shc.kanagawa.jp/incident/273021#8e13bf88bd6c7078ca8aed09fb1b22cd02921601d1035f454036a0fc2880947a NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/273021 Sun, 15 Oct 2023 18:33:54 -0000 https://status.shc.kanagawa.jp/incident/273021#f7fa28788351e4b2c706c987643e5ce01f75a7f8fc930d5b4786d359c0b0711a NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/272767 Sat, 14 Oct 2023 21:09:53 -0000 https://status.shc.kanagawa.jp/incident/272767#7539f5dfc4332af3425f7bf9ef3c411e4ef92c15a21bf536c108124b2374e4fd NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/272767 Sat, 14 Oct 2023 21:05:43 -0000 https://status.shc.kanagawa.jp/incident/272767#3f964b254c988f2e59577217834023bb5a20affa767ab640253e19aa070a8655 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/272767 Sat, 14 Oct 2023 18:36:52 -0000 https://status.shc.kanagawa.jp/incident/272767#69d88ba456f78a89594949906c5e570f21e1dbab2ee12cc0a970acf1db4fe6b7 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/272767 Sat, 14 Oct 2023 18:33:32 -0000 https://status.shc.kanagawa.jp/incident/272767#19e333ec90b0fd81d9aa6ef762c0ac15dfd5f95bfa23e84fb72984f719040276 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/272076 Fri, 13 Oct 2023 19:31:35 -0000 https://status.shc.kanagawa.jp/incident/272076#2517241dfe438ff0979058020ea992055b14f7c3293b4b1cac06368974a444a8 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/272076 Fri, 13 Oct 2023 19:24:57 -0000 https://status.shc.kanagawa.jp/incident/272076#4221ad9a0c95810d5b78430cb98d4b2d4a5acb9a6126a8ede68ee1fbba84e711 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/272076 Fri, 13 Oct 2023 18:14:29 -0000 https://status.shc.kanagawa.jp/incident/272076#44dce6c57371d707b53415bcddd1f53a99bda664ef7b23bdc3e0b2e8a6d4101f NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/272076 Fri, 13 Oct 2023 18:13:39 -0000 https://status.shc.kanagawa.jp/incident/272076#5a7735e6860094ec692f3c6474b4840d1de242a8032e135239f50984870cd7df NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/272076 Fri, 13 Oct 2023 04:45:06 -0000 https://status.shc.kanagawa.jp/incident/272076#d8cf992b092ccdec1619702b3b8991ffd203ea830c2391e46bcdb0523cb64008 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/272076 Fri, 13 Oct 2023 04:44:51 -0000 https://status.shc.kanagawa.jp/incident/272076#167e3bbf7fb9a8c20b0f00affad1ce4e0039f5bba2c466c44eff679db5e5453b Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/272076 Fri, 13 Oct 2023 01:09:11 -0000 https://status.shc.kanagawa.jp/incident/272076#789d36449f2ef39bd2e2ffa92112274399e2b4d403135e99ec0f577a12c8d3d0 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/272076 Fri, 13 Oct 2023 01:08:23 -0000 https://status.shc.kanagawa.jp/incident/272076#c17f0b91752731e4c9fceadf8f85d9c7b6e0ed91554a552b4332eae85f608aaf Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/271499 Thu, 12 Oct 2023 23:17:47 -0000 https://status.shc.kanagawa.jp/incident/271499#3fa60b260e5978dbdfe8d998e97699b9070f4cf06b072b33f9df6a9726e75569 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/271499 Thu, 12 Oct 2023 23:11:14 -0000 https://status.shc.kanagawa.jp/incident/271499#64f84b5b29993002dd13dc000e4ea50721ed8246f789b102b8722478fb0cbadd Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/271499 Thu, 12 Oct 2023 21:09:55 -0000 https://status.shc.kanagawa.jp/incident/271499#937bfbfe92463ccdb8ae61fbbdf6e6c236f9e7252cacdbc0c69e3fcba09dccc7 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/271499 Thu, 12 Oct 2023 21:09:39 -0000 https://status.shc.kanagawa.jp/incident/271499#1250eafa8316551bf8d8dc83474a9a0d5cb00557d78c84ead53605e3dc70b45e NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/271499 Thu, 12 Oct 2023 18:33:45 -0000 https://status.shc.kanagawa.jp/incident/271499#c64a146773bab6dca61dde1a5d5fdb67d512cee4a0c5b49bc95fcde2d071ef60 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/271499 Thu, 12 Oct 2023 18:32:53 -0000 https://status.shc.kanagawa.jp/incident/271499#a44480174e6bd0b4b46691f8a5cd717efaf6e01edc3b414b18e27fc3239b3941 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/271499 Thu, 12 Oct 2023 18:17:43 -0000 https://status.shc.kanagawa.jp/incident/271499#f0b4a7a62ccc1fbe729cb075fb10fb0d8b5518cf9824e3e030171572a01f2dbb Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/271499 Thu, 12 Oct 2023 18:17:03 -0000 https://status.shc.kanagawa.jp/incident/271499#89080a106083a74826c852aea160bc2d7e88c440ce9c94c1a0d44686767909b6 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/271499 Thu, 12 Oct 2023 17:35:40 -0000 https://status.shc.kanagawa.jp/incident/271499#50c789bdab8a788e6cb16a738542abdfb15a24e39d34b4d98317307e9dd7f166 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/271499 Thu, 12 Oct 2023 17:31:59 -0000 https://status.shc.kanagawa.jp/incident/271499#3b426ea28aa1f8f5d20b42185a962a692761c2e8d97af271e559748f3191bf3e Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/271499 Thu, 12 Oct 2023 14:14:29 -0000 https://status.shc.kanagawa.jp/incident/271499#d628b29a1c567bd5ab4cbf51fb513f6df482fa88ad70e53275ea8daa4059cb57 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/271499 Thu, 12 Oct 2023 14:13:57 -0000 https://status.shc.kanagawa.jp/incident/271499#45435473da077813edf524b9fb063eef72e91a34d45eef6408aaade538a2e342 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/271499 Thu, 12 Oct 2023 05:48:19 -0000 https://status.shc.kanagawa.jp/incident/271499#8d554a491a8826ee8e8d5dda8b3b966b17e6b05b596b4b73b54d7a533c69ac3f Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/271499 Thu, 12 Oct 2023 05:44:41 -0000 https://status.shc.kanagawa.jp/incident/271499#6aa3c7b4f0f7321333fb33be3b8048f25512c89a8778aa16500f86e9a96760b8 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/271499 Thu, 12 Oct 2023 03:06:10 -0000 https://status.shc.kanagawa.jp/incident/271499#e7706bc6f28bcb979a3903f6cf21edc685f30ffd709f0fbad14832d6d3616e6d Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/271499 Thu, 12 Oct 2023 03:02:59 -0000 https://status.shc.kanagawa.jp/incident/271499#7ee4ce1bbaff0afcb2d49114563c8c7d2ea8b5c3913f5ffc1a6fb8f2ff6cecbe Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/271008 Wed, 11 Oct 2023 23:51:02 -0000 https://status.shc.kanagawa.jp/incident/271008#bbe14ec23ee62211718f0e1114d23f4f95bd31791ad75c61399f94fedd4e7efb Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/271008 Wed, 11 Oct 2023 23:50:25 -0000 https://status.shc.kanagawa.jp/incident/271008#61ec389de181935e82956aa75012fbed39c5f003592c484e75431219c4cbc41e Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/271008 Wed, 11 Oct 2023 20:08:28 -0000 https://status.shc.kanagawa.jp/incident/271008#6141d546b2a63f675bcf3fb5883c208ce86962e84399c87b350ef0f23404651f NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/271008 Wed, 11 Oct 2023 20:04:30 -0000 https://status.shc.kanagawa.jp/incident/271008#0428cc560ed879204b4e41cdc3dc202b3394f6c296c2b91bfbebb08d7565b4df NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/271008 Wed, 11 Oct 2023 18:34:16 -0000 https://status.shc.kanagawa.jp/incident/271008#a98a69e3999ef5438ee17fe14934642b3c5f569c5f2615cd30e7e1aba059af9e Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/271008 Wed, 11 Oct 2023 18:33:38 -0000 https://status.shc.kanagawa.jp/incident/271008#eb42f5f90e3420fb9d65556f33c06e3e9fa4ccdd40e8f94476815fe342a3e834 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/271008 Wed, 11 Oct 2023 15:40:10 -0000 https://status.shc.kanagawa.jp/incident/271008#028698924e715713319820f383ce2f250a631246389e6491c5ffb351d849eb3e Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/271008 Wed, 11 Oct 2023 15:39:29 -0000 https://status.shc.kanagawa.jp/incident/271008#e204a524b0b19d5d91d0e199e77eecd48531991289b1ec03c6ebdb656230db73 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/271008 Wed, 11 Oct 2023 14:40:49 -0000 https://status.shc.kanagawa.jp/incident/271008#09c373c41e86c89b42bf82ea3f62105d7be248915cb4c8015cdd2c6471cded3a NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/271008 Wed, 11 Oct 2023 14:37:50 -0000 https://status.shc.kanagawa.jp/incident/271008#fd3d7524fe0ff975fb4db4dfe89e50ecd06fb1f802025aec565d7a1589f25bef NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/271008 Wed, 11 Oct 2023 03:41:24 -0000 https://status.shc.kanagawa.jp/incident/271008#26d4516bb9fee3fec2ea3bb754460839dcea7265942d7a04e5e4dc7526b34777 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/271008 Wed, 11 Oct 2023 03:40:40 -0000 https://status.shc.kanagawa.jp/incident/271008#de82187f500b38b0bddf2dacf04df452f6c26363c2dbf2236314eed86844f5ed Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/271008 Wed, 11 Oct 2023 00:59:10 -0000 https://status.shc.kanagawa.jp/incident/271008#bbd7e7140de32f336c36b6a5c28da414d3a31e9e5ea5c8d71cf97d52f644d1c4 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/271008 Wed, 11 Oct 2023 00:56:07 -0000 https://status.shc.kanagawa.jp/incident/271008#77d76d32f6f0b6e3e59520b5316abe1945112b2034e0d4c0c71a0fcefb6d73ab Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/270478 Tue, 10 Oct 2023 20:18:22 -0000 https://status.shc.kanagawa.jp/incident/270478#28e6c0ce4389119170f4a85e0ea81f4e22a8696ad13675e4abbd0953dc4b612e NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/270478 Tue, 10 Oct 2023 20:14:52 -0000 https://status.shc.kanagawa.jp/incident/270478#0bbfb7be7bba669419c8cc12856f02d98e1bab4623aaff8ddede7613364ae962 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/270478 Tue, 10 Oct 2023 10:15:48 -0000 https://status.shc.kanagawa.jp/incident/270478#3936377e4464cadcbc4da478f94707dd2da12373dcb8e6a43c2823ea4ba7b85a Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/270478 Tue, 10 Oct 2023 10:15:05 -0000 https://status.shc.kanagawa.jp/incident/270478#aa2130b3592346b6713b0519301fd1ee9c86297d0b1628b23d648f6720d486cf Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/270478 Tue, 10 Oct 2023 08:36:22 -0000 https://status.shc.kanagawa.jp/incident/270478#09fc8aed3c643febf6f45632104e466cc2c9a71f7bacfdbe0ea124eb7e0bde30 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/270478 Tue, 10 Oct 2023 08:35:31 -0000 https://status.shc.kanagawa.jp/incident/270478#ad28f200ae8237bbd2bd141625d0261260d5a9034edc0b9c199a3f6bfeb57f12 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/270478 Tue, 10 Oct 2023 02:17:40 -0000 https://status.shc.kanagawa.jp/incident/270478#35ec6a10ff2c964a2430ecd1918672e58c59ada517dd591a5e5add19c5014c10 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/270478 Tue, 10 Oct 2023 02:17:07 -0000 https://status.shc.kanagawa.jp/incident/270478#edef070de9e83274d4d4081e48c7a11246a2c82a19da7c59d7ed21071c2f062f Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/270478 Tue, 10 Oct 2023 00:59:29 -0000 https://status.shc.kanagawa.jp/incident/270478#69a4e9d253e42aef99179070251692fd7cb37f5c4c22911d24f0d14c6a2d5620 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/270478 Tue, 10 Oct 2023 00:52:53 -0000 https://status.shc.kanagawa.jp/incident/270478#6fc07c88e6574932f589694bef673ca95f8b72a8ecf1925cae1f2f52b4aca5f1 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/270205 Mon, 09 Oct 2023 20:02:11 -0000 https://status.shc.kanagawa.jp/incident/270205#56497cc31acfb28604f70d938dcbd64dd486cdd70bc3605a4e8d2cbec558dfe8 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/270205 Mon, 09 Oct 2023 19:58:00 -0000 https://status.shc.kanagawa.jp/incident/270205#a31ba218e69b60d6fa5565f4b4df2aa7b4492532120c6f53ef772e8b4e4386c8 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/270205 Mon, 09 Oct 2023 19:57:08 -0000 https://status.shc.kanagawa.jp/incident/270205#f4814f72a1d6f214313b847806f3d179a4429c1f916ffb8b468d098296da2ad6 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/270205 Mon, 09 Oct 2023 19:54:02 -0000 https://status.shc.kanagawa.jp/incident/270205#79fd8c7d3e307a2f4a2087beb456548273d564774b1f1668a2db7c898f930de4 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/270205 Mon, 09 Oct 2023 18:09:05 -0000 https://status.shc.kanagawa.jp/incident/270205#b7b807e35f757bbd52d977da220c291b62891a21b93c49a23b25c7010c7e8ce8 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/270205 Mon, 09 Oct 2023 18:08:15 -0000 https://status.shc.kanagawa.jp/incident/270205#7d9e8d1be0e386240a67eb61eaaab0b670b6aee9cb8b323a996002f422ea5e87 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/270205 Mon, 09 Oct 2023 10:52:24 -0000 https://status.shc.kanagawa.jp/incident/270205#1f8992171687b23a77d22971129c340a64442d24ab37396356f381f3711708d6 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/270205 Mon, 09 Oct 2023 10:51:38 -0000 https://status.shc.kanagawa.jp/incident/270205#8d3feee88835f8f2663eff8a134977045e81da283c043a7b35bf2efb7fb6387b Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/269761 Sun, 08 Oct 2023 20:43:23 -0000 https://status.shc.kanagawa.jp/incident/269761#c54beb1f16ded56fd0efa87e540ca553a042a9099ca478fe78ad6a8e44c2015a NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/269761 Sun, 08 Oct 2023 20:42:31 -0000 https://status.shc.kanagawa.jp/incident/269761#c3762eb349b2bd81b1a975193358186c9361b031856bda2f24499dca470fa1e4 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/269761 Sun, 08 Oct 2023 13:56:54 -0000 https://status.shc.kanagawa.jp/incident/269761#325d737186d8cefcab59e3b4adca79c9c2b42cc47f81c0aa5d082ddc9c3a5748 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/269761 Sun, 08 Oct 2023 13:50:55 -0000 https://status.shc.kanagawa.jp/incident/269761#f2d17353f40e0f69a5ca5701516d069fb765917aaf315d45be42a21d9eeb3652 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/269761 Sun, 08 Oct 2023 12:36:05 -0000 https://status.shc.kanagawa.jp/incident/269761#7ef3d3ef68b2b26c3f02abf8176b5855f45bd929696942f9993f8b5915fac11f Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/269761 Sun, 08 Oct 2023 12:32:16 -0000 https://status.shc.kanagawa.jp/incident/269761#f7c790f5806312178b20e29332a56990fcf3b45c5c633ec214a37fa7f270ffbf Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/269761 Sun, 08 Oct 2023 11:50:56 -0000 https://status.shc.kanagawa.jp/incident/269761#0a01e4f76de22f31393ecf1bec537b3d7c225adf7ddc4a2369aa21ec0ae1bda4 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/269761 Sun, 08 Oct 2023 11:44:11 -0000 https://status.shc.kanagawa.jp/incident/269761#9db741e8944d6bf3d17e4b28f1884a0d7d9b15181f6c14c6fe9f8c2db675c116 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/269761 Sun, 08 Oct 2023 09:36:12 -0000 https://status.shc.kanagawa.jp/incident/269761#60ac13793948298a2212ffea87fce3400be473bc583ffeb43f7269d2e2c5e911 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/269761 Sun, 08 Oct 2023 09:35:14 -0000 https://status.shc.kanagawa.jp/incident/269761#13fe853697c97b104bcbd95e564585a752f6c113f6f8d41bcb20849489af9123 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/269761 Sun, 08 Oct 2023 04:32:28 -0000 https://status.shc.kanagawa.jp/incident/269761#4148f7905cd783a757a034b9ce04889e5954be7c105d79d027ca1199524e1b55 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/269761 Sun, 08 Oct 2023 04:32:00 -0000 https://status.shc.kanagawa.jp/incident/269761#c84ef8cb6cb29f3d881f03a6ccc3cfdb17fb7fb7b94cd98e03dd42e3710da6bf Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/269392 Sat, 07 Oct 2023 21:21:02 -0000 https://status.shc.kanagawa.jp/incident/269392#553a2e84eb4e8ef11e2c33990af1245550357a5978c8626a89e7f96608e2cdc7 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/269392 Sat, 07 Oct 2023 21:16:57 -0000 https://status.shc.kanagawa.jp/incident/269392#8009fdf2662e337a7a3f2b73ac01c719f7e8f4814c28bcdc4776c21d3a678eb5 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/269392 Sat, 07 Oct 2023 18:38:57 -0000 https://status.shc.kanagawa.jp/incident/269392#7365f6f18509a66d682bc8260697b386f2719ad424c92f338445408101df0cc8 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/269392 Sat, 07 Oct 2023 18:37:50 -0000 https://status.shc.kanagawa.jp/incident/269392#3a225233cd79728c904f1b535d0bb01a045431b1168136aee2328a0d5070901d NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/269392 Sat, 07 Oct 2023 16:58:49 -0000 https://status.shc.kanagawa.jp/incident/269392#10a9ee3edcac48aeeb438ad945f899aba4067bbe6d0efe99dac6649623c7e1b5 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/269392 Sat, 07 Oct 2023 16:58:04 -0000 https://status.shc.kanagawa.jp/incident/269392#1b01c3804c7a59745617050a536df0b3c6de13ae3d7ce874d5d1f113326f1b18 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/269392 Sat, 07 Oct 2023 03:19:14 -0000 https://status.shc.kanagawa.jp/incident/269392#8c09a34f06e68121c5189cd44282c938cb131fbe3e17b7ce672b6c828838bcca Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/269392 Sat, 07 Oct 2023 03:18:36 -0000 https://status.shc.kanagawa.jp/incident/269392#323a906e6ef6f7e2d3dc9abca8d810a9530cdc0528f0cd73007ddd34a0dbe0cb Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/269249 Fri, 06 Oct 2023 21:16:45 -0000 https://status.shc.kanagawa.jp/incident/269249#7f919b3dbe6487e9a5337f1ddd59ea4a535daf931462498e8270bd2c9a447262 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/269249 Fri, 06 Oct 2023 21:16:26 -0000 https://status.shc.kanagawa.jp/incident/269249#15fb160aad04c2abb8098b5acfc8f6b225708f2f0a1544cb917efb66a5b39021 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/269249 Fri, 06 Oct 2023 18:34:29 -0000 https://status.shc.kanagawa.jp/incident/269249#9311dab0c5cd198665a82f794f80501735cdbed88fb4a754efaa9d89c55d90da NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/269249 Fri, 06 Oct 2023 18:31:24 -0000 https://status.shc.kanagawa.jp/incident/269249#51e0ecd446468952961626cb284adecd9eae7099cc12fc6c1b08c352a498e534 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/268700 Thu, 05 Oct 2023 18:10:33 -0000 https://status.shc.kanagawa.jp/incident/268700#833b3169df8b4391be28423e50055a90d2ef1d8963834747510311f518721d0c NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/268700 Thu, 05 Oct 2023 18:09:22 -0000 https://status.shc.kanagawa.jp/incident/268700#b820a80e1b93bcf3bfcfc0f2365804a0cad91f9e68b9c25eb1e48ded31e298dd NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/267007 Wed, 04 Oct 2023 20:11:05 -0000 https://status.shc.kanagawa.jp/incident/267007#2fc733d09fdf7d66776aa6d88ef259706e0a31a51b12097009e7c46e23e19002 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/267007 Wed, 04 Oct 2023 20:07:07 -0000 https://status.shc.kanagawa.jp/incident/267007#3d6d2d82937105fea07d321e09dff8ccd313d7fcdad10aa38b97643d1cbf25a9 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/267007 Wed, 04 Oct 2023 10:40:04 -0000 https://status.shc.kanagawa.jp/incident/267007#6b3da0cacefca1a5ab1671e964743e588107c2c7395d985e24896297684d4616 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/267007 Mon, 02 Oct 2023 18:14:23 -0000 https://status.shc.kanagawa.jp/incident/267007#4af858389700385c6581442f5188e3e08839dea3329928bf2051192fb299e0cf NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/266668 Sun, 01 Oct 2023 20:33:05 -0000 https://status.shc.kanagawa.jp/incident/266668#a3005bbfda4fa382d6d88da9a271e6168630238a1fce77e5d07420e779b6bf65 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/266668 Sun, 01 Oct 2023 20:28:52 -0000 https://status.shc.kanagawa.jp/incident/266668#70e1c6c8faecb99a7548d77d5e0ac7ade6654d0a5b567d080fa11f09e01eeea0 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/266379 Sat, 30 Sep 2023 20:57:58 -0000 https://status.shc.kanagawa.jp/incident/266379#2368ac0605775aa661416c7bef6e7ccfbd0c76c5206a00ac69dd0aeb17abf3a2 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/266379 Sat, 30 Sep 2023 20:54:46 -0000 https://status.shc.kanagawa.jp/incident/266379#b22fd43b137917150d369f6ca5ad5f2cc8e14ad3b2ed0a91dd11435c9879ae9a NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/266379 Sat, 30 Sep 2023 18:39:53 -0000 https://status.shc.kanagawa.jp/incident/266379#da1afb10ba0149618dabc5f00fa24025ac6e00d89d0913d4224eeedd71008045 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/266379 Sat, 30 Sep 2023 18:35:42 -0000 https://status.shc.kanagawa.jp/incident/266379#3e3e3be211ff82e48256b188001704ae260e49d5700e96efc027b4b4441302f7 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/266115 Fri, 29 Sep 2023 21:14:06 -0000 https://status.shc.kanagawa.jp/incident/266115#a199963edf93f50e72d3175a86b699c0b240f83eaa3bb988a4319f28ff226f7d NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/266115 Fri, 29 Sep 2023 21:09:51 -0000 https://status.shc.kanagawa.jp/incident/266115#0a3e3baf5d547fc64ab6016e7cf2990384349aca05a2208e1a9a87b9f697c213 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/266115 Fri, 29 Sep 2023 18:28:39 -0000 https://status.shc.kanagawa.jp/incident/266115#ce13c03054367d36196eb365ad05734789827f48a31c9752febd2cf97bf524f7 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/266115 Fri, 29 Sep 2023 18:28:19 -0000 https://status.shc.kanagawa.jp/incident/266115#621b9d372f0d7c7624fa2dc00f8a30775bf3634fca046926ff935a43e3b77d0c NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/265542 Thu, 28 Sep 2023 21:03:15 -0000 https://status.shc.kanagawa.jp/incident/265542#cb9e5944c861339f1941ec47c28b5ce145338065bb03bb05b9abb0fcd737887b NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/265542 Thu, 28 Sep 2023 20:59:09 -0000 https://status.shc.kanagawa.jp/incident/265542#1b514fd5cac48ed6d604c61ce31f775f81f07078a85d74583e8339d65c422785 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/265542 Thu, 28 Sep 2023 18:09:20 -0000 https://status.shc.kanagawa.jp/incident/265542#d9a39c26ec9744c88d8a0fda9540a9d2bef50f0e88e2a10bc5bfbf40a5e22443 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/265542 Thu, 28 Sep 2023 18:08:10 -0000 https://status.shc.kanagawa.jp/incident/265542#18de4313944eeaf10fa5836b26d5a9329ff50aa11c8e6ad55944e05007a6963d NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/264801 Wed, 27 Sep 2023 21:25:45 -0000 https://status.shc.kanagawa.jp/incident/264801#d9efc1fbf991d71cb373fbc0eab4c33be27b21be9ed21f9d2731045c3871b204 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/264801 Wed, 27 Sep 2023 21:24:45 -0000 https://status.shc.kanagawa.jp/incident/264801#5d312f608e09e375b492dec4d90b7ed1111a36e58570fcd6903764b381e48ab7 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/264389 Tue, 26 Sep 2023 20:24:51 -0000 https://status.shc.kanagawa.jp/incident/264389#7a78c6c649c85fd171b28e9843a37858880b921189712e228ad8f3e4461dd240 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/264389 Tue, 26 Sep 2023 20:21:43 -0000 https://status.shc.kanagawa.jp/incident/264389#edd838209ca106f81227c1d8cc3530adeb48aba8d0a852021975bd74aae51692 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/263899 Mon, 25 Sep 2023 22:27:52 -0000 https://status.shc.kanagawa.jp/incident/263899#60b6538bac9500de4c134f51c5039a23cca1f5f15638e5f2abb414d662f6dc54 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/263899 Mon, 25 Sep 2023 22:26:37 -0000 https://status.shc.kanagawa.jp/incident/263899#b05dd2c3dc1b7b1330adc89ee5efbf5c63c6a36cd0a8ad973d722c2ea7dad3a3 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/263899 Mon, 25 Sep 2023 20:16:30 -0000 https://status.shc.kanagawa.jp/incident/263899#9bdb22f96c696102a49f2a0243450f344f5557586129d9244eed4441f219ab8d MongoDB Repliction went down and NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/263899 Mon, 25 Sep 2023 20:12:14 -0000 https://status.shc.kanagawa.jp/incident/263899#1d66a131a8c030fd16ea83bd14eec134bdda039e9ae95873baff416e825d9a52 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/263406 Sun, 24 Sep 2023 21:33:22 -0000 https://status.shc.kanagawa.jp/incident/263406#96bc8a2696a7fa875f425b9d3b7f11409091bc3512ab59022cdc3fcb395a5176 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/263406 Sun, 24 Sep 2023 21:32:24 -0000 https://status.shc.kanagawa.jp/incident/263406#46fa1b4d6a42f9346ddd7af4e6df476ca9eef4fe0ddfb156fa5806b1ef9fd635 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/263406 Sun, 24 Sep 2023 18:27:16 -0000 https://status.shc.kanagawa.jp/incident/263406#bdf550df5e0a34d3c8172e0377f77dc1194142eeb7778cd6aa49e2b619041051 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/263406 Sun, 24 Sep 2023 18:27:04 -0000 https://status.shc.kanagawa.jp/incident/263406#44f85dc3a345f8ff5cce8218e8b7195a001ceabe5493e2d139063f9a2f3eef82 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/263406 Sat, 23 Sep 2023 21:08:45 -0000 https://status.shc.kanagawa.jp/incident/263406#54a4777574183b497b7db2e4aa6d372ecd3c351c4f0cb700dbe69ac047bc45fc NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/263406 Sat, 23 Sep 2023 21:05:37 -0000 https://status.shc.kanagawa.jp/incident/263406#6719a88532fe3b16896b890fcebf02498b381c66bdb86f7dce0a0e4e87622dd5 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/263406 Sat, 23 Sep 2023 18:35:41 -0000 https://status.shc.kanagawa.jp/incident/263406#6c2b930fd1dc0fed7c58aefc31ed8ea205c113cd545b30a6743d050bd1535764 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/263406 Sat, 23 Sep 2023 18:34:58 -0000 https://status.shc.kanagawa.jp/incident/263406#bd313ec1978b4c156da8bf253a168b4ed03240e9b05b2f89187c2a738cbda1de NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/262750 Fri, 22 Sep 2023 21:29:33 -0000 https://status.shc.kanagawa.jp/incident/262750#45e7ee2fe1a635038f716885e8979e78374a208608072e4b294ada66107c9cc1 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/262750 Fri, 22 Sep 2023 21:25:30 -0000 https://status.shc.kanagawa.jp/incident/262750#0ee728ceb42432f0242fa35538eddd870ae2b630901d437d8a9090e7536a1751 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/262750 Fri, 22 Sep 2023 18:11:37 -0000 https://status.shc.kanagawa.jp/incident/262750#109d420e330e7c21604294723dcc63bcec9c729e55b5add752fe8431453ab9f2 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/262750 Fri, 22 Sep 2023 18:10:41 -0000 https://status.shc.kanagawa.jp/incident/262750#ef46363a2f7c8e350ce59a9d95479d5535b8284f94131b605eb743b1de4122ad NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/262123 Thu, 21 Sep 2023 21:20:16 -0000 https://status.shc.kanagawa.jp/incident/262123#655e2825fefb1b21f8119c54a872eb8a3b882593cfdb8b9777345865ebeec533 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/262123 Thu, 21 Sep 2023 21:14:54 -0000 https://status.shc.kanagawa.jp/incident/262123#2b89a41019540174f1ed4f00ae8c63b57be3723b977de94bc6be9ee3d7c221f8 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/261557 Wed, 20 Sep 2023 21:03:54 -0000 https://status.shc.kanagawa.jp/incident/261557#3451263cfce31be8ec9704f151028c74b41f94929012350ed513cda98c1e208a NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/261557 Wed, 20 Sep 2023 21:02:49 -0000 https://status.shc.kanagawa.jp/incident/261557#fdb8c9645b361b0f86ae293ae5a3b934ace1f9e34aed23e29cecf677454bbd71 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/261557 Wed, 20 Sep 2023 18:10:24 -0000 https://status.shc.kanagawa.jp/incident/261557#b2276c60e8260cc6e3c428853cc0eff80fc3fe06b22f1cbca6e4e56604584851 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/261557 Wed, 20 Sep 2023 18:09:32 -0000 https://status.shc.kanagawa.jp/incident/261557#102fd84382617feeec54a09e1e6ad641ce6f87188d84f94fcc77dc65649bb3f3 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/261172 Tue, 19 Sep 2023 21:01:06 -0000 https://status.shc.kanagawa.jp/incident/261172#5235d0d54f9b1c78b4bc45d57f953e004c8ccf6c3ec89fd1e3a3222eadda8400 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/261172 Tue, 19 Sep 2023 20:57:13 -0000 https://status.shc.kanagawa.jp/incident/261172#ab60b115d945bf135f5c0d3e4c169b858203b4307e261e72d684b9b317318c0a NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/261172 Tue, 19 Sep 2023 18:36:56 -0000 https://status.shc.kanagawa.jp/incident/261172#dcb867dad88a9f07d2834d2dffeee67ffa274382259e99cb76218eb7f2823954 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/261172 Tue, 19 Sep 2023 18:33:24 -0000 https://status.shc.kanagawa.jp/incident/261172#1d59f68461d1c4f0d0e7546b7b3f4894672ebb52e487f52c294df3629d3a692c NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/260670 Mon, 18 Sep 2023 20:58:08 -0000 https://status.shc.kanagawa.jp/incident/260670#3949eb57965eceb3636abb5eac52381a114fa717f2ddaa6c4adf93f2d29166a8 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/260670 Mon, 18 Sep 2023 20:54:03 -0000 https://status.shc.kanagawa.jp/incident/260670#6711d0d4eda697166c504577a448760411c18e92d0aab9648af02a4b016fe9f7 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/260670 Mon, 18 Sep 2023 18:33:56 -0000 https://status.shc.kanagawa.jp/incident/260670#c79e472500845256c1ca471f42f631e070bb4c18ea52cf788dc9fd04ee7647c2 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/260670 Mon, 18 Sep 2023 18:30:17 -0000 https://status.shc.kanagawa.jp/incident/260670#a2c26bdbc6ca7be08992ab56f59e024487f3e45cc622096329d6a30af5169adc NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/260302 Sun, 17 Sep 2023 20:55:00 -0000 https://status.shc.kanagawa.jp/incident/260302#3b158ba21ed49e0ca9bba023d4fe538af048b38c80e7e1f19213a84a25eeb7a0 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/260302 Sun, 17 Sep 2023 20:50:56 -0000 https://status.shc.kanagawa.jp/incident/260302#6c1627e6c0372c11f626eb3d04e6ebcad70076961a0136b78ea276e4f3df7e07 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/260302 Sun, 17 Sep 2023 18:39:55 -0000 https://status.shc.kanagawa.jp/incident/260302#dd909ceb1fe438c4383578c79526b1c72095ec4ec51760de111f0c1f4c9c1848 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/260302 Sun, 17 Sep 2023 18:35:47 -0000 https://status.shc.kanagawa.jp/incident/260302#3e8c14a5a4b85f4f87e5de00a6a803aab272e684d91af323fd729cb449da4b54 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/259914 Sat, 16 Sep 2023 21:43:59 -0000 https://status.shc.kanagawa.jp/incident/259914#f0984bef44ba1f815091f42d4af02cf8c0ce3cbbc48d6888303169fca6b43418 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/259914 Sat, 16 Sep 2023 21:36:43 -0000 https://status.shc.kanagawa.jp/incident/259914#9ec5c18ed2dc74683e5e33f86fe45551a1f0011210b0c4b5d4c8d80ec05e0f5c NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/259914 Sat, 16 Sep 2023 18:28:51 -0000 https://status.shc.kanagawa.jp/incident/259914#486172f372a50d84933b00dfb048a91f3e9409bf15d3b27d0a9aaac619b10167 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/259914 Sat, 16 Sep 2023 18:24:28 -0000 https://status.shc.kanagawa.jp/incident/259914#6258169c71f1ac77a627a75b7697b8463bcfc077f0ce53c62a099d76b0badefa NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/259413 Fri, 15 Sep 2023 21:14:25 -0000 https://status.shc.kanagawa.jp/incident/259413#77808d1a7d7ba4127cecd4477fcf27ae84e85435e68058112aa4dc0e161bdc7f NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/259413 Fri, 15 Sep 2023 21:10:24 -0000 https://status.shc.kanagawa.jp/incident/259413#9b249238934816f25da8a734af337fdfdf6488d2f368413389b36723b34be869 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/259413 Fri, 15 Sep 2023 18:38:18 -0000 https://status.shc.kanagawa.jp/incident/259413#12fa9c2e51420187b1db457f3e02195565354d3c2b22f52d3025112987a8ece2 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/259413 Fri, 15 Sep 2023 18:34:21 -0000 https://status.shc.kanagawa.jp/incident/259413#0de6af70cfe6f6285964328dbf7911531f7193254c2505eff6043b7b1a95944f NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/259145 Thu, 14 Sep 2023 21:11:10 -0000 https://status.shc.kanagawa.jp/incident/259145#b8e7f63633f2935517d7e9f1fce5f930ae15228e4c3ad7cc71ca93ec0e3358b0 Mastodon Object Storage went down and NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/259145 Thu, 14 Sep 2023 21:07:52 -0000 https://status.shc.kanagawa.jp/incident/259145#a8d250dbd887d867c94d2da0af24806e280f6c577e7abde1aca5094d6b918c8e NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/259145 Thu, 14 Sep 2023 18:26:01 -0000 https://status.shc.kanagawa.jp/incident/259145#026e7a7ee62252f1ca02bfac7b5223fb150932b7f1f0943fa80fa1a2735ad69f NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/259145 Thu, 14 Sep 2023 18:22:30 -0000 https://status.shc.kanagawa.jp/incident/259145#013aab2869592dbe819f1595f5522df1defd63d9260bfe63a8faf37a70aa8107 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/258576 Wed, 13 Sep 2023 21:18:25 -0000 https://status.shc.kanagawa.jp/incident/258576#bedf7e9157452300e1803383fd04166e5641b2526961319a2d7abe2f9d9411c2 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/258576 Wed, 13 Sep 2023 21:10:53 -0000 https://status.shc.kanagawa.jp/incident/258576#c51d082afcae6216c7d3b556084300c5c0081868d0bc410681e5ee26b1f356e8 NextCloud (cloud.shc.kanagawa.jp) went down and Mastodon Object Storage recovered. https://status.shc.kanagawa.jp/incident/258576 Wed, 13 Sep 2023 18:36:01 -0000 https://status.shc.kanagawa.jp/incident/258576#7b87b259d90f5ee4e75cb5eb69dcad7ade16b446de3e621cc491c37f757df869 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/258576 Wed, 13 Sep 2023 18:32:07 -0000 https://status.shc.kanagawa.jp/incident/258576#4b76f42e0cd3c820c24e9604a0dc4d5d99c8a7941a65f2268bc60eacd0d90959 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/258051 Tue, 12 Sep 2023 21:22:37 -0000 https://status.shc.kanagawa.jp/incident/258051#00c1a04de9b6e8ff475f0999f9d6ef3c6a9dec2c29845a1958eb017b06081ade NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/258051 Tue, 12 Sep 2023 21:18:41 -0000 https://status.shc.kanagawa.jp/incident/258051#56e0978bb1aa3b1a5559889ba08c4cb398e0d4f2ea4925cde1348bb340860451 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/258051 Tue, 12 Sep 2023 18:15:39 -0000 https://status.shc.kanagawa.jp/incident/258051#8f2a5c5a1c056f76623ee3cde687a161275bc005c4bdcb2d235713697926e384 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/258051 Tue, 12 Sep 2023 18:11:40 -0000 https://status.shc.kanagawa.jp/incident/258051#12ebb9752057a5f3452d54129b766b64b05d789cfc2f9f4d1f243d587fc3f844 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/257704 Mon, 11 Sep 2023 21:53:19 -0000 https://status.shc.kanagawa.jp/incident/257704#1c2c9e94656563b6a8026278a0bc9f5249e486edd2655ec47ce06e4ef849dfac Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/257704 Mon, 11 Sep 2023 21:53:19 -0000 https://status.shc.kanagawa.jp/incident/257704#1c2c9e94656563b6a8026278a0bc9f5249e486edd2655ec47ce06e4ef849dfac Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/257704 Mon, 11 Sep 2023 21:52:29 -0000 https://status.shc.kanagawa.jp/incident/257704#959a8db719db4c3a7bef1418608ac4278957fa682fa56b472efe5db03924dc67 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/257704 Mon, 11 Sep 2023 21:52:29 -0000 https://status.shc.kanagawa.jp/incident/257704#959a8db719db4c3a7bef1418608ac4278957fa682fa56b472efe5db03924dc67 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/257324 Sun, 10 Sep 2023 12:46:42 -0000 https://status.shc.kanagawa.jp/incident/257324#2e019dd8c27cbd424fc84194b1fb8f58487907b560355f8ab858215ff1ce4ed7 demo.shc.kanagawa.jp Initialize recovered. https://status.shc.kanagawa.jp/incident/257324 Sun, 10 Sep 2023 06:30:05 -0000 https://status.shc.kanagawa.jp/incident/257324#cb4b1fc0c2762bb7fbe83f60dc569e89368611d04c89c80601c4dea759db9149 demo.shc.kanagawa.jp Initialize went down. https://status.shc.kanagawa.jp/incident/250884 Sat, 26 Aug 2023 09:06:28 -0000 https://status.shc.kanagawa.jp/incident/250884#dcfc98abb6cd3bc928f1c7fa7b0c6c5c2795da6f90fc27982d1cf265080f59dd NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/250884 Sat, 26 Aug 2023 09:06:09 -0000 https://status.shc.kanagawa.jp/incident/250884#248b50ddb8fbc8540a311a77fa40f03129b203783f798de3d38c2a8daab9a151 ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/250884 Sat, 26 Aug 2023 09:05:53 -0000 https://status.shc.kanagawa.jp/incident/250884#6f24f1a8fc9e288a4f6381ea6fb4d873f5d16b0761ce0dd725651f8bc5782218 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/250884 Sat, 26 Aug 2023 09:05:28 -0000 https://status.shc.kanagawa.jp/incident/250884#7b9f6793eb011f333dc20a20c5bf776d5adefcdf8eec132df3a65af1733a9be8 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/250884 Sat, 26 Aug 2023 09:05:11 -0000 https://status.shc.kanagawa.jp/incident/250884#971cbd8ccdc5b020efc4d29dcc1b25ec1858cf491c7a78652b7481e48c3442e6 Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/250884 Sat, 26 Aug 2023 09:04:29 -0000 https://status.shc.kanagawa.jp/incident/250884#e19c721e51651dcd691cda7af21e8e968d897dff93f899cb3f665e3f2bd06213 ownCloud (share.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/250884 Sat, 26 Aug 2023 09:03:14 -0000 https://status.shc.kanagawa.jp/incident/250884#2dd87820fbf9b543166b535982a1f9cd0816394d50eb144a76b56872c264a9d2 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/250884 Sat, 26 Aug 2023 09:02:45 -0000 https://status.shc.kanagawa.jp/incident/250884#3bd087dc68f3a6c6d8aae834dc735e86a8ded72c948774a5acf1130e4a5ee2ed Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/250884 Sat, 26 Aug 2023 09:02:06 -0000 https://status.shc.kanagawa.jp/incident/250884#501b524c7eed959baa5d4cae29982b4ef827ec0f08e4f62b5e44b44fb188460b Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/250884 Sat, 26 Aug 2023 09:02:06 -0000 https://status.shc.kanagawa.jp/incident/250884#501b524c7eed959baa5d4cae29982b4ef827ec0f08e4f62b5e44b44fb188460b Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/247869 Sat, 19 Aug 2023 18:13:40 -0000 https://status.shc.kanagawa.jp/incident/247869#8e82d9b8f746ee549cab4ce9cf7e06d7b419194be918f13aff0d8e9448721c02 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/247869 Sat, 19 Aug 2023 18:12:42 -0000 https://status.shc.kanagawa.jp/incident/247869#e61a442decd200b597d00fbf0588e5f7acc3fadf49a0bd6cb811bb8726979049 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/247869 Sat, 19 Aug 2023 11:16:13 -0000 https://status.shc.kanagawa.jp/incident/247869#505e2d905caa186fe0dfc8d25ee77b57ea23ffd55a844881c60922e3d3d79d1a Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/247869 Sat, 19 Aug 2023 11:15:07 -0000 https://status.shc.kanagawa.jp/incident/247869#cf662129db408cb9120fa6c0af9bb61964434b5d1196001726e39c014e5ec0a8 Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/246895 Thu, 17 Aug 2023 21:44:05 -0000 https://status.shc.kanagawa.jp/incident/246895#4b7133fcad3a2fbade655dba06bee13bfdde627c2623735cfa21cfe1c93ba459 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/246895 Thu, 17 Aug 2023 21:43:06 -0000 https://status.shc.kanagawa.jp/incident/246895#3092938a130302390b67b68afbf6a6c0289599245d9aa26627a15b0811f968a1 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/246895 Thu, 17 Aug 2023 20:58:55 -0000 https://status.shc.kanagawa.jp/incident/246895#3d13a2cabeea9341bab4b969c1e51ce5b71d2aef072e5e3b9f4dc08acd439853 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/246895 Thu, 17 Aug 2023 20:57:56 -0000 https://status.shc.kanagawa.jp/incident/246895#6bd9bdd7ce0bb13b4cbca018b8e7c3e5886e53c6994af2a43e5ca084cc6ea610 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/246895 Thu, 17 Aug 2023 06:25:21 -0000 https://status.shc.kanagawa.jp/incident/246895#903e8e61fee748bc666a653b162006a657b2969bfb193857264811ab04cef813 Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/246895 Thu, 17 Aug 2023 06:24:14 -0000 https://status.shc.kanagawa.jp/incident/246895#7fc4e309b6366b3310f009a5b70d4b749e287bd77c09fd329f7a9f5bd0a11871 Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/246895 Thu, 17 Aug 2023 06:23:27 -0000 https://status.shc.kanagawa.jp/incident/246895#90571b2e3a14221f79045d09bf46987a14c26e76d167b792e8d65d8cd818d24c ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/246895 Thu, 17 Aug 2023 06:23:10 -0000 https://status.shc.kanagawa.jp/incident/246895#e73c538a408be5b97546dbccd4c5993de2f34dd2af2dcec207eafec2bc1717d4 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/246895 Thu, 17 Aug 2023 05:59:36 -0000 https://status.shc.kanagawa.jp/incident/246895#ee25c5dc6c01dac0f26a15f8dfb8f60c87666656efde5d6eb3f3fad5c95a582e NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/246895 Thu, 17 Aug 2023 05:58:32 -0000 https://status.shc.kanagawa.jp/incident/246895#d990f6ed83eaa17fe2264edec3f85c22bf001a8651b6f3db1930d908baacc57a Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/246895 Thu, 17 Aug 2023 05:56:03 -0000 https://status.shc.kanagawa.jp/incident/246895#62bf56afca220ab9102cbd9358ccab340a1d3319b431c27a21200c7561bc3f46 NextCloud Maintenance recovered. https://status.shc.kanagawa.jp/incident/246895 Thu, 17 Aug 2023 05:52:24 -0000 https://status.shc.kanagawa.jp/incident/246895#b098304417c8cdc406c4171665310843459ad32a85b986c866820b2e98eab55d Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/246895 Thu, 17 Aug 2023 05:46:14 -0000 https://status.shc.kanagawa.jp/incident/246895#9639e2fe920af3fa8a7885a56d55f927bb6b3dfc0522b0181da64ad190fe5072 Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/246895 Thu, 17 Aug 2023 05:45:30 -0000 https://status.shc.kanagawa.jp/incident/246895#c88bc3455c0da256324778f3852c582da55f5b444b5b849cbb2d7bb89c246528 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/246895 Thu, 17 Aug 2023 05:44:27 -0000 https://status.shc.kanagawa.jp/incident/246895#a1126955fd07b6c2e8c6a336268bc9054cdbd1e20c49631b58fdcec6eb460ee7 ownCloud (share.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/246895 Thu, 17 Aug 2023 05:42:53 -0000 https://status.shc.kanagawa.jp/incident/246895#c1552019dcc39e27dd203a9f4fce5caf40a6ef072a2f3b7c1a5bd0a4ec74aba4 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/246895 Thu, 17 Aug 2023 05:36:23 -0000 https://status.shc.kanagawa.jp/incident/246895#03410ef60c441982b331beb328daf8d9838aacc314db789800342a227374fce3 NextCloud Maintenance went down. https://status.shc.kanagawa.jp/incident/246895 Thu, 17 Aug 2023 05:28:31 -0000 https://status.shc.kanagawa.jp/incident/246895#408ca128310d538e2babe40403321309b76cd2d9d3099d90703d7d090f268aba Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/246895 Thu, 17 Aug 2023 05:27:26 -0000 https://status.shc.kanagawa.jp/incident/246895#22ba832868741e9d78d18d4c3af707128f9ac7035120105a76fc9bb9fd4f414b Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/246895 Thu, 17 Aug 2023 05:23:10 -0000 https://status.shc.kanagawa.jp/incident/246895#b4827c805bcb15370069831db95ea7a64d10467815885fcc6f2a33fc9c5c18a0 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/245887 Tue, 15 Aug 2023 18:45:29 -0000 https://status.shc.kanagawa.jp/incident/245887#8ed3a93fbbaedf9d6385d21e8fabc423f8e652eaf668286e094bbfce53242b48 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/245887 Tue, 15 Aug 2023 18:44:24 -0000 https://status.shc.kanagawa.jp/incident/245887#ff03491cb1b224056dcf428bdc531746fc1b2163ac652d18a32b3197aa012fb0 NextCloud (cloud.shc.kanagawa.jp) went down and Mastodon Object Storage recovered. https://status.shc.kanagawa.jp/incident/245107 Mon, 14 Aug 2023 18:13:55 -0000 https://status.shc.kanagawa.jp/incident/245107#288896775195d5d0eebeac6365cee1ab3a2c4dcf1d3c7d5409b1c143bfc801ff Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/245107 Mon, 14 Aug 2023 18:12:39 -0000 https://status.shc.kanagawa.jp/incident/245107#43800e9e00d05d6d560f6e72b629a27ce3139f5e684b0f5e9bb654b6f831018e Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/245107 Sun, 13 Aug 2023 18:55:38 -0000 https://status.shc.kanagawa.jp/incident/245107#de5f668e9303794c6f257fdf3e5cd6df393a32ac46b542d7f104842ca79b99ab Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/245107 Sun, 13 Aug 2023 18:54:34 -0000 https://status.shc.kanagawa.jp/incident/245107#c5fed389d2df69b20101ef43abbd5e96c60f253201f74c9229810f3b177fd1f3 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/243754 Fri, 11 Aug 2023 18:12:51 -0000 https://status.shc.kanagawa.jp/incident/243754#3c814035e790af0a420618a647ab7fdae0c51276aa90bfd1cfe5a6f6b1cbd677 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/243754 Fri, 11 Aug 2023 18:11:50 -0000 https://status.shc.kanagawa.jp/incident/243754#976e35057ab7540ce36baac2d2e1fa3d0456f7348e122904b852a37bad20d514 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/243754 Thu, 10 Aug 2023 18:47:56 -0000 https://status.shc.kanagawa.jp/incident/243754#84b50b9b98ca3de7b3dbadb8be0301ea6a0e0944602991e5c2b77daedf97fa5c NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/243754 Thu, 10 Aug 2023 18:46:53 -0000 https://status.shc.kanagawa.jp/incident/243754#b29b867d3a62c57ac254ffc3e5c0b120e9e0a22e7d3c8dbbb274ed474e7cfd1c NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/241886 Wed, 09 Aug 2023 10:33:58 -0000 https://status.shc.kanagawa.jp/incident/241886#09d5568513281120d30c01fb72f1178dc8f3a98e8e54625f3289fb725ad2190a Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/241886 Wed, 09 Aug 2023 00:05:29 -0000 https://status.shc.kanagawa.jp/incident/241886#22d760bd4e6fa681c87d12e38c113e562259bc213b79ec2f26fc5103dd3caa95 Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/241886 Tue, 08 Aug 2023 18:37:44 -0000 https://status.shc.kanagawa.jp/incident/241886#fdb9e0eca38df0a4915c2d7a075cd27d072251306d31e253fb373032f69d9e26 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/241886 Tue, 08 Aug 2023 18:36:33 -0000 https://status.shc.kanagawa.jp/incident/241886#efc5249deafa5c1d9659538bbb6dfcebe38dddd41265bdd1050c934225fd8398 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/241886 Mon, 07 Aug 2023 18:47:35 -0000 https://status.shc.kanagawa.jp/incident/241886#074c8059b5c92d2c08f5dba4de6bd04cef16f8431a5b1145d5d67cb2fe2464c6 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/241886 Mon, 07 Aug 2023 18:46:38 -0000 https://status.shc.kanagawa.jp/incident/241886#00748165eca879c4da5bfeb949fe7122d130d6edfd9f1d37144bcbea7767d7f1 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/241886 Mon, 07 Aug 2023 11:35:26 -0000 https://status.shc.kanagawa.jp/incident/241886#4662ff3ea03e92ca5566ca842918cfea935802fe3e14080859bde043557960d6 Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/241886 Mon, 07 Aug 2023 11:22:32 -0000 https://status.shc.kanagawa.jp/incident/241886#4c207b0d793981762d4f6285a45662b9a0cd3c927c7838a4f6d0dd1231ecb573 Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/241585 Sat, 05 Aug 2023 18:16:58 -0000 https://status.shc.kanagawa.jp/incident/241585#9fde2c32afa4c8025f6817ab940849bb6927aaf9b8a1509a7bf2d235164d69fb NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/241585 Sat, 05 Aug 2023 18:15:59 -0000 https://status.shc.kanagawa.jp/incident/241585#bcd994646e3ddd8ed533cede44cb167c11729ad4e2c12e785645d037102f4c38 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/241307 Fri, 04 Aug 2023 07:44:58 -0000 https://status.shc.kanagawa.jp/incident/241307#ce4e0a6f87abf52a84720fcaa66d67f465bc17f569a57b7a593b9f09feb90650 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/241307 Fri, 04 Aug 2023 07:44:03 -0000 https://status.shc.kanagawa.jp/incident/241307#1cc6a9d72bb062c0a67e20210ef2f3d0ef4fd572cf189bd93c094789baf74c09 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/239906 Tue, 01 Aug 2023 09:21:42 -0000 https://status.shc.kanagawa.jp/incident/239906#9571f15550ada7d51493ff7b50ff213f1a1f7f9279fc97f160123ba259396be4 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/239906 Tue, 01 Aug 2023 07:51:35 -0000 https://status.shc.kanagawa.jp/incident/239906#076b546154bade58a4583de3e43f97b017c863228c64e665f5c8052f5b3a947c Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/239906 Tue, 01 Aug 2023 03:00:37 -0000 https://status.shc.kanagawa.jp/incident/239906#f301961d233d766129ae7ea845e716bd02360e5f772e081e36320ffb9193c1d9 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/239906 Tue, 01 Aug 2023 02:42:38 -0000 https://status.shc.kanagawa.jp/incident/239906#99e2936fd7d68456f4c4c33341dee1dd3b27b9d3672db79c612274e18936886f Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/239760 Mon, 31 Jul 2023 18:27:14 -0000 https://status.shc.kanagawa.jp/incident/239760#fe5be49ec0ea3901dc989f82c6d69d8c55b89eeb97ce74c0ffa3ff78edc7204b Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/239760 Mon, 31 Jul 2023 18:25:56 -0000 https://status.shc.kanagawa.jp/incident/239760#32ec8155f6adb6dd23b60cf6c87e061634b25d6007dd2bc3e8d1fb37b7343581 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/238853 Sun, 30 Jul 2023 18:19:34 -0000 https://status.shc.kanagawa.jp/incident/238853#8f78ba00bd3675fbe7129bf1e660ada58381b73d16e5a378b48836d5027741c6 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/238853 Sun, 30 Jul 2023 18:18:31 -0000 https://status.shc.kanagawa.jp/incident/238853#b21c51e561282e7321ca1efa6ca16f227c6c1ac9ef236675c531a07e5acce43e Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/238853 Sun, 30 Jul 2023 03:01:19 -0000 https://status.shc.kanagawa.jp/incident/238853#4007f6923ac627ab8d6aaa80953f6493bee707c8df99d969286cc8564e3f86b8 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/238853 Sat, 29 Jul 2023 18:52:36 -0000 https://status.shc.kanagawa.jp/incident/238853#9637ab4a1e4e75b53dced118d94a826f5581a7f404c7101abe4ce2fbe75a1943 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/238853 Sat, 29 Jul 2023 18:51:31 -0000 https://status.shc.kanagawa.jp/incident/238853#5fb85f58c75abf4f878afa0ae58222dde14c36d0f7da06fbbb5938f1df5d7333 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/238853 Sat, 29 Jul 2023 06:21:55 -0000 https://status.shc.kanagawa.jp/incident/238853#99ebe4c200de958ad7050643a0c5be6f6ad1db3c685bce9aa1329c8967d23ac5 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/238853 Sat, 29 Jul 2023 05:48:57 -0000 https://status.shc.kanagawa.jp/incident/238853#54641dd9ce176b3064ea2635fd73915d6669346f701043c841a2863e325d04bc Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/238853 Sat, 29 Jul 2023 05:43:00 -0000 https://status.shc.kanagawa.jp/incident/238853#1d3e291644ab5b6c2e5e4f6b69bb815b95ca0b7d46b7ef793085eea6eaf31dfe Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/238853 Sat, 29 Jul 2023 05:19:13 -0000 https://status.shc.kanagawa.jp/incident/238853#0a96a54c561df8cf93f5b7949b3891f8952503c72f11cb12e910a7dfad1afef5 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/238853 Sat, 29 Jul 2023 05:18:56 -0000 https://status.shc.kanagawa.jp/incident/238853#f155aeaea8a35f8b464a5bafe64965252e3d8075aa61eeb45dc8bd66fb01fa48 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/237937 Thu, 27 Jul 2023 18:23:07 -0000 https://status.shc.kanagawa.jp/incident/237937#c1e265056e21804b306f7f7e8edf21ab2867795feeac1efa1b2f59f4210bcc50 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/237937 Thu, 27 Jul 2023 18:21:56 -0000 https://status.shc.kanagawa.jp/incident/237937#d883e8df6ed68d65af5af16c79889978d16c7068a67729ecd6aced9485021ecb Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/237937 Thu, 27 Jul 2023 08:47:01 -0000 https://status.shc.kanagawa.jp/incident/237937#35511f0ea3e83567c1673a808a48f8a3d8f995fd8d633ff845496dc2eafa1a74 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/237937 Thu, 27 Jul 2023 04:40:53 -0000 https://status.shc.kanagawa.jp/incident/237937#7ca8683fcc96ce6bba3e0cc798636734e82b2ec05451d5cb57217b9058f9f435 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/237456 Wed, 26 Jul 2023 10:45:50 -0000 https://status.shc.kanagawa.jp/incident/237456#a6afe3d9af19c69722bf3610ae9b58ecfffbfa2475165345820ee914b824b5cf Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/237456 Wed, 26 Jul 2023 08:09:42 -0000 https://status.shc.kanagawa.jp/incident/237456#140fc13993032d0578a7ed5db0f1ea500b7ef205d4785409d6a11487098b2545 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/237456 Wed, 26 Jul 2023 07:57:44 -0000 https://status.shc.kanagawa.jp/incident/237456#7ef18c7fefeaa186339ccf43017f946ebe7a4d93216294eb3def662798fabfd8 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/237456 Wed, 26 Jul 2023 07:51:31 -0000 https://status.shc.kanagawa.jp/incident/237456#7e7b1dfa7fbec66e65dbf665e31ecc790505ef48c66df81f0a7bc817872dff3c Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/237456 Wed, 26 Jul 2023 07:33:43 -0000 https://status.shc.kanagawa.jp/incident/237456#2f0d3b00f8d8ab45cfbd0854d3efabc6d0d48b2a894cf1678d944475ee97b291 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/237456 Wed, 26 Jul 2023 07:30:39 -0000 https://status.shc.kanagawa.jp/incident/237456#8581107e21a239e055002bd3b5b117c43f6c14e48590ec7258dcfccf2543e046 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/237456 Wed, 26 Jul 2023 03:54:41 -0000 https://status.shc.kanagawa.jp/incident/237456#42929a6c273f56318ed6d0289106bbc93a8b8c64dc6022bc8f5c63d825ca35ec Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/237456 Wed, 26 Jul 2023 03:09:29 -0000 https://status.shc.kanagawa.jp/incident/237456#79f540370e4fb310c3ba7fd1784a611d860366486b11963a87097955381a6929 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/237283 Tue, 25 Jul 2023 18:30:34 -0000 https://status.shc.kanagawa.jp/incident/237283#467aa9ff2cf715596e5b7aa4e0917fe5c3e920a2bc942734bc18012085fb29e4 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/237283 Tue, 25 Jul 2023 18:29:31 -0000 https://status.shc.kanagawa.jp/incident/237283#e281a47e9f49858b82d596c5c6a991a58f8b03d07cdfed892c47d2328f2b757f NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/236438 Sun, 23 Jul 2023 18:34:33 -0000 https://status.shc.kanagawa.jp/incident/236438#bbb246958a3a9e6d092710f5e42240a95ff8654d81e85219c4c6c815cb3cade9 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/236438 Sun, 23 Jul 2023 18:33:37 -0000 https://status.shc.kanagawa.jp/incident/236438#5a31dd9e96509950568863d9c7fb89b279f75ef6d5287b27356d07c59819c82a NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/235895 Sat, 22 Jul 2023 18:23:39 -0000 https://status.shc.kanagawa.jp/incident/235895#180926c3920768a5fc82d1c1825c8704a94782d658546619bb2784629b5320bc Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/235895 Sat, 22 Jul 2023 18:21:52 -0000 https://status.shc.kanagawa.jp/incident/235895#b138966f6460f1c8301982aad4817be6cac2a9a8c65be30a142f0bc9709dea60 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/235895 Sat, 22 Jul 2023 11:02:26 -0000 https://status.shc.kanagawa.jp/incident/235895#e0c4597d940c8b97437ef2ff7101e6e4ce97034176f7cd544a2be462a04ee089 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/235895 Sat, 22 Jul 2023 11:01:27 -0000 https://status.shc.kanagawa.jp/incident/235895#c62e6b0eb92c43b57065cfa155da90b654e23307c2aea82f74e2d4b76e6d0ec5 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/235895 Sat, 22 Jul 2023 10:47:23 -0000 https://status.shc.kanagawa.jp/incident/235895#f1bfcefff339460755bcea8d27e5af671813b9b607a88aa0b914569827b140f7 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/235895 Sat, 22 Jul 2023 10:46:15 -0000 https://status.shc.kanagawa.jp/incident/235895#0c3728a8f98f916ae1d8a8a9d3883ff8c4e3bf44fdf3633e45eeb1524225007d Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/235895 Sat, 22 Jul 2023 10:32:04 -0000 https://status.shc.kanagawa.jp/incident/235895#cd1e1c240fc202b1bf891aff3efb9e2906567bcefdfc941e1d7a0d6b5888d4db Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/235895 Sat, 22 Jul 2023 10:31:04 -0000 https://status.shc.kanagawa.jp/incident/235895#8be0f02c84faf85672113222f875e7c44c5016d0166227e95ef4a3ed595e145b Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/235895 Sat, 22 Jul 2023 00:55:50 -0000 https://status.shc.kanagawa.jp/incident/235895#0e7bdc6734f77bc693c4d0c591dc1ded3ab19f154f842ec12e3c54775dd94746 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/235895 Sat, 22 Jul 2023 00:55:50 -0000 https://status.shc.kanagawa.jp/incident/235895#0e7bdc6734f77bc693c4d0c591dc1ded3ab19f154f842ec12e3c54775dd94746 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/235895 Sat, 22 Jul 2023 00:52:51 -0000 https://status.shc.kanagawa.jp/incident/235895#c50874fc435f76406abd784df22ba10a316792e8ab93201b96960df5c3a63169 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/235895 Sat, 22 Jul 2023 00:49:54 -0000 https://status.shc.kanagawa.jp/incident/235895#05033787ef8cd3ae20328bcb42da85bde8fbdd1eda8be838986992fdef9747c0 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/235573 Fri, 21 Jul 2023 18:55:48 -0000 https://status.shc.kanagawa.jp/incident/235573#fe5f87efe0e8a3b7dc81f26acf04c12c41ed991450fd017cf7df297c6efe8bab NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/235573 Fri, 21 Jul 2023 18:54:50 -0000 https://status.shc.kanagawa.jp/incident/235573#8aecf563ead8d6792ce9f27cb1ed0cf453a9d7edda6a6e744660924fc33f0191 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/235573 Fri, 21 Jul 2023 11:52:25 -0000 https://status.shc.kanagawa.jp/incident/235573#d9492fa098619b9fc750e7afaf3be03c134b760ed69152d1708a0fd5874773ac Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/235573 Fri, 21 Jul 2023 11:49:28 -0000 https://status.shc.kanagawa.jp/incident/235573#1abcdd821c501650431a0d8110274503e9e44a1f6dacb7c53eb5e0bf6c9d82c6 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/235573 Fri, 21 Jul 2023 11:37:15 -0000 https://status.shc.kanagawa.jp/incident/235573#f21f59f26678dc043d2a797fa9299fb89b53cce337985afdca8deffb542b6547 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/235573 Fri, 21 Jul 2023 11:37:15 -0000 https://status.shc.kanagawa.jp/incident/235573#f21f59f26678dc043d2a797fa9299fb89b53cce337985afdca8deffb542b6547 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/235573 Fri, 21 Jul 2023 11:28:59 -0000 https://status.shc.kanagawa.jp/incident/235573#a099d5c4cc48a0fd136c61fd7a21554be5a20f81d0c92750163997f22bac5d26 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/235573 Fri, 21 Jul 2023 11:28:18 -0000 https://status.shc.kanagawa.jp/incident/235573#f044afe6008a4491a689027213a0fb4d889ac4945db53a9d15960dbe1c0d0396 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/235573 Fri, 21 Jul 2023 11:27:33 -0000 https://status.shc.kanagawa.jp/incident/235573#8c4c320269eb3620024250a30c2da82b215e1307a2dbd9bc2f4052e66c126eac Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/235573 Fri, 21 Jul 2023 11:19:32 -0000 https://status.shc.kanagawa.jp/incident/235573#f0cd13c5e091942454c094e6d692d8a7c11fe0c122522c19e02f15a2fbcadde1 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/235573 Fri, 21 Jul 2023 09:46:28 -0000 https://status.shc.kanagawa.jp/incident/235573#dfc26f365faf3e05e9ec6d3735fbf4df596748226f70bfecc7c03f59bfb781d3 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/235573 Fri, 21 Jul 2023 09:46:09 -0000 https://status.shc.kanagawa.jp/incident/235573#ffca297ac8e1f835b5300db3505dd273e2d832cc7c8591d27d9a9c3e7f8c0452 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/235573 Fri, 21 Jul 2023 08:34:48 -0000 https://status.shc.kanagawa.jp/incident/235573#de7b464e60607b4713e107dd3ebe3226d2dab44c761f4259b730944d61f86c5f Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/235573 Fri, 21 Jul 2023 08:31:25 -0000 https://status.shc.kanagawa.jp/incident/235573#f176e6012194671fdf3743f1cd222a4b29ac01812c134fa76201d671aeec869d Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/235573 Fri, 21 Jul 2023 05:49:16 -0000 https://status.shc.kanagawa.jp/incident/235573#0fe33c6347f5752f39426afc56b716e1e115406315193e8a9bafce42affd6045 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/235573 Fri, 21 Jul 2023 05:49:16 -0000 https://status.shc.kanagawa.jp/incident/235573#0fe33c6347f5752f39426afc56b716e1e115406315193e8a9bafce42affd6045 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/235235 Thu, 20 Jul 2023 11:34:09 -0000 https://status.shc.kanagawa.jp/incident/235235#5cdde06899f62c35a4e45fe077614cf687b8776f85721e6601073e49e16de2b1 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/235235 Thu, 20 Jul 2023 11:30:23 -0000 https://status.shc.kanagawa.jp/incident/235235#81e4e9c878f70cd8a6db8408382198186935fbea2c33fe9a2c2cb3b08138b93c Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/235235 Thu, 20 Jul 2023 11:03:07 -0000 https://status.shc.kanagawa.jp/incident/235235#725fbe6acdd8af05de56e1580ea31df8af975478f6baa1d08756b0c2f0d7abac Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/235235 Thu, 20 Jul 2023 10:54:24 -0000 https://status.shc.kanagawa.jp/incident/235235#34cb8363b1448be746e0216f37f900a040750811c243b537abc10185b35f1868 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/235235 Thu, 20 Jul 2023 09:36:09 -0000 https://status.shc.kanagawa.jp/incident/235235#c1bb2cb818d0c1309d3e1d27b3a76c81e495dde4bd266720b0c8cd087a06af0a Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/235235 Thu, 20 Jul 2023 09:33:20 -0000 https://status.shc.kanagawa.jp/incident/235235#aa4ac6b785054c16bcfbc63765085a0f33d0620f4b832aacca91bed2b03d3d12 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/234886 Wed, 19 Jul 2023 18:18:22 -0000 https://status.shc.kanagawa.jp/incident/234886#e53b68535b5313531f3ad9cdff501028b66d87481178e77f45d1c5aab1f7f265 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/234886 Wed, 19 Jul 2023 18:17:31 -0000 https://status.shc.kanagawa.jp/incident/234886#b093d1cc83c4fcd67b6a525d1ed7871be2ac6e9d96fe4c0788aaec7c383f74c0 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/234886 Wed, 19 Jul 2023 17:18:04 -0000 https://status.shc.kanagawa.jp/incident/234886#27bf466b4c0a9955dc53a6898f3e07e3d0dec451584c244318f53cefc73449d1 Internet Relay Chat Web (webirc.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/234886 Wed, 19 Jul 2023 17:15:10 -0000 https://status.shc.kanagawa.jp/incident/234886#49293bc82317dab22a8b4e2567036314c693780da215dffff60d0aa698066fbd Internet Relay Chat Web (webirc.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/234886 Wed, 19 Jul 2023 16:20:32 -0000 https://status.shc.kanagawa.jp/incident/234886#a4673a3e8ca90d83f40fa64e0503ab6b4defd5dc4fd4f824a0a5ecd771460f09 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/234886 Wed, 19 Jul 2023 16:20:14 -0000 https://status.shc.kanagawa.jp/incident/234886#57b2372b58fc5ca43598fc68d7c82faecf0e83d3bb99075a4138724ea7483ecb Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/234886 Wed, 19 Jul 2023 14:35:21 -0000 https://status.shc.kanagawa.jp/incident/234886#6b6a902e4d03768514120ecc09fed7ac7a285999b17f6102b8d8c51adbd09715 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/234886 Wed, 19 Jul 2023 14:35:21 -0000 https://status.shc.kanagawa.jp/incident/234886#6b6a902e4d03768514120ecc09fed7ac7a285999b17f6102b8d8c51adbd09715 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/233655 Tue, 18 Jul 2023 18:57:41 -0000 https://status.shc.kanagawa.jp/incident/233655#d54625326a6e8b6b07790197b2151f2c6f2b296fa6098ee7b5d52a65ea03e2a4 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/233655 Tue, 18 Jul 2023 18:56:49 -0000 https://status.shc.kanagawa.jp/incident/233655#39c20a03b3da1bd1fa1df2d01b260e47d30d322ad7f6f488cba7bc1db770c811 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/233655 Tue, 18 Jul 2023 01:54:44 -0000 https://status.shc.kanagawa.jp/incident/233655#ac78d5f04139918137a105d6528c715047f5415738a53ce718ccd02c538861ac Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/233655 Tue, 18 Jul 2023 01:54:44 -0000 https://status.shc.kanagawa.jp/incident/233655#ac78d5f04139918137a105d6528c715047f5415738a53ce718ccd02c538861ac Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/233655 Mon, 17 Jul 2023 12:02:52 -0000 https://status.shc.kanagawa.jp/incident/233655#6753c6a7f6315edb067d80d8288dfac731ebbf399884147e3eb2aa33dd1d4d8a Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/233655 Mon, 17 Jul 2023 12:02:52 -0000 https://status.shc.kanagawa.jp/incident/233655#6753c6a7f6315edb067d80d8288dfac731ebbf399884147e3eb2aa33dd1d4d8a Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/233588 Sun, 16 Jul 2023 18:55:29 -0000 https://status.shc.kanagawa.jp/incident/233588#d9bee3892e50722f9c5006c8a8a4f0344efaeadc429a745137fbe9bb69cebdc7 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/233588 Sun, 16 Jul 2023 18:54:30 -0000 https://status.shc.kanagawa.jp/incident/233588#bbbe8b94ff0032d716df9b45b7892605f4459ddb9616ec73b9bbcf33d59b7007 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/233237 Sat, 15 Jul 2023 15:52:11 -0000 https://status.shc.kanagawa.jp/incident/233237#7974adf4d457aa741b87d9d55dcd4aaf50637bf340d67bbc733bbcb2aff129e5 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/233237 Sat, 15 Jul 2023 15:51:09 -0000 https://status.shc.kanagawa.jp/incident/233237#7596178140ebf67dfb2f833015c86778f3835e6817ae9e2db9a5afcc4b3e23f0 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/232919 Fri, 14 Jul 2023 15:54:32 -0000 https://status.shc.kanagawa.jp/incident/232919#eecaaf264c4e750c38961d35b967a11fb4c548e07d33bbabc025440aeeca80b1 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/232919 Fri, 14 Jul 2023 15:53:29 -0000 https://status.shc.kanagawa.jp/incident/232919#d1ea4ba9d1d2ae7e67d7ddb8628aaa4dd8fc54dd321284e3a0ab77f6a0308805 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/232385 Thu, 13 Jul 2023 18:50:25 -0000 https://status.shc.kanagawa.jp/incident/232385#a0fe813fc3564655f39e0f01359ef6603e099f4167e0161b21311cb1abb73878 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/232385 Thu, 13 Jul 2023 18:49:37 -0000 https://status.shc.kanagawa.jp/incident/232385#a12d8fa90d8c697f4b7493822825e00895bc2f1719eac6eed7efc088ad0214cf Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/232385 Thu, 13 Jul 2023 10:13:25 -0000 https://status.shc.kanagawa.jp/incident/232385#24d27bb3f9c6a90089b3c7ed2d167a4771eb77ccef12acf230b7103679d4d897 Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/232385 Thu, 13 Jul 2023 10:12:08 -0000 https://status.shc.kanagawa.jp/incident/232385#1aa974ae0e95afc58b428190cbd7f36696438cb4b2257739df5fd14d2c5021cd Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/231365 Tue, 11 Jul 2023 11:38:43 -0000 https://status.shc.kanagawa.jp/incident/231365#9178acee1692b46ef37eba4b52be64fc3fdfdc80d87011452b0f4e8905c6c94c Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/231365 Tue, 11 Jul 2023 11:38:00 -0000 https://status.shc.kanagawa.jp/incident/231365#d818441bea30c71f37474e7ef0ba78aa9864de295d2a5fd4e009cdcea832f969 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/231365 Tue, 11 Jul 2023 08:58:09 -0000 https://status.shc.kanagawa.jp/incident/231365#0ab772d1a4f7cc73e505237e5c639c03e0f8bbb2a5b21689277deec9ef98bbfc Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/231365 Tue, 11 Jul 2023 08:58:09 -0000 https://status.shc.kanagawa.jp/incident/231365#0ab772d1a4f7cc73e505237e5c639c03e0f8bbb2a5b21689277deec9ef98bbfc Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/231365 Tue, 11 Jul 2023 05:19:16 -0000 https://status.shc.kanagawa.jp/incident/231365#fb0f3c5be67eadaee1dad7a7c5f65097c738958006de4867c6159e3a174d787a Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/231365 Tue, 11 Jul 2023 05:18:10 -0000 https://status.shc.kanagawa.jp/incident/231365#089e7da74a46cee89a92617094e07c3c7376c0ba220dfd1189ec267fb7132df4 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/230149 Sat, 08 Jul 2023 18:39:31 -0000 https://status.shc.kanagawa.jp/incident/230149#636e8bdc585b4446469efcd3ed86d09cb289e3630df58c2c8dab4de51ea2c94a NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/230149 Sat, 08 Jul 2023 18:38:30 -0000 https://status.shc.kanagawa.jp/incident/230149#d1b47963f33ef9123a042244db2fd079b37a235862fd9e887a585f825fb04122 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/230149 Sat, 08 Jul 2023 16:29:50 -0000 https://status.shc.kanagawa.jp/incident/230149#3fdff510bef9b79d586cd6b14f9a6620d571b7eb984494a31ea5e28533dd7ed9 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/230149 Sat, 08 Jul 2023 16:28:57 -0000 https://status.shc.kanagawa.jp/incident/230149#bf5e1f6c4790aa609d13ec86bad1b86fee52ecc537abe48eb6d80da147967f35 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/230149 Sat, 08 Jul 2023 06:32:06 -0000 https://status.shc.kanagawa.jp/incident/230149#cafabaa4ceacab47f1b0ec8168e06f61663d349f8c6565112a9ffcb8cfa8ba4a Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/230149 Sat, 08 Jul 2023 06:30:07 -0000 https://status.shc.kanagawa.jp/incident/230149#4752501bdfb39562a17742b8fde5cde8985fc3194fddc7acfcce7b16781b111b NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/230149 Sat, 08 Jul 2023 06:25:05 -0000 https://status.shc.kanagawa.jp/incident/230149#d145100ba9a296ed4b99338f1a5b33759930b395a2523e52b7753a7047f07cd2 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/230149 Sat, 08 Jul 2023 06:23:14 -0000 https://status.shc.kanagawa.jp/incident/230149#7d8e53e9dac6c676057111f52c77e13e417f853c5740c76a973b681bf5dfbe99 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/230149 Sat, 08 Jul 2023 05:26:54 -0000 https://status.shc.kanagawa.jp/incident/230149#3832a0a193d924562534ed6ed924081d7089041e3bbaab4d74b29d715235115c Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/230149 Sat, 08 Jul 2023 05:17:46 -0000 https://status.shc.kanagawa.jp/incident/230149#500239a229088767d4fd8a421bdca1c031a5f0875172d4dbd561658c20aeaa23 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/230149 Sat, 08 Jul 2023 04:47:32 -0000 https://status.shc.kanagawa.jp/incident/230149#fb936a09c4a28d9f1926091b411818902ce38e25989abc2764f319b80a07b887 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/230149 Sat, 08 Jul 2023 04:22:51 -0000 https://status.shc.kanagawa.jp/incident/230149#6bcb337c5d11e46b382eb3fb05ceecf8708178672a0db006d4f75882a6fb4da6 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/230149 Sat, 08 Jul 2023 03:44:53 -0000 https://status.shc.kanagawa.jp/incident/230149#ba4ff444da42a9da75bff7235a223bc1f5427c27eaa417a4fd25c22fc7b6789c NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/230149 Sat, 08 Jul 2023 03:44:17 -0000 https://status.shc.kanagawa.jp/incident/230149#cf6931b1f30a748a3c9ddac2cdf51fe18d4af2fe48ab29d213f5761c3c8f0aa8 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/230149 Sat, 08 Jul 2023 03:37:49 -0000 https://status.shc.kanagawa.jp/incident/230149#296f7fcd631b6649a42b210343da5a0735c7252b425273a3b6b4ea43e0f23135 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/230149 Sat, 08 Jul 2023 03:22:19 -0000 https://status.shc.kanagawa.jp/incident/230149#4ac2897e320c75200c22d95fdd5a56d14ae9d15b55725271406d3f66b2948eb6 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/230149 Sat, 08 Jul 2023 02:41:55 -0000 https://status.shc.kanagawa.jp/incident/230149#6de7d4483baf7186a460c6eb1763b0611f372f30205a582f3aba2f1a9634bbf1 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/230149 Sat, 08 Jul 2023 02:35:19 -0000 https://status.shc.kanagawa.jp/incident/230149#5bd22fc9b2a1ae384eb749695ad7605100f045efa70b8da7ed1648b229fdeb31 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/230149 Sat, 08 Jul 2023 02:34:49 -0000 https://status.shc.kanagawa.jp/incident/230149#bda32086449172c8743512958fa222a40868286eb7e174e79833db423db81a6a Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/230149 Sat, 08 Jul 2023 02:17:53 -0000 https://status.shc.kanagawa.jp/incident/230149#ce79782aed43aedc51bb4c06861956e6a18f78f5ab44ac57e0bfd90d81cb4e43 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/230149 Sat, 08 Jul 2023 02:02:16 -0000 https://status.shc.kanagawa.jp/incident/230149#afb20aaa3786e79d7daad62532e8caab6249cdad32c31a827bbf27bd8e4d366c NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/230149 Sat, 08 Jul 2023 01:55:52 -0000 https://status.shc.kanagawa.jp/incident/230149#50602b3e0ac705fbabeb6f965b4df97b2048901c882bc279ad399ea10a575cf2 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/230149 Sat, 08 Jul 2023 01:50:50 -0000 https://status.shc.kanagawa.jp/incident/230149#9ecd1bf464e2f5a7265f9d7a22bd0958bc89260f8f2b0f15e5e3c8c5833beb38 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/230149 Sat, 08 Jul 2023 01:50:16 -0000 https://status.shc.kanagawa.jp/incident/230149#5dace1952c8ab7e522ab700a9536e73ee248fa082638f18e73b83f7c7505630a NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/230149 Sat, 08 Jul 2023 01:43:51 -0000 https://status.shc.kanagawa.jp/incident/230149#a017aba112f202952855668d852d07a539eb61f9c6d6beebf4efb2ef7b54ae84 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/230149 Sat, 08 Jul 2023 01:38:54 -0000 https://status.shc.kanagawa.jp/incident/230149#d7d9300fe53f5afb134821657f7673f2e317eb7b2f6dbe4794bb1e4fa7b94b38 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/230149 Sat, 08 Jul 2023 01:28:20 -0000 https://status.shc.kanagawa.jp/incident/230149#0b1fbea9c18803fba4f460beee4692223c4255b489cf3280abf3910747f4c9ee Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/230149 Sat, 08 Jul 2023 01:13:44 -0000 https://status.shc.kanagawa.jp/incident/230149#b820dc083a1ccaca225007e2b3c1a266a4dfa3c6fa9783210b96639678a4f7e9 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/230149 Sat, 08 Jul 2023 00:53:29 -0000 https://status.shc.kanagawa.jp/incident/230149#c63c4e49d15cffae28a3443b404050ccaf9840d11d003e80ffedb643d4e0063b NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/230149 Sat, 08 Jul 2023 00:47:40 -0000 https://status.shc.kanagawa.jp/incident/230149#4854e24e8d3c6d29390b9a45cf57d91bcbe40de6bc0d2c5564bf39781e0f0635 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/230149 Sat, 08 Jul 2023 00:40:16 -0000 https://status.shc.kanagawa.jp/incident/230149#2767c79577ef18752ac7e48ae78b613501c6d9ba4c7156610a3acc7c55077e7a Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/230149 Sat, 08 Jul 2023 00:32:07 -0000 https://status.shc.kanagawa.jp/incident/230149#8dbbaf8a9f9f71716dc9ff9e21487ed9502d9054cf066f57c3290d1c4e7897a8 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/229778 Fri, 07 Jul 2023 17:58:23 -0000 https://status.shc.kanagawa.jp/incident/229778#9998af74543bbb3b6b22486c1d8e8ce44b17ecbca058a8d037d3b1eace5774a3 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/229778 Fri, 07 Jul 2023 17:39:44 -0000 https://status.shc.kanagawa.jp/incident/229778#38caba63dba125ff17a645ec7ce4a669536998c72b731779e1ab2c8d4924309f Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/229778 Fri, 07 Jul 2023 16:01:31 -0000 https://status.shc.kanagawa.jp/incident/229778#28d3097c81bd66d25a8641b41463a1a5273869cca2f515d6c7507a8b99d6888e Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/229778 Fri, 07 Jul 2023 16:00:49 -0000 https://status.shc.kanagawa.jp/incident/229778#e16a31fac7ee427930734660a23771d13bb3c461867f57c755a8955f527078a6 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/229778 Fri, 07 Jul 2023 11:06:09 -0000 https://status.shc.kanagawa.jp/incident/229778#98b960574e5de851c505341a68cf1d1dcc5a3d741a134a7e7fe005d207a0c4b3 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/229778 Fri, 07 Jul 2023 11:05:32 -0000 https://status.shc.kanagawa.jp/incident/229778#e3d27dfa27caba9bf569da53d96bc9e3335df75095d986df7e22fdc360630619 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/229778 Fri, 07 Jul 2023 09:57:11 -0000 https://status.shc.kanagawa.jp/incident/229778#3e65263f2490a6d5cde0e2f7c24cc47889fb1f58524f4c8df62084d7935d0b99 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/229778 Fri, 07 Jul 2023 09:56:49 -0000 https://status.shc.kanagawa.jp/incident/229778#45b550563c308290c5e71f3b998d3e261bfa7f286d4235ed4b7f5012bb5a39f1 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/229778 Fri, 07 Jul 2023 06:36:10 -0000 https://status.shc.kanagawa.jp/incident/229778#6d1f0a9b99f7237aaf25058cec1ac9b71d0e3c3ad63834691a2800c86f226a5f Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/229778 Fri, 07 Jul 2023 06:35:48 -0000 https://status.shc.kanagawa.jp/incident/229778#704edfffc1e853f2967cf868c5a39afe9e90e878578b2aca46305dd7dfc19840 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/229778 Fri, 07 Jul 2023 05:05:53 -0000 https://status.shc.kanagawa.jp/incident/229778#3a8dc11115b77c6a0374281d495f1bf4e8581f57b780be4020af7f6950c0b6e5 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/229778 Fri, 07 Jul 2023 05:05:13 -0000 https://status.shc.kanagawa.jp/incident/229778#de2c296e6130100233b0dee4b0994919928bede48b38de6a8d8606aa5fa9f12a Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/229778 Fri, 07 Jul 2023 04:53:53 -0000 https://status.shc.kanagawa.jp/incident/229778#16882f7f88f84c32120395b561d7a212dfedab7e40a962067e85c339d31be198 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/229778 Fri, 07 Jul 2023 04:47:46 -0000 https://status.shc.kanagawa.jp/incident/229778#477ca19f01b05e1225074ad115340d29eda7e6d88d9919bb8f17f54eed20affd Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/229532 Thu, 06 Jul 2023 21:53:22 -0000 https://status.shc.kanagawa.jp/incident/229532#4c90d49745443c5d6ddd23fa8fc927388ff252a7199b5d059c9c048bf43c02b5 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/229532 Thu, 06 Jul 2023 21:50:19 -0000 https://status.shc.kanagawa.jp/incident/229532#7ec7fdfba778786a9ca1977c1ffb79f1506cbd3ad48cad21025db4663bb7dda4 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/229532 Thu, 06 Jul 2023 20:11:28 -0000 https://status.shc.kanagawa.jp/incident/229532#ada19dc9578a15d54b84a1d0b8dedd00140bfb23754d33f56d27c6c863088b0f Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/229532 Thu, 06 Jul 2023 20:10:48 -0000 https://status.shc.kanagawa.jp/incident/229532#addbefe38d97b33a7cdbd7c1895bf4a5abcc2a823ee4fbab4a31dfd8dc200c31 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/229532 Thu, 06 Jul 2023 17:38:19 -0000 https://status.shc.kanagawa.jp/incident/229532#c3d33fa9387a56d1aa7c13f1a563a3632f5d88ac4d40acf4a05792b3e13d9765 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/229532 Thu, 06 Jul 2023 17:37:44 -0000 https://status.shc.kanagawa.jp/incident/229532#6b92dd722b594d0638c9141311f9580e2735b9db91b631525d261482c361e050 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/229532 Thu, 06 Jul 2023 14:26:15 -0000 https://status.shc.kanagawa.jp/incident/229532#ba376b9e344a26369d8954d700cf4b5ffd0acfd371f04c3848069edc5b33857e Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/229532 Thu, 06 Jul 2023 14:25:49 -0000 https://status.shc.kanagawa.jp/incident/229532#587a818e97ed674af7bb8e8f04a6a4ea4685a91fa411a2a203a053a403cdcf0b Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/228882 Wed, 05 Jul 2023 21:50:09 -0000 https://status.shc.kanagawa.jp/incident/228882#a40ca76e57f2ecbe30264b30455cfaa37be856d1faf7bf9ffaca2dbb196efe26 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/228882 Wed, 05 Jul 2023 21:47:01 -0000 https://status.shc.kanagawa.jp/incident/228882#133d9ca4126573b21e898e52ecae7f412b16470c3a542e5992ed07fd2019244f Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/228882 Wed, 05 Jul 2023 21:32:05 -0000 https://status.shc.kanagawa.jp/incident/228882#fc0e52cdde129853ede7d77c5e4d74bcb681da9624aadd02d291277b23a45a49 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/228882 Wed, 05 Jul 2023 21:31:35 -0000 https://status.shc.kanagawa.jp/incident/228882#111093b91b01cc18599b51b173ea26730f9905698943e33c39be2778e6bf3efa Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/228882 Wed, 05 Jul 2023 21:08:12 -0000 https://status.shc.kanagawa.jp/incident/228882#f7452b02da3bcc7a3f68fd81a8ef01b49a4fd33260f54005c4e9dc7f679e347e Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/228882 Wed, 05 Jul 2023 21:05:03 -0000 https://status.shc.kanagawa.jp/incident/228882#3ce317766cba8c7aa3ebc62a2c7971e8d1117172a5a480c0ade571490b75a2b3 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/228882 Wed, 05 Jul 2023 07:03:31 -0000 https://status.shc.kanagawa.jp/incident/228882#fa44b253fbd2290366fd47ab195ec88fd666fe934846c405ac30b63849c2575d Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/228882 Wed, 05 Jul 2023 07:02:42 -0000 https://status.shc.kanagawa.jp/incident/228882#f34034b8500c97e913c803667d824a939b102226261d9e9e81c7b331ffc54806 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/228882 Wed, 05 Jul 2023 06:59:32 -0000 https://status.shc.kanagawa.jp/incident/228882#28cc3ba5b83765090b120031aea819c3f588e673559515a4a15c9bd924f5a861 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/228882 Wed, 05 Jul 2023 06:59:32 -0000 https://status.shc.kanagawa.jp/incident/228882#28cc3ba5b83765090b120031aea819c3f588e673559515a4a15c9bd924f5a861 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/228882 Wed, 05 Jul 2023 06:52:08 -0000 https://status.shc.kanagawa.jp/incident/228882#850fa3ca8e648f4546a01388e8d2af160f76933f271210b9aa2264909f11a85f NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/228882 Wed, 05 Jul 2023 06:50:56 -0000 https://status.shc.kanagawa.jp/incident/228882#db68cbaa3f3e69c2e4816317fdb19c2a31596218d2e3ed557ab25cb99171f36b Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/228882 Wed, 05 Jul 2023 06:43:46 -0000 https://status.shc.kanagawa.jp/incident/228882#fcbdea57a8ddb838f5097d4669fbe1f43b04cfb287317a6210c3aa1bf5add179 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/228882 Wed, 05 Jul 2023 06:41:52 -0000 https://status.shc.kanagawa.jp/incident/228882#6936422e8f92d4a55c1af67144dfb8e154aa4aba8a5072b644cce7bbaeddd549 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/228003 Tue, 04 Jul 2023 18:19:10 -0000 https://status.shc.kanagawa.jp/incident/228003#53c9893e0a0806a4b5c155e7cb51a9a5d97e4df331defb149e9dbaad0df235e4 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/228003 Tue, 04 Jul 2023 18:12:05 -0000 https://status.shc.kanagawa.jp/incident/228003#68b05a35ffc31a001ffa36fde884a99d14862bdf3515776d95bce25f43c0a79e Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/228003 Tue, 04 Jul 2023 17:55:19 -0000 https://status.shc.kanagawa.jp/incident/228003#387cf62a76842999dd47421a851452ac15bcddba3d98d7e08ab82928588ca139 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/228003 Tue, 04 Jul 2023 17:52:03 -0000 https://status.shc.kanagawa.jp/incident/228003#d827a2766d605f31f59b950935d80c949a1f06cb8719e62b5bce6ceec0d02893 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/228003 Tue, 04 Jul 2023 16:07:47 -0000 https://status.shc.kanagawa.jp/incident/228003#f071b2e6a8a9aabbdfc16accd1b0e444ff4d945601647e0b8cc01b759a7b3c6c NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/228003 Tue, 04 Jul 2023 15:51:47 -0000 https://status.shc.kanagawa.jp/incident/228003#6ae8205d98125a84297415cb9c52d28b0bda1bfe4228579be053bcee268cec77 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/228003 Tue, 04 Jul 2023 15:36:45 -0000 https://status.shc.kanagawa.jp/incident/228003#7d494606ccf2090f53fbd77abae624f86dbac7c3f3faed29c65c97665f18ef0c Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/228003 Tue, 04 Jul 2023 15:12:44 -0000 https://status.shc.kanagawa.jp/incident/228003#5556836563b972f7b7f738dabe842aba3cd54a3a1b34ba91d161051ec227743f Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/228003 Tue, 04 Jul 2023 15:12:11 -0000 https://status.shc.kanagawa.jp/incident/228003#c7972717d3f6784b30c87445af1aa2124bb060e07215fead237fce467a29cf23 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/228003 Tue, 04 Jul 2023 15:03:46 -0000 https://status.shc.kanagawa.jp/incident/228003#f8db08a41e16ef104332216f3a29b4471adba363184b64dca79f356e59f1d4f9 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/228003 Tue, 04 Jul 2023 14:21:06 -0000 https://status.shc.kanagawa.jp/incident/228003#f72fd9bfe3fb0300a9e44253eb85f5f7da31e4fe158ef1e5b63c44650f95fec1 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/228003 Tue, 04 Jul 2023 14:00:47 -0000 https://status.shc.kanagawa.jp/incident/228003#00a52493953e73f6cff28330778232f8da3d0c1f6ef3f17546788ceebafe7ef3 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/228003 Tue, 04 Jul 2023 13:57:04 -0000 https://status.shc.kanagawa.jp/incident/228003#6c7d042e5d1aaa72cf6ecd16f69d106e2b34244f7f6bb239a55c0c87744f8587 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/228003 Tue, 04 Jul 2023 13:39:40 -0000 https://status.shc.kanagawa.jp/incident/228003#0e74697efa761e041ba6e46baa8ea6a6840682a563e7255aa0173d19272855db Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/228003 Tue, 04 Jul 2023 13:17:56 -0000 https://status.shc.kanagawa.jp/incident/228003#e95ce93ebcd078c6de0e7bb98d7ee453a8b63a06fe6b29ebfd4a83c4ac282434 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/228003 Tue, 04 Jul 2023 12:55:18 -0000 https://status.shc.kanagawa.jp/incident/228003#0181f78cafb3d4e429cdc00f929512c46f9cd6600bc3d2a434d3ad0415f3d1f9 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/228003 Tue, 04 Jul 2023 12:48:36 -0000 https://status.shc.kanagawa.jp/incident/228003#0bdd2fe53801f5224a35f5d2c0e7d3bd311fd814a96e35ecaf752b4bcc1f749d Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/228003 Tue, 04 Jul 2023 12:41:55 -0000 https://status.shc.kanagawa.jp/incident/228003#5e8bd6f075891a8cc20a12b35e5711a79b71868b9c42a5e3148e8d6daf0442c1 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/228003 Tue, 04 Jul 2023 12:25:30 -0000 https://status.shc.kanagawa.jp/incident/228003#6581862040229e5e42451e03352bceab2ea920d29b5709c87448ccd9d6f15221 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/228003 Tue, 04 Jul 2023 12:09:30 -0000 https://status.shc.kanagawa.jp/incident/228003#0d9a2c069610716a56d7adb9c01bc8d43cd359ef437db8f21df3d5599108c776 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/228003 Tue, 04 Jul 2023 12:06:28 -0000 https://status.shc.kanagawa.jp/incident/228003#67225f102ff6e7e4be0af25f59bba8b374444fd7c4ad7593bb8919fe009251a7 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/228003 Tue, 04 Jul 2023 11:48:54 -0000 https://status.shc.kanagawa.jp/incident/228003#3bc9d9ea67aebec01570a2b511280e8ca1d529b1a3b9937f24583b439a490d2f NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/228003 Tue, 04 Jul 2023 11:28:29 -0000 https://status.shc.kanagawa.jp/incident/228003#854e2a81f61f764799b8d84a285673a477321ce3a9658b7fa382d56254c4465c NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/228003 Tue, 04 Jul 2023 11:27:55 -0000 https://status.shc.kanagawa.jp/incident/228003#8ae72757acb1ccfc4a07c43c7e4b100705d23ee7c8d83d71261fe1aae308de5e NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/228003 Tue, 04 Jul 2023 11:24:21 -0000 https://status.shc.kanagawa.jp/incident/228003#97dcc874304caa35efa7703b353f56d709dc4ebd4df993f420526c418410a9be Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/228003 Tue, 04 Jul 2023 11:21:31 -0000 https://status.shc.kanagawa.jp/incident/228003#79db15d3c3534dfe74592be49d1a2f89e5e5cfe9fc7fd252d8c14f97e2b5d885 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/228003 Tue, 04 Jul 2023 11:19:29 -0000 https://status.shc.kanagawa.jp/incident/228003#d0133f9037ae4f7c5d240f7980744e96ce8742b7d82c48042e02098ebb6ad5b7 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/228003 Tue, 04 Jul 2023 10:51:54 -0000 https://status.shc.kanagawa.jp/incident/228003#853d3ed481a11bdfa9a1d5385d64bcde68888e7d2a7339c123e69e4e7670fe6d NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/228003 Tue, 04 Jul 2023 10:39:23 -0000 https://status.shc.kanagawa.jp/incident/228003#15ecedae23273c8ac671451d33663da162237aa2b75b29aef179bacd32729eb9 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/228003 Tue, 04 Jul 2023 10:23:51 -0000 https://status.shc.kanagawa.jp/incident/228003#38ee77478adaf2292a868f44a392c2e157372d1acb1753460f1960470abc853f Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/228003 Tue, 04 Jul 2023 10:10:18 -0000 https://status.shc.kanagawa.jp/incident/228003#279981619006d2e54d469be460150f3291f789aecdc0b324a679ad9c37334d36 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/228003 Tue, 04 Jul 2023 09:57:48 -0000 https://status.shc.kanagawa.jp/incident/228003#51fb8d4482ecdd2360f81ab1e139e547c792cceceff1aa39c2e37b592f7ff4e8 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/228003 Tue, 04 Jul 2023 09:46:26 -0000 https://status.shc.kanagawa.jp/incident/228003#1914e5c1a77a3736e076383852e13f037849d978b1350ddff5432fd6dfa822c5 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/228003 Tue, 04 Jul 2023 09:24:17 -0000 https://status.shc.kanagawa.jp/incident/228003#028b72add451f99cf47bece08aa886b0883cca352a71486e17d380fe85970850 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/228003 Tue, 04 Jul 2023 08:56:39 -0000 https://status.shc.kanagawa.jp/incident/228003#46c4e483fdc924b46bdbb914924b87b1b687882c8679fbb4bbc4abaf361b74de Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/228003 Tue, 04 Jul 2023 08:51:18 -0000 https://status.shc.kanagawa.jp/incident/228003#55d7ebc9f9b8018b3e6f9bea3574d50362013382ce0fab2a7b9d3fabac471359 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/228003 Tue, 04 Jul 2023 08:42:36 -0000 https://status.shc.kanagawa.jp/incident/228003#52f3b865df80cf228e8d47fafc8e090921d52c82cfb50ce3fa14ce0595b9ab79 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/228003 Tue, 04 Jul 2023 08:41:39 -0000 https://status.shc.kanagawa.jp/incident/228003#b3242e82f29d5671cafa9e29f77215e73143ef89155b5630e03a3288d7c50328 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/228003 Tue, 04 Jul 2023 08:25:08 -0000 https://status.shc.kanagawa.jp/incident/228003#22b1d351ca69576e702c63b1182f1c34f843be5089db78ba948e924e2f7ec78c NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/228003 Tue, 04 Jul 2023 08:15:14 -0000 https://status.shc.kanagawa.jp/incident/228003#e9e94fc52487ed343d0c368939be907509e27003ae8a4158ef3f12f3f285c743 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/228003 Tue, 04 Jul 2023 08:13:04 -0000 https://status.shc.kanagawa.jp/incident/228003#cd675b07c2c8631bc6d7ffdb1a9b9e65e89b03a6a57bdca3ae950e121921702e NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/228003 Tue, 04 Jul 2023 08:12:07 -0000 https://status.shc.kanagawa.jp/incident/228003#115196832f39c718222a733d82407d793d144c1017cd9e80938e5c3b23be0ead Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/228003 Tue, 04 Jul 2023 00:29:25 -0000 https://status.shc.kanagawa.jp/incident/228003#773cda1dbd361e031851431e6804e1d9281ddbfd1f21ded1525d494ec5aef35e Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/228003 Tue, 04 Jul 2023 00:23:27 -0000 https://status.shc.kanagawa.jp/incident/228003#68dadb21eb36487bc5f871ea6bb89c8535d68d4df665c1d31642e80fa44cd220 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/227573 Mon, 03 Jul 2023 13:20:16 -0000 https://status.shc.kanagawa.jp/incident/227573#61b8359e587f53cf13ec8ff9955f042245a5f4f84f2c50c313fa42045ab55277 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/227573 Mon, 03 Jul 2023 13:19:27 -0000 https://status.shc.kanagawa.jp/incident/227573#7c58a0399faee0f22e5950e8256daa9704e668ad5de865113419d8ca5dfdc36c Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/227573 Mon, 03 Jul 2023 00:40:19 -0000 https://status.shc.kanagawa.jp/incident/227573#e1cc633b8cbfe67d3baae6d757ac3ee0aaa52922120f5191fefa827c1a4fa0ac Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/227573 Mon, 03 Jul 2023 00:40:10 -0000 https://status.shc.kanagawa.jp/incident/227573#de52144a1c686a64827b16feb3f2053f07ad940eae129267c54aa2176c467414 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/227348 Sun, 02 Jul 2023 14:31:09 -0000 https://status.shc.kanagawa.jp/incident/227348#467ed608d3b27ce40aec73f1a9b67c3cd2737af40a8129b487edc16f47b83aaf Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/227348 Sun, 02 Jul 2023 14:30:25 -0000 https://status.shc.kanagawa.jp/incident/227348#fab490a15f743f7d5fc16da921e9e83a173cf0eedb9dd264f7ea78559e38b12c Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/227348 Sun, 02 Jul 2023 06:08:55 -0000 https://status.shc.kanagawa.jp/incident/227348#71d680797c5e15ecbc3eb1ee9bae70063bc534f6cc451f7c7737d4619f030039 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/227348 Sun, 02 Jul 2023 06:02:44 -0000 https://status.shc.kanagawa.jp/incident/227348#0f8aec009e7596b1f467da01029e8c1d2d949361b4fabf361e5354e7b9441a8d Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/227348 Sun, 02 Jul 2023 04:15:19 -0000 https://status.shc.kanagawa.jp/incident/227348#25119ace8dc06f530538d9642b5d27c9fc5628353b2dbcdb9dbb447832d12f0f Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/227348 Sun, 02 Jul 2023 04:14:26 -0000 https://status.shc.kanagawa.jp/incident/227348#a0a24226fc32a90bada37f08a3d2108ed68b7eea5fae58ab5f02fc815000a3ab Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/226775 Fri, 30 Jun 2023 18:17:39 -0000 https://status.shc.kanagawa.jp/incident/226775#f4ea273f5191d7e5a3b4bc9a2da5bafc21ceaf04f3c831083d65b3bb7156177a NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/226775 Fri, 30 Jun 2023 18:16:27 -0000 https://status.shc.kanagawa.jp/incident/226775#63abba033720c29b410094b0f618245a2b8e736acb6dc3a4aa7319e66707d089 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/223969 Fri, 23 Jun 2023 21:02:37 -0000 https://status.shc.kanagawa.jp/incident/223969#e6c89f2f12e6cc9035f0297544cef50eb6c2eb4a1c84c93c61cab822d7434e08 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/223969 Fri, 23 Jun 2023 21:01:56 -0000 https://status.shc.kanagawa.jp/incident/223969#4438c1c5444823bdd20fa5fc0f449ea578360192cac83cfa0d96631a030f59a9 Pleroma(pr.shc.kanagawa.jp) went down and Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/223969 Fri, 23 Jun 2023 21:01:56 -0000 https://status.shc.kanagawa.jp/incident/223969#4438c1c5444823bdd20fa5fc0f449ea578360192cac83cfa0d96631a030f59a9 Pleroma(pr.shc.kanagawa.jp) went down and Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/223969 Fri, 23 Jun 2023 21:00:55 -0000 https://status.shc.kanagawa.jp/incident/223969#11832499f75773ad0bf5b8623a96c999d271290bc3557d596801c26e9e1e96a8 Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/222936 Wed, 21 Jun 2023 18:29:30 -0000 https://status.shc.kanagawa.jp/incident/222936#13214da5605a7f751e579540a5c4cd077ac7a8a7fff175aa5b9f573569b4e142 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/222936 Wed, 21 Jun 2023 18:28:38 -0000 https://status.shc.kanagawa.jp/incident/222936#b3c4bcb8f95bed7378c82b2d48f991aeba84237e459229d46ff96ce9d5ef95d7 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/222936 Wed, 21 Jun 2023 13:17:30 -0000 https://status.shc.kanagawa.jp/incident/222936#ac012ba1c9905e9f736a74c9aa38141b699a71e96f6941a5e8652c5b349e116c Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/222936 Wed, 21 Jun 2023 13:17:01 -0000 https://status.shc.kanagawa.jp/incident/222936#91c2012f3ef7c0bed8e4b73792b35928dc4d4bf703b901271a8d3024f2ae3006 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/222936 Wed, 21 Jun 2023 09:00:30 -0000 https://status.shc.kanagawa.jp/incident/222936#087026893c0af047e6ca9c4f59ea5a72fc703d96961e4bf524bb602c097ee7aa Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/222936 Wed, 21 Jun 2023 08:54:49 -0000 https://status.shc.kanagawa.jp/incident/222936#4e8b27bc222e3ee6ea5f41cf07ea336dcc5a80d6647570f5c10681b3343c0794 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/222419 Tue, 20 Jun 2023 23:39:43 -0000 https://status.shc.kanagawa.jp/incident/222419#6d34a2acca34fe26730944d8916b6fdfc74eba7f04f560dec64307acfeac1f3d Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/222419 Tue, 20 Jun 2023 23:39:25 -0000 https://status.shc.kanagawa.jp/incident/222419#e127119d67596496fd5bbf2eb5bd4fba86ab75bbc4c36194f8880c2f79e0be16 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/222419 Tue, 20 Jun 2023 15:44:03 -0000 https://status.shc.kanagawa.jp/incident/222419#764b8d3fdf6a6318b64268032145b01f71398fc7f6065391961e334413fcb5f2 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/222419 Tue, 20 Jun 2023 15:41:42 -0000 https://status.shc.kanagawa.jp/incident/222419#9949ef72c04b10dbf88d85c37e061686928284565c5433507c94023e1ff5ecd5 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/221453 Sat, 17 Jun 2023 16:07:59 -0000 https://status.shc.kanagawa.jp/incident/221453#ac680eee7a044753e1bc65a69a857b3d98e035ca5ca08022fb32455628b83fca Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/221453 Sat, 17 Jun 2023 16:06:57 -0000 https://status.shc.kanagawa.jp/incident/221453#db9206615fc9d2f4791d6ba09f8d1e4de662ccd56c05a955d35efbd74c39b069 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/221032 Fri, 16 Jun 2023 11:12:34 -0000 https://status.shc.kanagawa.jp/incident/221032#a62a44b638b5c990ff9cc6ef4f20c582674ed482e875d84e698bbd01b3be2080 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/221032 Fri, 16 Jun 2023 11:11:16 -0000 https://status.shc.kanagawa.jp/incident/221032#e4ef2742bbcacb9812262224b9fd9610c06eb04024141a4d49b8fdb33c144734 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/220697 Thu, 15 Jun 2023 18:55:49 -0000 https://status.shc.kanagawa.jp/incident/220697#93e3e555f0d88b899a1966c9a9e6ce99ab52c0e9d854de9c408ea558c49aa72d Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/220697 Thu, 15 Jun 2023 18:54:31 -0000 https://status.shc.kanagawa.jp/incident/220697#182892a702801b7cdcc7dcdc56fa7722bf33c01144d281dbb958aaed2ad62dd5 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/219082 Tue, 13 Jun 2023 18:47:45 -0000 https://status.shc.kanagawa.jp/incident/219082#6a0dd48fe4856e90c81fa41c4014604a82bf6e63f1a1c5e00aa519272b2b245d Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/219082 Tue, 13 Jun 2023 18:46:59 -0000 https://status.shc.kanagawa.jp/incident/219082#ce90ad506856b33c79d89260e695d1115913b0ad1d5a79454e52402129cafb35 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/219082 Tue, 13 Jun 2023 11:11:27 -0000 https://status.shc.kanagawa.jp/incident/219082#c11d58937ab8e6ee5fd7a651a516bd0701f2b89e498c5d7bffe5bbf5489e0e64 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/219082 Tue, 13 Jun 2023 11:10:17 -0000 https://status.shc.kanagawa.jp/incident/219082#0da842a3d25d9a8e8eeab4bb2c67b4dfcfa5f455e080c69294b4cc356a31f896 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/219082 Tue, 13 Jun 2023 10:41:43 -0000 https://status.shc.kanagawa.jp/incident/219082#d330009324f49f827d8d7185192405ce95a1be759835bad6f837c156b5f83be3 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/219082 Tue, 13 Jun 2023 10:41:17 -0000 https://status.shc.kanagawa.jp/incident/219082#47d5a8d8367e41315c5ab62bd9e8a494d9ef37ce527f05df97a579a1f5a71840 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/219082 Mon, 12 Jun 2023 10:06:34 -0000 https://status.shc.kanagawa.jp/incident/219082#1c5abbd0fb85f4b88455f511c293eade280d20957184a905a95495ee26bfd608 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/219082 Mon, 12 Jun 2023 10:03:08 -0000 https://status.shc.kanagawa.jp/incident/219082#6d20ffc89d9cee10e3bbe10a938a24d4b5a7cb139e6330685bac28224ca22e9a Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/217835 Sat, 10 Jun 2023 09:52:21 -0000 https://status.shc.kanagawa.jp/incident/217835#1a98be42b47ed900091e3b7449d7f6baa1019a1497ca9039d62bb5f214213844 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/217835 Sat, 10 Jun 2023 08:54:37 -0000 https://status.shc.kanagawa.jp/incident/217835#550f4dac496d33d1e457333e696184dd9a9ba5c72609df942e06c1b25feab9a8 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/217835 Sat, 10 Jun 2023 08:43:19 -0000 https://status.shc.kanagawa.jp/incident/217835#80a9f1d5a47fd5bca70dd5e1f12606dd73c71b29c86005a90be2842c5c0b2179 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/217835 Sat, 10 Jun 2023 05:33:29 -0000 https://status.shc.kanagawa.jp/incident/217835#18f954478ba40e0e44001d26054d25eae3f844a336d20fa5562e5bfcda3b1bc6 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/217835 Sat, 10 Jun 2023 05:22:15 -0000 https://status.shc.kanagawa.jp/incident/217835#d4fe9754fac84c35f488ada7bd364c7e94ac93bbc548018adfc463960d9860fc NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/217835 Sat, 10 Jun 2023 03:54:31 -0000 https://status.shc.kanagawa.jp/incident/217835#25595fc5bf937fb4eef694500cfd251d6f4d9c72405c379429db4aaa2fa98fdd NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/217835 Sat, 10 Jun 2023 03:31:26 -0000 https://status.shc.kanagawa.jp/incident/217835#b8fb4ed8c16c8c2b3a3744ae522e1bca7d977c0d6bfac1e455e5049bda81d47a NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/217835 Sat, 10 Jun 2023 03:15:29 -0000 https://status.shc.kanagawa.jp/incident/217835#273b68281bb99123caacf40b92fc92b8947c74c2805c3e89040d2a052b6965eb NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/217835 Sat, 10 Jun 2023 02:58:11 -0000 https://status.shc.kanagawa.jp/incident/217835#7390248056cb8981ce0ae1f95157a732842fd1c8e9a488f8b2b2c78cfee6d7ee NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/217835 Sat, 10 Jun 2023 01:24:34 -0000 https://status.shc.kanagawa.jp/incident/217835#26c4d88dc0d8b36ab7bd6a25cff57c5ca9cdb95d5f1ee74603aef20037c8e46a NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/217835 Sat, 10 Jun 2023 00:52:27 -0000 https://status.shc.kanagawa.jp/incident/217835#128db11f873d0379d21af1161c02273c3b85c5f4311de2ec7b1a8f94165d4ca4 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/217835 Sat, 10 Jun 2023 00:33:24 -0000 https://status.shc.kanagawa.jp/incident/217835#171a5b7853dbc61661f4587c193a1156a6bc395e3e76ee32256ff89121aa29c9 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/217835 Sat, 10 Jun 2023 00:22:10 -0000 https://status.shc.kanagawa.jp/incident/217835#cc27ba721056eefdcd7838e72375ab379a1660df7b5af0de2393c2ed31663d41 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/217835 Fri, 09 Jun 2023 23:54:21 -0000 https://status.shc.kanagawa.jp/incident/217835#dbb0753587aea36fee2d18d9c13eb4f8e324001871ee8961366aa7b8cd188ddd NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/217835 Fri, 09 Jun 2023 23:33:54 -0000 https://status.shc.kanagawa.jp/incident/217835#14b907f00d54790d5f5cc5b8790d4ebad88c7424a3da8e561fe41481dcefc059 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/217835 Fri, 09 Jun 2023 21:18:24 -0000 https://status.shc.kanagawa.jp/incident/217835#df2f5a4d4b4719d6c95c7d09d8878dfd8fb6ae72f16c527cfe78fe807d82ae81 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/217045 Wed, 07 Jun 2023 18:26:56 -0000 https://status.shc.kanagawa.jp/incident/217045#4a4dc97f1c8d2cd5623832ecd1812e3c4ec93abc662506263b479ed0e2f8f36a NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/217045 Wed, 07 Jun 2023 18:26:07 -0000 https://status.shc.kanagawa.jp/incident/217045#d4db3e4ce40782e8a0960e0f808d4fdb1550ee8f7336aba94a1df2863deeb099 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/217045 Wed, 07 Jun 2023 10:05:29 -0000 https://status.shc.kanagawa.jp/incident/217045#e096d1a936d9a6334cd3751516c11b150d9ce0aaa83493e05b5c4661c3bc8e62 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/217045 Wed, 07 Jun 2023 10:01:06 -0000 https://status.shc.kanagawa.jp/incident/217045#cc9f18662d36c39d4eff4c2afff91ba993f04ba37cbcc52872a2dae8b0c907b0 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/217045 Wed, 07 Jun 2023 09:53:20 -0000 https://status.shc.kanagawa.jp/incident/217045#0405ba311597c7f4e495886fb2481955e30105f5e576ec423a9a5de5d2fe5140 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/217045 Wed, 07 Jun 2023 09:37:04 -0000 https://status.shc.kanagawa.jp/incident/217045#e94c3f72efae9ac3a888edb8052672a4cb17a9420524b2719afb6b3c2e5cfa1c NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/217045 Wed, 07 Jun 2023 09:29:03 -0000 https://status.shc.kanagawa.jp/incident/217045#5f0b831e79aa4b845b39cd6f7707d6bd8a877133a271a4bcfefc4661e2a3d028 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/217045 Wed, 07 Jun 2023 03:56:43 -0000 https://status.shc.kanagawa.jp/incident/217045#0fead0b022b231f47cccfc000f0207d630d4c08bec66f4d83d97cb722c851eee Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/217045 Wed, 07 Jun 2023 03:51:17 -0000 https://status.shc.kanagawa.jp/incident/217045#1c1e604f0eaf7a7b195af1efdf7367a9286b33e8ec16b82dd0742428d9bd0f17 Pleroma(pr.shc.kanagawa.jp) and ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/217045 Wed, 07 Jun 2023 03:51:17 -0000 https://status.shc.kanagawa.jp/incident/217045#1c1e604f0eaf7a7b195af1efdf7367a9286b33e8ec16b82dd0742428d9bd0f17 Pleroma(pr.shc.kanagawa.jp) and ownCloud (share.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/217045 Wed, 07 Jun 2023 03:50:38 -0000 https://status.shc.kanagawa.jp/incident/217045#18c76b3002de6062aa28bb3a2baf5f2fb63619675cdb1c8883397784ad790675 Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/217045 Wed, 07 Jun 2023 03:50:00 -0000 https://status.shc.kanagawa.jp/incident/217045#223740676f1279bf27b7c7862fa975257a832664daf421a9fb8351f984344c0b Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/217045 Wed, 07 Jun 2023 03:49:23 -0000 https://status.shc.kanagawa.jp/incident/217045#284d8e05cfcf457dd0c46a9fb433df492e65b4aa513d3359bb52839ddaa13386 Mastodon(mt.shc.kanagawa.jp) and ownCloud (share.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/217045 Wed, 07 Jun 2023 03:49:23 -0000 https://status.shc.kanagawa.jp/incident/217045#284d8e05cfcf457dd0c46a9fb433df492e65b4aa513d3359bb52839ddaa13386 Mastodon(mt.shc.kanagawa.jp) and ownCloud (share.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/217045 Wed, 07 Jun 2023 03:48:04 -0000 https://status.shc.kanagawa.jp/incident/217045#af41df6c9aaeba22acfbf8c4d9702b235ad1dc9588128f55f9bcf05ace4aa664 Pleroma(pr.shc.kanagawa.jp) and NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/217045 Wed, 07 Jun 2023 03:48:04 -0000 https://status.shc.kanagawa.jp/incident/217045#af41df6c9aaeba22acfbf8c4d9702b235ad1dc9588128f55f9bcf05ace4aa664 Pleroma(pr.shc.kanagawa.jp) and NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/216842 Tue, 06 Jun 2023 18:20:26 -0000 https://status.shc.kanagawa.jp/incident/216842#688d75519c80ab26ffcd18c8162a8da796d7f07c96211a6f7d9b5e0a56e3786e Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/216842 Tue, 06 Jun 2023 18:16:30 -0000 https://status.shc.kanagawa.jp/incident/216842#a23d5634a7297576f3551194d1c61cc48bfa32e7e43ddeb642395a6bed9e060d Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/216168 Mon, 05 Jun 2023 18:48:47 -0000 https://status.shc.kanagawa.jp/incident/216168#9aebe85109c03c1f86719d68b71809cec4cda3e34c96acada20033a6d5221056 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/216168 Mon, 05 Jun 2023 18:44:39 -0000 https://status.shc.kanagawa.jp/incident/216168#3ac89e8fa7a46884c95faa479448cf348638c812d866df25678dcc3a85f8741a Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/215940 Sun, 04 Jun 2023 18:43:33 -0000 https://status.shc.kanagawa.jp/incident/215940#716121bb932b5be324b5d289d275364c74c68551c7a7a08fc50c48a8fd07cd1d Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/215940 Sun, 04 Jun 2023 18:39:33 -0000 https://status.shc.kanagawa.jp/incident/215940#fd7bc29d862d75c0092bff5d51e534f9ce4d7d0a187273efd9f0c3abc04d9d74 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/214321 Wed, 31 May 2023 18:35:27 -0000 https://status.shc.kanagawa.jp/incident/214321#f23e7e6a65eef88e1084f804172432821fc25d19c0beb9ed49ac8787eeecd56c Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/214321 Wed, 31 May 2023 18:30:44 -0000 https://status.shc.kanagawa.jp/incident/214321#a751cf08d27066c60d94f79ce2702d3613eed644e91b9f5f61b9f87727719ccd Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/212502 Fri, 26 May 2023 18:31:47 -0000 https://status.shc.kanagawa.jp/incident/212502#8d5bac4dfa75e64a4d0676e2dc39fdec19e3652ec4be5928d46e8580cb0bdb7a NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/212502 Fri, 26 May 2023 18:30:42 -0000 https://status.shc.kanagawa.jp/incident/212502#4bc70c4467cba9ab2df3c2b6279d6fe28270d3649900500712af0257235b3197 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/212068 Thu, 25 May 2023 18:57:03 -0000 https://status.shc.kanagawa.jp/incident/212068#10ee66f5a805f90e1dd7ea0c31ff559d2d4fd48ce0d919748d09e536091769b9 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/212068 Thu, 25 May 2023 18:52:49 -0000 https://status.shc.kanagawa.jp/incident/212068#3d441668ef39311f35c4a955830bd2267f068dac34af0b217654f19758fcd87c Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/211095 Tue, 23 May 2023 18:54:47 -0000 https://status.shc.kanagawa.jp/incident/211095#591c91ae4c0a94d289b19b38a1bbb09207db986c63bdb95fd6ee5af3cfafb18c Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/211095 Tue, 23 May 2023 18:50:47 -0000 https://status.shc.kanagawa.jp/incident/211095#87ed8099a9c188f7559c711dcd332472ae9f82e46da7d9ca8bc876d7e8598e55 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/209898 Sat, 20 May 2023 18:56:16 -0000 https://status.shc.kanagawa.jp/incident/209898#02f98f3cd45fb19c9f6456f43aaed9f8e231d4d4360cc229ed506ff3af9c4d37 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/209898 Sat, 20 May 2023 18:52:23 -0000 https://status.shc.kanagawa.jp/incident/209898#48a4974f9ece56749387a2a7a7c57eb620e325d0262a882e948da01bc0667eab Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/209499 Fri, 19 May 2023 13:38:14 -0000 https://status.shc.kanagawa.jp/incident/209499#ef348483793ae844024214a4c43138ada327c472f474870e9c2a50a27d071ed4 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/209499 Fri, 19 May 2023 13:37:00 -0000 https://status.shc.kanagawa.jp/incident/209499#c5662120075d46273192935629452776b2b6dc825e3e57862eadee6876c1e4b9 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/207791 Mon, 15 May 2023 18:35:33 -0000 https://status.shc.kanagawa.jp/incident/207791#4f7b64daddf4d3b0fc881102892537f16f5b0e849611dd1cdbc0ce380b9f2d11 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/207791 Mon, 15 May 2023 18:31:32 -0000 https://status.shc.kanagawa.jp/incident/207791#bf1bede0076bf3f62e797a578ac3715d91162e3ece247a86f693c766689fc25f Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/207068 Sat, 13 May 2023 18:36:41 -0000 https://status.shc.kanagawa.jp/incident/207068#849e494fbce9cdaf8c229162b842e0239d9623631c8bfbe2645e25cef43cd6f4 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/207068 Sat, 13 May 2023 18:29:41 -0000 https://status.shc.kanagawa.jp/incident/207068#9a212ede3e17c35199a1e7354cd00809a4261f5d4d31699223cd5f428bc2f30a Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/206646 Fri, 12 May 2023 18:39:34 -0000 https://status.shc.kanagawa.jp/incident/206646#9645aafc86f23c2c9990f2b7266032600779e85c270ce4665d800eb31086971a Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/206646 Fri, 12 May 2023 18:35:29 -0000 https://status.shc.kanagawa.jp/incident/206646#8855bfe6be2856cf330d1c31ea874add7781bcb6703c119ebbadf6971b52e804 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/206646 Fri, 12 May 2023 14:07:41 -0000 https://status.shc.kanagawa.jp/incident/206646#afd6b636955301e65e6ac1c3522b8828bc82dd0a054cec69f76592afff64af75 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/206646 Fri, 12 May 2023 14:07:27 -0000 https://status.shc.kanagawa.jp/incident/206646#5eaf8b56f6ba813637fee9b8e21dfde27d65758fbcc3a38cb27f1c930d3ba832 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/205957 Thu, 11 May 2023 20:50:16 -0000 https://status.shc.kanagawa.jp/incident/205957#181901ea2db60473284e61fa1af408def3a91c769340751eba7e109d9c195faf Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/205957 Thu, 11 May 2023 20:47:09 -0000 https://status.shc.kanagawa.jp/incident/205957#8686cd0b0d3a0cf2e305a75febe33ecb97f5fb447a478dc99ca19ead269045ea Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/205957 Thu, 11 May 2023 20:17:10 -0000 https://status.shc.kanagawa.jp/incident/205957#5efbbb3a5d6103d9fe766ec460850ed6fa976be8888e4deb1a2c5ec92b467643 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/205957 Thu, 11 May 2023 20:07:36 -0000 https://status.shc.kanagawa.jp/incident/205957#c446c1e778a5aeb6d53d660f83827b0e8e2c8ee3de962a577df5f8c90f903dc5 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/205957 Thu, 11 May 2023 19:38:13 -0000 https://status.shc.kanagawa.jp/incident/205957#44baeb81f42b79d7eb4a5e46e22bc9c7f35611d8941a27f30aefcca20a4361e8 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/205957 Thu, 11 May 2023 19:34:33 -0000 https://status.shc.kanagawa.jp/incident/205957#95ca55a0493621531477074f14477193d503bd05eb37ac1919ad50e2f7e437c4 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/205957 Thu, 11 May 2023 18:47:11 -0000 https://status.shc.kanagawa.jp/incident/205957#31263fe31e4e53065150903f97be5d5990c3646a81ade9c5df8eee263f5bb7bc Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/205957 Thu, 11 May 2023 18:40:27 -0000 https://status.shc.kanagawa.jp/incident/205957#9be111516355c62346608a19b8447b250e8501507fa7208927e68a201eb5ca49 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/205957 Thu, 11 May 2023 18:08:29 -0000 https://status.shc.kanagawa.jp/incident/205957#402c2886229e50a6a16661c7b9f1da0ee6317b0ce02ce8cfb2703a0c13558bbc Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/205957 Thu, 11 May 2023 18:04:25 -0000 https://status.shc.kanagawa.jp/incident/205957#724ab790e6add44d3103e41e2954ed6e7877848e9898f6f375c89d8f8a335a1f Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/205957 Thu, 11 May 2023 07:35:00 -0000 https://status.shc.kanagawa.jp/incident/205957#19b52807c952a9a326d49c1ba6253aabd14396ec2c3f5ca7d5e3f60634887dea Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/205957 Thu, 11 May 2023 07:34:08 -0000 https://status.shc.kanagawa.jp/incident/205957#5e82ccc8a2cb77a2033d5b2c8715ebe006b24d8d98c5198a8a0323ce60f2c55d Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/205957 Thu, 11 May 2023 03:09:41 -0000 https://status.shc.kanagawa.jp/incident/205957#49c471c69709d1caae16ffa910e0fac37dc589cbf6ae50bbe5b83f909fc82503 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/205957 Thu, 11 May 2023 03:03:05 -0000 https://status.shc.kanagawa.jp/incident/205957#219da8203ce5fa293da531e0f55b5753e125f8ffc4e9e55ef67f2aa0bf852dd6 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/205716 Wed, 10 May 2023 20:12:26 -0000 https://status.shc.kanagawa.jp/incident/205716#ebcb6447ed173035d880eda4336f56cd274a1def81b6a6a6365cb1811e02085d Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/205716 Wed, 10 May 2023 20:08:22 -0000 https://status.shc.kanagawa.jp/incident/205716#0a43788f8639c61008c04418c6b66aef34ec6be8a7731415c161026f5cfa6f99 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/205716 Wed, 10 May 2023 19:53:50 -0000 https://status.shc.kanagawa.jp/incident/205716#5a967f5fd81dcddb4d8ef4665e4562969b2b57ae85963eaa181263b411e273cd Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/205716 Wed, 10 May 2023 19:53:35 -0000 https://status.shc.kanagawa.jp/incident/205716#33e9bb897560411c71a8a4dcb4255de17ed331a8e12ca8a19f46f28c8f563657 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/205716 Wed, 10 May 2023 13:26:21 -0000 https://status.shc.kanagawa.jp/incident/205716#9004fe786df349bbd30398d01c405c4a0e4c9049484d408cd1473440f69a16ea NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/205716 Wed, 10 May 2023 12:58:29 -0000 https://status.shc.kanagawa.jp/incident/205716#eddd3d430286096b3a8325ae6622e8aa2caeb8043b11a91ab9b07df034d6b1b9 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/204155 Sat, 06 May 2023 13:35:43 -0000 https://status.shc.kanagawa.jp/incident/204155#753bb4eda877597a2b76d3e04d9dce814e47552631ae83bb4e335392973f4c12 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/204155 Sat, 06 May 2023 13:35:19 -0000 https://status.shc.kanagawa.jp/incident/204155#ff9d86528211abcd47219ecebd1ee359db6520ea9ab6fa09b65df4f93bd370f1 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/204155 Sat, 06 May 2023 09:11:11 -0000 https://status.shc.kanagawa.jp/incident/204155#43e4e6dc375f45e1ba7406adb1323014acbf5c419761c1fc1b06160a6319f759 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/204155 Sat, 06 May 2023 09:08:20 -0000 https://status.shc.kanagawa.jp/incident/204155#4c8e43931744fc9ff79a3565f0f7c4154ab30af3941beb9d9f0d836e700cddae Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/203667 Fri, 05 May 2023 01:17:34 -0000 https://status.shc.kanagawa.jp/incident/203667#916ab4ebade085eeea2ea8995bf9fbfa12a7fe139eb6d65b9839ccc9e81a6b7b Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/203667 Fri, 05 May 2023 01:16:25 -0000 https://status.shc.kanagawa.jp/incident/203667#d1e136ad95868ed22c1db0a66653b4eb4afe43add3f1c5b0466e243de15a3859 Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/203449 Thu, 04 May 2023 11:20:50 -0000 https://status.shc.kanagawa.jp/incident/203449#eb1ae5aa209b4b4945cbf1e890e227954a7d518e42c1436d536f3d43e605f2f2 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/203449 Thu, 04 May 2023 11:19:53 -0000 https://status.shc.kanagawa.jp/incident/203449#09a6fe21bf8a0eb700806b5db3128300f71a23916eda07dcd8132f3b22fbe2bc Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/202835 Wed, 03 May 2023 23:46:58 -0000 https://status.shc.kanagawa.jp/incident/202835#01b59eabe6c249d339c0a8605d4d3315e68abb1002dcb4a9aa78f896162a0aed Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/202835 Wed, 03 May 2023 23:38:00 -0000 https://status.shc.kanagawa.jp/incident/202835#c8181aa47c539c6a782b6aa70cad14c64346c8ee730008c54ce5c2ecbd7808f8 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/202835 Wed, 03 May 2023 21:40:55 -0000 https://status.shc.kanagawa.jp/incident/202835#56d91a10169dda800a84f8c45d4f67f0a86d63ba567c3bbd53802d50bb78c820 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/202835 Wed, 03 May 2023 21:37:46 -0000 https://status.shc.kanagawa.jp/incident/202835#472ec1bc0a686c640fa4aa83a644823759d790f4f906376f035ea0e4fa2a7b66 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/202835 Wed, 03 May 2023 09:01:17 -0000 https://status.shc.kanagawa.jp/incident/202835#b59f92ab75d92cdae5574f9cd222a1ad759f94b3a18339e6167abc696e93e167 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/202835 Wed, 03 May 2023 08:54:47 -0000 https://status.shc.kanagawa.jp/incident/202835#bc382dd6c9ad0c8eef1e0809a8589db25cd86f66b2b061e5fbb8744b5011c68d Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/202835 Wed, 03 May 2023 08:28:33 -0000 https://status.shc.kanagawa.jp/incident/202835#47bcdecb84555809e54bf8839450d754c8a01d66bd3cd24e1ca55aeae088bcaa Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/202835 Wed, 03 May 2023 08:24:50 -0000 https://status.shc.kanagawa.jp/incident/202835#9f982fd75ae8620bd93e76479be1b485e7de93e29791f2905fa4ff911705e6c5 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/202835 Wed, 03 May 2023 04:45:51 -0000 https://status.shc.kanagawa.jp/incident/202835#f82239e85c1f2a1bbfe07e36a1ffaf095a183e99d91d7f1c0ab811f1d02ff55d Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/202835 Wed, 03 May 2023 04:42:11 -0000 https://status.shc.kanagawa.jp/incident/202835#3e06f81e983f02b7ae56a0dde8e1f80629a8e08f944ceeee5d9ab64028ae2e88 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/202835 Wed, 03 May 2023 04:03:47 -0000 https://status.shc.kanagawa.jp/incident/202835#c8c6a26079197f364c0ec4d0c8f4d24352fed12127cf9478f6717439d59e36b8 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/202835 Wed, 03 May 2023 03:45:22 -0000 https://status.shc.kanagawa.jp/incident/202835#061cd83e379528163f1a1a7a49870d81f502263c597c21f3e8938d847db7b349 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/202835 Wed, 03 May 2023 03:24:48 -0000 https://status.shc.kanagawa.jp/incident/202835#15ada308299cb23d52cdb20d8d5e60ccbbbdf840f70d5881013075a37d04beda Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/202835 Wed, 03 May 2023 03:18:13 -0000 https://status.shc.kanagawa.jp/incident/202835#2a485c3c883f02ab0cc32295c687847b4c35cd02c8f5ddf27f235878c090a1ac Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/202835 Wed, 03 May 2023 02:21:57 -0000 https://status.shc.kanagawa.jp/incident/202835#327355847ff6799f3372f599e57f6948386893ef783a9499ad27455257dfe290 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/202835 Wed, 03 May 2023 02:21:19 -0000 https://status.shc.kanagawa.jp/incident/202835#2797aac15d850482b1939c140f8a0a8b5c134cde4704a758dce3135156569289 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/202835 Wed, 03 May 2023 02:06:50 -0000 https://status.shc.kanagawa.jp/incident/202835#d17a5e5d44570d5fc9e9422a33e265ef61c30d32fd7ee5043f2b34922e7523e3 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/202835 Wed, 03 May 2023 02:00:43 -0000 https://status.shc.kanagawa.jp/incident/202835#4693b8bb50fda0f23cee3466e33ae7e3b0ecc5641271db711e0d3939d8d84103 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/202835 Wed, 03 May 2023 01:51:49 -0000 https://status.shc.kanagawa.jp/incident/202835#553a4f439f3114f471f3a5d04c51d61b1928ee10b577488a5d9a388e792d72df Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/202835 Wed, 03 May 2023 01:45:17 -0000 https://status.shc.kanagawa.jp/incident/202835#bfd2c9464cd9b45e0688a9e1d2349125cece47cb1af7311c68ed30506130604c Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/202765 Tue, 02 May 2023 21:03:50 -0000 https://status.shc.kanagawa.jp/incident/202765#dd333e45417cf24177d8a196e927cf3107e31e4aead2bb91c840adadbfcf1b1b Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/202765 Tue, 02 May 2023 20:54:28 -0000 https://status.shc.kanagawa.jp/incident/202765#4570d552cc4d2bf9f04191adb271027fb8957f3d83a66da9299c6cc574b7609d Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/201978 Sun, 30 Apr 2023 18:38:25 -0000 https://status.shc.kanagawa.jp/incident/201978#7ca82b041c8f0a3049460e1ec29d8f1a3378ab19b56ad1057465ec72a133c0e7 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/201978 Sun, 30 Apr 2023 18:37:01 -0000 https://status.shc.kanagawa.jp/incident/201978#943ddfac05a80263fe9983afec0b5f9e349736e8fd69a2cd0932ca8a82a8e7da Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/200411 Wed, 26 Apr 2023 12:33:23 -0000 https://status.shc.kanagawa.jp/incident/200411#9715551e9f7ec7159771e2fd6c74c332aa4e09270dbd0b1a9711c907d6e8af22 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/200411 Wed, 26 Apr 2023 12:33:23 -0000 https://status.shc.kanagawa.jp/incident/200411#9715551e9f7ec7159771e2fd6c74c332aa4e09270dbd0b1a9711c907d6e8af22 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/200411 Wed, 26 Apr 2023 12:29:34 -0000 https://status.shc.kanagawa.jp/incident/200411#50c669d803e44fb972c87a113300ba2e268162eede2e79ef64e1aa9cbf0635f1 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/200411 Wed, 26 Apr 2023 12:29:34 -0000 https://status.shc.kanagawa.jp/incident/200411#50c669d803e44fb972c87a113300ba2e268162eede2e79ef64e1aa9cbf0635f1 Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/200411 Wed, 26 Apr 2023 05:53:19 -0000 https://status.shc.kanagawa.jp/incident/200411#9790885c3c190b874b5e8421d626f190661dd7fdf5f2c12e864853dd2ff277b1 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/200411 Wed, 26 Apr 2023 05:52:14 -0000 https://status.shc.kanagawa.jp/incident/200411#9f108d89b9a7b1612a2fa6e09b6a6774f67abc7a996a8788719625ce35596714 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/195923 Thu, 13 Apr 2023 18:16:12 -0000 https://status.shc.kanagawa.jp/incident/195923#51b131ebdd9aa258cc3602481e47e71000a264c6c6d8ab0859864452e83ce4e5 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/195923 Thu, 13 Apr 2023 18:15:09 -0000 https://status.shc.kanagawa.jp/incident/195923#68008bfc1061ff53637f5ccc6e4ab74eb49572301dc862bf262a09315adeefe4 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/194802 Tue, 11 Apr 2023 05:56:56 -0000 https://status.shc.kanagawa.jp/incident/194802#7f80bd6098f223ff562315f43119212ea5edf667955493242d757e5aafa98ff3 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/194802 Tue, 11 Apr 2023 05:46:53 -0000 https://status.shc.kanagawa.jp/incident/194802#12d6f57905d7e7a748f0034575e1be5e4fbd84f1cc9bab7c8456b6790062b636 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/194802 Tue, 11 Apr 2023 01:27:24 -0000 https://status.shc.kanagawa.jp/incident/194802#5bf589c3fb062da5a119ec3ac6ec1826b2876f6914922fcaf6cf46d6a5cb1c0b Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/194802 Mon, 10 Apr 2023 23:38:59 -0000 https://status.shc.kanagawa.jp/incident/194802#ae891e88915840c987c90cded8067f6249687fd81cf8d84303b86d0fae29d1c1 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/194802 Mon, 10 Apr 2023 23:31:57 -0000 https://status.shc.kanagawa.jp/incident/194802#effb78c6dc099dd36e4cde2ab18691997612c2d9825429eabd40ad10620201ef Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/194802 Mon, 10 Apr 2023 23:21:14 -0000 https://status.shc.kanagawa.jp/incident/194802#98e80d41d8bd4015b5d2192b1774d7a2274e96506d69e3bb513dd99472fd2b0e NextCloud Maintenance recovered. https://status.shc.kanagawa.jp/incident/194802 Mon, 10 Apr 2023 23:19:16 -0000 https://status.shc.kanagawa.jp/incident/194802#57450096b685860ce6316768453c6b3d7b23de75168edba3abe0fd56cebe35d7 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/194802 Mon, 10 Apr 2023 23:10:44 -0000 https://status.shc.kanagawa.jp/incident/194802#e6fa8af3f0cac4607eb3d128d2fe82f54d8f4941749bd8d77e0f3c0c499c21ac Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/194802 Mon, 10 Apr 2023 22:58:25 -0000 https://status.shc.kanagawa.jp/incident/194802#df250e4684e0030b9d4b7bc8077f673f92b0829d3c5d4c2e6e60d720a5c6c96f Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/194802 Mon, 10 Apr 2023 22:49:47 -0000 https://status.shc.kanagawa.jp/incident/194802#15ab2259c17f97e784738563ba28a1c524e742b4a20d177e2d7c431dfcf1ad7d Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/194802 Mon, 10 Apr 2023 22:42:53 -0000 https://status.shc.kanagawa.jp/incident/194802#5f9f88125bf3b4c311738862574b29ae143aa6373c9883680422580b3d088527 NextCloud Maintenance went down. https://status.shc.kanagawa.jp/incident/194802 Mon, 10 Apr 2023 22:37:15 -0000 https://status.shc.kanagawa.jp/incident/194802#f589509403d1ce06fb53b4853d77cc3ac7f6a056b96d01a2cdff2aaf8ebbc409 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/194802 Mon, 10 Apr 2023 22:22:51 -0000 https://status.shc.kanagawa.jp/incident/194802#022d43a756eae8dc361ffe413531d94fa53409e06097663af7564fb56d1ec845 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/194802 Mon, 10 Apr 2023 22:22:11 -0000 https://status.shc.kanagawa.jp/incident/194802#66da0cc3ee5bb459af8551529c62650fe5fbe3607a8d5ffb3be6df3ad524a322 NextCloud Maintenance recovered. https://status.shc.kanagawa.jp/incident/194802 Mon, 10 Apr 2023 22:16:50 -0000 https://status.shc.kanagawa.jp/incident/194802#48f13eb8680e3479f01fd5a58468017b96705e6fd8d0730ead58dea7c6bd52a5 Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/194802 Mon, 10 Apr 2023 22:16:30 -0000 https://status.shc.kanagawa.jp/incident/194802#ee422fb8c1ae2677eda0efd9d0dbb210bdb01660c0e15fb266585e01ea6ef2b5 NextCloud Maintenance went down. https://status.shc.kanagawa.jp/incident/194802 Mon, 10 Apr 2023 22:08:22 -0000 https://status.shc.kanagawa.jp/incident/194802#6f3fc805cb19caac52ad75a7e19e48fa7a45ce63cac21a08883011362b9931a7 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/194802 Mon, 10 Apr 2023 22:07:37 -0000 https://status.shc.kanagawa.jp/incident/194802#b4a2adfae4f2f35dbd0b0ec9c4f7c1dc9d1116733bfb64084cc4087c8e07bf7e Mastodon(mt.shc.kanagawa.jp) and Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/194802 Mon, 10 Apr 2023 22:07:37 -0000 https://status.shc.kanagawa.jp/incident/194802#b4a2adfae4f2f35dbd0b0ec9c4f7c1dc9d1116733bfb64084cc4087c8e07bf7e Mastodon(mt.shc.kanagawa.jp) and Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/194802 Mon, 10 Apr 2023 22:07:16 -0000 https://status.shc.kanagawa.jp/incident/194802#e1b8e874883e9187586208f6667d55ed6712618e02db15fe10df02f3f9a0a567 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/193195 Wed, 05 Apr 2023 14:14:47 -0000 https://status.shc.kanagawa.jp/incident/193195#f046ec5ff705b518c8baf705e673586d726561553a88418c107bc7ddd9fa0b5f Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/193195 Wed, 05 Apr 2023 14:08:27 -0000 https://status.shc.kanagawa.jp/incident/193195#302cd1b075ed59a35be01c43189f3a44ba9a97e4a9a7ab89198add305c5d25fa Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/187056 Thu, 30 Mar 2023 23:15:33 -0000 https://status.shc.kanagawa.jp/incident/187056#bcdc8530e982456b034350f19886b22a29494d3e1d36f06aab1495dc32713539 Mastodon Daily Database Backup and Pleroma Daily Database Backup recovered. https://status.shc.kanagawa.jp/incident/187056 Thu, 30 Mar 2023 23:15:33 -0000 https://status.shc.kanagawa.jp/incident/187056#bcdc8530e982456b034350f19886b22a29494d3e1d36f06aab1495dc32713539 Mastodon Daily Database Backup and Pleroma Daily Database Backup recovered. https://status.shc.kanagawa.jp/incident/187056 Wed, 29 Mar 2023 16:01:19 -0000 https://status.shc.kanagawa.jp/incident/187056#f2a1f0756936815784e40be938301ac7c9b7da62f8c5e9439b5f7daa082eb048 Mastodon Daily Database Backup went down. https://status.shc.kanagawa.jp/incident/187056 Wed, 29 Mar 2023 15:45:47 -0000 https://status.shc.kanagawa.jp/incident/187056#31761ab58263923e30d47848a3e47b6fdc5abc1f9589a1a02f18b26598a1ca45 Pleroma Daily Database Backup went down. https://status.shc.kanagawa.jp/incident/183703 Sat, 11 Mar 2023 09:23:01 -0000 https://status.shc.kanagawa.jp/incident/183703#7d800f622701b014b77e17111a91acf6959179a5d34929ae9c3b1cacae155690 NextCloud Maintenance recovered. https://status.shc.kanagawa.jp/incident/183703 Fri, 10 Mar 2023 16:25:10 -0000 https://status.shc.kanagawa.jp/incident/183703#496ea9e56e3c52493e37b8cfd1c98ebb7940aaabd44c8d56fd3ecde6d9fef51a NextCloud Maintenance went down. https://status.shc.kanagawa.jp/incident/183703 Fri, 10 Mar 2023 16:11:32 -0000 https://status.shc.kanagawa.jp/incident/183703#e975bf40ed92da8ec33d91d69a84a73c36e67cda53997f787b33601f96d5696f NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/183703 Fri, 10 Mar 2023 16:06:11 -0000 https://status.shc.kanagawa.jp/incident/183703#6f5a58dee6f6923874514df9f17ac7880c22ba5dc9415c78c4d1bb8178e56c39 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/183703 Fri, 10 Mar 2023 16:04:13 -0000 https://status.shc.kanagawa.jp/incident/183703#0a4c66b0245492a8859639f4ff910919528f48ae9760784159c3671646fb1ccf NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/183703 Fri, 10 Mar 2023 16:02:24 -0000 https://status.shc.kanagawa.jp/incident/183703#c2674136b6c79d06b037ae9d1504d0bb9f3a377681225db9ee25d97e546ba859 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and 4 other resources recovered. https://status.shc.kanagawa.jp/incident/183703 Fri, 10 Mar 2023 16:02:24 -0000 https://status.shc.kanagawa.jp/incident/183703#c2674136b6c79d06b037ae9d1504d0bb9f3a377681225db9ee25d97e546ba859 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and 4 other resources recovered. https://status.shc.kanagawa.jp/incident/183703 Fri, 10 Mar 2023 16:02:24 -0000 https://status.shc.kanagawa.jp/incident/183703#c2674136b6c79d06b037ae9d1504d0bb9f3a377681225db9ee25d97e546ba859 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and 4 other resources recovered. https://status.shc.kanagawa.jp/incident/183703 Fri, 10 Mar 2023 16:02:24 -0000 https://status.shc.kanagawa.jp/incident/183703#c2674136b6c79d06b037ae9d1504d0bb9f3a377681225db9ee25d97e546ba859 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and 4 other resources recovered. https://status.shc.kanagawa.jp/incident/183703 Fri, 10 Mar 2023 15:51:42 -0000 https://status.shc.kanagawa.jp/incident/183703#cf7727f50e0ffb37b106dc4cb8674a4ad98c1710dcda12b68c63adf1a00cb97b NextCloud Maintenance went down. https://status.shc.kanagawa.jp/incident/183703 Fri, 10 Mar 2023 15:43:56 -0000 https://status.shc.kanagawa.jp/incident/183703#fb3c0db94cf5d546d6a524c343d5ded748167129b34e5018ef0b45f1402fbba0 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and 2 other resources went down. https://status.shc.kanagawa.jp/incident/183703 Fri, 10 Mar 2023 15:43:56 -0000 https://status.shc.kanagawa.jp/incident/183703#fb3c0db94cf5d546d6a524c343d5ded748167129b34e5018ef0b45f1402fbba0 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and 2 other resources went down. https://status.shc.kanagawa.jp/incident/183703 Fri, 10 Mar 2023 15:43:56 -0000 https://status.shc.kanagawa.jp/incident/183703#fb3c0db94cf5d546d6a524c343d5ded748167129b34e5018ef0b45f1402fbba0 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and 2 other resources went down. https://status.shc.kanagawa.jp/incident/183703 Fri, 10 Mar 2023 15:43:56 -0000 https://status.shc.kanagawa.jp/incident/183703#fb3c0db94cf5d546d6a524c343d5ded748167129b34e5018ef0b45f1402fbba0 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and 2 other resources went down. https://status.shc.kanagawa.jp/incident/182838 Wed, 08 Mar 2023 14:10:14 -0000 https://status.shc.kanagawa.jp/incident/182838#6fb0ebc9b6e18f5927485ad74d606dfe08d7e9c69946592df09f57f79aa96d19 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/182838 Wed, 08 Mar 2023 13:57:09 -0000 https://status.shc.kanagawa.jp/incident/182838#b70addf6aba84308ac77289e2d21251ee8cbbf92c4cfc2c887b6045b2359132a Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/182838 Wed, 08 Mar 2023 13:06:31 -0000 https://status.shc.kanagawa.jp/incident/182838#93f8780f250d9833ef62d5607df0e053318272432df2e879ec9e8e97fff705ac Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/182838 Wed, 08 Mar 2023 13:06:31 -0000 https://status.shc.kanagawa.jp/incident/182838#93f8780f250d9833ef62d5607df0e053318272432df2e879ec9e8e97fff705ac Activity Relay(relay.shc.kanagawa.jp) and Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/181161 Fri, 03 Mar 2023 18:59:22 -0000 https://status.shc.kanagawa.jp/incident/181161#db0ec11a7ba98b94372aebef9b92cb35669e1fb7a77c356a56be77bccbdb1dda Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/181161 Fri, 03 Mar 2023 18:15:54 -0000 https://status.shc.kanagawa.jp/incident/181161#7d8e27070ba2a981a536b17c47b902008bb36b2c3dd30d1af1f0d47a3fa96dd0 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/179452 Mon, 27 Feb 2023 06:38:08 -0000 https://status.shc.kanagawa.jp/incident/179452#79e9f8d5ae2c1eb7ed944a4109f0dac80e6e8974f19aae481beb96f6108b3c93 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/179452 Mon, 27 Feb 2023 06:33:30 -0000 https://status.shc.kanagawa.jp/incident/179452#dd33b5ac37578e8bc0a7784f650005417de3cb539409215f3aa20fdbecda9b86 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/178538 Fri, 24 Feb 2023 22:45:45 -0000 https://status.shc.kanagawa.jp/incident/178538#af8437393b7ba18dd6328d71e77d0c7d480741998b7a8db64fca692f14e365cb Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/178538 Fri, 24 Feb 2023 22:29:15 -0000 https://status.shc.kanagawa.jp/incident/178538#1bf2fe86e3ed3c4102282539431cd79ac5ef370934b21ff7af4a64139788b4eb Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/178538 Fri, 24 Feb 2023 21:06:43 -0000 https://status.shc.kanagawa.jp/incident/178538#b5500e8fe6a55da6ef2199b57eb2a90172e2dc37b398ea0fcffa054bc3b0ba50 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/178538 Fri, 24 Feb 2023 20:58:14 -0000 https://status.shc.kanagawa.jp/incident/178538#19ddb69885e77621138c7438a5607c8c56f8b5912fc40fcf75d3faf0ab3013f2 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/178538 Fri, 24 Feb 2023 19:33:55 -0000 https://status.shc.kanagawa.jp/incident/178538#d54b498087845b9c36e5a5bc65aba2607faa51ca2e2db0b62d4ced88c88d2779 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/178538 Fri, 24 Feb 2023 19:19:47 -0000 https://status.shc.kanagawa.jp/incident/178538#8e3d640df15576d0025ce69138faf8f3ec4c5238616b83ba18f035dd6f25b545 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/178538 Fri, 24 Feb 2023 17:54:49 -0000 https://status.shc.kanagawa.jp/incident/178538#2ed200b2c08447897014eb94f44446e72334ad8b966dd2056e173dac4ddd8291 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/178538 Fri, 24 Feb 2023 17:22:53 -0000 https://status.shc.kanagawa.jp/incident/178538#f41fb14ef9d7152d961c83418e3a23cc3f13a422dc56f003913fa61aca64fc0a Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/178538 Fri, 24 Feb 2023 15:43:00 -0000 https://status.shc.kanagawa.jp/incident/178538#cd4513094d245c5f7ec0a45d3b1126091a64e398cb42f31d958952aec6d7068e Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/178538 Fri, 24 Feb 2023 15:34:11 -0000 https://status.shc.kanagawa.jp/incident/178538#a7d44f30dfcfc34636c5899b31efd9a9a587b8019d8d3b2cf0dc6fcf03e2f9fb Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/178538 Fri, 24 Feb 2023 14:16:08 -0000 https://status.shc.kanagawa.jp/incident/178538#94a3a40b13ba5128fbe9e4b8e24eb9366ad9ae096d232c27926d86e62f00bbe8 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/178538 Fri, 24 Feb 2023 14:00:45 -0000 https://status.shc.kanagawa.jp/incident/178538#8e9dd3ebc6df8d785a77604adae04e397b279719cdd6470a800e0979cd8aa03d Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/178538 Fri, 24 Feb 2023 03:07:36 -0000 https://status.shc.kanagawa.jp/incident/178538#389e723561614cbb2ae7af5279a424d8bfcb7f893ff363faba40ca3b0338e1f6 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/178538 Fri, 24 Feb 2023 03:03:28 -0000 https://status.shc.kanagawa.jp/incident/178538#8100cafb061a233beefbe9cfe79f0b5d982408ba2deb9859f22692cd69c7e18f Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/178163 Thu, 23 Feb 2023 22:21:24 -0000 https://status.shc.kanagawa.jp/incident/178163#b5b20742da2a7bc0bf238fec75902065fb507463a7ae539c550074f9398a4ab7 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/178163 Thu, 23 Feb 2023 22:13:46 -0000 https://status.shc.kanagawa.jp/incident/178163#0afccff0343b8549f07509082c1ba5073bed7c172534a674b96ece7f4f83d520 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/178163 Thu, 23 Feb 2023 21:33:35 -0000 https://status.shc.kanagawa.jp/incident/178163#78b2882b2070c2a8d2992bf53314d43b7167b05c043d461b871af3adc5448242 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/178163 Thu, 23 Feb 2023 21:15:26 -0000 https://status.shc.kanagawa.jp/incident/178163#db79ba98ee1982bb3e29844fba108f64ed24a4c2ad7d677417cefde76d79a977 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/178163 Thu, 23 Feb 2023 20:33:29 -0000 https://status.shc.kanagawa.jp/incident/178163#44dc401219e65e7ed38f10e5cf4a8c0002bddfa190ea04a818ee98c947f7d237 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/178163 Thu, 23 Feb 2023 20:25:22 -0000 https://status.shc.kanagawa.jp/incident/178163#25b57e3ea26eeaf36deccda60ddbc371e4d89b7f4ddc7928835664c9c49c11ed Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/178163 Thu, 23 Feb 2023 19:48:29 -0000 https://status.shc.kanagawa.jp/incident/178163#75d00fd926e24813c407ed66ffff66d6a747400995656cfa7a2eee44daf5abde Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/178163 Thu, 23 Feb 2023 19:15:34 -0000 https://status.shc.kanagawa.jp/incident/178163#a9e3be7681485680057db188199f34789ad506833dbd998169f40faf02984eea Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/178163 Thu, 23 Feb 2023 18:24:33 -0000 https://status.shc.kanagawa.jp/incident/178163#4d6d148036864a54d134a78f36a72dfbbd46a62633016a5880cb6635f8ac3f9d Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/178163 Thu, 23 Feb 2023 18:07:22 -0000 https://status.shc.kanagawa.jp/incident/178163#92d447215a4d27a8cda95f311ea51980cecf9f873e61bcefaa7e31116786d9e6 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/178163 Thu, 23 Feb 2023 17:57:33 -0000 https://status.shc.kanagawa.jp/incident/178163#23ecfafbd1bf2df2cf39edb6c741049ce712e0787f87362e5df2bc3182536e23 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/178163 Thu, 23 Feb 2023 17:43:00 -0000 https://status.shc.kanagawa.jp/incident/178163#53d9e0e526898cc3750ad8759020e8d9b460a2d2ef4f67334b3d5e33f580ece4 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/178163 Thu, 23 Feb 2023 17:21:26 -0000 https://status.shc.kanagawa.jp/incident/178163#44e30489259d73d829297b41c96643989455d3a897c144e06c0e6e2eaa09699f Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/178163 Thu, 23 Feb 2023 17:01:23 -0000 https://status.shc.kanagawa.jp/incident/178163#e0fb4fcdde09bb314eecdfd8a302b84abb6c2f7057bc14efe0d0c7d5e894e2d6 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/178163 Thu, 23 Feb 2023 16:39:27 -0000 https://status.shc.kanagawa.jp/incident/178163#3c6a9f707db1850733c32f5f3ae44637428f8448db86494195d55e0b91b2fcf6 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/178163 Thu, 23 Feb 2023 16:31:04 -0000 https://status.shc.kanagawa.jp/incident/178163#c3729e5ee8e9f375f29dfff96e0f06e9f7a1e1e82b31c8d4c5cdd201e91afcfe Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/178163 Thu, 23 Feb 2023 16:09:23 -0000 https://status.shc.kanagawa.jp/incident/178163#bc9ed6bbbba039155c10247c9c918154269d93695c848b7b1df38b1434616d7f demo.shc.kanagawa.jp Initialize recovered. https://status.shc.kanagawa.jp/incident/178163 Thu, 23 Feb 2023 14:54:18 -0000 https://status.shc.kanagawa.jp/incident/178163#d317bd5e855e13b0f7c4ac3df1407794aa7895a3f0b8269de295ffaa7d413b99 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/178163 Thu, 23 Feb 2023 14:46:01 -0000 https://status.shc.kanagawa.jp/incident/178163#bc8f0d48594028798a9ca5b8f7ea53fdba45da2a0a85febe119ec1f3fc400bd6 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/178163 Thu, 23 Feb 2023 12:29:09 -0000 https://status.shc.kanagawa.jp/incident/178163#941581ad26529838bcc36f2d83c9b1fa93536e169ac62c648c8de3415d17ad16 demo.shc.kanagawa.jp Initialize went down. https://status.shc.kanagawa.jp/incident/178163 Thu, 23 Feb 2023 12:18:20 -0000 https://status.shc.kanagawa.jp/incident/178163#327ca599b7386076f2d2bfba624b453cee9e33ecb9cdd77cfa5f68abb7e690b4 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/178163 Thu, 23 Feb 2023 12:10:07 -0000 https://status.shc.kanagawa.jp/incident/178163#23c0cdd72a5d7cbd0bc7b991b8a580adee8d096c9547c8fa042c5a30a8059c13 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/178163 Thu, 23 Feb 2023 12:00:35 -0000 https://status.shc.kanagawa.jp/incident/178163#cc0720928140f4955e9b24049c7857c9d44f8568310ea4f7a30a71c100d1555b Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/178163 Thu, 23 Feb 2023 11:40:17 -0000 https://status.shc.kanagawa.jp/incident/178163#2d43cb07a9a6490403318a6c2b86425d1fe7f36a5c72f6714481deabb0b1ac77 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/178163 Thu, 23 Feb 2023 11:21:25 -0000 https://status.shc.kanagawa.jp/incident/178163#0fabe71115f3cfbd80b84acc09b7a609187faa70b2991a3d74262b106a535136 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/178163 Thu, 23 Feb 2023 10:55:14 -0000 https://status.shc.kanagawa.jp/incident/178163#862d468df3a0d492d86a1443313d6bd040e9c3c5a5abbdb48d3f9d93f00ae686 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/178163 Thu, 23 Feb 2023 10:00:44 -0000 https://status.shc.kanagawa.jp/incident/178163#0799da5a49989cb930970b54ecc339c4fe967136aaa7d13716dee045de0b9aa6 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/178163 Thu, 23 Feb 2023 09:45:48 -0000 https://status.shc.kanagawa.jp/incident/178163#f42bbaf72405e2317e8ba78a29cd777fa14045a48766eed327e2540831fc23d9 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/178163 Thu, 23 Feb 2023 09:06:32 -0000 https://status.shc.kanagawa.jp/incident/178163#6f8d10540df4416c5c902a194ae2ef03d52a1afdccebf05266f69440bc8b3dc0 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/178163 Thu, 23 Feb 2023 08:52:04 -0000 https://status.shc.kanagawa.jp/incident/178163#fba22888dedc7c9f8b8c63fc73984dbae5948ce7ee862b0e6d16afec03800dfb Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/178163 Thu, 23 Feb 2023 08:45:26 -0000 https://status.shc.kanagawa.jp/incident/178163#6cba586d57b79aa68aea8a4247157a6e3e93b71bad1451059947f381de04802a Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/178163 Thu, 23 Feb 2023 08:34:02 -0000 https://status.shc.kanagawa.jp/incident/178163#9bdf356b1b2bf11da8f72b69ef6072033e758d233a95fcfbf80acbf85f660e13 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/178163 Thu, 23 Feb 2023 08:12:28 -0000 https://status.shc.kanagawa.jp/incident/178163#9409d186a6ac6b9c1938dcea0484f52d5c9db496a21796f140b7bde20dd0b080 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/178163 Thu, 23 Feb 2023 07:51:57 -0000 https://status.shc.kanagawa.jp/incident/178163#323b85ce19985bb638a14bd6037c377b6d5f1022f24343f0be1bae7f194aba4f Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/178163 Thu, 23 Feb 2023 03:48:17 -0000 https://status.shc.kanagawa.jp/incident/178163#91c729f6072d964aa07d2fa9d76f5ad396edd97a90c32d5d4588f6b6c24bf604 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/178163 Thu, 23 Feb 2023 03:31:00 -0000 https://status.shc.kanagawa.jp/incident/178163#13c8235aa4a14a929adfe4287a67f0c920c57af2733ae4c706e74335350177f4 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/177942 Wed, 22 Feb 2023 23:03:16 -0000 https://status.shc.kanagawa.jp/incident/177942#eceda7e27a8ec5035c9a10cdc095932862c9523482ca5bc050e8ca00136e0210 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/177942 Wed, 22 Feb 2023 22:55:09 -0000 https://status.shc.kanagawa.jp/incident/177942#bd57713886113eff045fdb9f75802ac4348d3ff253dc3b236bd87abbcb19831c Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/177942 Wed, 22 Feb 2023 22:36:22 -0000 https://status.shc.kanagawa.jp/incident/177942#5dcab08778c9cc5bf5153e48a3277ab0abab9d995ff3fe8df37e5d3e4b8724b2 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/177942 Wed, 22 Feb 2023 22:16:02 -0000 https://status.shc.kanagawa.jp/incident/177942#c84a82534b6a7bd55cea4334d1e23879d327b2cf2b88149e01a7cdb3edf828a2 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/177942 Wed, 22 Feb 2023 21:15:30 -0000 https://status.shc.kanagawa.jp/incident/177942#227b3b7aef6fa119b8f52a2ebe2d01413da5ca7b841058a2ad9e0ef74a345b5c Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/177942 Wed, 22 Feb 2023 20:42:54 -0000 https://status.shc.kanagawa.jp/incident/177942#4db870a63600e5774f1b901e2667cdc0f3691448ee4285bce142433875d41d7c Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/177942 Wed, 22 Feb 2023 20:33:18 -0000 https://status.shc.kanagawa.jp/incident/177942#93a2ba8451ecd6d297083835e25503047f7476f49ece14dfd7bb13c8940b0ef6 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/177942 Wed, 22 Feb 2023 20:22:16 -0000 https://status.shc.kanagawa.jp/incident/177942#d319dd017e7c0f5c84716dde018523d567e674fbbb77467289beaeaef9ff371e Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/177942 Wed, 22 Feb 2023 18:09:27 -0000 https://status.shc.kanagawa.jp/incident/177942#ab28cf9daf105c67bb2f3483097a3a43b0a3dfb056bde3b1a5b5ba486d013f88 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/177942 Wed, 22 Feb 2023 18:00:53 -0000 https://status.shc.kanagawa.jp/incident/177942#5637bb8f542fd7adc0d27abc6bea74d955fcab011aed804a3dab0e55efe797fb Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/177942 Wed, 22 Feb 2023 16:09:28 -0000 https://status.shc.kanagawa.jp/incident/177942#79704821d4e2f5e8d65960f03a8ff32ed38b1238fd251049d6d41476825a79cf Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/177942 Wed, 22 Feb 2023 15:57:16 -0000 https://status.shc.kanagawa.jp/incident/177942#db93131c2b81bdd44b93c7b994b13031fb1e978481d6387968e69081549f51dd Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/177942 Wed, 22 Feb 2023 15:18:16 -0000 https://status.shc.kanagawa.jp/incident/177942#a34dd16c15dac5a4078b2adbf325d188094c08c192096f902c41059fbb349f40 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/177942 Wed, 22 Feb 2023 14:54:12 -0000 https://status.shc.kanagawa.jp/incident/177942#cdedc838ea478adcf153829f02337e374fa50d267d6bcb5e7d71b392d044591a Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/177942 Wed, 22 Feb 2023 14:06:26 -0000 https://status.shc.kanagawa.jp/incident/177942#3e4de24ea8f299e8dfc8a2d62b15c8e268d5436a74fae7a0c05aa0132dc29901 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/177942 Wed, 22 Feb 2023 13:49:17 -0000 https://status.shc.kanagawa.jp/incident/177942#0f3382ce37b10bf2b3d0cc7181279cd5811c52b2152c71b049e6423a1a17f8c6 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/177491 Tue, 21 Feb 2023 23:04:59 -0000 https://status.shc.kanagawa.jp/incident/177491#9df66edc158ef84e2b00e45d73bfdd059fb713e4759cdcdd9c13eacf362dca10 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/177491 Tue, 21 Feb 2023 22:41:31 -0000 https://status.shc.kanagawa.jp/incident/177491#600560834565ccaecbdf3e6e1695afd7d0016f9df788ffb259fb421cc3ec8107 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/177491 Tue, 21 Feb 2023 21:52:32 -0000 https://status.shc.kanagawa.jp/incident/177491#62fbdb72454e41e57d149f1559a10e5ae6f11f253473f6407e48d4af16c598f0 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/177491 Tue, 21 Feb 2023 21:43:59 -0000 https://status.shc.kanagawa.jp/incident/177491#0b6dc2f2ab573a7d4e79db958fd07b8c9c2796b9d0dc42a91b8f311e8da87828 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/177491 Tue, 21 Feb 2023 21:20:05 -0000 https://status.shc.kanagawa.jp/incident/177491#a623c9acbf934946b06669fbb6c6793cb538babd1927d38716b421f3983b4f78 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/177491 Tue, 21 Feb 2023 21:16:32 -0000 https://status.shc.kanagawa.jp/incident/177491#7f93462102ede900f6e45f94f3b651f70ebf88c9b1edb538fb3180bc7dc40efe Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/177491 Tue, 21 Feb 2023 19:53:08 -0000 https://status.shc.kanagawa.jp/incident/177491#bbe76568363ddf7e09705cfc396e4d78ecde71f5c670cdd1007a1fa157f5e53e Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/177491 Tue, 21 Feb 2023 19:48:58 -0000 https://status.shc.kanagawa.jp/incident/177491#8843ba7f40a03298477ee2629ac89ee0b9ec675299fe6ee8f691d2c33e94d2f0 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/177491 Tue, 21 Feb 2023 18:49:02 -0000 https://status.shc.kanagawa.jp/incident/177491#0f2c7e1e1454e7548c6cc62f6cddc4b41e070fa61207d0aa2cc33874a41a6f48 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/177491 Tue, 21 Feb 2023 18:22:54 -0000 https://status.shc.kanagawa.jp/incident/177491#23a9df13fe7e94d07e7412c2a126e0fec4ad84170ef08b37d69f42d5a44699ea Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/177491 Tue, 21 Feb 2023 13:55:07 -0000 https://status.shc.kanagawa.jp/incident/177491#7e53798b9143c260362dcfe8c1c45ba08fce67480c8cd5420044b22a0341cede Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/177491 Tue, 21 Feb 2023 13:34:41 -0000 https://status.shc.kanagawa.jp/incident/177491#7fea842d376c1cd3241aa5fbf5f3a18c18654e473dcda3a47a1d921ae05600a6 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/177491 Tue, 21 Feb 2023 13:15:50 -0000 https://status.shc.kanagawa.jp/incident/177491#5278a9951525c7d67c9f3a8ab92878bd1f84ba94525e4eaf562db4fb2333faab Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/177491 Tue, 21 Feb 2023 13:07:27 -0000 https://status.shc.kanagawa.jp/incident/177491#bce18aeeb988b9e528f6f829ba00d037f24257ca47789389f70e17e00c620fd4 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/177491 Tue, 21 Feb 2023 12:57:42 -0000 https://status.shc.kanagawa.jp/incident/177491#e4cb65c4a03cbdeeeba3f09124580313d9e888565b2f47673d42edd27bcf71af Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/177491 Tue, 21 Feb 2023 12:46:23 -0000 https://status.shc.kanagawa.jp/incident/177491#c17b2d324b22148f8740ddb52b777ecdb37ccd16f1774e10a59fb7bb3d4402b4 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/177491 Tue, 21 Feb 2023 11:39:42 -0000 https://status.shc.kanagawa.jp/incident/177491#7cf525eaa4936996ee65dd1b598bceefd6758e029b7a3dc8b6135526e17c6fd1 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/177491 Tue, 21 Feb 2023 11:12:40 -0000 https://status.shc.kanagawa.jp/incident/177491#15e6ff08a167ce8a8c770dcd73775cff11345c2539603e9a40a7e89c84fdf20e Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/177491 Tue, 21 Feb 2023 11:06:55 -0000 https://status.shc.kanagawa.jp/incident/177491#c1fd33e65c99e06e16fe1059ce3b79a6d05b7db0cd22e368acccda1759bc8551 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/177491 Tue, 21 Feb 2023 10:49:28 -0000 https://status.shc.kanagawa.jp/incident/177491#20cda41220847df527bfbbd01a70a0cacc0124df3c6fe5155c0667108ee0e4ec Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/177491 Tue, 21 Feb 2023 08:58:07 -0000 https://status.shc.kanagawa.jp/incident/177491#9100cb872c215d08cb3d4d0795d94a2cb1fe060c9cb9eecc8df2febd9cad3395 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/177491 Tue, 21 Feb 2023 08:48:25 -0000 https://status.shc.kanagawa.jp/incident/177491#7dac617274b69fc1fa2990ddf4334d3f23c46420aa264ed1663e8d14b60f723d Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/177222 Mon, 20 Feb 2023 21:12:22 -0000 https://status.shc.kanagawa.jp/incident/177222#e75cfb6f9258c33bd7c5413ab53b1fdb644444e383ac8dbacb29c287fe06e1b7 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/177222 Mon, 20 Feb 2023 21:00:49 -0000 https://status.shc.kanagawa.jp/incident/177222#c65d55ddd334ae707e8bd88c877b921db40587be7a8712e4e31152de5d791f5c Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/177222 Mon, 20 Feb 2023 20:18:34 -0000 https://status.shc.kanagawa.jp/incident/177222#27abcb7ccdce2a18d9935bb42fe63493c957038a2a6c6007077d362a46e51b5e Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/177222 Mon, 20 Feb 2023 20:06:40 -0000 https://status.shc.kanagawa.jp/incident/177222#66f12b2d6ce611b6a049b03c2bb1090c0fed70fa3dce564d0f4b9c85e680f879 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/177222 Mon, 20 Feb 2023 19:58:27 -0000 https://status.shc.kanagawa.jp/incident/177222#ff59b67e893fcc291068ce9a1fc94a123ccc1cdc5e874c54047bdc0cf4547216 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/177222 Mon, 20 Feb 2023 19:54:30 -0000 https://status.shc.kanagawa.jp/incident/177222#06830044180e07b523ba670f1efa7788c9992faf180b2b2fa7c9526ecc322650 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/177222 Mon, 20 Feb 2023 18:33:49 -0000 https://status.shc.kanagawa.jp/incident/177222#f220d0b817ce1230eee68395b2fbea3138f318f97a9819b0246c020147c68482 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/177222 Mon, 20 Feb 2023 18:30:21 -0000 https://status.shc.kanagawa.jp/incident/177222#f040049ae35a143d827b2749cd25e6868fb5f12f7161c86d2a5109ee63888282 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/177222 Mon, 20 Feb 2023 17:27:31 -0000 https://status.shc.kanagawa.jp/incident/177222#11faf3ebec8c64af1253175faf3b4f70602b963cf2fdb57e84e55396932de66d Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/177222 Mon, 20 Feb 2023 17:12:47 -0000 https://status.shc.kanagawa.jp/incident/177222#fcf11b09d50121dd49b55487eb6534022d0ccdf9d2881a75beacee27545ba54d Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/177222 Mon, 20 Feb 2023 15:45:34 -0000 https://status.shc.kanagawa.jp/incident/177222#0fd0ed9565edd725b59a53923bd3a74b59d4605c27bc352bf5b6c9eaa2b62b42 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/177222 Mon, 20 Feb 2023 15:37:36 -0000 https://status.shc.kanagawa.jp/incident/177222#4b5eec64e35fc9b07871f9ee10ecef9681d96aa1afcb408ccb53f52ab7158201 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/177222 Mon, 20 Feb 2023 15:21:26 -0000 https://status.shc.kanagawa.jp/incident/177222#9989e83e52a964af526782ffb78d686457fe8f0f944c5ba29ceca2179f144b88 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/177222 Mon, 20 Feb 2023 15:09:24 -0000 https://status.shc.kanagawa.jp/incident/177222#5ea7e3bf0224c830607ecbf5285bda9fa463c2416d93cbde7fc252bc620eda44 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/177222 Mon, 20 Feb 2023 14:45:04 -0000 https://status.shc.kanagawa.jp/incident/177222#49f093c40540b7002e3fcda81285da2ce8ce649e22609ce493f7a71200b42f14 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/177222 Mon, 20 Feb 2023 14:23:50 -0000 https://status.shc.kanagawa.jp/incident/177222#fa946f124ed60baea70e237da22c20abe61a29f7e708da92ac5ee6158e262ef9 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/176364 Fri, 17 Feb 2023 23:09:59 -0000 https://status.shc.kanagawa.jp/incident/176364#f4168b4e863be9429c6cd22c339d7ae7665f35cfe4e555d0f426c077092cad41 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/176364 Fri, 17 Feb 2023 17:47:11 -0000 https://status.shc.kanagawa.jp/incident/176364#34e51d76b644a796d917dcbed5eb343889ca3435e474af3e0804d14bb9bab628 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/175418 Wed, 15 Feb 2023 10:42:00 -0000 https://status.shc.kanagawa.jp/incident/175418#12de9b40ee2f5ebc47bc96bc776ca0cdc685552d3caaf6df6d0edce5230d4b2e Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/175418 Wed, 15 Feb 2023 08:42:02 -0000 https://status.shc.kanagawa.jp/incident/175418#527ff520cd5ae7802063bfda862aba81844806a4cd5f3ae6dc827c0b7a9aaec9 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/175116 Tue, 14 Feb 2023 23:06:16 -0000 https://status.shc.kanagawa.jp/incident/175116#9a22489e52654a2fcbd08ea4c41e57e942d86c4ee0544f55efaeda85d58431d5 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/175116 Tue, 14 Feb 2023 22:44:48 -0000 https://status.shc.kanagawa.jp/incident/175116#654a36ae77a8c2c3cd7791dcbe08b91254bcee1d2711b19fe53244a8a96776ea Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/175116 Tue, 14 Feb 2023 12:41:03 -0000 https://status.shc.kanagawa.jp/incident/175116#d0d965b045201095012b15e737709246f7387528b3896c8431d0451dce15e0c9 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/175116 Tue, 14 Feb 2023 11:26:03 -0000 https://status.shc.kanagawa.jp/incident/175116#dc39d5eb97725d39a84b7e1c94bd1d88b7fb6c927ef62440ca5ced94e8316e0e Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/174380 Sun, 12 Feb 2023 11:49:56 -0000 https://status.shc.kanagawa.jp/incident/174380#b11255b985522833ed757e125fc278acf51947f0bf872823ef7009dce2130e36 Pleroma(pr.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/174380 Sun, 12 Feb 2023 11:49:56 -0000 https://status.shc.kanagawa.jp/incident/174380#b11255b985522833ed757e125fc278acf51947f0bf872823ef7009dce2130e36 Pleroma(pr.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/174380 Sun, 12 Feb 2023 11:49:56 -0000 https://status.shc.kanagawa.jp/incident/174380#b11255b985522833ed757e125fc278acf51947f0bf872823ef7009dce2130e36 Pleroma(pr.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/174380 Sun, 12 Feb 2023 11:48:54 -0000 https://status.shc.kanagawa.jp/incident/174380#27bb526bc68bee206713dfc39e0fdf9a54ee00d22b3868d7ab6419a7f942dd41 Misskey(mk.shc.kanagawa.jp) went down and NextCloud (cloud.shc.kanagawa.jp) and Moodle (lms.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/174380 Sun, 12 Feb 2023 11:48:54 -0000 https://status.shc.kanagawa.jp/incident/174380#27bb526bc68bee206713dfc39e0fdf9a54ee00d22b3868d7ab6419a7f942dd41 Misskey(mk.shc.kanagawa.jp) went down and NextCloud (cloud.shc.kanagawa.jp) and Moodle (lms.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/174380 Sun, 12 Feb 2023 11:42:54 -0000 https://status.shc.kanagawa.jp/incident/174380#20060d24568e54078b29bea9c8246dd6861e50b0426b3b7d1191071ab52658c8 Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/174380 Sun, 12 Feb 2023 11:36:56 -0000 https://status.shc.kanagawa.jp/incident/174380#aaec6c3dfb192bc70ee779663675651bc54ba481e3bf220e61af5691fef19c10 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/174380 Sun, 12 Feb 2023 11:16:48 -0000 https://status.shc.kanagawa.jp/incident/174380#dc52379d604c1cc76406a72dbf86d92b900155e946f27ccdd0c9f53b03c7123d Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/174380 Sun, 12 Feb 2023 11:01:44 -0000 https://status.shc.kanagawa.jp/incident/174380#990dade046b1c3d7159e306943f272493f7fcd582f719af125aebb2e8343df84 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Activity Relay(relay.shc.kanagawa.jp), and 2 other resources went down. https://status.shc.kanagawa.jp/incident/174380 Sun, 12 Feb 2023 11:01:44 -0000 https://status.shc.kanagawa.jp/incident/174380#990dade046b1c3d7159e306943f272493f7fcd582f719af125aebb2e8343df84 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Activity Relay(relay.shc.kanagawa.jp), and 2 other resources went down. https://status.shc.kanagawa.jp/incident/174380 Sun, 12 Feb 2023 11:01:44 -0000 https://status.shc.kanagawa.jp/incident/174380#990dade046b1c3d7159e306943f272493f7fcd582f719af125aebb2e8343df84 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Activity Relay(relay.shc.kanagawa.jp), and 2 other resources went down. https://status.shc.kanagawa.jp/incident/174380 Sun, 12 Feb 2023 11:01:44 -0000 https://status.shc.kanagawa.jp/incident/174380#990dade046b1c3d7159e306943f272493f7fcd582f719af125aebb2e8343df84 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Activity Relay(relay.shc.kanagawa.jp), and 2 other resources went down. https://status.shc.kanagawa.jp/incident/174380 Sun, 12 Feb 2023 10:08:36 -0000 https://status.shc.kanagawa.jp/incident/174380#9f5eaaedee7ff3302dd0835ba033665c9e2923ae18e2fc0cffc6471ec3d697ae Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Activity Relay(relay.shc.kanagawa.jp), and 2 other resources recovered. https://status.shc.kanagawa.jp/incident/174380 Sun, 12 Feb 2023 10:08:36 -0000 https://status.shc.kanagawa.jp/incident/174380#9f5eaaedee7ff3302dd0835ba033665c9e2923ae18e2fc0cffc6471ec3d697ae Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Activity Relay(relay.shc.kanagawa.jp), and 2 other resources recovered. https://status.shc.kanagawa.jp/incident/174380 Sun, 12 Feb 2023 10:08:36 -0000 https://status.shc.kanagawa.jp/incident/174380#9f5eaaedee7ff3302dd0835ba033665c9e2923ae18e2fc0cffc6471ec3d697ae Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Activity Relay(relay.shc.kanagawa.jp), and 2 other resources recovered. https://status.shc.kanagawa.jp/incident/174380 Sun, 12 Feb 2023 10:08:36 -0000 https://status.shc.kanagawa.jp/incident/174380#9f5eaaedee7ff3302dd0835ba033665c9e2923ae18e2fc0cffc6471ec3d697ae Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Activity Relay(relay.shc.kanagawa.jp), and 2 other resources recovered. https://status.shc.kanagawa.jp/incident/174380 Sun, 12 Feb 2023 10:03:19 -0000 https://status.shc.kanagawa.jp/incident/174380#205e0ef6c253702d52e61b4d873a363d59efedbc5cd740b1fdea02cca818b004 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/174380 Sun, 12 Feb 2023 10:01:09 -0000 https://status.shc.kanagawa.jp/incident/174380#11ae60533a738fb60006fb3243a72d827f81b6964d9b3781255b10ac051a04dc Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and 3 other resources went down. https://status.shc.kanagawa.jp/incident/174380 Sun, 12 Feb 2023 10:01:09 -0000 https://status.shc.kanagawa.jp/incident/174380#11ae60533a738fb60006fb3243a72d827f81b6964d9b3781255b10ac051a04dc Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and 3 other resources went down. https://status.shc.kanagawa.jp/incident/174380 Sun, 12 Feb 2023 10:01:09 -0000 https://status.shc.kanagawa.jp/incident/174380#11ae60533a738fb60006fb3243a72d827f81b6964d9b3781255b10ac051a04dc Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and 3 other resources went down. https://status.shc.kanagawa.jp/incident/174380 Sun, 12 Feb 2023 10:01:09 -0000 https://status.shc.kanagawa.jp/incident/174380#11ae60533a738fb60006fb3243a72d827f81b6964d9b3781255b10ac051a04dc Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and 3 other resources went down. https://status.shc.kanagawa.jp/incident/174380 Sun, 12 Feb 2023 10:01:09 -0000 https://status.shc.kanagawa.jp/incident/174380#11ae60533a738fb60006fb3243a72d827f81b6964d9b3781255b10ac051a04dc Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and 3 other resources went down. https://status.shc.kanagawa.jp/incident/174380 Sun, 12 Feb 2023 08:49:04 -0000 https://status.shc.kanagawa.jp/incident/174380#ad7c1106a8122e093b004a98bd476df01acb037ba74c940bb44225daa650ff3d Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Activity Relay(relay.shc.kanagawa.jp), and 2 other resources recovered. https://status.shc.kanagawa.jp/incident/174380 Sun, 12 Feb 2023 08:49:04 -0000 https://status.shc.kanagawa.jp/incident/174380#ad7c1106a8122e093b004a98bd476df01acb037ba74c940bb44225daa650ff3d Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Activity Relay(relay.shc.kanagawa.jp), and 2 other resources recovered. https://status.shc.kanagawa.jp/incident/174380 Sun, 12 Feb 2023 08:49:04 -0000 https://status.shc.kanagawa.jp/incident/174380#ad7c1106a8122e093b004a98bd476df01acb037ba74c940bb44225daa650ff3d Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Activity Relay(relay.shc.kanagawa.jp), and 2 other resources recovered. https://status.shc.kanagawa.jp/incident/174380 Sun, 12 Feb 2023 08:49:04 -0000 https://status.shc.kanagawa.jp/incident/174380#ad7c1106a8122e093b004a98bd476df01acb037ba74c940bb44225daa650ff3d Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Activity Relay(relay.shc.kanagawa.jp), and 2 other resources recovered. https://status.shc.kanagawa.jp/incident/174380 Sun, 12 Feb 2023 08:37:33 -0000 https://status.shc.kanagawa.jp/incident/174380#d481be952cadff007439b2d352ec342e8d448d01a71a5435c3fe47d97e0c6885 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/174380 Sun, 12 Feb 2023 08:19:15 -0000 https://status.shc.kanagawa.jp/incident/174380#0940d8e661c819722e1db75603606076ac8097382c0781ccfa522ee23d73d454 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/174380 Sun, 12 Feb 2023 08:10:55 -0000 https://status.shc.kanagawa.jp/incident/174380#af02c8c3f5365c050fd775da9f01806e020ff59446a819a17f3d0f1b1dfb5825 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Activity Relay(relay.shc.kanagawa.jp), and 2 other resources went down. https://status.shc.kanagawa.jp/incident/174380 Sun, 12 Feb 2023 08:10:55 -0000 https://status.shc.kanagawa.jp/incident/174380#af02c8c3f5365c050fd775da9f01806e020ff59446a819a17f3d0f1b1dfb5825 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Activity Relay(relay.shc.kanagawa.jp), and 2 other resources went down. https://status.shc.kanagawa.jp/incident/174380 Sun, 12 Feb 2023 08:10:55 -0000 https://status.shc.kanagawa.jp/incident/174380#af02c8c3f5365c050fd775da9f01806e020ff59446a819a17f3d0f1b1dfb5825 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Activity Relay(relay.shc.kanagawa.jp), and 2 other resources went down. https://status.shc.kanagawa.jp/incident/174380 Sun, 12 Feb 2023 08:10:55 -0000 https://status.shc.kanagawa.jp/incident/174380#af02c8c3f5365c050fd775da9f01806e020ff59446a819a17f3d0f1b1dfb5825 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Activity Relay(relay.shc.kanagawa.jp), and 2 other resources went down. https://status.shc.kanagawa.jp/incident/173794 Fri, 10 Feb 2023 15:50:47 -0000 https://status.shc.kanagawa.jp/incident/173794#55a661ad7bbe42427143745804f939f5858919609be4cef07ac11a16879c9895 demo.shc.kanagawa.jp Initialize recovered. https://status.shc.kanagawa.jp/incident/173794 Fri, 10 Feb 2023 15:32:03 -0000 https://status.shc.kanagawa.jp/incident/173794#5fc0f15e10b4c7a9b95ee954da66450833e22f27dab36975c01281fbdc16d474 Pleroma(pr.shc.kanagawa.jp) and Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/173794 Fri, 10 Feb 2023 15:32:03 -0000 https://status.shc.kanagawa.jp/incident/173794#5fc0f15e10b4c7a9b95ee954da66450833e22f27dab36975c01281fbdc16d474 Pleroma(pr.shc.kanagawa.jp) and Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/173794 Fri, 10 Feb 2023 15:29:03 -0000 https://status.shc.kanagawa.jp/incident/173794#c3afb891ae7f4acc8506fd48fdbfc59f8558e98e84dc9d38735d36ba10b219d0 Pleroma(pr.shc.kanagawa.jp), Activity Relay(relay.shc.kanagawa.jp), and demo.shc.kanagawa.jp Initialize went down. https://status.shc.kanagawa.jp/incident/173794 Fri, 10 Feb 2023 15:29:03 -0000 https://status.shc.kanagawa.jp/incident/173794#c3afb891ae7f4acc8506fd48fdbfc59f8558e98e84dc9d38735d36ba10b219d0 Pleroma(pr.shc.kanagawa.jp), Activity Relay(relay.shc.kanagawa.jp), and demo.shc.kanagawa.jp Initialize went down. https://status.shc.kanagawa.jp/incident/173794 Fri, 10 Feb 2023 15:29:03 -0000 https://status.shc.kanagawa.jp/incident/173794#c3afb891ae7f4acc8506fd48fdbfc59f8558e98e84dc9d38735d36ba10b219d0 Pleroma(pr.shc.kanagawa.jp), Activity Relay(relay.shc.kanagawa.jp), and demo.shc.kanagawa.jp Initialize went down. https://status.shc.kanagawa.jp/incident/172083 Mon, 06 Feb 2023 06:36:31 -0000 https://status.shc.kanagawa.jp/incident/172083#567a4904ffc2efcd1ee363aaa65715b6137a086b0dd178ed83ab0fcc575c3eab Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/172083 Mon, 06 Feb 2023 06:13:08 -0000 https://status.shc.kanagawa.jp/incident/172083#d262b0e87ff3924d4925336dbea4a954b247fddac73a654d8f15aed89b20dd6c Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/171555 Sat, 04 Feb 2023 11:17:48 -0000 https://status.shc.kanagawa.jp/incident/171555#48367ee1560e6cb7cfba19fcff0342b4c90277d932dc5f74db1fe7ffd604f8eb Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/171555 Sat, 04 Feb 2023 11:11:43 -0000 https://status.shc.kanagawa.jp/incident/171555#c5be21f19f49a7181d7902380aa4ae1f880b371fc6af2af36ca5070cb7ebf964 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/170820 Thu, 02 Feb 2023 08:24:46 -0000 https://status.shc.kanagawa.jp/incident/170820#f6509de5998166a0566edfe84a09159c9e9b7544424c4e036cffa1415e53a6a9 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/170820 Thu, 02 Feb 2023 07:40:35 -0000 https://status.shc.kanagawa.jp/incident/170820#8a0fc428aacc864c379196a7f3d8065937828be01f08984b0d7c301c59719eae Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/169400 Mon, 30 Jan 2023 10:14:30 -0000 https://status.shc.kanagawa.jp/incident/169400#e92e714c50b96fa22113d3071957a7a93a8d6303ca57d63f3fed6c767b02d6eb Internet Relay Chat (irc.shc.kanagawa.jp) and Internet Relay Chat Web (webirc.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/169400 Mon, 30 Jan 2023 10:14:30 -0000 https://status.shc.kanagawa.jp/incident/169400#e92e714c50b96fa22113d3071957a7a93a8d6303ca57d63f3fed6c767b02d6eb Internet Relay Chat (irc.shc.kanagawa.jp) and Internet Relay Chat Web (webirc.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/169400 Mon, 30 Jan 2023 10:12:32 -0000 https://status.shc.kanagawa.jp/incident/169400#ea191514ebe05629dd9ef4eb9436b771e70c93780f200c16081b218acc05e2ec Internet Relay Chat (irc.shc.kanagawa.jp) and Internet Relay Chat Web (webirc.shc.kanagawa.jp) went down and Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/169400 Mon, 30 Jan 2023 10:12:32 -0000 https://status.shc.kanagawa.jp/incident/169400#ea191514ebe05629dd9ef4eb9436b771e70c93780f200c16081b218acc05e2ec Internet Relay Chat (irc.shc.kanagawa.jp) and Internet Relay Chat Web (webirc.shc.kanagawa.jp) went down and Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/169400 Mon, 30 Jan 2023 10:12:32 -0000 https://status.shc.kanagawa.jp/incident/169400#ea191514ebe05629dd9ef4eb9436b771e70c93780f200c16081b218acc05e2ec Internet Relay Chat (irc.shc.kanagawa.jp) and Internet Relay Chat Web (webirc.shc.kanagawa.jp) went down and Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/169400 Mon, 30 Jan 2023 01:45:53 -0000 https://status.shc.kanagawa.jp/incident/169400#0e54d83c6249a1d85a1cc6afcd6684851e69614fbac8eaa7554740f95c753966 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/169400 Mon, 30 Jan 2023 01:39:27 -0000 https://status.shc.kanagawa.jp/incident/169400#11f639ff0e28de2b157a756770dd4a34c5088d02df04e184224a9cd66758329e Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/169400 Sun, 29 Jan 2023 20:41:49 -0000 https://status.shc.kanagawa.jp/incident/169400#a4ed4ec2ea96dc63043697736b2ecffcfa1baf9b84ef4bc23abbf604e51d6160 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/169400 Sun, 29 Jan 2023 20:36:44 -0000 https://status.shc.kanagawa.jp/incident/169400#0573ed6f1bc86a632a494c5b3fdb7bcb45de93b64a90aa75b5ec8814da20ae70 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/169400 Sun, 29 Jan 2023 20:33:17 -0000 https://status.shc.kanagawa.jp/incident/169400#17f118c990660f3f2e4f03c39c9a504eadc5aab9217fd87f330ff0fdec138897 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/169400 Sun, 29 Jan 2023 20:27:53 -0000 https://status.shc.kanagawa.jp/incident/169400#e741a45011efd7d831ee97ea2658245fe87435cb47f5aa4f8cd13ea2ee00cf1b Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/169400 Sun, 29 Jan 2023 20:23:56 -0000 https://status.shc.kanagawa.jp/incident/169400#f8c89c93b1451e84b99f07e9eee68af595a976a3368f59aab46da3eda3e4a948 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/169400 Sun, 29 Jan 2023 17:51:06 -0000 https://status.shc.kanagawa.jp/incident/169400#5f995dbe22305b3c8d94e85c13298d81338ddf47c0db856e787d4c3d79d448ef Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/169400 Sun, 29 Jan 2023 17:12:24 -0000 https://status.shc.kanagawa.jp/incident/169400#6b7c2c2f3ac418425f0babfe7ca9a85ee7b2f980be1d15970d90ed5ba377d88d Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/169400 Sun, 29 Jan 2023 16:43:00 -0000 https://status.shc.kanagawa.jp/incident/169400#c99ecfbfd36fcb72bd7c307fcef818313a5941b7e49d86b2793dc48ee0b48306 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/169400 Sun, 29 Jan 2023 16:38:49 -0000 https://status.shc.kanagawa.jp/incident/169400#89da7b2214b4363338f14f1a85b0a5dd66ea9106095b8839a766494c24bafc07 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/169400 Sun, 29 Jan 2023 06:09:16 -0000 https://status.shc.kanagawa.jp/incident/169400#c840e611b4173947993043d9b3c2f6ca63b126b862a71a0a957d113af4033650 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/169400 Sun, 29 Jan 2023 06:02:56 -0000 https://status.shc.kanagawa.jp/incident/169400#d5b42693129669b0cc3e0a3bc5e71f3515633c736828d6e88cbf0e9b2756396c Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/169242 Sat, 28 Jan 2023 18:29:37 -0000 https://status.shc.kanagawa.jp/incident/169242#7f061fdfe98d0b6b84c7df4abd72506eb1627e8f25e42cfab6f13f59a94036dd Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/169242 Sat, 28 Jan 2023 18:20:38 -0000 https://status.shc.kanagawa.jp/incident/169242#85904312c1374b325f93965505d2dfb24da18d705eb589a49fda6aeea2fc4f86 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/168623 Thu, 26 Jan 2023 18:09:51 -0000 https://status.shc.kanagawa.jp/incident/168623#6200dc49fefc3541281de57b6a8ca71acd0f3a6df44eb49f8e529a68149d0488 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/168623 Thu, 26 Jan 2023 18:08:22 -0000 https://status.shc.kanagawa.jp/incident/168623#4bf035ce5d31a0c857ee2530569a001e6fc8007016851c04232f2999796ffce6 Misskey(mk.shc.kanagawa.jp) and MongoDB Repliction recovered. https://status.shc.kanagawa.jp/incident/168623 Thu, 26 Jan 2023 18:07:27 -0000 https://status.shc.kanagawa.jp/incident/168623#f257f15afb3159ba68ffc099bf13649d73d96e18f214ff7a2c63d444568a6c65 Internet Relay Chat (irc.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/168623 Thu, 26 Jan 2023 18:05:44 -0000 https://status.shc.kanagawa.jp/incident/168623#49f282fa2a1ca9da8678b1ec477cd9426b2bb01c2baea772c65fd4362e6b2531 Activity Relay(relay.shc.kanagawa.jp), Pub-Relay(pub-relay.shc.kanagawa.jp), and Internet Relay Chat Web (webirc.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/168623 Thu, 26 Jan 2023 18:05:44 -0000 https://status.shc.kanagawa.jp/incident/168623#49f282fa2a1ca9da8678b1ec477cd9426b2bb01c2baea772c65fd4362e6b2531 Activity Relay(relay.shc.kanagawa.jp), Pub-Relay(pub-relay.shc.kanagawa.jp), and Internet Relay Chat Web (webirc.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/168623 Thu, 26 Jan 2023 18:05:44 -0000 https://status.shc.kanagawa.jp/incident/168623#49f282fa2a1ca9da8678b1ec477cd9426b2bb01c2baea772c65fd4362e6b2531 Activity Relay(relay.shc.kanagawa.jp), Pub-Relay(pub-relay.shc.kanagawa.jp), and Internet Relay Chat Web (webirc.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/168623 Thu, 26 Jan 2023 18:04:37 -0000 https://status.shc.kanagawa.jp/incident/168623#4c4ec51e954f05a6bf00ee0a52e9e4f95c118899414010c5975840cb196e9049 Misskey(mk.shc.kanagawa.jp), Activity Relay(relay.shc.kanagawa.jp), Pub-Relay(pub-relay.shc.kanagawa.jp), and 5 other resources went down. https://status.shc.kanagawa.jp/incident/168623 Thu, 26 Jan 2023 18:04:37 -0000 https://status.shc.kanagawa.jp/incident/168623#4c4ec51e954f05a6bf00ee0a52e9e4f95c118899414010c5975840cb196e9049 Misskey(mk.shc.kanagawa.jp), Activity Relay(relay.shc.kanagawa.jp), Pub-Relay(pub-relay.shc.kanagawa.jp), and 5 other resources went down. https://status.shc.kanagawa.jp/incident/168623 Thu, 26 Jan 2023 18:04:37 -0000 https://status.shc.kanagawa.jp/incident/168623#4c4ec51e954f05a6bf00ee0a52e9e4f95c118899414010c5975840cb196e9049 Misskey(mk.shc.kanagawa.jp), Activity Relay(relay.shc.kanagawa.jp), Pub-Relay(pub-relay.shc.kanagawa.jp), and 5 other resources went down. https://status.shc.kanagawa.jp/incident/168623 Thu, 26 Jan 2023 18:04:37 -0000 https://status.shc.kanagawa.jp/incident/168623#4c4ec51e954f05a6bf00ee0a52e9e4f95c118899414010c5975840cb196e9049 Misskey(mk.shc.kanagawa.jp), Activity Relay(relay.shc.kanagawa.jp), Pub-Relay(pub-relay.shc.kanagawa.jp), and 5 other resources went down. https://status.shc.kanagawa.jp/incident/168623 Thu, 26 Jan 2023 18:04:37 -0000 https://status.shc.kanagawa.jp/incident/168623#4c4ec51e954f05a6bf00ee0a52e9e4f95c118899414010c5975840cb196e9049 Misskey(mk.shc.kanagawa.jp), Activity Relay(relay.shc.kanagawa.jp), Pub-Relay(pub-relay.shc.kanagawa.jp), and 5 other resources went down. https://status.shc.kanagawa.jp/incident/168623 Thu, 26 Jan 2023 18:04:37 -0000 https://status.shc.kanagawa.jp/incident/168623#4c4ec51e954f05a6bf00ee0a52e9e4f95c118899414010c5975840cb196e9049 Misskey(mk.shc.kanagawa.jp), Activity Relay(relay.shc.kanagawa.jp), Pub-Relay(pub-relay.shc.kanagawa.jp), and 5 other resources went down. https://status.shc.kanagawa.jp/incident/168084 Wed, 25 Jan 2023 09:10:56 -0000 https://status.shc.kanagawa.jp/incident/168084#0b531b6cc5ff9fcfe2bf5bac30391d0b18d29b81e1a25a46180f24930b363487 Internet Relay Chat (irc.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/168084 Wed, 25 Jan 2023 08:51:25 -0000 https://status.shc.kanagawa.jp/incident/168084#13293e51879f55c8d73f9432007935d67e4711b4b0c35b3100dee3631d0aff67 Internet Relay Chat (irc.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/166725 Sun, 22 Jan 2023 06:32:40 -0000 https://status.shc.kanagawa.jp/incident/166725#2d11e380d4a8fdc2c9e0b2dcce162d8c2e9173d7ecf633c91d9bb5e6d3272d3f Pub-Relay(pub-relay.shc.kanagawa.jp), Internet Relay Chat (irc.shc.kanagawa.jp), and Internet Relay Chat Web (webirc.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/166725 Sun, 22 Jan 2023 06:32:40 -0000 https://status.shc.kanagawa.jp/incident/166725#2d11e380d4a8fdc2c9e0b2dcce162d8c2e9173d7ecf633c91d9bb5e6d3272d3f Pub-Relay(pub-relay.shc.kanagawa.jp), Internet Relay Chat (irc.shc.kanagawa.jp), and Internet Relay Chat Web (webirc.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/166725 Sun, 22 Jan 2023 06:32:40 -0000 https://status.shc.kanagawa.jp/incident/166725#2d11e380d4a8fdc2c9e0b2dcce162d8c2e9173d7ecf633c91d9bb5e6d3272d3f Pub-Relay(pub-relay.shc.kanagawa.jp), Internet Relay Chat (irc.shc.kanagawa.jp), and Internet Relay Chat Web (webirc.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/166725 Sun, 22 Jan 2023 06:29:03 -0000 https://status.shc.kanagawa.jp/incident/166725#5868c414b8fc064fa1308af3ef23eb5f5228dc9b5df7310bbcb990373b7d1aab Internet Relay Chat (irc.shc.kanagawa.jp) went down and Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/166725 Sun, 22 Jan 2023 06:29:03 -0000 https://status.shc.kanagawa.jp/incident/166725#5868c414b8fc064fa1308af3ef23eb5f5228dc9b5df7310bbcb990373b7d1aab Internet Relay Chat (irc.shc.kanagawa.jp) went down and Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/166725 Sun, 22 Jan 2023 06:20:15 -0000 https://status.shc.kanagawa.jp/incident/166725#848e7c2638065b983e9b2bc45963b624b129d11b172cc9fb8dad641ab1c6547d Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/166725 Sun, 22 Jan 2023 02:38:14 -0000 https://status.shc.kanagawa.jp/incident/166725#1376f0ad829203b705bb915173cb7d828df43939669da15f9c6743e9eb2b28e5 Internet Relay Chat Web (webirc.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/166725 Sun, 22 Jan 2023 00:57:22 -0000 https://status.shc.kanagawa.jp/incident/166725#04717407a30a379da3c4ebf43ecf9f979601a995e4d6c3ea7de484b4328f13d0 Internet Relay Chat Web (webirc.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/166725 Sun, 22 Jan 2023 00:50:07 -0000 https://status.shc.kanagawa.jp/incident/166725#d859504a98b8ad3ccaf397893188988ee7ae0354b462df56242d2186a9ce028e Internet Relay Chat Web (webirc.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/166725 Sat, 21 Jan 2023 12:14:17 -0000 https://status.shc.kanagawa.jp/incident/166725#d60686a09b35bdbd207f8dd82095c9b9f72eb7953dcaa237cdf89aeac9be3284 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/166725 Sat, 21 Jan 2023 07:50:35 -0000 https://status.shc.kanagawa.jp/incident/166725#590622956417c1993fd9659929cd2394b8c368a168af768518a03274275fd6b3 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/166725 Sat, 21 Jan 2023 07:33:16 -0000 https://status.shc.kanagawa.jp/incident/166725#ae9f5f665a0aca281a29525989e93a02d36196afe8441489eaf5806dc7f9c478 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/166412 Fri, 20 Jan 2023 12:57:53 -0000 https://status.shc.kanagawa.jp/incident/166412#b3cd8a3558621c0f7ba686ad39b6b25abc5b02f880367878485345628fb74721 Pub-Relay(pub-relay.shc.kanagawa.jp), Internet Relay Chat (irc.shc.kanagawa.jp), and Internet Relay Chat Web (webirc.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/166412 Fri, 20 Jan 2023 12:57:53 -0000 https://status.shc.kanagawa.jp/incident/166412#b3cd8a3558621c0f7ba686ad39b6b25abc5b02f880367878485345628fb74721 Pub-Relay(pub-relay.shc.kanagawa.jp), Internet Relay Chat (irc.shc.kanagawa.jp), and Internet Relay Chat Web (webirc.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/166412 Fri, 20 Jan 2023 12:57:53 -0000 https://status.shc.kanagawa.jp/incident/166412#b3cd8a3558621c0f7ba686ad39b6b25abc5b02f880367878485345628fb74721 Pub-Relay(pub-relay.shc.kanagawa.jp), Internet Relay Chat (irc.shc.kanagawa.jp), and Internet Relay Chat Web (webirc.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/166412 Fri, 20 Jan 2023 12:49:37 -0000 https://status.shc.kanagawa.jp/incident/166412#e8128e14319c8c53aba81c23e0a0a9ceab1aaba064c84b132038d80afaf3187d Internet Relay Chat (irc.shc.kanagawa.jp) and Internet Relay Chat Web (webirc.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/166412 Fri, 20 Jan 2023 12:49:37 -0000 https://status.shc.kanagawa.jp/incident/166412#e8128e14319c8c53aba81c23e0a0a9ceab1aaba064c84b132038d80afaf3187d Internet Relay Chat (irc.shc.kanagawa.jp) and Internet Relay Chat Web (webirc.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/166412 Fri, 20 Jan 2023 11:05:52 -0000 https://status.shc.kanagawa.jp/incident/166412#0041a5bc53c5635707ee1128753e00c8e31b9385f56eb4dc2b3caef2b8b40a3e Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/165938 Thu, 19 Jan 2023 15:47:34 -0000 https://status.shc.kanagawa.jp/incident/165938#e3a2b7a67c5a3c49c41b74c10bd2672b2bd24cb02bbc14ee4d724e3b9798b5ae Pub-Relay(pub-relay.shc.kanagawa.jp), Internet Relay Chat (irc.shc.kanagawa.jp), and Internet Relay Chat Web (webirc.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/165938 Thu, 19 Jan 2023 15:47:34 -0000 https://status.shc.kanagawa.jp/incident/165938#e3a2b7a67c5a3c49c41b74c10bd2672b2bd24cb02bbc14ee4d724e3b9798b5ae Pub-Relay(pub-relay.shc.kanagawa.jp), Internet Relay Chat (irc.shc.kanagawa.jp), and Internet Relay Chat Web (webirc.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/165938 Thu, 19 Jan 2023 15:47:34 -0000 https://status.shc.kanagawa.jp/incident/165938#e3a2b7a67c5a3c49c41b74c10bd2672b2bd24cb02bbc14ee4d724e3b9798b5ae Pub-Relay(pub-relay.shc.kanagawa.jp), Internet Relay Chat (irc.shc.kanagawa.jp), and Internet Relay Chat Web (webirc.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/165938 Thu, 19 Jan 2023 15:36:42 -0000 https://status.shc.kanagawa.jp/incident/165938#944c50b734619f499e2659ee79744619442ff6cd0b14bed8068033eec169c3f2 Pub-Relay(pub-relay.shc.kanagawa.jp), Internet Relay Chat (irc.shc.kanagawa.jp), and Internet Relay Chat Web (webirc.shc.kanagawa.jp) went down and Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/165938 Thu, 19 Jan 2023 15:36:42 -0000 https://status.shc.kanagawa.jp/incident/165938#944c50b734619f499e2659ee79744619442ff6cd0b14bed8068033eec169c3f2 Pub-Relay(pub-relay.shc.kanagawa.jp), Internet Relay Chat (irc.shc.kanagawa.jp), and Internet Relay Chat Web (webirc.shc.kanagawa.jp) went down and Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/165938 Thu, 19 Jan 2023 15:36:42 -0000 https://status.shc.kanagawa.jp/incident/165938#944c50b734619f499e2659ee79744619442ff6cd0b14bed8068033eec169c3f2 Pub-Relay(pub-relay.shc.kanagawa.jp), Internet Relay Chat (irc.shc.kanagawa.jp), and Internet Relay Chat Web (webirc.shc.kanagawa.jp) went down and Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/165938 Thu, 19 Jan 2023 15:36:42 -0000 https://status.shc.kanagawa.jp/incident/165938#944c50b734619f499e2659ee79744619442ff6cd0b14bed8068033eec169c3f2 Pub-Relay(pub-relay.shc.kanagawa.jp), Internet Relay Chat (irc.shc.kanagawa.jp), and Internet Relay Chat Web (webirc.shc.kanagawa.jp) went down and Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/165938 Thu, 19 Jan 2023 07:22:13 -0000 https://status.shc.kanagawa.jp/incident/165938#f418475a24f0e2a969e3a296a57ac0f67e852244c1614105dd44f177ebcda886 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/165550 Wed, 18 Jan 2023 14:32:42 -0000 https://status.shc.kanagawa.jp/incident/165550#a6c99d48502dc99872ead02d0fce0f2951e5ec8e9e46ea445e8734962c148d6f Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/165550 Wed, 18 Jan 2023 12:41:44 -0000 https://status.shc.kanagawa.jp/incident/165550#f481b2c59f21b96778005d38c7d613bb6da173c72b47db04a30adca6ab2fc277 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/165550 Wed, 18 Jan 2023 11:47:09 -0000 https://status.shc.kanagawa.jp/incident/165550#261e2ed3a4f5487d63d7b566d2b74b0bd06754acd2abb436698a02087b68981f Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/165550 Wed, 18 Jan 2023 11:38:16 -0000 https://status.shc.kanagawa.jp/incident/165550#02157cd6aca8b708e60dd2c03879b816d05a11a0e87b6c72055dc7f6ce2c4651 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/165550 Wed, 18 Jan 2023 09:50:33 -0000 https://status.shc.kanagawa.jp/incident/165550#294bb7b3ee29d52b4d2c948e249e701e2b5a0a4fbafb24b87c54b509467d743c Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/165550 Wed, 18 Jan 2023 09:38:22 -0000 https://status.shc.kanagawa.jp/incident/165550#f7ea4c945c987a21a779f68d765e5719791b02e0c04bcf561bc92076edd037db Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/165550 Wed, 18 Jan 2023 09:17:00 -0000 https://status.shc.kanagawa.jp/incident/165550#2fd61c01ea8557b42e2771fcb0caea085d696141b6de841cab3b1868cec57d42 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/165550 Wed, 18 Jan 2023 08:56:32 -0000 https://status.shc.kanagawa.jp/incident/165550#7ee4b4b082bc5f1fee00ba83cd4e8669e74e6b6f0ea85c8d09fcdcffa4774bcb Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/165550 Wed, 18 Jan 2023 08:17:26 -0000 https://status.shc.kanagawa.jp/incident/165550#639e1bc39c5eff6241b4eb4e20901a25bd36ee5bb9faee5ff17da3bafedf2a1b Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/165550 Wed, 18 Jan 2023 08:14:09 -0000 https://status.shc.kanagawa.jp/incident/165550#287d4f5f2b97ca3cbb02e168525329ef63b02d52393ef5051877becaec13daa9 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/165550 Wed, 18 Jan 2023 06:59:22 -0000 https://status.shc.kanagawa.jp/incident/165550#3608613bf89015f55fd810366f696ef145dac49c132ec778f388b597a9a1fb52 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/165550 Wed, 18 Jan 2023 06:29:32 -0000 https://status.shc.kanagawa.jp/incident/165550#07d18bca25d4ec2336cfd3b3c90224b72016b55169986af8541cd486f1c18680 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/165273 Tue, 17 Jan 2023 10:21:17 -0000 https://status.shc.kanagawa.jp/incident/165273#70e85d5f4dab04f134d677f6046155e3e54cfcedea66d7d194d9f00b77478c4d Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/165273 Tue, 17 Jan 2023 10:10:33 -0000 https://status.shc.kanagawa.jp/incident/165273#5aeebe23c0cbbfce95797428fbfe3f051112be85e0f9584746a96d2d572f0ec0 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/164965 Mon, 16 Jan 2023 11:41:44 -0000 https://status.shc.kanagawa.jp/incident/164965#5cda2be28ba5fef82cadb3dd35a9a7fc62142411f821e8a0653d93cc133067cf Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/164965 Mon, 16 Jan 2023 11:33:10 -0000 https://status.shc.kanagawa.jp/incident/164965#eec6b08dd5d86d96dbecda51ffb17368ea8e46676c8abbee9fe8d1b26c073c87 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/164584 Sun, 15 Jan 2023 14:03:33 -0000 https://status.shc.kanagawa.jp/incident/164584#80d35323de7aa99163c0b06212a0deab427d4cd85250ba1cc33e5a5233316dc6 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/164584 Sun, 15 Jan 2023 06:18:50 -0000 https://status.shc.kanagawa.jp/incident/164584#a9df3b2477928839c787649e84fe138f29b652a31a71c0ea033095b27ca97f5e Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/164584 Sun, 15 Jan 2023 05:39:43 -0000 https://status.shc.kanagawa.jp/incident/164584#35b56a2f6cfe0e9c0d9aa1ba1e67e99da675ebf93936eda4a13265849dd62b5d Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/164584 Sun, 15 Jan 2023 04:59:16 -0000 https://status.shc.kanagawa.jp/incident/164584#101db8a8dfb994704aef50528982bd65ce1b6f07e3bd2f8d79d7cc01a8d48f31 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/164584 Sun, 15 Jan 2023 04:19:03 -0000 https://status.shc.kanagawa.jp/incident/164584#e8cea167feb4fd11d796293f5e2da799f28d7b3ff5a935bd05d8d9224dd00370 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/164584 Sun, 15 Jan 2023 04:07:23 -0000 https://status.shc.kanagawa.jp/incident/164584#5fce3f824cde732051742c7a74f0b16092c635e775f05d491dd4ed0b419c1435 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/164584 Sun, 15 Jan 2023 03:09:52 -0000 https://status.shc.kanagawa.jp/incident/164584#e7e8b57cf6ad5454e49d3bc0631e9ebd6414116bf06ed06fa7138a7ae03e05dc Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/164584 Sun, 15 Jan 2023 02:25:19 -0000 https://status.shc.kanagawa.jp/incident/164584#f7e5a40f82ed9569e757df898a518eff91f5dd39283104fa5c6b1a85f5ff222e Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/164584 Sun, 15 Jan 2023 02:12:58 -0000 https://status.shc.kanagawa.jp/incident/164584#9b1b5d13438de14de59172b4741dbf41d1fbae016471f301b4f1c3451dd62a31 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/164584 Sun, 15 Jan 2023 01:57:41 -0000 https://status.shc.kanagawa.jp/incident/164584#4a05a634d0eed72f2a5d5a16f66127a96704ddce30a6067708ffc96f885c0298 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/164405 Sat, 14 Jan 2023 11:29:27 -0000 https://status.shc.kanagawa.jp/incident/164405#344cf712e20753b578f90b6a49a6a582b8a00334c207ad2184f4692f5a2f21e9 Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/164405 Sat, 14 Jan 2023 11:23:27 -0000 https://status.shc.kanagawa.jp/incident/164405#492b1d21a4537fbc4f043277c4e18843faee202d7ec0062e05b5a4010f718baa Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/153888 Fri, 13 Jan 2023 00:12:43 -0000 https://status.shc.kanagawa.jp/incident/153888#b64c5cc15afb4721c8a7de248a2f7b8808e299a5cda353a6a195fd3e632cccba Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/153888 Fri, 13 Jan 2023 00:01:24 -0000 https://status.shc.kanagawa.jp/incident/153888#9a39edbddd908cb97e72bdc1771a5b93b9a23fe62e8217b6542d9935d1d27afb Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/152225 Tue, 10 Jan 2023 13:02:37 -0000 https://status.shc.kanagawa.jp/incident/152225#3c8d0c9e95d13e696d14a2129d7315ea962936b6bd09baa2c95610cb524ad52f Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/152225 Tue, 10 Jan 2023 12:54:08 -0000 https://status.shc.kanagawa.jp/incident/152225#0a40296c33767f7fa0098de4460b9042a831082972d50d6b00b03ed826c3b66c Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/151753 Mon, 09 Jan 2023 12:22:27 -0000 https://status.shc.kanagawa.jp/incident/151753#96a269739c8b1244650842290170ab2f75ea9498130237ea98bd1aafa435773f Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/151753 Mon, 09 Jan 2023 11:52:07 -0000 https://status.shc.kanagawa.jp/incident/151753#3d8c1a0ac36c7d7e01833d7b8fc157771f54da30b68d2032368932a522777bc4 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/151753 Mon, 09 Jan 2023 10:39:51 -0000 https://status.shc.kanagawa.jp/incident/151753#5828076ed69850c9aad2afd417d4ea29c0a38be447c7ca91f53c4ba75ff0af38 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/151753 Mon, 09 Jan 2023 09:54:51 -0000 https://status.shc.kanagawa.jp/incident/151753#b65b1a4012cd572006b6650b9a5f9ace113fa3c521586fb4d96d2eaad3c51437 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/151753 Mon, 09 Jan 2023 02:33:43 -0000 https://status.shc.kanagawa.jp/incident/151753#ba646b67696920cb0de6133dcd5d1ee4c6f2fbf6b048b62e097618a4093c562c Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/151753 Mon, 09 Jan 2023 01:39:49 -0000 https://status.shc.kanagawa.jp/incident/151753#695f934a6a962333be1220a0b8fb248b86829c5dedce4ed61afd1f2130e788c6 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/151657 Sun, 08 Jan 2023 15:39:26 -0000 https://status.shc.kanagawa.jp/incident/151657#bed5a62948772d6f816dfe8fdbd4541ec14a6ce3c5abd6443b11c4fde2b386d6 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/151657 Sun, 08 Jan 2023 14:43:19 -0000 https://status.shc.kanagawa.jp/incident/151657#a4b893b19269802cc60c948bec1b00b055d5016668a58028b7f9280603ffcebe Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/150760 Thu, 05 Jan 2023 01:59:13 -0000 https://status.shc.kanagawa.jp/incident/150760#7f6b91d6a64915210524b4b892df1a68910ab65a0e64edec8b1439929eb1abcb Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/150760 Thu, 05 Jan 2023 01:17:39 -0000 https://status.shc.kanagawa.jp/incident/150760#f39adb07d9912c52abfaf02e5a9fd6a3ca6bcf69fdc52441c7f8faa9db6c80ec Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/150440 Wed, 04 Jan 2023 03:23:44 -0000 https://status.shc.kanagawa.jp/incident/150440#95f1fdefa2f1e6e66dd38d7370a8870775b2e15c8e43584f0942000d8b81465e demo.shc.kanagawa.jp Initialize recovered. https://status.shc.kanagawa.jp/incident/150440 Wed, 04 Jan 2023 01:28:35 -0000 https://status.shc.kanagawa.jp/incident/150440#b87ccb82c84449fcdffb0d4442ba63b0e5ad74f608742766f70328bcdee12f8a demo.shc.kanagawa.jp Initialize went down. https://status.shc.kanagawa.jp/incident/150155 Tue, 03 Jan 2023 19:00:44 -0000 https://status.shc.kanagawa.jp/incident/150155#ba92ad004f1deee35358983c7ce7f67f4506ceac5b4e1dee66aac28888e0815a Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/150155 Tue, 03 Jan 2023 18:54:38 -0000 https://status.shc.kanagawa.jp/incident/150155#fd7d4d65acf1a0578ab3980f9fbe1b522ef18e93e09b6a2309de638507d79e33 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/150155 Tue, 03 Jan 2023 09:06:39 -0000 https://status.shc.kanagawa.jp/incident/150155#6b82fb635d4ea57ce6cf311dcf2bffe5861a658abb37260cd7fbf324fe9eb8ba Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/150155 Tue, 03 Jan 2023 08:22:38 -0000 https://status.shc.kanagawa.jp/incident/150155#ea4c3a33cb10d974434c074cdedbb4078326ce5917d327ef75e53cc728594bf9 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/150155 Tue, 03 Jan 2023 08:13:10 -0000 https://status.shc.kanagawa.jp/incident/150155#8ec1ec1b10aa7aa554eeb1eaea6cc65ad1cf87b65ad9ca32ac82aae74cb7db85 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/150155 Tue, 03 Jan 2023 05:05:49 -0000 https://status.shc.kanagawa.jp/incident/150155#b345ead77f4d63e2ebde278675265352cd1f5b027b0437e8eea051e3fced17a5 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/150155 Tue, 03 Jan 2023 04:51:50 -0000 https://status.shc.kanagawa.jp/incident/150155#ba020151961d79a9e5d03e6ccf500e103d767be941f8f8e329f1ec432f3b6236 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/150155 Tue, 03 Jan 2023 04:10:10 -0000 https://status.shc.kanagawa.jp/incident/150155#9bfb3495760685921fbed4d510f61231ea7e00d5bb4f7ea8c114eb368cba0014 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/150155 Tue, 03 Jan 2023 03:57:51 -0000 https://status.shc.kanagawa.jp/incident/150155#929662d03c74bd5561d8719cba54aa97e3c5d6b84a82544a795f33e8ca9ddff7 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/150155 Tue, 03 Jan 2023 02:59:14 -0000 https://status.shc.kanagawa.jp/incident/150155#9a98bfacba4c68273da845c56b84f7e4927ce45c2aabe404574b8c061e3e6747 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/150155 Tue, 03 Jan 2023 02:43:18 -0000 https://status.shc.kanagawa.jp/incident/150155#12317b184a482f5e0927648dd41d2e62735a2ae018427dcf662968aa99d29ccc Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/150155 Tue, 03 Jan 2023 01:55:42 -0000 https://status.shc.kanagawa.jp/incident/150155#bd7023a4c69c88dc5e5967350a2258c5657b67adfd0e3ac0db88b4c160aa7f5c Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/150155 Tue, 03 Jan 2023 01:48:40 -0000 https://status.shc.kanagawa.jp/incident/150155#9bb7ac6341356eb993872eb723604f20f38fbc2013a1c8a497e1347fd3a4e8a3 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/150155 Tue, 03 Jan 2023 01:34:34 -0000 https://status.shc.kanagawa.jp/incident/150155#44ee8e70d5da272a0cd79abd7d741ea3113c0414e1665ecb1c229b926ab514d5 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/150155 Tue, 03 Jan 2023 01:18:59 -0000 https://status.shc.kanagawa.jp/incident/150155#3ae9b93d3c123e8f589c7e92957c305387c247939e9a4e504b5762bbfe98efbb Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/150155 Tue, 03 Jan 2023 00:25:39 -0000 https://status.shc.kanagawa.jp/incident/150155#cbe095760b01e770efb1f4c707c9762c1b5bd037e7277fc1085ee5b85a6424e9 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/149891 Mon, 02 Jan 2023 23:10:25 -0000 https://status.shc.kanagawa.jp/incident/149891#04786f1a1f14ccfed37bf6f3aded0c3992e903c998fdd0ab9025b1848e9917ff demo.shc.kanagawa.jp Initialize recovered. https://status.shc.kanagawa.jp/incident/149891 Mon, 02 Jan 2023 16:28:30 -0000 https://status.shc.kanagawa.jp/incident/149891#1137244a74ae12e3b171fb08dfb1df3769635601888726b1c36f37f3b12b4281 demo.shc.kanagawa.jp Initialize went down. https://status.shc.kanagawa.jp/incident/149891 Mon, 02 Jan 2023 14:07:35 -0000 https://status.shc.kanagawa.jp/incident/149891#986c4aa3277d2374df66cc24676c5f96ab25687c1aa190c48544ff08b04f4a66 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/149891 Mon, 02 Jan 2023 14:05:12 -0000 https://status.shc.kanagawa.jp/incident/149891#d7721196b52381213716fc0d699909f744a6bee24672e47a82aec8f6b7fce8e5 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/149891 Mon, 02 Jan 2023 13:45:59 -0000 https://status.shc.kanagawa.jp/incident/149891#2bc93e4a2c34629c5ff89567d471be03ec16babbdda41fc84ec3688cc14c4a62 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/149891 Mon, 02 Jan 2023 12:49:41 -0000 https://status.shc.kanagawa.jp/incident/149891#8604191bcb4166eccd45c55c3460a840b9d8d9b7caecc5da68b369bb47767f7a Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/149891 Mon, 02 Jan 2023 03:18:29 -0000 https://status.shc.kanagawa.jp/incident/149891#a691fa1138853d04553459c6fd4533fc2219bf4425aa22002754cfe19afcac43 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/149891 Mon, 02 Jan 2023 03:07:13 -0000 https://status.shc.kanagawa.jp/incident/149891#b52df5fbf3bb31c126c9c23ae9622be34d711862ec2776bfb8e9dfa1d89faff5 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/149891 Mon, 02 Jan 2023 02:57:39 -0000 https://status.shc.kanagawa.jp/incident/149891#f4a66d3c9cb06693d35a77fc055677945c18c565d90985a3ec4dbe7cb5c53f80 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/149891 Mon, 02 Jan 2023 02:06:47 -0000 https://status.shc.kanagawa.jp/incident/149891#9ac85504d148c09977a35705e2f58e30032690e5d8e064c406bd17732c9f5cb8 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/149891 Mon, 02 Jan 2023 02:00:41 -0000 https://status.shc.kanagawa.jp/incident/149891#4a60d91edf4d9329c89ceaa11eccd796f34d6b7a891c298a0dd7106ec1de8cde Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/149891 Mon, 02 Jan 2023 01:49:17 -0000 https://status.shc.kanagawa.jp/incident/149891#f952f733dac4a13b0d0a6c48fe742de4dd38b64ef01968f774fddcb485237db8 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/149891 Mon, 02 Jan 2023 01:39:20 -0000 https://status.shc.kanagawa.jp/incident/149891#3f5efee6acb498898d20d0300a04301c90e932b1baebf87c36aab7093593bb3a Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/149891 Mon, 02 Jan 2023 00:40:15 -0000 https://status.shc.kanagawa.jp/incident/149891#98584a4cd40442f57f10bff15eb94c5b38544f07b624a0afd802b4c08e3a3943 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/149723 Sun, 01 Jan 2023 23:54:31 -0000 https://status.shc.kanagawa.jp/incident/149723#d3386e9be748a96b5c9a232f42543e2f960ab4186f1f10292e50f246986e4773 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/149723 Sun, 01 Jan 2023 23:15:49 -0000 https://status.shc.kanagawa.jp/incident/149723#11833faf8e432bd9593d379bd2313919f7d5314f726ed7ddebcf1549a7d58ba4 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/149723 Sun, 01 Jan 2023 14:57:47 -0000 https://status.shc.kanagawa.jp/incident/149723#7c4e1b7e04283767f225bdcdfe28cb5a16c1e43bbaf47b694fe8e23d8af26659 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/149723 Sun, 01 Jan 2023 14:43:15 -0000 https://status.shc.kanagawa.jp/incident/149723#bebc1b631519e946d1a76349933e0d3d3bdd890e76c9848f1cfeaad80694cc7a Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/149723 Sun, 01 Jan 2023 13:57:33 -0000 https://status.shc.kanagawa.jp/incident/149723#18336f3b7fe50bd9b4e97d2066f26d8ee726d17de89d3eaf47f22fd3784035b7 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/149723 Sun, 01 Jan 2023 12:16:14 -0000 https://status.shc.kanagawa.jp/incident/149723#f3576ef16bcfd90f6495a85a7a1d4c30aaa56cc45882d543f2aace362fc44ed0 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/149723 Sun, 01 Jan 2023 11:51:44 -0000 https://status.shc.kanagawa.jp/incident/149723#afbee7f92524b5ba59f3430a9032aaea7e64c2369a7728d03af351a60b31bc8e Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/149723 Sun, 01 Jan 2023 11:06:55 -0000 https://status.shc.kanagawa.jp/incident/149723#b7cc0b92e9cc9b68229d852a84ad3b04e82a0f3a64cff8ecad673b1431316fe0 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/149723 Sun, 01 Jan 2023 10:43:02 -0000 https://status.shc.kanagawa.jp/incident/149723#fad6ce20346cc8656585abea8d6d7eceb6388607283ea8c6469ba000fccb4ab9 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/149723 Sun, 01 Jan 2023 09:46:16 -0000 https://status.shc.kanagawa.jp/incident/149723#6fc1bbc2f66e1a4b5cf6e1e678ff08cd54d4a6b202954279dce6693d197c6f87 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/149723 Sun, 01 Jan 2023 09:39:24 -0000 https://status.shc.kanagawa.jp/incident/149723#b107cf5a32be225f95a45a492ab13209a5cd0c9901fc378f6c62fd4e02e8b76b Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/149723 Sun, 01 Jan 2023 08:37:22 -0000 https://status.shc.kanagawa.jp/incident/149723#16168207a3cc1fe7fe0734fbeb1edd1426813fe515de2d1d7dcdf057076fa986 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/149723 Sun, 01 Jan 2023 08:21:21 -0000 https://status.shc.kanagawa.jp/incident/149723#4a286151b0a9b2ed7e12b2471434512163edb57b9bb7c277bfcc223c43a97862 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/149723 Sun, 01 Jan 2023 07:28:15 -0000 https://status.shc.kanagawa.jp/incident/149723#f4e98038db67d7af6534868e31b833d5bbb5332854c39e424215de4ff6f79da9 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/149723 Sun, 01 Jan 2023 07:12:44 -0000 https://status.shc.kanagawa.jp/incident/149723#f8b5110a1995727559ce7288eafbf3143407270b1e0aa895c78504d816c58cd6 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/149723 Sun, 01 Jan 2023 06:24:44 -0000 https://status.shc.kanagawa.jp/incident/149723#c07d744bd9deba6a388decbfb475ab00b103fe7f9c12084bf6a8a6518609b7e8 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/149723 Sun, 01 Jan 2023 05:36:48 -0000 https://status.shc.kanagawa.jp/incident/149723#c7fe0818bd084b88e7998a3728dba952bdf1bfb880132d0eed8626444f7c63dd Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/149723 Sun, 01 Jan 2023 05:25:23 -0000 https://status.shc.kanagawa.jp/incident/149723#1c99db18dd7c9ac647f18d0433505ea6b45f329f540a14e90f1ec028bbda87a9 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/149723 Sun, 01 Jan 2023 04:54:48 -0000 https://status.shc.kanagawa.jp/incident/149723#0e3d5e13a7c61c032de013c026db71c75d09dff3cce8a5ac7d505dd54a4fcb7d Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/149723 Sun, 01 Jan 2023 04:37:16 -0000 https://status.shc.kanagawa.jp/incident/149723#a8c1326884c5842af0828d4a9c340c2d7dc747aabc0d93736e5273f2e02d47e7 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/149723 Sun, 01 Jan 2023 04:27:42 -0000 https://status.shc.kanagawa.jp/incident/149723#7408954d38098da31e23c94d5ce2840b10a67c7ebe7d604b491f5229f81db7cd Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/149723 Sun, 01 Jan 2023 04:13:15 -0000 https://status.shc.kanagawa.jp/incident/149723#fbf5591f835a48ef7857f3ab3493064a9dc12e22abbe414338a95777380e6fd1 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/149723 Sun, 01 Jan 2023 03:09:37 -0000 https://status.shc.kanagawa.jp/incident/149723#b2a0bc9f2b43b50bddc286866f3df7cad5100b3a455397f7308a72a66097950c Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/149723 Sun, 01 Jan 2023 02:55:22 -0000 https://status.shc.kanagawa.jp/incident/149723#fbc53d39c00fe10148655bd0dfc7015395ee6d26fea3fc71c97656da03dcf86b Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/149723 Sun, 01 Jan 2023 02:30:46 -0000 https://status.shc.kanagawa.jp/incident/149723#4f9935e5c0c44f5f0b7811620257a434286105d6d8aef545119b45c825db93b3 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/149723 Sun, 01 Jan 2023 02:13:18 -0000 https://status.shc.kanagawa.jp/incident/149723#951f251e7134ea496e430321e68a50e1af23d987662bd1b181d6e6a35e47443a Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/149473 Sat, 31 Dec 2022 15:30:44 -0000 https://status.shc.kanagawa.jp/incident/149473#348fcb5b0eec267aaa80bdb75f4158c4707d96b047fa6afc5d7d7d36685b64ac Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/149473 Sat, 31 Dec 2022 01:08:44 -0000 https://status.shc.kanagawa.jp/incident/149473#a87c24776e14779e6aca28770d5b9a683c46d4eab57db5dc0ec62df370488875 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/149297 Fri, 30 Dec 2022 22:49:44 -0000 https://status.shc.kanagawa.jp/incident/149297#7ef5893aa76c97227c3ff894db7e96d4524de91bf145f31635e3331bc776c993 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/149297 Fri, 30 Dec 2022 21:08:05 -0000 https://status.shc.kanagawa.jp/incident/149297#659e890e2645c563a7395e6476f8216d73a4d1d0a657b7b4c4e38f54f1ceb810 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/149297 Fri, 30 Dec 2022 20:37:37 -0000 https://status.shc.kanagawa.jp/incident/149297#bdbc19acc19d96e2b519e25a8c2b1f9944c105011a930f04e1c8b14e6a01f68b Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/149297 Fri, 30 Dec 2022 17:41:11 -0000 https://status.shc.kanagawa.jp/incident/149297#0c6d4e859d2e9de5eb15f492ac447b055ed4aca6feec3ebd81b1502cf55d2e5a Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/149297 Fri, 30 Dec 2022 17:28:38 -0000 https://status.shc.kanagawa.jp/incident/149297#cf8582dd69a32d7f73a3dbd4157a865d95a80468f088359fede126e3b484dcf1 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/149297 Fri, 30 Dec 2022 16:23:31 -0000 https://status.shc.kanagawa.jp/incident/149297#5db117c41cc479261cd55fc22668f3d245be0d3ad3975ac50ce891640f0e8458 Misskey(mk.shc.kanagawa.jp) went down and demo.shc.kanagawa.jp Initialize recovered. https://status.shc.kanagawa.jp/incident/149297 Fri, 30 Dec 2022 16:23:31 -0000 https://status.shc.kanagawa.jp/incident/149297#5db117c41cc479261cd55fc22668f3d245be0d3ad3975ac50ce891640f0e8458 Misskey(mk.shc.kanagawa.jp) went down and demo.shc.kanagawa.jp Initialize recovered. https://status.shc.kanagawa.jp/incident/149297 Fri, 30 Dec 2022 14:11:45 -0000 https://status.shc.kanagawa.jp/incident/149297#6b36120eb32c1673381f36b36894c72e2929dbbd16c2ab5dd453077867ee3f76 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/149297 Fri, 30 Dec 2022 13:57:33 -0000 https://status.shc.kanagawa.jp/incident/149297#1421e370a2f71a29cabf1fef879d9f2756d695d25588099dba08fd5abc70b55d Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/149297 Fri, 30 Dec 2022 13:38:20 -0000 https://status.shc.kanagawa.jp/incident/149297#c9a091040354637ca0b8861c2af4ae9bd0cdfbdcb3bf00e5010e3fc6e23c5577 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/149297 Fri, 30 Dec 2022 12:39:00 -0000 https://status.shc.kanagawa.jp/incident/149297#b6699e4e6594ad0b75dfb30c44fd4a2cb8e4ddfede4ca0edcb06b89d29851233 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/149297 Fri, 30 Dec 2022 12:35:36 -0000 https://status.shc.kanagawa.jp/incident/149297#4bb404c80407b5589bc992a47630e59506ce20b2bd310083b429c1a8041c57e3 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/149297 Fri, 30 Dec 2022 12:28:42 -0000 https://status.shc.kanagawa.jp/incident/149297#ee6e507151f658c8ad776ab4cc70262681ee09d30f6c3c6df11f2487cf0aae17 demo.shc.kanagawa.jp Initialize went down. https://status.shc.kanagawa.jp/incident/149297 Fri, 30 Dec 2022 11:59:35 -0000 https://status.shc.kanagawa.jp/incident/149297#0d640e037663f0036c61770f1e1defa4a4b52a7f4312ffbb8b41064b535bb463 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/149297 Fri, 30 Dec 2022 07:23:29 -0000 https://status.shc.kanagawa.jp/incident/149297#6456effb0857882cfc4fc2d7df427d9bbd3b0be72762a0ec5c5e14712d477971 Misskey(mk.shc.kanagawa.jp) and Moodle (lms.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/149297 Fri, 30 Dec 2022 07:21:15 -0000 https://status.shc.kanagawa.jp/incident/149297#098edf18b8a451b79384173636a1cb4021df1442d8266a22c049353634e40696 NextCloud (cloud.shc.kanagawa.jp) and MongoDB Repliction recovered. https://status.shc.kanagawa.jp/incident/149297 Fri, 30 Dec 2022 07:15:28 -0000 https://status.shc.kanagawa.jp/incident/149297#00cd1495de53b76b8ab1966a6949f678999d35e0e9ac4af1b1c59a7656be6c55 Misskey(mk.shc.kanagawa.jp) and MongoDB Repliction went down. https://status.shc.kanagawa.jp/incident/149297 Fri, 30 Dec 2022 07:10:09 -0000 https://status.shc.kanagawa.jp/incident/149297#1fd76d83ea9a7d7f5bdbdae571e09b7bb05805b0879236fe7c01f21d400e5835 NextCloud (cloud.shc.kanagawa.jp) and Moodle (lms.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/148484 Tue, 27 Dec 2022 04:14:06 -0000 https://status.shc.kanagawa.jp/incident/148484#84d15defcc6fe700fa92e261a6e97563dc8f1a9a3f997e5cd6c8c364270fb21e Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/148484 Tue, 27 Dec 2022 03:26:59 -0000 https://status.shc.kanagawa.jp/incident/148484#de9d4725961910747f811e8a388102c8b031d4ba471449d35fd4fad3fc7326b8 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/148385 Mon, 26 Dec 2022 18:22:33 -0000 https://status.shc.kanagawa.jp/incident/148385#4ac00d7be0720309bdb2b6d6559d4fb553bf1f59b98006bc2d33eb3d3d25acdc Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/148385 Mon, 26 Dec 2022 18:16:31 -0000 https://status.shc.kanagawa.jp/incident/148385#3bdba261e37e55846726c484c5ec01ae74f011ba546372c095681e6fbfc0f61d Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/147662 Fri, 23 Dec 2022 23:59:08 -0000 https://status.shc.kanagawa.jp/incident/147662#156d0368612728cdfc0f4b26b51f2ed488547b07c1eee7332fe4ce7bc03fddcd Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/147662 Fri, 23 Dec 2022 23:35:20 -0000 https://status.shc.kanagawa.jp/incident/147662#3f0187f68fe38031437790fbe313007b788e00421ead5a6190062b4c4c106271 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/147662 Fri, 23 Dec 2022 23:14:26 -0000 https://status.shc.kanagawa.jp/incident/147662#f80d3de74cc18e0eb0d4465d3c75be382bc7500efde2b0b4513d71507d05b102 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/147662 Fri, 23 Dec 2022 22:17:58 -0000 https://status.shc.kanagawa.jp/incident/147662#2daede6913da1579c4f6b1da23fa98497f04503faf78b5a23239e066bc0109bf Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/147662 Fri, 23 Dec 2022 15:02:25 -0000 https://status.shc.kanagawa.jp/incident/147662#d028aae67a7b5b9ce5dc3a385fcbc667e3ca3fdb2e24be6bf3d4a8960b278097 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/147662 Fri, 23 Dec 2022 14:29:19 -0000 https://status.shc.kanagawa.jp/incident/147662#efa640b7fe4eb0d38fbfcb3059ec75373c54db239e5791194d7e642a5b1bf949 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/147662 Fri, 23 Dec 2022 14:08:11 -0000 https://status.shc.kanagawa.jp/incident/147662#f1060e5edfe28a0cbe10581e0ae9a9fd83d4c39b569e2cf6e7ab8ac6646c45ac MongoDB Repliction went down and Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/147662 Fri, 23 Dec 2022 08:44:14 -0000 https://status.shc.kanagawa.jp/incident/147662#df80229c058fef814d1ce4d07d14e025bcef61e8ec618405d02008ed483f1d91 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/146222 Sun, 18 Dec 2022 09:40:48 -0000 https://status.shc.kanagawa.jp/incident/146222#85af110b85b4f48fe3a247ef199b5ca109309ad095e4c8d6ca8bc1ce937a9a83 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/146222 Sun, 18 Dec 2022 09:36:52 -0000 https://status.shc.kanagawa.jp/incident/146222#827ebd222736fa49e642b06bd7b5c8c9025ce5339c375d308b6d7b5015164913 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), and Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/146222 Sun, 18 Dec 2022 09:36:52 -0000 https://status.shc.kanagawa.jp/incident/146222#827ebd222736fa49e642b06bd7b5c8c9025ce5339c375d308b6d7b5015164913 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), and Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/146222 Sun, 18 Dec 2022 09:36:52 -0000 https://status.shc.kanagawa.jp/incident/146222#827ebd222736fa49e642b06bd7b5c8c9025ce5339c375d308b6d7b5015164913 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), and Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/146222 Sun, 18 Dec 2022 09:34:26 -0000 https://status.shc.kanagawa.jp/incident/146222#e838fb7bb64ddaf28d0cc569fcd551a4083e82b409f4b2a76e02a1ca6efb0d98 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Activity Relay(relay.shc.kanagawa.jp), and 2 other resources went down. https://status.shc.kanagawa.jp/incident/146222 Sun, 18 Dec 2022 09:34:26 -0000 https://status.shc.kanagawa.jp/incident/146222#e838fb7bb64ddaf28d0cc569fcd551a4083e82b409f4b2a76e02a1ca6efb0d98 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Activity Relay(relay.shc.kanagawa.jp), and 2 other resources went down. https://status.shc.kanagawa.jp/incident/146222 Sun, 18 Dec 2022 09:34:26 -0000 https://status.shc.kanagawa.jp/incident/146222#e838fb7bb64ddaf28d0cc569fcd551a4083e82b409f4b2a76e02a1ca6efb0d98 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Activity Relay(relay.shc.kanagawa.jp), and 2 other resources went down. https://status.shc.kanagawa.jp/incident/146222 Sun, 18 Dec 2022 09:34:26 -0000 https://status.shc.kanagawa.jp/incident/146222#e838fb7bb64ddaf28d0cc569fcd551a4083e82b409f4b2a76e02a1ca6efb0d98 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Activity Relay(relay.shc.kanagawa.jp), and 2 other resources went down. https://status.shc.kanagawa.jp/incident/145904 Sat, 17 Dec 2022 02:14:32 -0000 https://status.shc.kanagawa.jp/incident/145904#8374b61291bbfe502f6801dcae1d00ab48e72ac0e1550b9e52348ff1051882da Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/145904 Sat, 17 Dec 2022 01:48:13 -0000 https://status.shc.kanagawa.jp/incident/145904#6a384e94fac126032f5191f64b4ff59c31b7f2bcd5c02261d5a0ef56fd3e50c6 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/145476 Thu, 15 Dec 2022 18:24:02 -0000 https://status.shc.kanagawa.jp/incident/145476#20e0305e5c464930f753bc02ab70358878b3e02a18960fb58361314e3ded85b9 demo.shc.kanagawa.jp Initialize recovered. https://status.shc.kanagawa.jp/incident/145476 Thu, 15 Dec 2022 17:27:55 -0000 https://status.shc.kanagawa.jp/incident/145476#b2f25d868a95a48b2071aac217d6827e796946040beefc12e6656c68d4571562 demo.shc.kanagawa.jp Initialize went down. https://status.shc.kanagawa.jp/incident/142874 Mon, 12 Dec 2022 02:00:00 -0000 https://status.shc.kanagawa.jp/incident/142874#58bac4e5fb08dfe214e2e73b0ee2dbeab3436d99a44ddb20c39ecafec1e25869 Maintenance completed https://status.shc.kanagawa.jp/incident/142874 Mon, 12 Dec 2022 02:00:00 -0000 https://status.shc.kanagawa.jp/incident/142874#58bac4e5fb08dfe214e2e73b0ee2dbeab3436d99a44ddb20c39ecafec1e25869 Maintenance completed https://status.shc.kanagawa.jp/incident/142874 Mon, 12 Dec 2022 02:00:00 -0000 https://status.shc.kanagawa.jp/incident/142874#58bac4e5fb08dfe214e2e73b0ee2dbeab3436d99a44ddb20c39ecafec1e25869 Maintenance completed https://status.shc.kanagawa.jp/incident/142874 Mon, 12 Dec 2022 02:00:00 -0000 https://status.shc.kanagawa.jp/incident/142874#58bac4e5fb08dfe214e2e73b0ee2dbeab3436d99a44ddb20c39ecafec1e25869 Maintenance completed https://status.shc.kanagawa.jp/incident/142874 Mon, 12 Dec 2022 02:00:00 -0000 https://status.shc.kanagawa.jp/incident/142874#58bac4e5fb08dfe214e2e73b0ee2dbeab3436d99a44ddb20c39ecafec1e25869 Maintenance completed https://status.shc.kanagawa.jp/incident/142874 Mon, 12 Dec 2022 02:00:00 -0000 https://status.shc.kanagawa.jp/incident/142874#58bac4e5fb08dfe214e2e73b0ee2dbeab3436d99a44ddb20c39ecafec1e25869 Maintenance completed https://status.shc.kanagawa.jp/incident/142874 Mon, 12 Dec 2022 02:00:00 -0000 https://status.shc.kanagawa.jp/incident/142874#58bac4e5fb08dfe214e2e73b0ee2dbeab3436d99a44ddb20c39ecafec1e25869 Maintenance completed https://status.shc.kanagawa.jp/incident/142874 Mon, 12 Dec 2022 02:00:00 -0000 https://status.shc.kanagawa.jp/incident/142874#58bac4e5fb08dfe214e2e73b0ee2dbeab3436d99a44ddb20c39ecafec1e25869 Maintenance completed https://status.shc.kanagawa.jp/incident/142874 Mon, 12 Dec 2022 02:00:00 -0000 https://status.shc.kanagawa.jp/incident/142874#58bac4e5fb08dfe214e2e73b0ee2dbeab3436d99a44ddb20c39ecafec1e25869 Maintenance completed https://status.shc.kanagawa.jp/incident/142874 Mon, 12 Dec 2022 02:00:00 -0000 https://status.shc.kanagawa.jp/incident/142874#58bac4e5fb08dfe214e2e73b0ee2dbeab3436d99a44ddb20c39ecafec1e25869 Maintenance completed https://status.shc.kanagawa.jp/incident/142874 Mon, 12 Dec 2022 02:00:00 -0000 https://status.shc.kanagawa.jp/incident/142874#58bac4e5fb08dfe214e2e73b0ee2dbeab3436d99a44ddb20c39ecafec1e25869 Maintenance completed https://status.shc.kanagawa.jp/incident/142874 Mon, 12 Dec 2022 00:00:00 -0000 https://status.shc.kanagawa.jp/incident/142874#0d2f3ec006747f69b38577004a5bbdbc5271b41a7043568971ff343c75c25827 管理人が年末年始に北海道のど田舎に帰るので、しばらくサーバーがあるところから離れます。 その前にこのサイトのお手入れをしようと思います。 そのため 2022/12/12 9:00~11:00 の間はこのサイトが使えないかもしれません。覚えておいてください。 メンテナンス状況は https://uptime.atsuchan.page で確認できます。 https://status.shc.kanagawa.jp/incident/142874 Mon, 12 Dec 2022 00:00:00 -0000 https://status.shc.kanagawa.jp/incident/142874#0d2f3ec006747f69b38577004a5bbdbc5271b41a7043568971ff343c75c25827 管理人が年末年始に北海道のど田舎に帰るので、しばらくサーバーがあるところから離れます。 その前にこのサイトのお手入れをしようと思います。 そのため 2022/12/12 9:00~11:00 の間はこのサイトが使えないかもしれません。覚えておいてください。 メンテナンス状況は https://uptime.atsuchan.page で確認できます。 https://status.shc.kanagawa.jp/incident/142874 Mon, 12 Dec 2022 00:00:00 -0000 https://status.shc.kanagawa.jp/incident/142874#0d2f3ec006747f69b38577004a5bbdbc5271b41a7043568971ff343c75c25827 管理人が年末年始に北海道のど田舎に帰るので、しばらくサーバーがあるところから離れます。 その前にこのサイトのお手入れをしようと思います。 そのため 2022/12/12 9:00~11:00 の間はこのサイトが使えないかもしれません。覚えておいてください。 メンテナンス状況は https://uptime.atsuchan.page で確認できます。 https://status.shc.kanagawa.jp/incident/142874 Mon, 12 Dec 2022 00:00:00 -0000 https://status.shc.kanagawa.jp/incident/142874#0d2f3ec006747f69b38577004a5bbdbc5271b41a7043568971ff343c75c25827 管理人が年末年始に北海道のど田舎に帰るので、しばらくサーバーがあるところから離れます。 その前にこのサイトのお手入れをしようと思います。 そのため 2022/12/12 9:00~11:00 の間はこのサイトが使えないかもしれません。覚えておいてください。 メンテナンス状況は https://uptime.atsuchan.page で確認できます。 https://status.shc.kanagawa.jp/incident/142874 Mon, 12 Dec 2022 00:00:00 -0000 https://status.shc.kanagawa.jp/incident/142874#0d2f3ec006747f69b38577004a5bbdbc5271b41a7043568971ff343c75c25827 管理人が年末年始に北海道のど田舎に帰るので、しばらくサーバーがあるところから離れます。 その前にこのサイトのお手入れをしようと思います。 そのため 2022/12/12 9:00~11:00 の間はこのサイトが使えないかもしれません。覚えておいてください。 メンテナンス状況は https://uptime.atsuchan.page で確認できます。 https://status.shc.kanagawa.jp/incident/142874 Mon, 12 Dec 2022 00:00:00 -0000 https://status.shc.kanagawa.jp/incident/142874#0d2f3ec006747f69b38577004a5bbdbc5271b41a7043568971ff343c75c25827 管理人が年末年始に北海道のど田舎に帰るので、しばらくサーバーがあるところから離れます。 その前にこのサイトのお手入れをしようと思います。 そのため 2022/12/12 9:00~11:00 の間はこのサイトが使えないかもしれません。覚えておいてください。 メンテナンス状況は https://uptime.atsuchan.page で確認できます。 https://status.shc.kanagawa.jp/incident/142874 Mon, 12 Dec 2022 00:00:00 -0000 https://status.shc.kanagawa.jp/incident/142874#0d2f3ec006747f69b38577004a5bbdbc5271b41a7043568971ff343c75c25827 管理人が年末年始に北海道のど田舎に帰るので、しばらくサーバーがあるところから離れます。 その前にこのサイトのお手入れをしようと思います。 そのため 2022/12/12 9:00~11:00 の間はこのサイトが使えないかもしれません。覚えておいてください。 メンテナンス状況は https://uptime.atsuchan.page で確認できます。 https://status.shc.kanagawa.jp/incident/142874 Mon, 12 Dec 2022 00:00:00 -0000 https://status.shc.kanagawa.jp/incident/142874#0d2f3ec006747f69b38577004a5bbdbc5271b41a7043568971ff343c75c25827 管理人が年末年始に北海道のど田舎に帰るので、しばらくサーバーがあるところから離れます。 その前にこのサイトのお手入れをしようと思います。 そのため 2022/12/12 9:00~11:00 の間はこのサイトが使えないかもしれません。覚えておいてください。 メンテナンス状況は https://uptime.atsuchan.page で確認できます。 https://status.shc.kanagawa.jp/incident/142874 Mon, 12 Dec 2022 00:00:00 -0000 https://status.shc.kanagawa.jp/incident/142874#0d2f3ec006747f69b38577004a5bbdbc5271b41a7043568971ff343c75c25827 管理人が年末年始に北海道のど田舎に帰るので、しばらくサーバーがあるところから離れます。 その前にこのサイトのお手入れをしようと思います。 そのため 2022/12/12 9:00~11:00 の間はこのサイトが使えないかもしれません。覚えておいてください。 メンテナンス状況は https://uptime.atsuchan.page で確認できます。 https://status.shc.kanagawa.jp/incident/142874 Mon, 12 Dec 2022 00:00:00 -0000 https://status.shc.kanagawa.jp/incident/142874#0d2f3ec006747f69b38577004a5bbdbc5271b41a7043568971ff343c75c25827 管理人が年末年始に北海道のど田舎に帰るので、しばらくサーバーがあるところから離れます。 その前にこのサイトのお手入れをしようと思います。 そのため 2022/12/12 9:00~11:00 の間はこのサイトが使えないかもしれません。覚えておいてください。 メンテナンス状況は https://uptime.atsuchan.page で確認できます。 https://status.shc.kanagawa.jp/incident/142874 Mon, 12 Dec 2022 00:00:00 -0000 https://status.shc.kanagawa.jp/incident/142874#0d2f3ec006747f69b38577004a5bbdbc5271b41a7043568971ff343c75c25827 管理人が年末年始に北海道のど田舎に帰るので、しばらくサーバーがあるところから離れます。 その前にこのサイトのお手入れをしようと思います。 そのため 2022/12/12 9:00~11:00 の間はこのサイトが使えないかもしれません。覚えておいてください。 メンテナンス状況は https://uptime.atsuchan.page で確認できます。 https://status.shc.kanagawa.jp/incident/143955 Sat, 10 Dec 2022 22:05:06 -0000 https://status.shc.kanagawa.jp/incident/143955#c0ee31222943f61b74feacaef9df9ba3671544b4cd52a39588512f698fd33ddf NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/143955 Sat, 10 Dec 2022 21:56:00 -0000 https://status.shc.kanagawa.jp/incident/143955#73a302aa7c1fa844261b79fd9e10b7b213683822c66d07245cc040ed7775ae02 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/142465 Wed, 07 Dec 2022 11:24:00 -0000 https://status.shc.kanagawa.jp/incident/142465#7c053902770f638d48ccdda43350ab86efd17d83aa13ffa3deeb4adaf3c657fa demo.shc.kanagawa.jp Initialize recovered. https://status.shc.kanagawa.jp/incident/142465 Wed, 07 Dec 2022 09:27:56 -0000 https://status.shc.kanagawa.jp/incident/142465#d25a3a26d3c0dc767b37b2d15a7c7b6d916052428b9c8387e67f2520f0404c04 demo.shc.kanagawa.jp Initialize went down. https://status.shc.kanagawa.jp/incident/141388 Sat, 03 Dec 2022 17:23:21 -0000 https://status.shc.kanagawa.jp/incident/141388#eca3c1f09bd18da5d8ceb239b4ca5cd58602327e7ad55931dc816568da393695 demo.shc.kanagawa.jp Initialize recovered. https://status.shc.kanagawa.jp/incident/141388 Sat, 03 Dec 2022 15:27:50 -0000 https://status.shc.kanagawa.jp/incident/141388#a092c3b83d1a0f6d4abf490e05cc951ec245bc027f7919ccb7aaad99f5eaec07 demo.shc.kanagawa.jp Initialize went down. https://status.shc.kanagawa.jp/incident/137076 Fri, 18 Nov 2022 04:49:05 -0000 https://status.shc.kanagawa.jp/incident/137076#b33b97faae45e4e1a4c527cf38a0752d576234088e46814a2c04d791d61c3ca6 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/137076 Fri, 18 Nov 2022 04:18:37 -0000 https://status.shc.kanagawa.jp/incident/137076#02dc834fe4541e1b66437ad5b9bab9785d2ff090b08c112e26aadc25a465ac9d Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/136265 Wed, 16 Nov 2022 01:39:18 -0000 https://status.shc.kanagawa.jp/incident/136265#ec9134ab6c044501afe3d374388c80811aacf72942ef82678779990ef88b3d34 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/136265 Wed, 16 Nov 2022 01:20:24 -0000 https://status.shc.kanagawa.jp/incident/136265#123b5d750cbc6d6ac7cd97beeea8aa5ae06d4b8be07d797752c30e65ddc798df Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/136265 Wed, 16 Nov 2022 01:18:17 -0000 https://status.shc.kanagawa.jp/incident/136265#23522bad372e8080013187e4e1512f2e14d8cc2cb1e67cb27814ce4acf4b810a Pleroma(pr.shc.kanagawa.jp) and Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/136265 Wed, 16 Nov 2022 01:18:17 -0000 https://status.shc.kanagawa.jp/incident/136265#23522bad372e8080013187e4e1512f2e14d8cc2cb1e67cb27814ce4acf4b810a Pleroma(pr.shc.kanagawa.jp) and Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/136265 Wed, 16 Nov 2022 01:05:43 -0000 https://status.shc.kanagawa.jp/incident/136265#e7e76918dd3811a398c690c9eebd9c9bd4bb788fc1546844a6f22f9707db0aaa Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/136265 Wed, 16 Nov 2022 00:03:37 -0000 https://status.shc.kanagawa.jp/incident/136265#0a492f7f7b63460274e969eacb6db85cd27e997ddd8da0ba80b8a8e52afd5ccf Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/135427 Sun, 13 Nov 2022 10:16:06 -0000 https://status.shc.kanagawa.jp/incident/135427#3b922ff7e8f770fc263183b6104596f5cf3c6eb6e02f53ecfb4d5f8123d83786 Misskey(mk.shc.kanagawa.jp), NextCloud (cloud.shc.kanagawa.jp), and Moodle (lms.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/135427 Sun, 13 Nov 2022 10:16:06 -0000 https://status.shc.kanagawa.jp/incident/135427#3b922ff7e8f770fc263183b6104596f5cf3c6eb6e02f53ecfb4d5f8123d83786 Misskey(mk.shc.kanagawa.jp), NextCloud (cloud.shc.kanagawa.jp), and Moodle (lms.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/135427 Sun, 13 Nov 2022 10:06:13 -0000 https://status.shc.kanagawa.jp/incident/135427#43d25a231bd9bfc091482eb98d536ad16c3bb6f975318ba90140210672a1d8a1 Misskey(mk.shc.kanagawa.jp), NextCloud (cloud.shc.kanagawa.jp), Moodle (lms.shc.kanagawa.jp), and 1 other resource went down. https://status.shc.kanagawa.jp/incident/135427 Sun, 13 Nov 2022 10:06:13 -0000 https://status.shc.kanagawa.jp/incident/135427#43d25a231bd9bfc091482eb98d536ad16c3bb6f975318ba90140210672a1d8a1 Misskey(mk.shc.kanagawa.jp), NextCloud (cloud.shc.kanagawa.jp), Moodle (lms.shc.kanagawa.jp), and 1 other resource went down. https://status.shc.kanagawa.jp/incident/134146 Wed, 09 Nov 2022 05:11:14 -0000 https://status.shc.kanagawa.jp/incident/134146#6b571f5d7c3f0c3d8c18d6ffa0d757fe14aa4db622e22e1a770e0c97f52ec5b8 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Activity Relay(relay.shc.kanagawa.jp), and 2 other resources recovered. https://status.shc.kanagawa.jp/incident/134146 Wed, 09 Nov 2022 05:11:14 -0000 https://status.shc.kanagawa.jp/incident/134146#6b571f5d7c3f0c3d8c18d6ffa0d757fe14aa4db622e22e1a770e0c97f52ec5b8 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Activity Relay(relay.shc.kanagawa.jp), and 2 other resources recovered. https://status.shc.kanagawa.jp/incident/134146 Wed, 09 Nov 2022 05:11:14 -0000 https://status.shc.kanagawa.jp/incident/134146#6b571f5d7c3f0c3d8c18d6ffa0d757fe14aa4db622e22e1a770e0c97f52ec5b8 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Activity Relay(relay.shc.kanagawa.jp), and 2 other resources recovered. https://status.shc.kanagawa.jp/incident/134146 Wed, 09 Nov 2022 05:11:14 -0000 https://status.shc.kanagawa.jp/incident/134146#6b571f5d7c3f0c3d8c18d6ffa0d757fe14aa4db622e22e1a770e0c97f52ec5b8 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Activity Relay(relay.shc.kanagawa.jp), and 2 other resources recovered. https://status.shc.kanagawa.jp/incident/134146 Wed, 09 Nov 2022 05:01:33 -0000 https://status.shc.kanagawa.jp/incident/134146#286a153cb3032cc8a20ebedb31b09a2338fb9f645c0cf2ccd608aa64d2c66278 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Activity Relay(relay.shc.kanagawa.jp), and 2 other resources went down. https://status.shc.kanagawa.jp/incident/134146 Wed, 09 Nov 2022 05:01:33 -0000 https://status.shc.kanagawa.jp/incident/134146#286a153cb3032cc8a20ebedb31b09a2338fb9f645c0cf2ccd608aa64d2c66278 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Activity Relay(relay.shc.kanagawa.jp), and 2 other resources went down. https://status.shc.kanagawa.jp/incident/134146 Wed, 09 Nov 2022 05:01:33 -0000 https://status.shc.kanagawa.jp/incident/134146#286a153cb3032cc8a20ebedb31b09a2338fb9f645c0cf2ccd608aa64d2c66278 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Activity Relay(relay.shc.kanagawa.jp), and 2 other resources went down. https://status.shc.kanagawa.jp/incident/134146 Wed, 09 Nov 2022 05:01:33 -0000 https://status.shc.kanagawa.jp/incident/134146#286a153cb3032cc8a20ebedb31b09a2338fb9f645c0cf2ccd608aa64d2c66278 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Activity Relay(relay.shc.kanagawa.jp), and 2 other resources went down. https://status.shc.kanagawa.jp/incident/134146 Wed, 09 Nov 2022 00:44:27 -0000 https://status.shc.kanagawa.jp/incident/134146#90475414003ec78db6b6b361fc36394b1770af13260fda449c0989e2b0cda737 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/134146 Wed, 09 Nov 2022 00:40:31 -0000 https://status.shc.kanagawa.jp/incident/134146#c0fa9bb816fbc7b32b37d4e0f32e896ada986cb9f39726b921cf5d20636151ac Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/134146 Wed, 09 Nov 2022 00:40:10 -0000 https://status.shc.kanagawa.jp/incident/134146#40925dee7c978625868f9621db5edbd171f1e624cffb12f2e60c719c0b86c69d Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/134146 Wed, 09 Nov 2022 00:40:10 -0000 https://status.shc.kanagawa.jp/incident/134146#40925dee7c978625868f9621db5edbd171f1e624cffb12f2e60c719c0b86c69d Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/134146 Wed, 09 Nov 2022 00:40:10 -0000 https://status.shc.kanagawa.jp/incident/134146#40925dee7c978625868f9621db5edbd171f1e624cffb12f2e60c719c0b86c69d Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/134146 Wed, 09 Nov 2022 00:38:10 -0000 https://status.shc.kanagawa.jp/incident/134146#9997ea0e914783db05a647a181e2501fa1c073e521b4ab01b312d57565d9ef0a Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and 3 other resources went down. https://status.shc.kanagawa.jp/incident/134146 Wed, 09 Nov 2022 00:38:10 -0000 https://status.shc.kanagawa.jp/incident/134146#9997ea0e914783db05a647a181e2501fa1c073e521b4ab01b312d57565d9ef0a Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and 3 other resources went down. https://status.shc.kanagawa.jp/incident/134146 Wed, 09 Nov 2022 00:38:10 -0000 https://status.shc.kanagawa.jp/incident/134146#9997ea0e914783db05a647a181e2501fa1c073e521b4ab01b312d57565d9ef0a Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and 3 other resources went down. https://status.shc.kanagawa.jp/incident/134146 Wed, 09 Nov 2022 00:38:10 -0000 https://status.shc.kanagawa.jp/incident/134146#9997ea0e914783db05a647a181e2501fa1c073e521b4ab01b312d57565d9ef0a Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and 3 other resources went down. https://status.shc.kanagawa.jp/incident/134146 Wed, 09 Nov 2022 00:38:10 -0000 https://status.shc.kanagawa.jp/incident/134146#9997ea0e914783db05a647a181e2501fa1c073e521b4ab01b312d57565d9ef0a Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and 3 other resources went down. https://status.shc.kanagawa.jp/incident/133908 Tue, 08 Nov 2022 23:01:40 -0000 https://status.shc.kanagawa.jp/incident/133908#55fa134996d94c603a3351b11ee7a23e239f61630acf24bc5871ce338f191c6a Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and 1 other resource recovered. https://status.shc.kanagawa.jp/incident/133908 Tue, 08 Nov 2022 23:01:40 -0000 https://status.shc.kanagawa.jp/incident/133908#55fa134996d94c603a3351b11ee7a23e239f61630acf24bc5871ce338f191c6a Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and 1 other resource recovered. https://status.shc.kanagawa.jp/incident/133908 Tue, 08 Nov 2022 23:01:40 -0000 https://status.shc.kanagawa.jp/incident/133908#55fa134996d94c603a3351b11ee7a23e239f61630acf24bc5871ce338f191c6a Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and 1 other resource recovered. https://status.shc.kanagawa.jp/incident/133908 Tue, 08 Nov 2022 23:01:40 -0000 https://status.shc.kanagawa.jp/incident/133908#55fa134996d94c603a3351b11ee7a23e239f61630acf24bc5871ce338f191c6a Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and 1 other resource recovered. https://status.shc.kanagawa.jp/incident/133908 Tue, 08 Nov 2022 22:59:41 -0000 https://status.shc.kanagawa.jp/incident/133908#17ff625af401aa6a5f454bbcf5f88ff23222ea14321a426ad866542eda5812bc NextCloud (cloud.shc.kanagawa.jp) and Moodle (lms.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/133908 Tue, 08 Nov 2022 22:55:39 -0000 https://status.shc.kanagawa.jp/incident/133908#167124d734756459fd42ec9134ae1783ea299bb98529a436008edc7c1a49cf28 Pleroma(pr.shc.kanagawa.jp), NextCloud (cloud.shc.kanagawa.jp), and Moodle (lms.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/133908 Tue, 08 Nov 2022 22:55:39 -0000 https://status.shc.kanagawa.jp/incident/133908#167124d734756459fd42ec9134ae1783ea299bb98529a436008edc7c1a49cf28 Pleroma(pr.shc.kanagawa.jp), NextCloud (cloud.shc.kanagawa.jp), and Moodle (lms.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/133908 Tue, 08 Nov 2022 22:52:15 -0000 https://status.shc.kanagawa.jp/incident/133908#3b971c8374b9685f9088870e9dc594c75adb94a097b5400be0b3ec68913ab36c Pleroma(pr.shc.kanagawa.jp), NextCloud (cloud.shc.kanagawa.jp), and Moodle (lms.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/133908 Tue, 08 Nov 2022 22:52:15 -0000 https://status.shc.kanagawa.jp/incident/133908#3b971c8374b9685f9088870e9dc594c75adb94a097b5400be0b3ec68913ab36c Pleroma(pr.shc.kanagawa.jp), NextCloud (cloud.shc.kanagawa.jp), and Moodle (lms.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/133908 Tue, 08 Nov 2022 22:25:02 -0000 https://status.shc.kanagawa.jp/incident/133908#0a0fd2a4921c6271a5e6f29419847d0db81b309ef0f00203d0c774e157c5ff15 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and 3 other resources went down. https://status.shc.kanagawa.jp/incident/133908 Tue, 08 Nov 2022 22:25:02 -0000 https://status.shc.kanagawa.jp/incident/133908#0a0fd2a4921c6271a5e6f29419847d0db81b309ef0f00203d0c774e157c5ff15 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and 3 other resources went down. https://status.shc.kanagawa.jp/incident/133908 Tue, 08 Nov 2022 22:25:02 -0000 https://status.shc.kanagawa.jp/incident/133908#0a0fd2a4921c6271a5e6f29419847d0db81b309ef0f00203d0c774e157c5ff15 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and 3 other resources went down. https://status.shc.kanagawa.jp/incident/133908 Tue, 08 Nov 2022 22:25:02 -0000 https://status.shc.kanagawa.jp/incident/133908#0a0fd2a4921c6271a5e6f29419847d0db81b309ef0f00203d0c774e157c5ff15 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and 3 other resources went down. https://status.shc.kanagawa.jp/incident/133908 Tue, 08 Nov 2022 22:25:02 -0000 https://status.shc.kanagawa.jp/incident/133908#0a0fd2a4921c6271a5e6f29419847d0db81b309ef0f00203d0c774e157c5ff15 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and 3 other resources went down. https://status.shc.kanagawa.jp/incident/133908 Tue, 08 Nov 2022 06:55:39 -0000 https://status.shc.kanagawa.jp/incident/133908#d30ca0183536f281eae713ae27734349f8dd0b9cb36117baba035b73451684fa Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/133908 Tue, 08 Nov 2022 06:42:12 -0000 https://status.shc.kanagawa.jp/incident/133908#6d622f2aa708af8d29b77e6e98127c020f2228df2714af7588f3e0f790fa2449 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/133908 Tue, 08 Nov 2022 05:51:54 -0000 https://status.shc.kanagawa.jp/incident/133908#4874279511392221aeb28354f3bc43495f69037bf4c4a90ad09a51b9ae9e0b62 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/133908 Tue, 08 Nov 2022 05:51:54 -0000 https://status.shc.kanagawa.jp/incident/133908#4874279511392221aeb28354f3bc43495f69037bf4c4a90ad09a51b9ae9e0b62 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/133908 Tue, 08 Nov 2022 05:51:54 -0000 https://status.shc.kanagawa.jp/incident/133908#4874279511392221aeb28354f3bc43495f69037bf4c4a90ad09a51b9ae9e0b62 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/133908 Tue, 08 Nov 2022 05:45:12 -0000 https://status.shc.kanagawa.jp/incident/133908#d1a8e20270c8984e72c77ad139d2eb5a9abe50f34d58ff2c0b973a7be22b20e4 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/133908 Tue, 08 Nov 2022 05:45:12 -0000 https://status.shc.kanagawa.jp/incident/133908#d1a8e20270c8984e72c77ad139d2eb5a9abe50f34d58ff2c0b973a7be22b20e4 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/133908 Tue, 08 Nov 2022 05:45:12 -0000 https://status.shc.kanagawa.jp/incident/133908#d1a8e20270c8984e72c77ad139d2eb5a9abe50f34d58ff2c0b973a7be22b20e4 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/133309 Sun, 06 Nov 2022 10:26:08 -0000 https://status.shc.kanagawa.jp/incident/133309#ec5a1c5cd940262f3c16b6b98d6c4d4cfe102dc22a8d61aa4b0ac9492bbac307 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/133309 Sun, 06 Nov 2022 10:22:29 -0000 https://status.shc.kanagawa.jp/incident/133309#2aba71a6403b28fff37be9d2934d846d3f777f95cf9ffc0f5674508c754bb8d7 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/133113 Sat, 05 Nov 2022 23:18:15 -0000 https://status.shc.kanagawa.jp/incident/133113#a3f28a226cf19b3e2f244db606d02b6c050f31407c7e01d7757cfd815656504a Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/133113 Sat, 05 Nov 2022 18:09:58 -0000 https://status.shc.kanagawa.jp/incident/133113#6a15ba8761aff338b13709c1e9c001ed0e3a54f71f80a1dbda2ac0fe3809ae63 Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/131111 Fri, 04 Nov 2022 08:12:55 -0000 https://status.shc.kanagawa.jp/incident/131111#4e3f09ac69d657af548015ccb15eb9e122a265b5e402e4fa60577e0ec070c3c4 demo.shc.kanagawa.jp Initialize recovered. https://status.shc.kanagawa.jp/incident/131111 Fri, 04 Nov 2022 04:04:20 -0000 https://status.shc.kanagawa.jp/incident/131111#508dacb3ba085118cfeae204296d84187b8f46c1f055f3530aff36219bf522e0 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and 6 other resources recovered. https://status.shc.kanagawa.jp/incident/131111 Fri, 04 Nov 2022 04:04:20 -0000 https://status.shc.kanagawa.jp/incident/131111#508dacb3ba085118cfeae204296d84187b8f46c1f055f3530aff36219bf522e0 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and 6 other resources recovered. https://status.shc.kanagawa.jp/incident/131111 Fri, 04 Nov 2022 04:04:20 -0000 https://status.shc.kanagawa.jp/incident/131111#508dacb3ba085118cfeae204296d84187b8f46c1f055f3530aff36219bf522e0 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and 6 other resources recovered. https://status.shc.kanagawa.jp/incident/131111 Fri, 04 Nov 2022 04:04:20 -0000 https://status.shc.kanagawa.jp/incident/131111#508dacb3ba085118cfeae204296d84187b8f46c1f055f3530aff36219bf522e0 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and 6 other resources recovered. https://status.shc.kanagawa.jp/incident/131111 Fri, 04 Nov 2022 04:04:20 -0000 https://status.shc.kanagawa.jp/incident/131111#508dacb3ba085118cfeae204296d84187b8f46c1f055f3530aff36219bf522e0 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and 6 other resources recovered. https://status.shc.kanagawa.jp/incident/131111 Sun, 30 Oct 2022 23:27:07 -0000 https://status.shc.kanagawa.jp/incident/131111#13f3b6b5ffa3346a6c85d9166b60553252e135e1fae46e27d56167b995b5f488 demo.shc.kanagawa.jp Initialize went down. https://status.shc.kanagawa.jp/incident/131111 Sun, 30 Oct 2022 22:43:43 -0000 https://status.shc.kanagawa.jp/incident/131111#0b490d812261458874bbdf6f3a6d2f9d155bdbad16ac219e9bd3642b3e8696f3 NextCloud Maintenance recovered. https://status.shc.kanagawa.jp/incident/131111 Sun, 30 Oct 2022 22:36:17 -0000 https://status.shc.kanagawa.jp/incident/131111#d277ac3b8de8ddadc8cb18ef1f390e987c17eec60025ab714f86687e16018b77 NextCloud Maintenance went down. https://status.shc.kanagawa.jp/incident/131111 Sun, 30 Oct 2022 22:09:58 -0000 https://status.shc.kanagawa.jp/incident/131111#5087052724b911cdd3e01478db9b6ba7ee3ba3291af92a3b1f4dc8627fb5a4c3 NextCloud Maintenance recovered. https://status.shc.kanagawa.jp/incident/131111 Sun, 30 Oct 2022 22:08:14 -0000 https://status.shc.kanagawa.jp/incident/131111#1512f10c72f1b3ac09396f4bb6292e4166d38344e39f78380453dbd45eaea8cd NextCloud Maintenance went down. https://status.shc.kanagawa.jp/incident/128854 Sun, 30 Oct 2022 22:00:00 -0000 https://status.shc.kanagawa.jp/incident/128854#80cae1093a205954cbdc093f3be07eadad133929f05ae67f968fff88ae10731e Maintenance completed https://status.shc.kanagawa.jp/incident/128854 Sun, 30 Oct 2022 22:00:00 -0000 https://status.shc.kanagawa.jp/incident/128854#80cae1093a205954cbdc093f3be07eadad133929f05ae67f968fff88ae10731e Maintenance completed https://status.shc.kanagawa.jp/incident/128854 Sun, 30 Oct 2022 22:00:00 -0000 https://status.shc.kanagawa.jp/incident/128854#80cae1093a205954cbdc093f3be07eadad133929f05ae67f968fff88ae10731e Maintenance completed https://status.shc.kanagawa.jp/incident/128854 Sun, 30 Oct 2022 22:00:00 -0000 https://status.shc.kanagawa.jp/incident/128854#80cae1093a205954cbdc093f3be07eadad133929f05ae67f968fff88ae10731e Maintenance completed https://status.shc.kanagawa.jp/incident/128854 Sun, 30 Oct 2022 22:00:00 -0000 https://status.shc.kanagawa.jp/incident/128854#80cae1093a205954cbdc093f3be07eadad133929f05ae67f968fff88ae10731e Maintenance completed https://status.shc.kanagawa.jp/incident/128854 Sun, 30 Oct 2022 22:00:00 -0000 https://status.shc.kanagawa.jp/incident/128854#80cae1093a205954cbdc093f3be07eadad133929f05ae67f968fff88ae10731e Maintenance completed https://status.shc.kanagawa.jp/incident/128854 Sun, 30 Oct 2022 22:00:00 -0000 https://status.shc.kanagawa.jp/incident/128854#80cae1093a205954cbdc093f3be07eadad133929f05ae67f968fff88ae10731e Maintenance completed https://status.shc.kanagawa.jp/incident/128854 Sun, 30 Oct 2022 22:00:00 -0000 https://status.shc.kanagawa.jp/incident/128854#80cae1093a205954cbdc093f3be07eadad133929f05ae67f968fff88ae10731e Maintenance completed https://status.shc.kanagawa.jp/incident/128854 Sun, 30 Oct 2022 22:00:00 -0000 https://status.shc.kanagawa.jp/incident/128854#80cae1093a205954cbdc093f3be07eadad133929f05ae67f968fff88ae10731e Maintenance completed https://status.shc.kanagawa.jp/incident/131111 Sun, 30 Oct 2022 21:48:55 -0000 https://status.shc.kanagawa.jp/incident/131111#48fe09b3aa8048402ec1901395404adcef75eee560ace6ead0b5a78444c61656 Activity Relay(relay.shc.kanagawa.jp), NextCloud (cloud.shc.kanagawa.jp), MongoDB Repliction, and 2 other resources went down. https://status.shc.kanagawa.jp/incident/131111 Sun, 30 Oct 2022 21:48:55 -0000 https://status.shc.kanagawa.jp/incident/131111#48fe09b3aa8048402ec1901395404adcef75eee560ace6ead0b5a78444c61656 Activity Relay(relay.shc.kanagawa.jp), NextCloud (cloud.shc.kanagawa.jp), MongoDB Repliction, and 2 other resources went down. https://status.shc.kanagawa.jp/incident/131111 Sun, 30 Oct 2022 21:44:59 -0000 https://status.shc.kanagawa.jp/incident/131111#0a9bbe77e471d2b0fb4be9f92829e65be386bfc72bfb80cb06fc98c4a5ae5c78 Mastodon(mt.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and Moodle (lms.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/131111 Sun, 30 Oct 2022 21:44:59 -0000 https://status.shc.kanagawa.jp/incident/131111#0a9bbe77e471d2b0fb4be9f92829e65be386bfc72bfb80cb06fc98c4a5ae5c78 Mastodon(mt.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and Moodle (lms.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/131111 Sun, 30 Oct 2022 21:39:25 -0000 https://status.shc.kanagawa.jp/incident/131111#48c7c919531f099c131288759e2f4e727b52b9153bf73053dcbfd509c1f5d580 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/128854 Sun, 30 Oct 2022 21:00:00 -0000 https://status.shc.kanagawa.jp/incident/128854#5e644c9081f31f72f7afc40ea9d36884631ffa0815235a42eb563456b350aa2e データベースサーバーの定期メンテナンスを行います。 これに伴いメンテナンス期間中はインスタンスの利用ができなくなります。 日時：2022/10/31 6:00 ~ 2022/10/31 7:00 メンテナンス状況はこちらで更新します メンテナンスに関するお問い合わせは @atsuchan@atsuchan.page まで https://status.shc.kanagawa.jp/incident/128854 Sun, 30 Oct 2022 21:00:00 -0000 https://status.shc.kanagawa.jp/incident/128854#5e644c9081f31f72f7afc40ea9d36884631ffa0815235a42eb563456b350aa2e データベースサーバーの定期メンテナンスを行います。 これに伴いメンテナンス期間中はインスタンスの利用ができなくなります。 日時：2022/10/31 6:00 ~ 2022/10/31 7:00 メンテナンス状況はこちらで更新します メンテナンスに関するお問い合わせは @atsuchan@atsuchan.page まで https://status.shc.kanagawa.jp/incident/128854 Sun, 30 Oct 2022 21:00:00 -0000 https://status.shc.kanagawa.jp/incident/128854#5e644c9081f31f72f7afc40ea9d36884631ffa0815235a42eb563456b350aa2e データベースサーバーの定期メンテナンスを行います。 これに伴いメンテナンス期間中はインスタンスの利用ができなくなります。 日時：2022/10/31 6:00 ~ 2022/10/31 7:00 メンテナンス状況はこちらで更新します メンテナンスに関するお問い合わせは @atsuchan@atsuchan.page まで https://status.shc.kanagawa.jp/incident/128854 Sun, 30 Oct 2022 21:00:00 -0000 https://status.shc.kanagawa.jp/incident/128854#5e644c9081f31f72f7afc40ea9d36884631ffa0815235a42eb563456b350aa2e データベースサーバーの定期メンテナンスを行います。 これに伴いメンテナンス期間中はインスタンスの利用ができなくなります。 日時：2022/10/31 6:00 ~ 2022/10/31 7:00 メンテナンス状況はこちらで更新します メンテナンスに関するお問い合わせは @atsuchan@atsuchan.page まで https://status.shc.kanagawa.jp/incident/128854 Sun, 30 Oct 2022 21:00:00 -0000 https://status.shc.kanagawa.jp/incident/128854#5e644c9081f31f72f7afc40ea9d36884631ffa0815235a42eb563456b350aa2e データベースサーバーの定期メンテナンスを行います。 これに伴いメンテナンス期間中はインスタンスの利用ができなくなります。 日時：2022/10/31 6:00 ~ 2022/10/31 7:00 メンテナンス状況はこちらで更新します メンテナンスに関するお問い合わせは @atsuchan@atsuchan.page まで https://status.shc.kanagawa.jp/incident/128854 Sun, 30 Oct 2022 21:00:00 -0000 https://status.shc.kanagawa.jp/incident/128854#5e644c9081f31f72f7afc40ea9d36884631ffa0815235a42eb563456b350aa2e データベースサーバーの定期メンテナンスを行います。 これに伴いメンテナンス期間中はインスタンスの利用ができなくなります。 日時：2022/10/31 6:00 ~ 2022/10/31 7:00 メンテナンス状況はこちらで更新します メンテナンスに関するお問い合わせは @atsuchan@atsuchan.page まで https://status.shc.kanagawa.jp/incident/128854 Sun, 30 Oct 2022 21:00:00 -0000 https://status.shc.kanagawa.jp/incident/128854#5e644c9081f31f72f7afc40ea9d36884631ffa0815235a42eb563456b350aa2e データベースサーバーの定期メンテナンスを行います。 これに伴いメンテナンス期間中はインスタンスの利用ができなくなります。 日時：2022/10/31 6:00 ~ 2022/10/31 7:00 メンテナンス状況はこちらで更新します メンテナンスに関するお問い合わせは @atsuchan@atsuchan.page まで https://status.shc.kanagawa.jp/incident/128854 Sun, 30 Oct 2022 21:00:00 -0000 https://status.shc.kanagawa.jp/incident/128854#5e644c9081f31f72f7afc40ea9d36884631ffa0815235a42eb563456b350aa2e データベースサーバーの定期メンテナンスを行います。 これに伴いメンテナンス期間中はインスタンスの利用ができなくなります。 日時：2022/10/31 6:00 ~ 2022/10/31 7:00 メンテナンス状況はこちらで更新します メンテナンスに関するお問い合わせは @atsuchan@atsuchan.page まで https://status.shc.kanagawa.jp/incident/128854 Sun, 30 Oct 2022 21:00:00 -0000 https://status.shc.kanagawa.jp/incident/128854#5e644c9081f31f72f7afc40ea9d36884631ffa0815235a42eb563456b350aa2e データベースサーバーの定期メンテナンスを行います。 これに伴いメンテナンス期間中はインスタンスの利用ができなくなります。 日時：2022/10/31 6:00 ~ 2022/10/31 7:00 メンテナンス状況はこちらで更新します メンテナンスに関するお問い合わせは @atsuchan@atsuchan.page まで https://status.shc.kanagawa.jp/incident/129278 Mon, 24 Oct 2022 16:03:45 -0000 https://status.shc.kanagawa.jp/incident/129278#efb5e7eb2243d1d8a0515d3b6a10634783dfde7c011196811fc4ad42ce2a0bbd Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/129278 Mon, 24 Oct 2022 15:39:32 -0000 https://status.shc.kanagawa.jp/incident/129278#e445b82d327365d77284c174e712321571e9a94e91d53b807d3958d3d1dc22cb Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/123858 Thu, 06 Oct 2022 03:49:36 -0000 https://status.shc.kanagawa.jp/incident/123858#c4bbb93dbf9e5b6684f48441ba96dd6214dbeb838c7496a689f95657a43060e2 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/123858 Thu, 06 Oct 2022 03:31:20 -0000 https://status.shc.kanagawa.jp/incident/123858#187fd75cc25f5b8f0ab4b3e4c29d1d62db69be555b4ce8e47b7eabbf33ee9c0a Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/121214 Mon, 26 Sep 2022 11:13:46 -0000 https://status.shc.kanagawa.jp/incident/121214#c8335a419a578aba91b6ab7c2aa948f6352b27ff4df31e9643e79322dacd7a67 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/121214 Mon, 26 Sep 2022 11:13:23 -0000 https://status.shc.kanagawa.jp/incident/121214#0f1a8ccb1c499904cbdd52ea8574e420e63835549caa4fa2010638f0d6cabd6c NextCloud (cloud.shc.kanagawa.jp) and Moodle (lms.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/121045 Sun, 25 Sep 2022 23:24:35 -0000 https://status.shc.kanagawa.jp/incident/121045#a50a2352793708a6e66573a8190225758ebe10a2992e70da32797559ff1b7d9f Mastodon Daily Database Backup and Pleroma Daily Database Backup recovered. https://status.shc.kanagawa.jp/incident/121045 Sun, 25 Sep 2022 23:24:35 -0000 https://status.shc.kanagawa.jp/incident/121045#a50a2352793708a6e66573a8190225758ebe10a2992e70da32797559ff1b7d9f Mastodon Daily Database Backup and Pleroma Daily Database Backup recovered. https://status.shc.kanagawa.jp/incident/121045 Sun, 25 Sep 2022 16:18:10 -0000 https://status.shc.kanagawa.jp/incident/121045#00aab07550cc482ca9c575efb14de476bd3cd2463fa1dd286559ed55ffd092ab Pleroma Daily Database Backup went down. https://status.shc.kanagawa.jp/incident/121045 Sun, 25 Sep 2022 16:04:32 -0000 https://status.shc.kanagawa.jp/incident/121045#0ee0fb375c2f85d06475a3656de6dbe367a0711a043b4dbd33c47df9d4f84645 Mastodon Daily Database Backup went down. https://status.shc.kanagawa.jp/incident/119307 Tue, 20 Sep 2022 05:47:48 -0000 https://status.shc.kanagawa.jp/incident/119307#9ede18595f9af1bd6322f8cdd36612bd3147ef064a5256a3a48a4cc7d4e81355 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/119307 Tue, 20 Sep 2022 05:41:41 -0000 https://status.shc.kanagawa.jp/incident/119307#61431dc1bfa4d3ea6cfa7d83bcf44a3d1af3ecd36a51fe766589d4112d61c69e Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/119307 Tue, 20 Sep 2022 02:30:00 -0000 https://status.shc.kanagawa.jp/incident/119307#06af2585f04fedf3cffa9bfd323ca9163242f259c43e853a24419a1e38d22a03 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/119307 Tue, 20 Sep 2022 02:23:42 -0000 https://status.shc.kanagawa.jp/incident/119307#1938eb8f2195a93c85ec2fe5c2fcaab462003cdb9a8d9099a5507902680f9226 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/119307 Tue, 20 Sep 2022 00:50:46 -0000 https://status.shc.kanagawa.jp/incident/119307#e6eec7a3026172a161c0c668f66bac0fc24bdc7cf0ccbedf889a601a7a1555bd Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/119307 Tue, 20 Sep 2022 00:44:41 -0000 https://status.shc.kanagawa.jp/incident/119307#66074a58b8faffff55994e7032dc4e2298aa309b486b1486d0e4dac7c6c6275b Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/119188 Mon, 19 Sep 2022 23:11:47 -0000 https://status.shc.kanagawa.jp/incident/119188#356141195e3dcaab6f3ce54f5bdf46397ad8b4bf2143b64629cc7e58b583b61b Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/119188 Mon, 19 Sep 2022 23:05:38 -0000 https://status.shc.kanagawa.jp/incident/119188#3f8d7469a47b2274c85ea10b08d9485c20ee41d815263c9295656dc7e8845f70 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/119188 Mon, 19 Sep 2022 13:17:41 -0000 https://status.shc.kanagawa.jp/incident/119188#9c0bcb6c8d8f3249ca31440d39e32b8ec62c5fb1df2ea6d8118575a1bcc10945 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/119188 Mon, 19 Sep 2022 13:11:38 -0000 https://status.shc.kanagawa.jp/incident/119188#cb64495f54dbd25480a7e7f4f924c668e4db710ff195a5f84cd7f1d4f5933f14 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/118995 Sun, 18 Sep 2022 23:19:53 -0000 https://status.shc.kanagawa.jp/incident/118995#0e4fbbaf9f503848dcc554a5c055a160d75c989848fe027db7729a43c71761ad Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/118995 Sun, 18 Sep 2022 23:15:52 -0000 https://status.shc.kanagawa.jp/incident/118995#8cae6815c362926af618835fa68794f4ade5c2d38d8f5dc964165affb48a5eeb Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/116335 Sun, 18 Sep 2022 23:00:00 -0000 https://status.shc.kanagawa.jp/incident/116335#b8402ec7217b7cee20b09091d82a86382feaaf0f42cb74a65ae15bfea87070c1 Maintenance completed https://status.shc.kanagawa.jp/incident/116335 Sun, 18 Sep 2022 23:00:00 -0000 https://status.shc.kanagawa.jp/incident/116335#b8402ec7217b7cee20b09091d82a86382feaaf0f42cb74a65ae15bfea87070c1 Maintenance completed https://status.shc.kanagawa.jp/incident/116335 Sun, 18 Sep 2022 23:00:00 -0000 https://status.shc.kanagawa.jp/incident/116335#b8402ec7217b7cee20b09091d82a86382feaaf0f42cb74a65ae15bfea87070c1 Maintenance completed https://status.shc.kanagawa.jp/incident/116335 Sun, 18 Sep 2022 23:00:00 -0000 https://status.shc.kanagawa.jp/incident/116335#b8402ec7217b7cee20b09091d82a86382feaaf0f42cb74a65ae15bfea87070c1 Maintenance completed https://status.shc.kanagawa.jp/incident/116335 Sun, 18 Sep 2022 23:00:00 -0000 https://status.shc.kanagawa.jp/incident/116335#b8402ec7217b7cee20b09091d82a86382feaaf0f42cb74a65ae15bfea87070c1 Maintenance completed https://status.shc.kanagawa.jp/incident/116335 Sun, 18 Sep 2022 21:00:00 -0000 https://status.shc.kanagawa.jp/incident/116335#57c574a8bd967ce2c2708227446b9e7e658c1ae605d5acb4cecb9dab6e5e8565 データベースサーバーのメンテナンスに伴いインスタンスが利用できなくなります。 メンテナンスに関するお問い合わせは @atsuchan@atsuchan.page まで https://status.shc.kanagawa.jp/incident/116335 Sun, 18 Sep 2022 21:00:00 -0000 https://status.shc.kanagawa.jp/incident/116335#57c574a8bd967ce2c2708227446b9e7e658c1ae605d5acb4cecb9dab6e5e8565 データベースサーバーのメンテナンスに伴いインスタンスが利用できなくなります。 メンテナンスに関するお問い合わせは @atsuchan@atsuchan.page まで https://status.shc.kanagawa.jp/incident/116335 Sun, 18 Sep 2022 21:00:00 -0000 https://status.shc.kanagawa.jp/incident/116335#57c574a8bd967ce2c2708227446b9e7e658c1ae605d5acb4cecb9dab6e5e8565 データベースサーバーのメンテナンスに伴いインスタンスが利用できなくなります。 メンテナンスに関するお問い合わせは @atsuchan@atsuchan.page まで https://status.shc.kanagawa.jp/incident/116335 Sun, 18 Sep 2022 21:00:00 -0000 https://status.shc.kanagawa.jp/incident/116335#57c574a8bd967ce2c2708227446b9e7e658c1ae605d5acb4cecb9dab6e5e8565 データベースサーバーのメンテナンスに伴いインスタンスが利用できなくなります。 メンテナンスに関するお問い合わせは @atsuchan@atsuchan.page まで https://status.shc.kanagawa.jp/incident/116335 Sun, 18 Sep 2022 21:00:00 -0000 https://status.shc.kanagawa.jp/incident/116335#57c574a8bd967ce2c2708227446b9e7e658c1ae605d5acb4cecb9dab6e5e8565 データベースサーバーのメンテナンスに伴いインスタンスが利用できなくなります。 メンテナンスに関するお問い合わせは @atsuchan@atsuchan.page まで https://status.shc.kanagawa.jp/incident/117983 Thu, 15 Sep 2022 14:31:33 -0000 https://status.shc.kanagawa.jp/incident/117983#931ae98a6884407dc857960d224db6bc4be5cc1e11811bfd20be4a93256707ed Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/117983 Thu, 15 Sep 2022 12:28:31 -0000 https://status.shc.kanagawa.jp/incident/117983#650b6df53adec8673e878f7f9630023ae4e89b30c84d70cf836c8949cd94aa13 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/117983 Thu, 15 Sep 2022 12:16:06 -0000 https://status.shc.kanagawa.jp/incident/117983#a1c94edb6652a0c7d4dc7a554c318a039476ae68d7a7f31c874b053cc80a294c Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/117983 Thu, 15 Sep 2022 01:10:30 -0000 https://status.shc.kanagawa.jp/incident/117983#fc9ae86c82c2a1df6bba146f95c4b2d2304879ea0c8ce6f72f539976e09876af Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/117983 Thu, 15 Sep 2022 00:57:58 -0000 https://status.shc.kanagawa.jp/incident/117983#28884a0ffb8e17baf86adae9562623e00f3d5550e994e3b1beea5601811a299d Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/117983 Wed, 14 Sep 2022 20:07:17 -0000 https://status.shc.kanagawa.jp/incident/117983#d9aac4205bfd3e9a2dcfa2e8d63293e0b2c0f148ee77841697e3996a6f0f57c2 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/116793 Sat, 10 Sep 2022 02:12:36 -0000 https://status.shc.kanagawa.jp/incident/116793#8c3f1a08751f4b103567f819b35e690b006a4193722240eefdf5f8b4560024de Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/116793 Sat, 10 Sep 2022 02:06:31 -0000 https://status.shc.kanagawa.jp/incident/116793#c19a369aae31e6d1831b04c3d2bb06bf5dd1d7593d855ed74f4531f53e6a1fc7 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/112718 Fri, 26 Aug 2022 17:22:41 -0000 https://status.shc.kanagawa.jp/incident/112718#987e16d79621e6c0d437ceb1a8a88598042deb3ba69e967f30e5d1a16bf4c0b3 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/112718 Fri, 26 Aug 2022 08:08:06 -0000 https://status.shc.kanagawa.jp/incident/112718#037d6223d885f1a5658ad243a79a7511b7c563775dbf964db48a4dc364bf0044 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/112718 Fri, 26 Aug 2022 07:31:55 -0000 https://status.shc.kanagawa.jp/incident/112718#52ee362f4af027f79884ec4a231ebc94cf355c377fd98ef060eb6e98c1018187 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/112718 Fri, 26 Aug 2022 06:20:48 -0000 https://status.shc.kanagawa.jp/incident/112718#7d4d216432de5d15363358250debf8b3b8a19c1855d7f876f197bed28c44731b Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/112718 Fri, 26 Aug 2022 06:13:53 -0000 https://status.shc.kanagawa.jp/incident/112718#d40f2e45d2b7f8888d1e27d9e01d16d2abbd15ce6ed19cdafa495cc7a10b0698 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/112718 Fri, 26 Aug 2022 00:51:37 -0000 https://status.shc.kanagawa.jp/incident/112718#24e8964014b6f250cf7aa0380714ee09c378e51014f3571376a9a485a4de80ee Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/112718 Fri, 26 Aug 2022 00:47:17 -0000 https://status.shc.kanagawa.jp/incident/112718#0780ef53cbd7fb72a5473735353a8faeaf0448ec3630a94ee2d650fb0919c00c Activity Relay(relay.shc.kanagawa.jp), Pub-Relay(pub-relay.shc.kanagawa.jp), Internet Relay Chat (irc.shc.kanagawa.jp), and 1 other resource recovered. https://status.shc.kanagawa.jp/incident/112718 Fri, 26 Aug 2022 00:47:17 -0000 https://status.shc.kanagawa.jp/incident/112718#0780ef53cbd7fb72a5473735353a8faeaf0448ec3630a94ee2d650fb0919c00c Activity Relay(relay.shc.kanagawa.jp), Pub-Relay(pub-relay.shc.kanagawa.jp), Internet Relay Chat (irc.shc.kanagawa.jp), and 1 other resource recovered. https://status.shc.kanagawa.jp/incident/112718 Fri, 26 Aug 2022 00:47:17 -0000 https://status.shc.kanagawa.jp/incident/112718#0780ef53cbd7fb72a5473735353a8faeaf0448ec3630a94ee2d650fb0919c00c Activity Relay(relay.shc.kanagawa.jp), Pub-Relay(pub-relay.shc.kanagawa.jp), Internet Relay Chat (irc.shc.kanagawa.jp), and 1 other resource recovered. https://status.shc.kanagawa.jp/incident/112718 Fri, 26 Aug 2022 00:47:17 -0000 https://status.shc.kanagawa.jp/incident/112718#0780ef53cbd7fb72a5473735353a8faeaf0448ec3630a94ee2d650fb0919c00c Activity Relay(relay.shc.kanagawa.jp), Pub-Relay(pub-relay.shc.kanagawa.jp), Internet Relay Chat (irc.shc.kanagawa.jp), and 1 other resource recovered. https://status.shc.kanagawa.jp/incident/112718 Fri, 26 Aug 2022 00:33:43 -0000 https://status.shc.kanagawa.jp/incident/112718#1e2552325494bfd0b683dfb55a246736b2dcd6cbdeb753e96cc5ab1abd2f96af Pub-Relay(pub-relay.shc.kanagawa.jp), Internet Relay Chat (irc.shc.kanagawa.jp), and Internet Relay Chat Web (webirc.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/112718 Fri, 26 Aug 2022 00:33:43 -0000 https://status.shc.kanagawa.jp/incident/112718#1e2552325494bfd0b683dfb55a246736b2dcd6cbdeb753e96cc5ab1abd2f96af Pub-Relay(pub-relay.shc.kanagawa.jp), Internet Relay Chat (irc.shc.kanagawa.jp), and Internet Relay Chat Web (webirc.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/112718 Fri, 26 Aug 2022 00:33:43 -0000 https://status.shc.kanagawa.jp/incident/112718#1e2552325494bfd0b683dfb55a246736b2dcd6cbdeb753e96cc5ab1abd2f96af Pub-Relay(pub-relay.shc.kanagawa.jp), Internet Relay Chat (irc.shc.kanagawa.jp), and Internet Relay Chat Web (webirc.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/112718 Fri, 26 Aug 2022 00:25:29 -0000 https://status.shc.kanagawa.jp/incident/112718#29f1f3bcad631569d7d84b9dcfa8146a153f8d90237f0b81c0338d80c277ce7b Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/112718 Fri, 26 Aug 2022 00:19:10 -0000 https://status.shc.kanagawa.jp/incident/112718#1c3e057eab13206e2f772a58ae1722c537efbc74ebc64db150cd1fd660960f20 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/112718 Fri, 26 Aug 2022 00:01:24 -0000 https://status.shc.kanagawa.jp/incident/112718#304c024679ecbce4d3fe7edcdbc95d21e37ee668dd7490bfd73986a68f17e6a2 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/112654 Thu, 25 Aug 2022 23:54:54 -0000 https://status.shc.kanagawa.jp/incident/112654#deb0ea81400971d023bcd215aaba35c10a3d405ebd2d9a0716f3de999631b500 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/112654 Thu, 25 Aug 2022 23:34:27 -0000 https://status.shc.kanagawa.jp/incident/112654#c0db0c0cbeafce2f90917d04f3fc3edccba8159f696f6548ae7ef413e64420b2 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/112654 Thu, 25 Aug 2022 23:18:47 -0000 https://status.shc.kanagawa.jp/incident/112654#5e7150e0ef959fe86c16a5f856029ba9a863e5c72ccfde2e1318c04471a03b38 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/112654 Thu, 25 Aug 2022 22:45:54 -0000 https://status.shc.kanagawa.jp/incident/112654#4b5c8766d8433ae617e1ef9fe56dd250fa2cc231ac6ac265acf045e84301f58c Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/112654 Thu, 25 Aug 2022 22:36:35 -0000 https://status.shc.kanagawa.jp/incident/112654#9ed454fb847236478d1ed721eb5286a15634587a9403713de1395e142297418d Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/112654 Thu, 25 Aug 2022 22:25:15 -0000 https://status.shc.kanagawa.jp/incident/112654#d0e3b00092dc3f7865ab5339b47d22392556639544836e4a618165b60c866f44 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/112654 Thu, 25 Aug 2022 22:21:49 -0000 https://status.shc.kanagawa.jp/incident/112654#2ee7739b87dbf10851011e375f0d06320d8ecea4680ae4c6943f3f5e5180a265 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/112654 Thu, 25 Aug 2022 21:39:53 -0000 https://status.shc.kanagawa.jp/incident/112654#13e47f81e9644745f7111a540e2f9f5cc137983c6e64fa4c1a23011da62cb00f Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/112654 Thu, 25 Aug 2022 21:27:36 -0000 https://status.shc.kanagawa.jp/incident/112654#a7c895036d642d5c523ce8b3a1362403cebd5a1f9ecdb3a622477715ad99896b Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/112654 Thu, 25 Aug 2022 21:16:27 -0000 https://status.shc.kanagawa.jp/incident/112654#e64d9407f4503a7565afa2216065d53255645770f6600bd331d40534a2567d29 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/112654 Thu, 25 Aug 2022 20:45:28 -0000 https://status.shc.kanagawa.jp/incident/112654#e26757811afec582461c621e55096572bba932070d0ceff6b9ab7122fe44d469 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/112654 Thu, 25 Aug 2022 20:25:23 -0000 https://status.shc.kanagawa.jp/incident/112654#5b76de9a1af7c96a905c10cee638d3f06a6fd2f44e2fa5b3932abf0f98684709 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/112654 Thu, 25 Aug 2022 20:12:57 -0000 https://status.shc.kanagawa.jp/incident/112654#12c865adde248d680c5b3210afcc088a45bdb2e8139c293b8b3523c11d0c1b10 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/112654 Thu, 25 Aug 2022 19:17:51 -0000 https://status.shc.kanagawa.jp/incident/112654#a3cfc0196ebe751fc4b1adde67448e15e48f6a71719d850a37af0bb183eb228b Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/112654 Thu, 25 Aug 2022 19:05:53 -0000 https://status.shc.kanagawa.jp/incident/112654#a40b56fd811b38ea8e1b264c8003f0f2342a8d07561d4412126bcdac7001e246 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/112654 Thu, 25 Aug 2022 19:00:48 -0000 https://status.shc.kanagawa.jp/incident/112654#9c791b07578e196a35b9adf04f640c655b18b2669dfa69c9d04fb573d72421e3 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/112654 Thu, 25 Aug 2022 18:56:07 -0000 https://status.shc.kanagawa.jp/incident/112654#d1fd4fd25225e07cc9b7708f1e12216b5b1be866d1c766d6f93b4404a1109003 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/112654 Thu, 25 Aug 2022 18:41:57 -0000 https://status.shc.kanagawa.jp/incident/112654#ed17ba212b404e3d7265240df1e0b27b0ee3b72f9454c72be6e70ad453783c7a Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/112654 Thu, 25 Aug 2022 18:33:43 -0000 https://status.shc.kanagawa.jp/incident/112654#98e50711130aa6626e73b16a457f83d06f3e3adb04db54e97432cf26379120c6 Pub-Relay(pub-relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/112654 Thu, 25 Aug 2022 17:08:54 -0000 https://status.shc.kanagawa.jp/incident/112654#c23e6a8b869243cfae688664aa6365f76259b51977e55f8b8848f1a77769a591 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/112194 Wed, 24 Aug 2022 04:30:05 -0000 https://status.shc.kanagawa.jp/incident/112194#b21a30404f16e602e25b03f617898d9ca407137305831139fad483ff00752bda Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/112194 Wed, 24 Aug 2022 04:23:46 -0000 https://status.shc.kanagawa.jp/incident/112194#dc2241c3b74788c3203ed0b51d7a94f48685efe98e40152ebd085a116364c7ab Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/111864 Tue, 23 Aug 2022 09:13:40 -0000 https://status.shc.kanagawa.jp/incident/111864#60a1b24cc4ae7c96505e889057237df44498c76b2fc75c76112bb49ec817daf3 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/111864 Tue, 23 Aug 2022 09:13:34 -0000 https://status.shc.kanagawa.jp/incident/111864#aebe08138d8a785bfef2d72b6b31e6f7d4ed0106929ae17eea2c949a84a17683 NextCloud (cloud.shc.kanagawa.jp) and Moodle (lms.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/111864 Tue, 23 Aug 2022 03:56:03 -0000 https://status.shc.kanagawa.jp/incident/111864#95c060db97325312f2271bb6addc844f1eb6516af2d7a326de1501173df21938 NextCloud (cloud.shc.kanagawa.jp), MongoDB Repliction, and NextCloud Maintenance recovered. https://status.shc.kanagawa.jp/incident/111864 Tue, 23 Aug 2022 03:56:03 -0000 https://status.shc.kanagawa.jp/incident/111864#95c060db97325312f2271bb6addc844f1eb6516af2d7a326de1501173df21938 NextCloud (cloud.shc.kanagawa.jp), MongoDB Repliction, and NextCloud Maintenance recovered. https://status.shc.kanagawa.jp/incident/111864 Tue, 23 Aug 2022 03:42:45 -0000 https://status.shc.kanagawa.jp/incident/111864#adf8da10c178a6288608d917798d3b336cf39817fef0805033e3171871d8fbdf NextCloud Maintenance went down. https://status.shc.kanagawa.jp/incident/111864 Tue, 23 Aug 2022 03:38:38 -0000 https://status.shc.kanagawa.jp/incident/111864#672807cea271fb3cfdfbe7fe7a521398f4be49d64ff7ab773f46aa740057269e NextCloud (cloud.shc.kanagawa.jp), Moodle (lms.shc.kanagawa.jp), and MongoDB Repliction went down. https://status.shc.kanagawa.jp/incident/111216 Sat, 20 Aug 2022 10:44:07 -0000 https://status.shc.kanagawa.jp/incident/111216#a784efea1a488595e98c2032d49aab01deef07f03825e7383297a48826e7305e NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/111216 Sat, 20 Aug 2022 10:43:25 -0000 https://status.shc.kanagawa.jp/incident/111216#a59ddff86a211008e34674b33ddfbdfa682613eeb4f06f381b5ab60e912d3cd7 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/111216 Sat, 20 Aug 2022 10:43:25 -0000 https://status.shc.kanagawa.jp/incident/111216#a59ddff86a211008e34674b33ddfbdfa682613eeb4f06f381b5ab60e912d3cd7 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/111216 Sat, 20 Aug 2022 10:43:25 -0000 https://status.shc.kanagawa.jp/incident/111216#a59ddff86a211008e34674b33ddfbdfa682613eeb4f06f381b5ab60e912d3cd7 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/111216 Sat, 20 Aug 2022 10:41:38 -0000 https://status.shc.kanagawa.jp/incident/111216#fe31d21b1f300b761f26ce32ff0c7df72b4170582c99808ed3580e5fd3a1fd12 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and 2 other resources went down. https://status.shc.kanagawa.jp/incident/111216 Sat, 20 Aug 2022 10:41:38 -0000 https://status.shc.kanagawa.jp/incident/111216#fe31d21b1f300b761f26ce32ff0c7df72b4170582c99808ed3580e5fd3a1fd12 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and 2 other resources went down. https://status.shc.kanagawa.jp/incident/111216 Sat, 20 Aug 2022 10:41:38 -0000 https://status.shc.kanagawa.jp/incident/111216#fe31d21b1f300b761f26ce32ff0c7df72b4170582c99808ed3580e5fd3a1fd12 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and 2 other resources went down. https://status.shc.kanagawa.jp/incident/111216 Sat, 20 Aug 2022 10:41:38 -0000 https://status.shc.kanagawa.jp/incident/111216#fe31d21b1f300b761f26ce32ff0c7df72b4170582c99808ed3580e5fd3a1fd12 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and 2 other resources went down. https://status.shc.kanagawa.jp/incident/111028 Fri, 19 Aug 2022 20:27:42 -0000 https://status.shc.kanagawa.jp/incident/111028#12f519387da8781e12a18adeeb2780cb873351d4d26892e43f569c1872c92718 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/111028 Fri, 19 Aug 2022 20:14:08 -0000 https://status.shc.kanagawa.jp/incident/111028#c69dee0ba7329105a432b79d56e4e092f8de334646ec9688bffeec362fb89753 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), and Moodle (lms.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/111028 Fri, 19 Aug 2022 20:14:08 -0000 https://status.shc.kanagawa.jp/incident/111028#c69dee0ba7329105a432b79d56e4e092f8de334646ec9688bffeec362fb89753 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), and Moodle (lms.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/111028 Fri, 19 Aug 2022 20:08:00 -0000 https://status.shc.kanagawa.jp/incident/111028#7b0fe0545adc22afb2e9dbbdf0303d55eb4185b8fd8614b552fc8af04276572f NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/111028 Fri, 19 Aug 2022 19:53:08 -0000 https://status.shc.kanagawa.jp/incident/111028#a9eb0856514aa36bc58c525c777c35f2fa056546dbe7cd45cd2fdb5d66813ed5 NextCloud (cloud.shc.kanagawa.jp) and Moodle (lms.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/111028 Fri, 19 Aug 2022 18:10:23 -0000 https://status.shc.kanagawa.jp/incident/111028#380783b64d6f16d741765324824f29a3ac08254fd3fd08afa3e5090acd13b906 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/111028 Fri, 19 Aug 2022 18:10:23 -0000 https://status.shc.kanagawa.jp/incident/111028#380783b64d6f16d741765324824f29a3ac08254fd3fd08afa3e5090acd13b906 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/111028 Fri, 19 Aug 2022 18:10:23 -0000 https://status.shc.kanagawa.jp/incident/111028#380783b64d6f16d741765324824f29a3ac08254fd3fd08afa3e5090acd13b906 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/111028 Fri, 19 Aug 2022 15:39:25 -0000 https://status.shc.kanagawa.jp/incident/111028#7b8f6a8d8b555eff81b2efdfec17867c79c510fa0d6a8aae5f9c7ab4c8947539 Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/111028 Fri, 19 Aug 2022 15:30:56 -0000 https://status.shc.kanagawa.jp/incident/111028#2611e27caf5ca6e634a0388b3e660a5b330a8c62f411d8fc3733edf7c273c0ac Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/111028 Fri, 19 Aug 2022 15:01:06 -0000 https://status.shc.kanagawa.jp/incident/111028#9e31e63cc28b874e01993a42dbc149358d5c5c4418618f55612b4a91ca93bbf0 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/111028 Fri, 19 Aug 2022 14:55:00 -0000 https://status.shc.kanagawa.jp/incident/111028#91a73878990be4de249b6f42d3d63f625bd8dede747916264517a63713cc750c Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/110745 Thu, 18 Aug 2022 14:50:34 -0000 https://status.shc.kanagawa.jp/incident/110745#3bc92f2022b29f3c0a70a4536686d9e8bff1803960fb78276cadb15e44dba923 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/110745 Thu, 18 Aug 2022 14:50:34 -0000 https://status.shc.kanagawa.jp/incident/110745#3bc92f2022b29f3c0a70a4536686d9e8bff1803960fb78276cadb15e44dba923 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/110745 Thu, 18 Aug 2022 14:50:34 -0000 https://status.shc.kanagawa.jp/incident/110745#3bc92f2022b29f3c0a70a4536686d9e8bff1803960fb78276cadb15e44dba923 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/110745 Thu, 18 Aug 2022 14:41:54 -0000 https://status.shc.kanagawa.jp/incident/110745#ae7634bef9176c596c70dfde60e474d40735b2a89cedba3cb129447b688ceec3 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/110745 Thu, 18 Aug 2022 14:41:54 -0000 https://status.shc.kanagawa.jp/incident/110745#ae7634bef9176c596c70dfde60e474d40735b2a89cedba3cb129447b688ceec3 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/110745 Thu, 18 Aug 2022 14:41:54 -0000 https://status.shc.kanagawa.jp/incident/110745#ae7634bef9176c596c70dfde60e474d40735b2a89cedba3cb129447b688ceec3 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/109493 Sun, 14 Aug 2022 06:11:07 -0000 https://status.shc.kanagawa.jp/incident/109493#7ce7904f8f7d58c3101a5b363b13396b51d5f31e69bc55a0082c2af2c59544ee Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/109493 Sun, 14 Aug 2022 06:08:45 -0000 https://status.shc.kanagawa.jp/incident/109493#cb1de931286de7a2028fb6358c34db02ce3836fb30665d480c4b15bbaa29bc68 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/109493 Sun, 14 Aug 2022 06:08:27 -0000 https://status.shc.kanagawa.jp/incident/109493#688240070047e6c3e4632167509bc2eee59493735e4a5fb0c0737b4575bf3141 Mastodon(mt.shc.kanagawa.jp) and Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/109493 Sun, 14 Aug 2022 06:08:27 -0000 https://status.shc.kanagawa.jp/incident/109493#688240070047e6c3e4632167509bc2eee59493735e4a5fb0c0737b4575bf3141 Mastodon(mt.shc.kanagawa.jp) and Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/109097 Fri, 12 Aug 2022 14:15:46 -0000 https://status.shc.kanagawa.jp/incident/109097#4520e4c9837c41ee060342294392e4b657fd78b46decebcb2323906d59eca947 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/109097 Fri, 12 Aug 2022 14:12:54 -0000 https://status.shc.kanagawa.jp/incident/109097#a4e6fee47d0b7e1308ffc6223bc95b61af0721924b99b63015925ba724e326c5 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/107476 Sun, 07 Aug 2022 03:32:16 -0000 https://status.shc.kanagawa.jp/incident/107476#e22707484e698f4aa33cc378a2f57a665a8eac92b4ff4f0657f82ddd7e7b9569 Mastodon(mt.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/107476 Sun, 07 Aug 2022 03:32:16 -0000 https://status.shc.kanagawa.jp/incident/107476#e22707484e698f4aa33cc378a2f57a665a8eac92b4ff4f0657f82ddd7e7b9569 Mastodon(mt.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/107476 Sun, 07 Aug 2022 03:32:16 -0000 https://status.shc.kanagawa.jp/incident/107476#e22707484e698f4aa33cc378a2f57a665a8eac92b4ff4f0657f82ddd7e7b9569 Mastodon(mt.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/107476 Sun, 07 Aug 2022 03:27:18 -0000 https://status.shc.kanagawa.jp/incident/107476#0a77460e7e0395675e99430b42bd49d0d40d589582cf23cbfb8f42d965cc0952 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/107476 Sun, 07 Aug 2022 03:19:46 -0000 https://status.shc.kanagawa.jp/incident/107476#121460468dc16741aaa72ca62abba312569c31933ed651a6fea6ae0691a60e79 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and 1 other resource went down. https://status.shc.kanagawa.jp/incident/107476 Sun, 07 Aug 2022 03:19:46 -0000 https://status.shc.kanagawa.jp/incident/107476#121460468dc16741aaa72ca62abba312569c31933ed651a6fea6ae0691a60e79 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and 1 other resource went down. https://status.shc.kanagawa.jp/incident/107476 Sun, 07 Aug 2022 03:19:46 -0000 https://status.shc.kanagawa.jp/incident/107476#121460468dc16741aaa72ca62abba312569c31933ed651a6fea6ae0691a60e79 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and 1 other resource went down. https://status.shc.kanagawa.jp/incident/107476 Sun, 07 Aug 2022 03:19:46 -0000 https://status.shc.kanagawa.jp/incident/107476#121460468dc16741aaa72ca62abba312569c31933ed651a6fea6ae0691a60e79 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and 1 other resource went down. https://status.shc.kanagawa.jp/incident/107476 Sun, 07 Aug 2022 00:04:50 -0000 https://status.shc.kanagawa.jp/incident/107476#e83dcb516c0b2cbae60858072e4a20e2ebb22b2baa14bb4d510ca9c290da0dde Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and 2 other resources recovered. https://status.shc.kanagawa.jp/incident/107476 Sun, 07 Aug 2022 00:04:50 -0000 https://status.shc.kanagawa.jp/incident/107476#e83dcb516c0b2cbae60858072e4a20e2ebb22b2baa14bb4d510ca9c290da0dde Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and 2 other resources recovered. https://status.shc.kanagawa.jp/incident/107476 Sun, 07 Aug 2022 00:04:50 -0000 https://status.shc.kanagawa.jp/incident/107476#e83dcb516c0b2cbae60858072e4a20e2ebb22b2baa14bb4d510ca9c290da0dde Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and 2 other resources recovered. https://status.shc.kanagawa.jp/incident/107476 Sun, 07 Aug 2022 00:04:50 -0000 https://status.shc.kanagawa.jp/incident/107476#e83dcb516c0b2cbae60858072e4a20e2ebb22b2baa14bb4d510ca9c290da0dde Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), and 2 other resources recovered. https://status.shc.kanagawa.jp/incident/107476 Sat, 06 Aug 2022 18:29:00 -0000 https://status.shc.kanagawa.jp/incident/107476#9a0bcc4570dedae8fbe95fb09d738b2aebd5453ae2476abc5b3788fa99fb6b49 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/107476 Sat, 06 Aug 2022 18:12:34 -0000 https://status.shc.kanagawa.jp/incident/107476#7250980f0369570e40b75fa1384887db8cab4c3298a06a557c765dde28ed7d06 Mastodon(mt.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), NextCloud (cloud.shc.kanagawa.jp), and 1 other resource went down. https://status.shc.kanagawa.jp/incident/107476 Sat, 06 Aug 2022 18:12:34 -0000 https://status.shc.kanagawa.jp/incident/107476#7250980f0369570e40b75fa1384887db8cab4c3298a06a557c765dde28ed7d06 Mastodon(mt.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), NextCloud (cloud.shc.kanagawa.jp), and 1 other resource went down. https://status.shc.kanagawa.jp/incident/107476 Sat, 06 Aug 2022 18:12:34 -0000 https://status.shc.kanagawa.jp/incident/107476#7250980f0369570e40b75fa1384887db8cab4c3298a06a557c765dde28ed7d06 Mastodon(mt.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), NextCloud (cloud.shc.kanagawa.jp), and 1 other resource went down. https://status.shc.kanagawa.jp/incident/107251 Fri, 05 Aug 2022 13:18:14 -0000 https://status.shc.kanagawa.jp/incident/107251#bbb814ead5e5b686311d301e41744a9210514e76419f1b1ecd855cc6c87ef954 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/107251 Fri, 05 Aug 2022 13:18:02 -0000 https://status.shc.kanagawa.jp/incident/107251#b7c4a0a5a2984b1f3077bdac2a44f9d8c2ccaf37f4e5eb68ea5992e46bda801d Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/106890 Thu, 04 Aug 2022 03:42:16 -0000 https://status.shc.kanagawa.jp/incident/106890#6a4053837584e094fc9cf3cf6226ac48bcaf3a77876650b561d12c3d6116d57b Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/106890 Thu, 04 Aug 2022 03:27:01 -0000 https://status.shc.kanagawa.jp/incident/106890#c9afab9688067b79d5731fe29808f36c2d2209ba3e36bb2e907900ae4bde6eb0 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/105519 Fri, 29 Jul 2022 07:00:05 -0000 https://status.shc.kanagawa.jp/incident/105519#0cc1373d55486a723b039717262f6e8205b147a6e463925b510c17186fc587a8 Misskey(mk.shc.kanagawa.jp) and Moodle (lms.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/105519 Fri, 29 Jul 2022 06:54:17 -0000 https://status.shc.kanagawa.jp/incident/105519#c2f128e785ce9a6e4cad298cc8b47e0b5851abf62e3a196834f4ca11de72015b NextCloud (cloud.shc.kanagawa.jp) and NextCloud Maintenance recovered. https://status.shc.kanagawa.jp/incident/105519 Fri, 29 Jul 2022 06:54:17 -0000 https://status.shc.kanagawa.jp/incident/105519#c2f128e785ce9a6e4cad298cc8b47e0b5851abf62e3a196834f4ca11de72015b NextCloud (cloud.shc.kanagawa.jp) and NextCloud Maintenance recovered. https://status.shc.kanagawa.jp/incident/105519 Fri, 29 Jul 2022 06:43:09 -0000 https://status.shc.kanagawa.jp/incident/105519#009f58e132b82b73d2258ebe15c2539e8e709fe6055cdcb10ac47f947d5a758f NextCloud Maintenance went down. https://status.shc.kanagawa.jp/incident/105519 Fri, 29 Jul 2022 06:38:13 -0000 https://status.shc.kanagawa.jp/incident/105519#f28f8a6453fd7436ce064bce7c5edbe2b74af63d63ab05c77a746102503995ae Mastodon(mt.shc.kanagawa.jp) and Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/105519 Fri, 29 Jul 2022 06:38:13 -0000 https://status.shc.kanagawa.jp/incident/105519#f28f8a6453fd7436ce064bce7c5edbe2b74af63d63ab05c77a746102503995ae Mastodon(mt.shc.kanagawa.jp) and Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/105519 Fri, 29 Jul 2022 06:33:46 -0000 https://status.shc.kanagawa.jp/incident/105519#c68ac8ea160cd1002005fddc53abe86301b0641642548e88c426476728bc62b7 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/105519 Fri, 29 Jul 2022 06:32:16 -0000 https://status.shc.kanagawa.jp/incident/105519#451d100327cec6ffc5f7127df8f66d933c646a867f07943c4bb77d10b5171525 Mastodon(mt.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), NextCloud (cloud.shc.kanagawa.jp), and 1 other resource went down. https://status.shc.kanagawa.jp/incident/105519 Fri, 29 Jul 2022 06:32:16 -0000 https://status.shc.kanagawa.jp/incident/105519#451d100327cec6ffc5f7127df8f66d933c646a867f07943c4bb77d10b5171525 Mastodon(mt.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), NextCloud (cloud.shc.kanagawa.jp), and 1 other resource went down. https://status.shc.kanagawa.jp/incident/105519 Fri, 29 Jul 2022 06:32:16 -0000 https://status.shc.kanagawa.jp/incident/105519#451d100327cec6ffc5f7127df8f66d933c646a867f07943c4bb77d10b5171525 Mastodon(mt.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), NextCloud (cloud.shc.kanagawa.jp), and 1 other resource went down. https://status.shc.kanagawa.jp/incident/105310 Thu, 28 Jul 2022 11:31:23 -0000 https://status.shc.kanagawa.jp/incident/105310#60210f830e854d4e96880ec88c31afa36e601c96a1c19d749e69457724cefa89 Moodle (lms.shc.kanagawa.jp) went down and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/105310 Thu, 28 Jul 2022 11:25:17 -0000 https://status.shc.kanagawa.jp/incident/105310#8b4e3abadd4d3bcf4a1dd5678ee3d6c5a1066b2ebbfca56edded3febeaaa4272 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/104540 Mon, 25 Jul 2022 13:38:42 -0000 https://status.shc.kanagawa.jp/incident/104540#ca29d0888025958f9418e90a83621eb1672df6f97c0d72f8418f82d33e208cdf Pleroma(pr.shc.kanagawa.jp), NextCloud (cloud.shc.kanagawa.jp), and Moodle (lms.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/104540 Mon, 25 Jul 2022 13:38:42 -0000 https://status.shc.kanagawa.jp/incident/104540#ca29d0888025958f9418e90a83621eb1672df6f97c0d72f8418f82d33e208cdf Pleroma(pr.shc.kanagawa.jp), NextCloud (cloud.shc.kanagawa.jp), and Moodle (lms.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/104540 Mon, 25 Jul 2022 13:35:02 -0000 https://status.shc.kanagawa.jp/incident/104540#3225064751807f62056879006e79076a8540615db490d33e97ebb116f67cbafa NextCloud Maintenance recovered. https://status.shc.kanagawa.jp/incident/104540 Mon, 25 Jul 2022 13:33:40 -0000 https://status.shc.kanagawa.jp/incident/104540#1a34fc5eb773cb63e3428da88d4a2e69712c2cb643793b0955580b62f6b893d6 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/104540 Mon, 25 Jul 2022 13:31:32 -0000 https://status.shc.kanagawa.jp/incident/104540#133523ab0b43cff96bec82227f9dbd812ad115f39207a5f2e5275f12343b0b6c Pleroma(pr.shc.kanagawa.jp), Moodle (lms.shc.kanagawa.jp), and NextCloud Maintenance went down. https://status.shc.kanagawa.jp/incident/104540 Mon, 25 Jul 2022 13:31:32 -0000 https://status.shc.kanagawa.jp/incident/104540#133523ab0b43cff96bec82227f9dbd812ad115f39207a5f2e5275f12343b0b6c Pleroma(pr.shc.kanagawa.jp), Moodle (lms.shc.kanagawa.jp), and NextCloud Maintenance went down. https://status.shc.kanagawa.jp/incident/104540 Mon, 25 Jul 2022 12:56:04 -0000 https://status.shc.kanagawa.jp/incident/104540#183110b26c99ad48796868f8d5aed50f908ebc7cc6280ddecfa99186bae168e7 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/104540 Mon, 25 Jul 2022 12:47:21 -0000 https://status.shc.kanagawa.jp/incident/104540#7627a07b043105000be5727eabcabd3feee151ec7cccd8267ca5a68d84852fd3 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/103098 Tue, 19 Jul 2022 15:56:08 -0000 https://status.shc.kanagawa.jp/incident/103098#7765fd0a68604b256ef5a16f85dc6dfc5957499641cc04e1874f723c42785372 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/103098 Tue, 19 Jul 2022 15:56:08 -0000 https://status.shc.kanagawa.jp/incident/103098#7765fd0a68604b256ef5a16f85dc6dfc5957499641cc04e1874f723c42785372 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/103098 Tue, 19 Jul 2022 15:52:38 -0000 https://status.shc.kanagawa.jp/incident/103098#c0e5e4e10c06d0e55b4984a031364a2898ac51c1c102d2ae8fffeb42e22d8934 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/103098 Tue, 19 Jul 2022 15:49:56 -0000 https://status.shc.kanagawa.jp/incident/103098#d05bbc3a76c64f974458f54f6f38addd8d5c10f7e965ae62238f12dcd48ed95e Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/103098 Tue, 19 Jul 2022 15:49:56 -0000 https://status.shc.kanagawa.jp/incident/103098#d05bbc3a76c64f974458f54f6f38addd8d5c10f7e965ae62238f12dcd48ed95e Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/103098 Tue, 19 Jul 2022 15:49:56 -0000 https://status.shc.kanagawa.jp/incident/103098#d05bbc3a76c64f974458f54f6f38addd8d5c10f7e965ae62238f12dcd48ed95e Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/102740 Mon, 18 Jul 2022 09:21:20 -0000 https://status.shc.kanagawa.jp/incident/102740#cd2f757da1ff4a0257963d5444ac8953f9446217f876be65282927cc3a27cedb Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/102740 Mon, 18 Jul 2022 09:15:40 -0000 https://status.shc.kanagawa.jp/incident/102740#f689c5bd46622ee7480f33e0be8401d4e60cefb16415afa97cddd2a0e6dc8d9f Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/102740 Mon, 18 Jul 2022 09:15:40 -0000 https://status.shc.kanagawa.jp/incident/102740#f689c5bd46622ee7480f33e0be8401d4e60cefb16415afa97cddd2a0e6dc8d9f Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/102740 Mon, 18 Jul 2022 09:09:48 -0000 https://status.shc.kanagawa.jp/incident/102740#049c70bae688dd8a82fd252e49ae1c02083fc4945470eb37cd217d905550f44d Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/102740 Mon, 18 Jul 2022 09:09:48 -0000 https://status.shc.kanagawa.jp/incident/102740#049c70bae688dd8a82fd252e49ae1c02083fc4945470eb37cd217d905550f44d Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/102740 Mon, 18 Jul 2022 09:09:48 -0000 https://status.shc.kanagawa.jp/incident/102740#049c70bae688dd8a82fd252e49ae1c02083fc4945470eb37cd217d905550f44d Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/102537 Sun, 17 Jul 2022 07:18:02 -0000 https://status.shc.kanagawa.jp/incident/102537#7d98fc24f12943db284317a77e0d938c0b471ca5ac458bdd6d3489dfe5596011 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/102537 Sun, 17 Jul 2022 07:18:02 -0000 https://status.shc.kanagawa.jp/incident/102537#7d98fc24f12943db284317a77e0d938c0b471ca5ac458bdd6d3489dfe5596011 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/102537 Sun, 17 Jul 2022 07:16:19 -0000 https://status.shc.kanagawa.jp/incident/102537#2be4834255268a3bd044efe57fc11b4ae7067e7125d11e53d7c7a0bbdfd1abc5 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/102537 Sun, 17 Jul 2022 07:16:19 -0000 https://status.shc.kanagawa.jp/incident/102537#2be4834255268a3bd044efe57fc11b4ae7067e7125d11e53d7c7a0bbdfd1abc5 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/100789 Sat, 09 Jul 2022 13:59:42 -0000 https://status.shc.kanagawa.jp/incident/100789#59d5fee26af246fe99b51e4b7bf642b3c01e3f58075cd3dd00ed155d4a383008 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/100789 Sat, 09 Jul 2022 13:52:30 -0000 https://status.shc.kanagawa.jp/incident/100789#e2db1a3537d7640f064b075ab1f03b9a8129507e5e0e9ef1b0a58da05bbae610 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/100058 Wed, 06 Jul 2022 12:04:57 -0000 https://status.shc.kanagawa.jp/incident/100058#8634946c26b15ffec5feb9cf30e114475bdbf8844c45629632e11e5dd6a55f1b Activity Relay(relay.shc.kanagawa.jp), Pub-Relay(pub-relay.shc.kanagawa.jp), Internet Relay Chat (irc.shc.kanagawa.jp), and 1 other resource recovered. https://status.shc.kanagawa.jp/incident/100058 Wed, 06 Jul 2022 12:04:57 -0000 https://status.shc.kanagawa.jp/incident/100058#8634946c26b15ffec5feb9cf30e114475bdbf8844c45629632e11e5dd6a55f1b Activity Relay(relay.shc.kanagawa.jp), Pub-Relay(pub-relay.shc.kanagawa.jp), Internet Relay Chat (irc.shc.kanagawa.jp), and 1 other resource recovered. https://status.shc.kanagawa.jp/incident/100058 Wed, 06 Jul 2022 12:04:57 -0000 https://status.shc.kanagawa.jp/incident/100058#8634946c26b15ffec5feb9cf30e114475bdbf8844c45629632e11e5dd6a55f1b Activity Relay(relay.shc.kanagawa.jp), Pub-Relay(pub-relay.shc.kanagawa.jp), Internet Relay Chat (irc.shc.kanagawa.jp), and 1 other resource recovered. https://status.shc.kanagawa.jp/incident/100058 Wed, 06 Jul 2022 12:04:57 -0000 https://status.shc.kanagawa.jp/incident/100058#8634946c26b15ffec5feb9cf30e114475bdbf8844c45629632e11e5dd6a55f1b Activity Relay(relay.shc.kanagawa.jp), Pub-Relay(pub-relay.shc.kanagawa.jp), Internet Relay Chat (irc.shc.kanagawa.jp), and 1 other resource recovered. https://status.shc.kanagawa.jp/incident/100058 Wed, 06 Jul 2022 11:57:09 -0000 https://status.shc.kanagawa.jp/incident/100058#c2698ee60c26272228445578b2c7e9698f80118fe34a95ae98c5a9939ce96345 Activity Relay(relay.shc.kanagawa.jp), Pub-Relay(pub-relay.shc.kanagawa.jp), Internet Relay Chat (irc.shc.kanagawa.jp), and 1 other resource went down. https://status.shc.kanagawa.jp/incident/100058 Wed, 06 Jul 2022 11:57:09 -0000 https://status.shc.kanagawa.jp/incident/100058#c2698ee60c26272228445578b2c7e9698f80118fe34a95ae98c5a9939ce96345 Activity Relay(relay.shc.kanagawa.jp), Pub-Relay(pub-relay.shc.kanagawa.jp), Internet Relay Chat (irc.shc.kanagawa.jp), and 1 other resource went down. https://status.shc.kanagawa.jp/incident/100058 Wed, 06 Jul 2022 11:57:09 -0000 https://status.shc.kanagawa.jp/incident/100058#c2698ee60c26272228445578b2c7e9698f80118fe34a95ae98c5a9939ce96345 Activity Relay(relay.shc.kanagawa.jp), Pub-Relay(pub-relay.shc.kanagawa.jp), Internet Relay Chat (irc.shc.kanagawa.jp), and 1 other resource went down. https://status.shc.kanagawa.jp/incident/100058 Wed, 06 Jul 2022 11:57:09 -0000 https://status.shc.kanagawa.jp/incident/100058#c2698ee60c26272228445578b2c7e9698f80118fe34a95ae98c5a9939ce96345 Activity Relay(relay.shc.kanagawa.jp), Pub-Relay(pub-relay.shc.kanagawa.jp), Internet Relay Chat (irc.shc.kanagawa.jp), and 1 other resource went down. https://status.shc.kanagawa.jp/incident/97556 Sat, 25 Jun 2022 06:08:57 -0000 https://status.shc.kanagawa.jp/incident/97556#b22ee91d0aad69df6b8cd132d075d6ca365bd1a60f282d62e76345e2f9fb708f Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/97556 Sat, 25 Jun 2022 06:00:05 -0000 https://status.shc.kanagawa.jp/incident/97556#bd8ef83af202c80855249a129313e35545fc2719a922a3be34a060e197d0958d Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/96859 Wed, 22 Jun 2022 05:57:18 -0000 https://status.shc.kanagawa.jp/incident/96859#0f8781b9239a2a675bde9c811c27f204f3ddbbfece3c8bed5bc932a93bea101f Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/96859 Wed, 22 Jun 2022 05:46:15 -0000 https://status.shc.kanagawa.jp/incident/96859#d84a04fb1ebf31253c309463b6ff2c725d88d71f926ee51e740670493bbb5801 NextCloud (cloud.shc.kanagawa.jp) and Moodle (lms.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/96859 Wed, 22 Jun 2022 05:31:38 -0000 https://status.shc.kanagawa.jp/incident/96859#5fa7b76e74deb16501b25a6104b0bc30e41f908e69d41f0086a46222127e5db7 Misskey(mk.shc.kanagawa.jp), NextCloud (cloud.shc.kanagawa.jp), and Moodle (lms.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/96859 Wed, 22 Jun 2022 05:31:38 -0000 https://status.shc.kanagawa.jp/incident/96859#5fa7b76e74deb16501b25a6104b0bc30e41f908e69d41f0086a46222127e5db7 Misskey(mk.shc.kanagawa.jp), NextCloud (cloud.shc.kanagawa.jp), and Moodle (lms.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/96440 Tue, 21 Jun 2022 08:28:25 -0000 https://status.shc.kanagawa.jp/incident/96440#861332dcf98e8eb9ba8883a038a267b073a63300b9c1e627ca5bcae255e7e036 Mastodon(mt.shc.kanagawa.jp) and NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/96440 Tue, 21 Jun 2022 08:28:25 -0000 https://status.shc.kanagawa.jp/incident/96440#861332dcf98e8eb9ba8883a038a267b073a63300b9c1e627ca5bcae255e7e036 Mastodon(mt.shc.kanagawa.jp) and NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/96440 Tue, 21 Jun 2022 07:58:56 -0000 https://status.shc.kanagawa.jp/incident/96440#97ca33a69582c49562ab81c5769418cb62cf963964554f3a8087394667af0c0b Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/96440 Tue, 21 Jun 2022 07:57:31 -0000 https://status.shc.kanagawa.jp/incident/96440#70095056b8f54dfa80e5eac45cc4af360255c47daf43ce0fd930861d68ca2be0 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/96440 Tue, 21 Jun 2022 07:42:39 -0000 https://status.shc.kanagawa.jp/incident/96440#8fd3ac2059339d6a426363d35737b71b5c452fd916a6cdbab72fc79b068a478a Mastodon(mt.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), Activity Relay(relay.shc.kanagawa.jp), and 2 other resources went down. https://status.shc.kanagawa.jp/incident/96440 Tue, 21 Jun 2022 07:42:39 -0000 https://status.shc.kanagawa.jp/incident/96440#8fd3ac2059339d6a426363d35737b71b5c452fd916a6cdbab72fc79b068a478a Mastodon(mt.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), Activity Relay(relay.shc.kanagawa.jp), and 2 other resources went down. https://status.shc.kanagawa.jp/incident/96440 Tue, 21 Jun 2022 07:42:39 -0000 https://status.shc.kanagawa.jp/incident/96440#8fd3ac2059339d6a426363d35737b71b5c452fd916a6cdbab72fc79b068a478a Mastodon(mt.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), Activity Relay(relay.shc.kanagawa.jp), and 2 other resources went down. https://status.shc.kanagawa.jp/incident/96440 Tue, 21 Jun 2022 07:42:39 -0000 https://status.shc.kanagawa.jp/incident/96440#8fd3ac2059339d6a426363d35737b71b5c452fd916a6cdbab72fc79b068a478a Mastodon(mt.shc.kanagawa.jp), Misskey(mk.shc.kanagawa.jp), Activity Relay(relay.shc.kanagawa.jp), and 2 other resources went down. https://status.shc.kanagawa.jp/incident/96176 Mon, 20 Jun 2022 14:50:32 -0000 https://status.shc.kanagawa.jp/incident/96176#13ddc6c78f03ae107d52c5dc07df4946db556b931871eddf6b6dfd6bbfe757b9 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/96176 Mon, 20 Jun 2022 14:49:52 -0000 https://status.shc.kanagawa.jp/incident/96176#8fbc9e499424d997e4458cc2d7727a331b4be342c1eddda71307f010d17c045a Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/96176 Mon, 20 Jun 2022 11:03:27 -0000 https://status.shc.kanagawa.jp/incident/96176#bb72bb0463be354e9c9bee81e3c2a40db2aaecf0b11e637caa2c21ee76e66d5c NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/96176 Mon, 20 Jun 2022 10:50:53 -0000 https://status.shc.kanagawa.jp/incident/96176#fb331a8688a05afa8a128f68280fd9d04d26e58d7dd96d1740accd1faf6f98a8 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/93389 Wed, 08 Jun 2022 17:10:25 -0000 https://status.shc.kanagawa.jp/incident/93389#0f8524837e526e482a8c613c1b4a0a1329f686f56d2b60a5ec238cda7b956457 Activity Relay(relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/93389 Wed, 08 Jun 2022 12:53:09 -0000 https://status.shc.kanagawa.jp/incident/93389#a4441777bec86cfafd23ff06db23580eed702d4ef5a9e57abfa59813b8b6c543 Activity Relay(relay.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/92498 Sat, 04 Jun 2022 16:13:29 -0000 https://status.shc.kanagawa.jp/incident/92498#24045b0db70f60dbd593a2e5ab25fa91b835aa36047af574a1dcbeafa00c73c3 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/92498 Sat, 04 Jun 2022 16:08:31 -0000 https://status.shc.kanagawa.jp/incident/92498#64745d0f5d60c8f5b4b70682c22cc2faccac240755712d4f9bcc35fd6104e0e2 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/90555 Thu, 26 May 2022 09:08:25 -0000 https://status.shc.kanagawa.jp/incident/90555#882a20d40142e1ff6bb28a29a5566fb67c4445b627ddf61a258675889b95f000 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/90555 Thu, 26 May 2022 09:08:25 -0000 https://status.shc.kanagawa.jp/incident/90555#882a20d40142e1ff6bb28a29a5566fb67c4445b627ddf61a258675889b95f000 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/90555 Thu, 26 May 2022 09:08:25 -0000 https://status.shc.kanagawa.jp/incident/90555#882a20d40142e1ff6bb28a29a5566fb67c4445b627ddf61a258675889b95f000 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/90555 Thu, 26 May 2022 09:05:24 -0000 https://status.shc.kanagawa.jp/incident/90555#0bedb7531ee231305a68a715296c5003962b75ba9b25df2cf013e9960e0d5571 NextCloud (cloud.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/90555 Thu, 26 May 2022 08:59:00 -0000 https://status.shc.kanagawa.jp/incident/90555#fbfdb5e51f3c4ea19a5340686798b596f42721e9b1afb15c31081a68d14ea578 NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/90555 Thu, 26 May 2022 08:52:32 -0000 https://status.shc.kanagawa.jp/incident/90555#9f97c8f3c852ac933f3cd5d24b5ad40c0fee68ee86f436c42e5a7f8c5ea574fc Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/90555 Thu, 26 May 2022 08:52:32 -0000 https://status.shc.kanagawa.jp/incident/90555#9f97c8f3c852ac933f3cd5d24b5ad40c0fee68ee86f436c42e5a7f8c5ea574fc Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/90555 Thu, 26 May 2022 08:52:32 -0000 https://status.shc.kanagawa.jp/incident/90555#9f97c8f3c852ac933f3cd5d24b5ad40c0fee68ee86f436c42e5a7f8c5ea574fc Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/89990 Tue, 24 May 2022 07:10:57 -0000 https://status.shc.kanagawa.jp/incident/89990#9af0c691fe78b82d88ca6a80a23cee40411a9d12cbc0fa53e00143145b0e1327 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/89990 Tue, 24 May 2022 07:10:08 -0000 https://status.shc.kanagawa.jp/incident/89990#d57fe2f9828ac62c9200f0c6c8fb76bffd4fa320d019cc8ee5689f2b2940837f Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/89990 Tue, 24 May 2022 07:09:54 -0000 https://status.shc.kanagawa.jp/incident/89990#cf91e8fa6cd4e765a7f154a5430500e618dc3bbf0a80fd383b45c197f33d1e77 Pleroma(pr.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/89990 Tue, 24 May 2022 07:09:54 -0000 https://status.shc.kanagawa.jp/incident/89990#cf91e8fa6cd4e765a7f154a5430500e618dc3bbf0a80fd383b45c197f33d1e77 Pleroma(pr.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/89990 Tue, 24 May 2022 01:23:51 -0000 https://status.shc.kanagawa.jp/incident/89990#88401b2f04f68aa19eaa0150d32f5e426edb7507dfbde340c91436d5c8a9d5c4 NextCloud (cloud.shc.kanagawa.jp) and Moodle (lms.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/89990 Tue, 24 May 2022 01:22:53 -0000 https://status.shc.kanagawa.jp/incident/89990#aa2a4eb1338dfa498703931e9ddc3884c08cf61539f8e4e7590ea5f001d48529 Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/89990 Tue, 24 May 2022 01:22:52 -0000 https://status.shc.kanagawa.jp/incident/89990#c7bde0c75122de5cf369fda7fd4eee164e20ffd1968fe547d22d49defbf35ce0 Activity Relay(relay.shc.kanagawa.jp) and Internet Relay Chat Web (webirc.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/89990 Tue, 24 May 2022 01:22:52 -0000 https://status.shc.kanagawa.jp/incident/89990#c7bde0c75122de5cf369fda7fd4eee164e20ffd1968fe547d22d49defbf35ce0 Activity Relay(relay.shc.kanagawa.jp) and Internet Relay Chat Web (webirc.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/89990 Tue, 24 May 2022 01:22:27 -0000 https://status.shc.kanagawa.jp/incident/89990#7ad1f850e08d934b84b2becaf4f6b0456dae73b20cf4d6863e51f1a81202f366 Internet Relay Chat (irc.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/89990 Tue, 24 May 2022 01:20:07 -0000 https://status.shc.kanagawa.jp/incident/89990#d6c558185b84236c263ef73d00680a8eed5a53597e00ba50848fcc49e3505729 Internet Relay Chat Web (webirc.shc.kanagawa.jp) went down and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/89990 Tue, 24 May 2022 01:20:07 -0000 https://status.shc.kanagawa.jp/incident/89990#d6c558185b84236c263ef73d00680a8eed5a53597e00ba50848fcc49e3505729 Internet Relay Chat Web (webirc.shc.kanagawa.jp) went down and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/89990 Tue, 24 May 2022 01:16:55 -0000 https://status.shc.kanagawa.jp/incident/89990#2af98b6bb89bb61111b8a9359b5ce8ab31554831784734aedbeadc41d459bfd3 Misskey(mk.shc.kanagawa.jp), Activity Relay(relay.shc.kanagawa.jp), Pub-Relay(pub-relay.shc.kanagawa.jp), and 1 other resource went down. https://status.shc.kanagawa.jp/incident/89990 Tue, 24 May 2022 01:16:55 -0000 https://status.shc.kanagawa.jp/incident/89990#2af98b6bb89bb61111b8a9359b5ce8ab31554831784734aedbeadc41d459bfd3 Misskey(mk.shc.kanagawa.jp), Activity Relay(relay.shc.kanagawa.jp), Pub-Relay(pub-relay.shc.kanagawa.jp), and 1 other resource went down. https://status.shc.kanagawa.jp/incident/89990 Tue, 24 May 2022 01:16:55 -0000 https://status.shc.kanagawa.jp/incident/89990#2af98b6bb89bb61111b8a9359b5ce8ab31554831784734aedbeadc41d459bfd3 Misskey(mk.shc.kanagawa.jp), Activity Relay(relay.shc.kanagawa.jp), Pub-Relay(pub-relay.shc.kanagawa.jp), and 1 other resource went down. https://status.shc.kanagawa.jp/incident/89990 Tue, 24 May 2022 01:16:55 -0000 https://status.shc.kanagawa.jp/incident/89990#2af98b6bb89bb61111b8a9359b5ce8ab31554831784734aedbeadc41d459bfd3 Misskey(mk.shc.kanagawa.jp), Activity Relay(relay.shc.kanagawa.jp), Pub-Relay(pub-relay.shc.kanagawa.jp), and 1 other resource went down. https://status.shc.kanagawa.jp/incident/89990 Tue, 24 May 2022 01:11:31 -0000 https://status.shc.kanagawa.jp/incident/89990#99785fe598a481613a5c9155e3a0da1e1f6b8a507794d7f80fb644f8d6e5c86b Pub-Relay(pub-relay.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/89990 Tue, 24 May 2022 01:07:34 -0000 https://status.shc.kanagawa.jp/incident/89990#e539cbbf6ac4f35751f8dbe107c8fce146fcf7d7c69bd972ae0f69f19512b979 Pub-Relay(pub-relay.shc.kanagawa.jp) and Moodle (lms.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/89990 Tue, 24 May 2022 01:02:04 -0000 https://status.shc.kanagawa.jp/incident/89990#dd27eb1ee5f3993cf981629ac89d09b1b0774b76077cf571e0a1b879d14c65cf Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/89990 Tue, 24 May 2022 00:58:35 -0000 https://status.shc.kanagawa.jp/incident/89990#6d83ab6d476e0ccd261cc468dd4b499ad1fcc391737b1f36d858a1f5325f8b6f Pleroma(pr.shc.kanagawa.jp) and NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/89990 Tue, 24 May 2022 00:58:35 -0000 https://status.shc.kanagawa.jp/incident/89990#6d83ab6d476e0ccd261cc468dd4b499ad1fcc391737b1f36d858a1f5325f8b6f Pleroma(pr.shc.kanagawa.jp) and NextCloud (cloud.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/88960 Thu, 19 May 2022 15:05:44 -0000 https://status.shc.kanagawa.jp/incident/88960#0186dc6050da6eb6133e41a2888bd308cb464548648540dbfc5093ee400be58a Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/88960 Thu, 19 May 2022 15:05:44 -0000 https://status.shc.kanagawa.jp/incident/88960#0186dc6050da6eb6133e41a2888bd308cb464548648540dbfc5093ee400be58a Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/88960 Thu, 19 May 2022 15:05:44 -0000 https://status.shc.kanagawa.jp/incident/88960#0186dc6050da6eb6133e41a2888bd308cb464548648540dbfc5093ee400be58a Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/88960 Thu, 19 May 2022 14:56:38 -0000 https://status.shc.kanagawa.jp/incident/88960#b1682a4030985fddfb5d13b14256b9351072bc26038a66404955f36c11bcfd84 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/88960 Thu, 19 May 2022 14:56:38 -0000 https://status.shc.kanagawa.jp/incident/88960#b1682a4030985fddfb5d13b14256b9351072bc26038a66404955f36c11bcfd84 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/88960 Thu, 19 May 2022 14:56:38 -0000 https://status.shc.kanagawa.jp/incident/88960#b1682a4030985fddfb5d13b14256b9351072bc26038a66404955f36c11bcfd84 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/88513 Tue, 17 May 2022 05:40:18 -0000 https://status.shc.kanagawa.jp/incident/88513#f6580a20e30263179c207f1096a9be29def52d2d0d022be0a7c418bc54cc0a35 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/88513 Tue, 17 May 2022 05:39:53 -0000 https://status.shc.kanagawa.jp/incident/88513#b69bbdca99cb3a2bab073f3f2ddec4b0d500ea44d0643ba4ca96e25560b86ed0 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/88513 Tue, 17 May 2022 05:39:42 -0000 https://status.shc.kanagawa.jp/incident/88513#da55be297220f9ef108d882b9d1a2c9894396c98384fd48960bfae42773987b3 Pleroma(pr.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/88513 Tue, 17 May 2022 05:39:42 -0000 https://status.shc.kanagawa.jp/incident/88513#da55be297220f9ef108d882b9d1a2c9894396c98384fd48960bfae42773987b3 Pleroma(pr.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/88513 Tue, 17 May 2022 01:09:40 -0000 https://status.shc.kanagawa.jp/incident/88513#4feae7377db4da442d1229fcbdcc1b9aaea2f0a454b92443733e8a7ff9685c77 NextCloud (cloud.shc.kanagawa.jp) and Moodle (lms.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/88513 Tue, 17 May 2022 01:05:01 -0000 https://status.shc.kanagawa.jp/incident/88513#446bcea111e4978f3808397fa9e65918009de62bbe6e761bc3ae3dff3b920261 NextCloud (cloud.shc.kanagawa.jp) and Moodle (lms.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/88217 Sun, 15 May 2022 12:13:39 -0000 https://status.shc.kanagawa.jp/incident/88217#c740eac349f3315d43215289e2c42adc4622851452108d84a9cc9ecf4aac55cb Internet Relay Chat (irc.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/88217 Sun, 15 May 2022 11:53:40 -0000 https://status.shc.kanagawa.jp/incident/88217#f297b6d960a2b10aff5843174310e5998d17c61215587929a7d272783ac46dae Internet Relay Chat (irc.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/86793 Mon, 09 May 2022 13:41:07 -0000 https://status.shc.kanagawa.jp/incident/86793#4ba24d7891bca31d3e9e6101f707f4ecab0cdc36c8d558ab148070c0f32247b8 Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/86793 Mon, 09 May 2022 13:28:31 -0000 https://status.shc.kanagawa.jp/incident/86793#08bd333b70c7bb895215739ffdf59736187ef2b052361ec5ac4b2587acaf3569 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/85706 Wed, 04 May 2022 08:26:03 -0000 https://status.shc.kanagawa.jp/incident/85706#f7e74d02f59103652d51a0ef08040b773ca032cfb2a95376dd291924cbecab6d Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/85706 Wed, 04 May 2022 08:19:45 -0000 https://status.shc.kanagawa.jp/incident/85706#5a5c9930628eefa8d4c8b81f7385a4464118f174470bea9b4f40d8fcb1d637f3 Mastodon(mt.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/85706 Wed, 04 May 2022 03:49:54 -0000 https://status.shc.kanagawa.jp/incident/85706#bc92db2612c11d8c9f4d774ce7b8f07ac147916b42801e30cca1889ae4587454 Mastodon(mt.shc.kanagawa.jp) and Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/85706 Wed, 04 May 2022 03:49:54 -0000 https://status.shc.kanagawa.jp/incident/85706#bc92db2612c11d8c9f4d774ce7b8f07ac147916b42801e30cca1889ae4587454 Mastodon(mt.shc.kanagawa.jp) and Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/85706 Wed, 04 May 2022 03:31:50 -0000 https://status.shc.kanagawa.jp/incident/85706#67ff63e4b2db18d13e83b0575cb1eae55d9b8119e650ba45fee800be41c9bb94 Mastodon(mt.shc.kanagawa.jp) and Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/85706 Wed, 04 May 2022 03:31:50 -0000 https://status.shc.kanagawa.jp/incident/85706#67ff63e4b2db18d13e83b0575cb1eae55d9b8119e650ba45fee800be41c9bb94 Mastodon(mt.shc.kanagawa.jp) and Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/84768 Fri, 29 Apr 2022 11:07:35 -0000 https://status.shc.kanagawa.jp/incident/84768#ac8423739c9e9857235073f7172eeeffef727dce8b44b9012a959909d96709c5 Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/84768 Fri, 29 Apr 2022 11:03:13 -0000 https://status.shc.kanagawa.jp/incident/84768#5b89969918ba4397a804db3bccca87e32860afd8a9a9ad2bd7be38e366f83fa9 Pleroma(pr.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/84768 Fri, 29 Apr 2022 11:03:13 -0000 https://status.shc.kanagawa.jp/incident/84768#5b89969918ba4397a804db3bccca87e32860afd8a9a9ad2bd7be38e366f83fa9 Pleroma(pr.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/84768 Fri, 29 Apr 2022 10:56:49 -0000 https://status.shc.kanagawa.jp/incident/84768#089330f885412971cfbb49e5cb93825330be19a233dd841703066ca6482ec060 Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/84768 Fri, 29 Apr 2022 10:37:34 -0000 https://status.shc.kanagawa.jp/incident/84768#4dc5662085b71532192467580a3d618bf16103a3878ab839555eb8d1d113d947 Mastodon(mt.shc.kanagawa.jp) and Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/84768 Fri, 29 Apr 2022 10:37:34 -0000 https://status.shc.kanagawa.jp/incident/84768#4dc5662085b71532192467580a3d618bf16103a3878ab839555eb8d1d113d947 Mastodon(mt.shc.kanagawa.jp) and Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/84768 Fri, 29 Apr 2022 10:31:35 -0000 https://status.shc.kanagawa.jp/incident/84768#7322ca7b29896bf8403eee666b6f5db2e8a0c00d78699d38e095268c8f83196a Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/84768 Fri, 29 Apr 2022 10:28:17 -0000 https://status.shc.kanagawa.jp/incident/84768#8a2decbb59b9758f7fd8b280befedf621c965f90673d6ce2f09724da6b2f5f54 Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/84768 Fri, 29 Apr 2022 10:22:52 -0000 https://status.shc.kanagawa.jp/incident/84768#7b32af9f2406fa0272796d773038d3da3566cec034118dd64f9c6d7d50a757f9 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/84768 Fri, 29 Apr 2022 10:22:32 -0000 https://status.shc.kanagawa.jp/incident/84768#adf3fe80a15084a3975baa892a35e0a61097c2d6a5026563687dffb0f08b3699 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/84768 Fri, 29 Apr 2022 10:22:32 -0000 https://status.shc.kanagawa.jp/incident/84768#adf3fe80a15084a3975baa892a35e0a61097c2d6a5026563687dffb0f08b3699 Mastodon(mt.shc.kanagawa.jp) and Misskey(mk.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/84768 Fri, 29 Apr 2022 10:21:50 -0000 https://status.shc.kanagawa.jp/incident/84768#8a3ff4d6d9e46d8008585da9e0a87315e82e3a5ab3a675bbc0af7e8c11bc7bd2 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/84768 Fri, 29 Apr 2022 10:21:50 -0000 https://status.shc.kanagawa.jp/incident/84768#8a3ff4d6d9e46d8008585da9e0a87315e82e3a5ab3a675bbc0af7e8c11bc7bd2 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/84768 Fri, 29 Apr 2022 10:21:50 -0000 https://status.shc.kanagawa.jp/incident/84768#8a3ff4d6d9e46d8008585da9e0a87315e82e3a5ab3a675bbc0af7e8c11bc7bd2 Mastodon(mt.shc.kanagawa.jp), Pleroma(pr.shc.kanagawa.jp), and Misskey(mk.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/84768 Fri, 29 Apr 2022 10:07:23 -0000 https://status.shc.kanagawa.jp/incident/84768#8c4b69932324f8ceb428b00b99955483cc9a59fc65c771e7546b38d1e439cdb8 Mastodon(mt.shc.kanagawa.jp) and Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/84768 Fri, 29 Apr 2022 10:07:23 -0000 https://status.shc.kanagawa.jp/incident/84768#8c4b69932324f8ceb428b00b99955483cc9a59fc65c771e7546b38d1e439cdb8 Mastodon(mt.shc.kanagawa.jp) and Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/84768 Fri, 29 Apr 2022 10:00:47 -0000 https://status.shc.kanagawa.jp/incident/84768#2696a35e386f4f71570cdc76f58c60f02d02a4108c63c2feea6d9d4f7f5ae684 Mastodon(mt.shc.kanagawa.jp) and Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/84768 Fri, 29 Apr 2022 10:00:47 -0000 https://status.shc.kanagawa.jp/incident/84768#2696a35e386f4f71570cdc76f58c60f02d02a4108c63c2feea6d9d4f7f5ae684 Mastodon(mt.shc.kanagawa.jp) and Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/84768 Fri, 29 Apr 2022 05:59:23 -0000 https://status.shc.kanagawa.jp/incident/84768#12dc0e41726cf2be1a07eb56f9e4bb62832e5112b658413bad8d4aee4f807d24 Pleroma(pr.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/84768 Fri, 29 Apr 2022 05:58:41 -0000 https://status.shc.kanagawa.jp/incident/84768#fca5b7490a5b26096280264df1c615cd5b50552cf94f9d4bb08010fe963fe136 Mastodon(mt.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/84768 Fri, 29 Apr 2022 05:57:23 -0000 https://status.shc.kanagawa.jp/incident/84768#cf257f21318b0a31feeab1c04fd2d23b653cd7260fb9d69ee7a777b03c8c81dd Mastodon(mt.shc.kanagawa.jp) and Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/84768 Fri, 29 Apr 2022 05:57:23 -0000 https://status.shc.kanagawa.jp/incident/84768#cf257f21318b0a31feeab1c04fd2d23b653cd7260fb9d69ee7a777b03c8c81dd Mastodon(mt.shc.kanagawa.jp) and Pleroma(pr.shc.kanagawa.jp) went down. https://status.shc.kanagawa.jp/incident/84352 Wed, 27 Apr 2022 10:05:20 -0000 https://status.shc.kanagawa.jp/incident/84352#e26ef4270a75d5ac503bf1fbc3a059b733e79907456474a0da85fb1d0cf076d0 Internet Relay Chat (irc.shc.kanagawa.jp) recovered. https://status.shc.kanagawa.jp/incident/84352 Wed, 27 Apr 2022 09:54:48 -0000 https://status.shc.kanagawa.jp/incident/84352#0edbe8bbd5e1580b83d4b3490f42f40a4ee9cc171057b1c5e457e3c0a759bdc1 Internet Relay Chat (irc.shc.kanagawa.jp) went down.