Incidents | Atmos Incidents reported on status page for Atmos https://status.atmos.style/ https://d1lppblt9t2x15.cloudfront.net/logos/580dcad145c3a79d33c362bd3fb824eb.png Incidents | Atmos https://status.atmos.style/ en App recovered https://status.atmos.style/ Thu, 05 Jun 2025 21:04:02 +0000 https://status.atmos.style/#3137937b44db51be0ba343edfe5282c940bb66d43eeb58076bfd0e880353e2bc App recovered App went down https://status.atmos.style/ Thu, 05 Jun 2025 20:59:59 +0000 https://status.atmos.style/#3137937b44db51be0ba343edfe5282c940bb66d43eeb58076bfd0e880353e2bc App went down Backend recovered https://status.atmos.style/ Sun, 11 May 2025 19:25:14 +0000 https://status.atmos.style/#7e504f000ccb6da8667fecd4777083deb79f211c186aec09d27819356bbd8044 Backend recovered Website recovered https://status.atmos.style/ Sun, 11 May 2025 19:24:54 +0000 https://status.atmos.style/#37b0b3290931b960f8fc95c1bc5b79eab0e0f1862ffa3ff977f234947952ca07 Website recovered App recovered https://status.atmos.style/ Sun, 11 May 2025 19:24:54 +0000 https://status.atmos.style/#5d7c3e853e8515ecb48ce6a1b8e9aec2e7eda7fdec3a07e75e3e2cad39fc8fb0 App recovered Backend went down https://status.atmos.style/ Sun, 11 May 2025 08:55:13 +0000 https://status.atmos.style/#7e504f000ccb6da8667fecd4777083deb79f211c186aec09d27819356bbd8044 Backend went down Website went down https://status.atmos.style/ Sun, 11 May 2025 08:54:50 +0000 https://status.atmos.style/#37b0b3290931b960f8fc95c1bc5b79eab0e0f1862ffa3ff977f234947952ca07 Website went down App went down https://status.atmos.style/ Sun, 11 May 2025 08:54:47 +0000 https://status.atmos.style/#5d7c3e853e8515ecb48ce6a1b8e9aec2e7eda7fdec3a07e75e3e2cad39fc8fb0 App went down Backend recovered https://status.atmos.style/ Wed, 07 May 2025 12:14:59 +0000 https://status.atmos.style/#ccf4ee8ffe5a889e0f60cd975c816a097f2385621ce3e6b0afcdda43a891d775 Backend recovered Website recovered https://status.atmos.style/ Wed, 07 May 2025 12:11:43 +0000 https://status.atmos.style/#6476b9fb4e2b53ce0d8671fae037628ea599541fa318c75bf8a6401735003754 Website recovered App recovered https://status.atmos.style/ Wed, 07 May 2025 12:11:38 +0000 https://status.atmos.style/#360adf4f1a793f0788188946707aec8da6b1d82895e9f6dfffd7bfb3d11e2a60 App recovered Application and website unavailable for a few minutes https://status.atmos.style/incident/558081 Wed, 07 May 2025 12:10:00 -0000 https://status.atmos.style/incident/558081#039ae967f6518f3783f5d6fd4f04cc685912be36b7008e9d1c02efdf6c70f53f Due to a migration to new server the application and website was unavailable for about 15 minutes. Application and website unavailable for a few minutes https://status.atmos.style/incident/558081 Wed, 07 May 2025 12:10:00 -0000 https://status.atmos.style/incident/558081#039ae967f6518f3783f5d6fd4f04cc685912be36b7008e9d1c02efdf6c70f53f Due to a migration to new server the application and website was unavailable for about 15 minutes. Application and website unavailable for a few minutes https://status.atmos.style/incident/558081 Wed, 07 May 2025 12:10:00 -0000 https://status.atmos.style/incident/558081#039ae967f6518f3783f5d6fd4f04cc685912be36b7008e9d1c02efdf6c70f53f Due to a migration to new server the application and website was unavailable for about 15 minutes. Backend went down https://status.atmos.style/ Wed, 07 May 2025 12:00:02 +0000 https://status.atmos.style/#ccf4ee8ffe5a889e0f60cd975c816a097f2385621ce3e6b0afcdda43a891d775 Backend went down Website went down https://status.atmos.style/ Wed, 07 May 2025 11:59:37 +0000 https://status.atmos.style/#6476b9fb4e2b53ce0d8671fae037628ea599541fa318c75bf8a6401735003754 Website went down App went down https://status.atmos.style/ Wed, 07 May 2025 11:59:36 +0000 https://status.atmos.style/#360adf4f1a793f0788188946707aec8da6b1d82895e9f6dfffd7bfb3d11e2a60 App went down Major provider outage https://status.atmos.style/incident/110289 Wed, 17 Aug 2022 05:23:00 -0000 https://status.atmos.style/incident/110289#684a42257167ddc38147eec3506dc78ed59263d6dc0a16c758537777597b03f3 Our provider experienced a major outage that took longer than expected. To mitigate this we've switched to a more reliable solution. No data was lost.