Incidents | Laminar AI Incidents reported on status page for Laminar AI https://status.laminar.sh/ https://d1lppblt9t2x15.cloudfront.net/logos/9758d8e836471527bf9d219dadbdb692.png Incidents | Laminar AI https://status.laminar.sh/ en Postgres database upgrade https://status.laminar.sh/incident/1005388 Sat, 08 Aug 2026 10:30:04 -0000 https://status.laminar.sh/incident/1005388#00d0ee1f85660a7ba945066c810a3b4f4b201fed24135e6311d206f64d192864 Frontend services will see downtime. Planned maintenance downtime is about 3-5 minutes. API authentication may be partially impaired DB upgrade https://status.laminar.sh/incident/487791 Sat, 28 Dec 2024 13:30:39 -0000 https://status.laminar.sh/incident/487791#77487cf698dadd9dc4252478947ad2aeac6b63429c887dfa1b5bd70c431d9708 Some downtime expected as we upgrade DB compute and Postgres version Message queue update https://status.laminar.sh/incident/422685 Sun, 01 Sep 2024 19:55:00 -0000 https://status.laminar.sh/incident/422685#1de29408f9e8a7c61e1c2795e138dd4a0ad9306c0b62ecd639247cb02ad598ab Update of the message queue to the new infra Minor infrastructure update https://status.laminar.sh/incident/407162 Thu, 01 Aug 2024 17:00:00 -0000 https://status.laminar.sh/incident/407162#d8e4d5d7e660c2fc7b475c8457352a3331fbe6b17bf1e940980d521d27147517 Maintenance completed Minor infrastructure update https://status.laminar.sh/incident/407162 Thu, 01 Aug 2024 15:00:00 -0000 https://status.laminar.sh/incident/407162#beedf125000a252900cf04e56363ba15681fdf09c3e72e31cefcc645456de2c3 Infrastructure migration might cause minor disruptions. Logs migration https://status.laminar.sh/incident/400965 Sat, 20 Jul 2024 05:20:00 -0000 https://status.laminar.sh/incident/400965#82e0f55c29ffeaccf1b23c064954ade9e93119e229240a5571b6c761e7dd1e2d Migrating the logs to new structure. New logs will be written, old logs will take some time to be transferred to the new system Misconfigured healthchecks https://status.laminar.sh/incident/394618 Tue, 02 Jul 2024 20:30:00 -0000 https://status.laminar.sh/incident/394618#3f3dec599dd5852e1f2ef19f1abeed8c2ed6098ce5cc5fdb69cd5fe73838a405 The status was reflected incorrectly between July 2 and July 7 2024, due to a configuration mistake in the status page. During that time, the servers were fully available and functional