Incidents reported on status page for Blaze https://status.runblaze.dev/ https://d1lppblt9t2x15.cloudfront.net/logos/1a5366d42d331a718e61e06ff26f5130.png https://status.runblaze.dev/ en https://status.runblaze.dev/ Sun, 12 Oct 2025 18:09:21 +0000 https://status.runblaze.dev/#c35d0be06d97c4c8d7caeee52600e6cba33e78286ad83346ef31a5f33a3523ca Product API recovered https://status.runblaze.dev/ Sun, 12 Oct 2025 18:00:20 +0000 https://status.runblaze.dev/#c35d0be06d97c4c8d7caeee52600e6cba33e78286ad83346ef31a5f33a3523ca Product API went down https://status.runblaze.dev/incident/722501 Thu, 11 Sep 2025 16:29:00 -0000 https://status.runblaze.dev/incident/722501#70d3de6efe5762234e286e7e7ce8e6fc52cbe4c5a1f92c2b7a495c19b6518e14 We’ve resolved the root cause of the issue and taken action to prevent future repetition. All services should be back to normal. https://status.runblaze.dev/incident/722501 Thu, 11 Sep 2025 16:03:00 -0000 https://status.runblaze.dev/incident/722501#77be1a97bac717fcafc2ef22ae65f984e67dbd88c016bcd5c66035741444b1a8 We’ve identified the root cause of the issue and are in the process of mitigating. https://status.runblaze.dev/ Thu, 11 Sep 2025 15:57:07 +0000 https://status.runblaze.dev/#8351a7478928ac6f91a2b562b5ef9eb7cb8a74a5f4e7a1a57a5308a659556b48 Payment & Github Hooks recovered https://status.runblaze.dev/ Thu, 11 Sep 2025 15:55:38 +0000 https://status.runblaze.dev/#a3805d29da7068fd761477434ed8d78583682822d3a8fc5ad45e7155531e39a3 Product API recovered https://status.runblaze.dev/ Thu, 11 Sep 2025 11:43:42 +0000 https://status.runblaze.dev/#45aee220825b3c6dbd3e96e14902376b6863b782a3309a037a862f89bbf40220 Database recovered https://status.runblaze.dev/ Thu, 11 Sep 2025 11:35:03 +0000 https://status.runblaze.dev/#45aee220825b3c6dbd3e96e14902376b6863b782a3309a037a862f89bbf40220 Database went down https://status.runblaze.dev/ Thu, 11 Sep 2025 11:31:45 +0000 https://status.runblaze.dev/#7e5498985bf6b00bde49eb50e7d2968185ec241909d67719aff1bef34a5c02d7 Database recovered https://status.runblaze.dev/ Thu, 11 Sep 2025 11:28:00 +0000 https://status.runblaze.dev/#8351a7478928ac6f91a2b562b5ef9eb7cb8a74a5f4e7a1a57a5308a659556b48 Payment & Github Hooks went down https://status.runblaze.dev/ Thu, 11 Sep 2025 11:26:05 +0000 https://status.runblaze.dev/#7e5498985bf6b00bde49eb50e7d2968185ec241909d67719aff1bef34a5c02d7 Database went down https://status.runblaze.dev/ Thu, 11 Sep 2025 11:24:46 +0000 https://status.runblaze.dev/#a3805d29da7068fd761477434ed8d78583682822d3a8fc5ad45e7155531e39a3 Product API went down https://status.runblaze.dev/ Thu, 11 Sep 2025 11:20:07 +0000 https://status.runblaze.dev/#ebdf265ecc53ee2780e631d2a6f78353917e6db4ab8f2648a4fe0ca862512113 Payment & Github Hooks recovered https://status.runblaze.dev/ Thu, 11 Sep 2025 11:14:29 +0000 https://status.runblaze.dev/#ebdf265ecc53ee2780e631d2a6f78353917e6db4ab8f2648a4fe0ca862512113 Payment & Github Hooks went down https://status.runblaze.dev/ Thu, 11 Sep 2025 11:02:04 +0000 https://status.runblaze.dev/#80835d7d17e734745f634bd3459b814215e8fb0b119851e1b3bdaae23ebe383a Payment & Github Hooks recovered https://status.runblaze.dev/ Thu, 11 Sep 2025 11:01:39 +0000 https://status.runblaze.dev/#bd8a13598db2597d141246f5782d96d6a837c51a20af049b60e16ab3b60fbb4d Database recovered https://status.runblaze.dev/ Thu, 11 Sep 2025 10:59:34 +0000 https://status.runblaze.dev/#80835d7d17e734745f634bd3459b814215e8fb0b119851e1b3bdaae23ebe383a Payment & Github Hooks went down https://status.runblaze.dev/ Thu, 11 Sep 2025 10:58:46 +0000 https://status.runblaze.dev/#bd8a13598db2597d141246f5782d96d6a837c51a20af049b60e16ab3b60fbb4d Database went down https://status.runblaze.dev/incident/722501 Thu, 11 Sep 2025 10:56:00 -0000 https://status.runblaze.dev/incident/722501#d02c4e193c1e83c2e41141db81b5b5119de8e72e37688414ca4121172b1b06cb Users might experience delays and failure to pick up jobs. Investigation ongoing https://status.runblaze.dev/ Thu, 11 Sep 2025 10:29:05 +0000 https://status.runblaze.dev/#b890579da8b4d0b2fbcbb155e73b41689b5421fda97003bffdafe6e84aec4133 Payment & Github Hooks recovered https://status.runblaze.dev/ Thu, 11 Sep 2025 10:26:28 +0000 https://status.runblaze.dev/#b890579da8b4d0b2fbcbb155e73b41689b5421fda97003bffdafe6e84aec4133 Payment & Github Hooks went down https://status.runblaze.dev/ Tue, 09 Sep 2025 20:15:04 +0000 https://status.runblaze.dev/#eb5247a20378068d89fac05bd5e0a4d623e956a36edabf73cec5e139608654d8 Product API recovered https://status.runblaze.dev/ Tue, 09 Sep 2025 20:12:02 +0000 https://status.runblaze.dev/#eb5247a20378068d89fac05bd5e0a4d623e956a36edabf73cec5e139608654d8 Product API went down https://status.runblaze.dev/incident/719164 Fri, 05 Sep 2025 23:08:00 -0000 https://status.runblaze.dev/incident/719164#4226ef7d850f2869bf8a63cf9b20505750fab12db87be483692dbc71081f0859 Systems fully working as expected https://status.runblaze.dev/incident/719164 Fri, 05 Sep 2025 21:49:00 -0000 https://status.runblaze.dev/incident/719164#237775bb986a2bed3aa7a0484c0a5462201dcc94b02c4f27939840173513134c We’ve started the rollout of the new systems. Services should be returning gradually to customers. Customers in the NA region should see their runners start to take new jobs https://status.runblaze.dev/ Fri, 05 Sep 2025 21:48:30 +0000 https://status.runblaze.dev/#91797562094a238d6b35d1415e2d0542303c7acd5b6154cbda2604b7dd8c39a6 Product API recovered https://status.runblaze.dev/ Fri, 05 Sep 2025 21:40:57 +0000 https://status.runblaze.dev/#c31d9cc01d5b31546e93f87ed812a18305f892d7a30f1aef2d50e3a769e85066 Payment & Github Hooks recovered https://status.runblaze.dev/ Fri, 05 Sep 2025 21:40:41 +0000 https://status.runblaze.dev/#6dde80a7c91ce7ed8ac6ed356e5dd9f52688aa523dc60f2ff2d71b53b72dc963 Database recovered https://status.runblaze.dev/ Fri, 05 Sep 2025 21:39:44 +0000 https://status.runblaze.dev/#91797562094a238d6b35d1415e2d0542303c7acd5b6154cbda2604b7dd8c39a6 Product API went down https://status.runblaze.dev/ Fri, 05 Sep 2025 21:38:50 +0000 https://status.runblaze.dev/#c31d9cc01d5b31546e93f87ed812a18305f892d7a30f1aef2d50e3a769e85066 Payment & Github Hooks went down https://status.runblaze.dev/ Fri, 05 Sep 2025 21:37:58 +0000 https://status.runblaze.dev/#6dde80a7c91ce7ed8ac6ed356e5dd9f52688aa523dc60f2ff2d71b53b72dc963 Database went down https://status.runblaze.dev/incident/719164 Fri, 05 Sep 2025 19:00:00 -0000 https://status.runblaze.dev/incident/719164#379bb8851c24bd23c32c28f1e531368fd7abf518cca7575ad4c5ebd1ef2e259a We’ve begun migration of some of our services to another provider as the provider continues to work on resolving the issue — will be ongoing for an hour. https://status.runblaze.dev/ Fri, 05 Sep 2025 17:07:54 +0000 https://status.runblaze.dev/#d4a2aa644a6e1faf9c95160a442026f9b1153e92acafbf9e35f23cec8b416220 Payment & Github Hooks recovered https://status.runblaze.dev/ Fri, 05 Sep 2025 17:05:04 +0000 https://status.runblaze.dev/#d4a2aa644a6e1faf9c95160a442026f9b1153e92acafbf9e35f23cec8b416220 Payment & Github Hooks went down https://status.runblaze.dev/incident/719164 Fri, 05 Sep 2025 15:25:00 -0000 https://status.runblaze.dev/incident/719164#52c669cde7f8147f59c74e3646467489df239f9a7681bfd0129efc9b3f880740 We continue to work with our provider on establishing some connections for our runners https://status.runblaze.dev/incident/719164 Fri, 05 Sep 2025 11:30:00 -0000 https://status.runblaze.dev/incident/719164#4aca70716af9b5854b090dac83cf5fb2c922bbb2acde3f46e9681284ee1f1020 Our runners are currently unavailable as our network provider experiences issues. We are working with them to resolve this as soon as possible.