Incidents | @im.sb Mastodon Incidents reported on status page for @im.sb Mastodon https://status.imsb.app/ en imsb.app recovered https://status.imsb.app/ Fri, 17 Jul 2026 02:38:09 +0000 https://status.imsb.app/#04491842cac858a4553d85e79c4801c5e2c2fe764d616ac1745ab144ffebdbbc imsb.app recovered mastodon.im.sb recovered https://status.imsb.app/ Fri, 17 Jul 2026 02:38:01 +0000 https://status.imsb.app/#153adb5153a236ef22885838f56c35e03e56810175a0fb31c5029cf0921e213d mastodon.im.sb recovered imsb.app went down https://status.imsb.app/ Fri, 17 Jul 2026 02:28:17 +0000 https://status.imsb.app/#04491842cac858a4553d85e79c4801c5e2c2fe764d616ac1745ab144ffebdbbc imsb.app went down mastodon.im.sb went down https://status.imsb.app/ Fri, 17 Jul 2026 02:27:47 +0000 https://status.imsb.app/#153adb5153a236ef22885838f56c35e03e56810175a0fb31c5029cf0921e213d mastodon.im.sb went down mastodon.im.sb recovered https://status.imsb.app/ Thu, 16 Jul 2026 02:32:52 +0000 https://status.imsb.app/#6d3d975d94e32ad99b4957aa336cfd86a3f60f969cafaf4412fe9e95eed32a7e mastodon.im.sb recovered mastodon.im.sb went down https://status.imsb.app/ Thu, 16 Jul 2026 02:27:48 +0000 https://status.imsb.app/#6d3d975d94e32ad99b4957aa336cfd86a3f60f969cafaf4412fe9e95eed32a7e mastodon.im.sb went down s3.imsb.app recovered https://status.imsb.app/ Sat, 20 Jun 2026 07:53:02 +0000 https://status.imsb.app/#142334d4f064956d672d51232dee6784bec0ecd5c5537461a7542e4eb4c99392 s3.imsb.app recovered s3.imsb.app went down https://status.imsb.app/ Sat, 20 Jun 2026 07:50:57 +0000 https://status.imsb.app/#142334d4f064956d672d51232dee6784bec0ecd5c5537461a7542e4eb4c99392 s3.imsb.app went down imsb.app recovered https://status.imsb.app/ Fri, 19 Jun 2026 02:23:20 +0000 https://status.imsb.app/#e2af1d7a544f1c0c1c5a90bea6a1ce2fc85ba408ab319a316d54b20f1575d1c9 imsb.app recovered imsb.app went down https://status.imsb.app/ Fri, 19 Jun 2026 02:18:06 +0000 https://status.imsb.app/#e2af1d7a544f1c0c1c5a90bea6a1ce2fc85ba408ab319a316d54b20f1575d1c9 imsb.app went down s3.imsb.app recovered https://status.imsb.app/ Mon, 15 Jun 2026 15:56:21 +0000 https://status.imsb.app/#c9df9fcd8324e3c509d98f6567b5f64afe71ac9d21816a42ab803582bfe089b8 s3.imsb.app recovered s3.imsb.app went down https://status.imsb.app/ Mon, 15 Jun 2026 15:54:06 +0000 https://status.imsb.app/#c9df9fcd8324e3c509d98f6567b5f64afe71ac9d21816a42ab803582bfe089b8 s3.imsb.app went down imsb.app recovered https://status.imsb.app/ Sat, 23 May 2026 02:43:09 +0000 https://status.imsb.app/#a471e11e3c2d0c94fa67c2419caf91dd46e2c2ca963fe5c454d6886797e2926d imsb.app recovered imsb.app went down https://status.imsb.app/ Sat, 23 May 2026 02:38:08 +0000 https://status.imsb.app/#a471e11e3c2d0c94fa67c2419caf91dd46e2c2ca963fe5c454d6886797e2926d imsb.app went down Mainsite suffered DNS pollution in mainland China https://status.imsb.app/incident/134225 Fri, 18 Nov 2022 07:57:00 -0000 https://status.imsb.app/incident/134225#76ccf54b721e6dde5115f2f21e1fe88e77408a1119a73f82758f4f7e2ba9ecdc 海外 DNS 污染已经恢复,大陆地区的 DNS 污染无解。 Mainsite suffered DNS pollution in mainland China https://status.imsb.app/incident/134225 Mon, 31 Oct 2022 18:00:00 -0000 https://status.imsb.app/incident/134225#44ce1108178c092bc9c1fccfd9526072a7093b02196c39de13bb4174fe7505af The mainsite suffered DNS pollution in mainland China, resulting in unusable access. Use the alternate domain instead.