Incidents reported on status page for @qianjunakasumi https://status.qianjunakasumi.moe/en https://d1lppblt9t2x15.cloudfront.net/logos/e9bdcef47ee32f6eb04971dd2fbf4aaf.png https://status.qianjunakasumi.moe/en en https://status.qianjunakasumi.moe/en/incident/520524 Fri, 28 Feb 2025 13:18:57 +0000 https://status.qianjunakasumi.moe/en/incident/520524#1c62fc5d01b24c5845927436e10af9c81d2e34a58dec77eaa78539f0a65e4603 Maintenance completed https://status.qianjunakasumi.moe/en/incident/520524 Fri, 28 Feb 2025 13:18:57 -0000 https://status.qianjunakasumi.moe/en/incident/520524#d8288d959aa319eda50655a86e24da72e84a05faf6d43d9a363a2d9dfd546f4c Migrate bitwarden service to a new domain prefix (warden.qianjunakasumi.moe) https://status.qianjunakasumi.moe/en/incident/520524 Fri, 28 Feb 2025 13:02:07 -0000 https://status.qianjunakasumi.moe/en/incident/520524#d8288d959aa319eda50655a86e24da72e84a05faf6d43d9a363a2d9dfd546f4c Migrate bitwarden service to a new domain prefix (warden.qianjunakasumi.moe) https://status.qianjunakasumi.moe/en/incident/504861 Fri, 31 Jan 2025 06:47:20 +0000 https://status.qianjunakasumi.moe/en/incident/504861#0324b9ffa1471f8a854c736e4a266b3a26a34d72c2951303d13da11c98ae7648 Maintenance completed https://status.qianjunakasumi.moe/en/incident/504861 Fri, 31 Jan 2025 06:47:20 -0000 https://status.qianjunakasumi.moe/en/incident/504861#cb439b321d6d04b23e895fdec8812a52da86d2e50f49f25abdc4cb4d51de562c We are now schedule a maintenance to update our Bitwarden Service https://status.qianjunakasumi.moe/en/incident/504861 Fri, 31 Jan 2025 06:45:14 -0000 https://status.qianjunakasumi.moe/en/incident/504861#cb439b321d6d04b23e895fdec8812a52da86d2e50f49f25abdc4cb4d51de562c We are now schedule a maintenance to update our Bitwarden Service https://status.qianjunakasumi.moe/en/incident/415490 Mon, 19 Aug 2024 07:12:00 -0000 https://status.qianjunakasumi.moe/en/incident/415490#1981921481139c5448c514ebdf7f5e1d34eeeff0cb538f2332bc2160bc7e8012 The Bitwarden container stopped unexpectedly, which is a relatively rare error. We will configure automatic restart in the future. #post-mortem #investigation-report https://status.qianjunakasumi.moe/en/incident/415490 Mon, 19 Aug 2024 06:13:07 -0000 https://status.qianjunakasumi.moe/en/incident/415490#7c33ab798e7eb9ad9178f8a64b0c65e31ec2e52b64df273fc002feef3dc9d87e Bitwarden APIs recovered. https://status.qianjunakasumi.moe/en/incident/415490 Sun, 18 Aug 2024 03:13:39 -0000 https://status.qianjunakasumi.moe/en/incident/415490#8f3d125b3e9522e9608940ff13c1e8fa269b5a43435a78bd85a15883faf10001 Bitwarden APIs went down. https://status.qianjunakasumi.moe/en/incident/405026 Sun, 11 Aug 2024 13:29:00 -0000 https://status.qianjunakasumi.moe/en/incident/405026#09eea0d6f9be9069f1ef33305ddd484d148ed9f47e79e8d718d1fb5b159a0797 The incident was caused by a DNS resolve problem of database connection resulting in a 503 Service Unavailable error, due to negligence in assessing the impact when changing DNS record. We are sorry for this. Thanks to bitwarden local cache, no one was affected by this incident.(In fact, I am the only user XD) #post-mortem #investigation-report https://status.qianjunakasumi.moe/en/incident/405026 Sat, 10 Aug 2024 15:05:00 -0000 https://status.qianjunakasumi.moe/en/incident/405026#da992f0dcf8a5c0242f083f979faf8ece2cffc3cbeb4187b17a0f44f60ae1201 Bitwarden APIs recovered. https://status.qianjunakasumi.moe/en/incident/405026 Sat, 10 Aug 2024 05:35:00 -0000 https://status.qianjunakasumi.moe/en/incident/405026#b8df282d9659e309cc8292e9f73207ca931f93994f8619d746588d5868a29248 Bitwarden APIs went down.