Status updates | Snowbee Software AS Incidents and maintenance reported on status page for Snowbee Software AS https://status.snowbee.no/ https://d1lppblt9t2x15.cloudfront.net/logos/baf64fc1077226c4619860baf1224501.png Status updates | Snowbee Software AS https://status.snowbee.no/ en Maintenance: Change of technical server provider https://status.snowbee.no/maintenance/1102630 Mon, 26 Oct 2026 09:17:30 -0000 https://status.snowbee.no/incident/1102630#05fe3524eefe867ce0b443a1226929c1958394595406a6a1543ddbd349b88e45 Maintenance The maintenance completed successfully after 20 minutes and all systems are healthy. Maintenance: Change of technical server provider https://status.snowbee.no/maintenance/1102630 Sat, 24 Oct 2026 20:30:00 -0000 https://status.snowbee.no/incident/1102630#b6fb637bb98233f233e7ad327949d16bf85dc02c1ec42bf8efa2af2afce1bda7 Maintenance Maintenance completed ERP Web Application, Public API, and 1 other service are down https://status.snowbee.no/incident/1101530 Sat, 24 Oct 2026 20:24:20 -0000 https://status.snowbee.no/incident/1101530#408f23c7b9faa6369514b8b29fe3165e446e81edb4c6c55f59066dfca8e2d59e Incident Internal API recovered. ERP Web Application, Public API, and 1 other service are down https://status.snowbee.no/incident/1101530 Sat, 24 Oct 2026 20:23:32 -0000 https://status.snowbee.no/incident/1101530#2f25d5874782010487f29aba1b2bf8e9107144394722bfa7aae32877d7e77a15 Incident Public API recovered. ERP Web Application, Public API, and 1 other service are down https://status.snowbee.no/incident/1101530 Sat, 24 Oct 2026 20:23:05 -0000 https://status.snowbee.no/incident/1101530#0c96eabb40ed71cdb5664ee4b733c5521570500e6ece10ac1001926b88b4fee1 Incident ERP Web Application recovered. ERP Web Application, Public API, and 1 other service are down https://status.snowbee.no/incident/1101530 Sat, 24 Oct 2026 20:03:00 -0000 https://status.snowbee.no/incident/1101530#55f5483df507e99730b4f828e2f878fd8de60a2752d68ab19e65ce0a36322515 Incident Planned maintenance. Database upgrade Maintenance: Change of technical server provider https://status.snowbee.no/maintenance/1102630 Sat, 24 Oct 2026 20:00:00 -0000 https://status.snowbee.no/incident/1102630#ca0bb849778ce846f633e455faf3bd3c2db6a54d59d0ea0ddf8005154144a7df Maintenance SnowBee is scheduled to migrate to a different hosting provider. We expect full downtime during this window. SnowBee is experiencing degraded performance and partial downtime https://status.snowbee.no/incident/1080084 Fri, 02 Oct 2026 14:22:00 -0000 https://status.snowbee.no/incident/1080084#0440b0f06e3db945c13fad04e81e347d447477546b1b9397a55554bdbfc01219 Incident At 15:00:02 Oslo time, a faulty deployment of our webapp frontend caused an extremely elevated error rate and partial unavailability. At 15:32:50 Oslo time, the issue was fully resolved. The root cause was a bad version of the webapp frontend that caused our API to become overloaded. A software bug caused a much larger number of API calls to happen than what is usual. Endpoints that typically sits at 30-40 or so request per minute now received almost 10 000 per minute, a rough 270x increase in traffic. We became aware of the issue within just a few seonds after the incident started, when error logs started flooding our monitoring channels. At 15:14 Oslo time, we deployed a new version of the webapp frontend that fixed the issue. However, the problem continued affecting our systems, as all webapp frontend clients had to be refreshed in order to stop sending the flood of API calls. At 15:32:50, we deployed a firewall rule that blocked the specific version of the webapp frontend that caused the issue. That instantly stopped the flood of API calls to reach our backend, and restored operations to normal. In terms of the quantity of successful retail sales compared to normal operations, the system experienced a 60% reduction between 15:00 and 15:10, and 90% reduction between 15:20 and 15:30, up until operations were restored 15:32:50. Here are the core issues that caused this prolonged period of degraded performance and partial unavailability, and what we'll do to mitigate issues like this in the future: We need faster emergency code updates in production. The initial fix was deployed to production 14 minutes after the incident started, but the fix was implemented at 15:03 Oslo time, only 3 minutes after the incident started. Our deployment process includes a handful of automated testing that takes extra time. On top of that, another build was already in the build pipeline that we cancelled, but the cancellation process is asynchronous and caused the actual build to 15:06 Oslo time, a delay of 3 extra minutes. We have documented and tested the procedure to circumvent this build process so we have the ability to emergency deploy and replace known poison pill versions. That would have caused the new version to be out at an estimate of 15:05, instead of 15:14. We need a streamlined process to block poison pill versions at the firewall level. After the poison pill version was replaced with a deployed fix, It still took a little more than 15 minutes until we had the firewall rule installed that blocked the poison pill. That's because we simply had no plan in place, and had to figure out the process to implement a firewall rule properly without blocking the entire system. For monitoring causes, we've already set up the system so that each API call that we make precisely identifies exactly which version of the software that performed the call, so we could rely on that for the firewall rule. But we were initially not sure at which layer in the networking stack the rule should be installed, and exactly how to operationally implement the rule in a safe way. We have documented and automated the procedure to block poison pill versions. In short, if an issue like this were to happen again, we'll now be able to deploy an update to replace the poison pill within 5 minutes, and when the update is deployed we can instantly block the poison pill version, causing an immediate full recovery. If we had that in place for this incident, the issue would only have lasted an estimated 5 minutes before fully recovering. SnowBee is experiencing degraded performance and partial downtime https://status.snowbee.no/incident/1080084 Fri, 02 Oct 2026 13:41:52 -0000 https://status.snowbee.no/incident/1080084#9b265f0856dd2afade454b0d5776deef579f2d691a1357ca0b69ebe0e022a692 Incident Internal API recovered. SnowBee is experiencing degraded performance and partial downtime https://status.snowbee.no/incident/1080084 Fri, 02 Oct 2026 13:38:50 -0000 https://status.snowbee.no/incident/1080084#1da92b1951fe093fb93c17f6e14d189d15e772d5ea732585ed0a6cc998f12335 Incident Public API recovered. SnowBee is experiencing degraded performance and partial downtime https://status.snowbee.no/incident/1080084 Fri, 02 Oct 2026 13:06:23 -0000 https://status.snowbee.no/incident/1080084#525df10467b91fdfa55d3c8d380b728683403609d9ff9a2bfe804e87f4d823b7 Incident Internal API went down. SnowBee is experiencing degraded performance and partial downtime https://status.snowbee.no/incident/1080084 Fri, 02 Oct 2026 13:05:02 -0000 https://status.snowbee.no/incident/1080084#c08bb8d2ed9e316317ccfaebf94fa7f3e6cf6e7ad621474e6b1ddf2405856634 Incident Public API went down. SnowBee is experiencing degraded performance and partial downtime https://status.snowbee.no/incident/1080084 Fri, 02 Oct 2026 13:04:20 -0000 https://status.snowbee.no/incident/1080084#2a5f2ffbcd9243d7e1397653022d6ca7556f44a74bf3b83f1d922899005ffe58 Incident Internal API recovered. SnowBee is experiencing degraded performance and partial downtime https://status.snowbee.no/incident/1080084 Fri, 02 Oct 2026 13:03:43 -0000 https://status.snowbee.no/incident/1080084#806394fe85e6b19efa2c088f352b79735e753d82cdaa9c2265bdaff650a6af5b Incident Internal API went down. Internal API is down https://status.snowbee.no/incident/1024861 Fri, 21 Aug 2026 04:15:21 -0000 https://status.snowbee.no/incident/1024861#773599f136089c8ddd17d64f7b8425e0173bfc02b4ce37161980fc9d23b53f2c Incident Internal API recovered. Internal API is down https://status.snowbee.no/incident/1024861 Fri, 21 Aug 2026 03:49:05 -0000 https://status.snowbee.no/incident/1024861#68bd8f0be6aa559650d19c679012035be7da7ccc14fca7a7e926b90ba15ef94f Incident Internal API went down. Maintenance: Database cluster upgrade https://status.snowbee.no/maintenance/1022893 Thu, 20 Aug 2026 08:30:13 -0000 https://status.snowbee.no/incident/1022893#9e476923443d6321846c9f1e9427f853e23b31badd98bd42b6b5803e2632a4ff Maintenance We expect roughly 10 minutes of downtime as we upgrade our database cluster. All customers are notified and no activity is expected during this early morning time window, so we've decide to implement this upgrade as downtime, and not a rolling update. Degraded performance of creation of shipments https://status.snowbee.no/incident/1021194 Wed, 19 Aug 2026 11:55:00 -0000 https://status.snowbee.no/incident/1021194#fd4bf38ffc8c4f6f01ad83b2d6687d64840add81e653d7eb7e0514fb943eb06d Incident The issue is now resolved and shipments can be created without slowdowns. Degraded performance of creation of shipments https://status.snowbee.no/incident/1021194 Wed, 19 Aug 2026 11:49:00 -0000 https://status.snowbee.no/incident/1021194#56847f5bfd83ac36070b94dca8ffc2c0708530db0b93c6526135c0fa05b124b7 Incident A fix is now being rolled out as we continue to monitor the performance of the system. Degraded performance of creation of shipments https://status.snowbee.no/incident/1021194 Wed, 19 Aug 2026 11:38:00 -0000 https://status.snowbee.no/incident/1021194#3f88fe6b52fd892276ce8796e12e62780db9a0fcc12937bc491fb7da49a75a5e Incident We have identified the root cause of the issue and expect to have a fix deployed soon. Degraded performance of creation of shipments https://status.snowbee.no/incident/1021194 Wed, 19 Aug 2026 11:10:00 -0000 https://status.snowbee.no/incident/1021194#07af2260ba45ffa9331f30ccc2ac0b83509be7c2a15782eba3e1fb7d7ca8c18a Incident There is currently an active issue where creating new shipments is slow and will occasionally time out. We're actively investigating the issue and working to ship a fix. ERP Web Authentication is down https://status.snowbee.no/incident/910522 Tue, 02 Jun 2026 01:29:33 -0000 https://status.snowbee.no/incident/910522#cb000a12db474e84d27673016e978080e9ed4d40816da675f05da084e921c506 Incident ERP Web Authentication recovered. ERP Web Authentication is down https://status.snowbee.no/incident/910522 Tue, 02 Jun 2026 01:23:13 -0000 https://status.snowbee.no/incident/910522#092886d18a213400106e5f8449ace8fbb81df2c8b8ec477bd36bee0b682aaa34 Incident ERP Web Authentication went down. Retail payments blocked from completing https://status.snowbee.no/incident/931171 Fri, 29 May 2026 09:04:00 -0000 https://status.snowbee.no/incident/931171#07c2b33544d8be923d353152799a1d31ffb2c27556b14fa622e64bb9baaa29e7 Incident The issue has been fixed and operations have now fully returned to normal. Retail payments blocked from completing https://status.snowbee.no/incident/931171 Fri, 29 May 2026 08:50:00 -0000 https://status.snowbee.no/incident/931171#c30457b7dd6ba5dc36921114bf3df91fecaa4a2c3f9bbaa666e0984a9300ddcd Incident In the retail mode, when a cashier finalize a transaction, the system is currently blocked from creating the underlying invoice. This has caused the checkout process to be fully unavailable. Degraded performance of B2C customer search https://status.snowbee.no/incident/887932 Tue, 05 May 2026 09:26:00 -0000 https://status.snowbee.no/incident/887932#2012c664301f7d60f3a9417bd3d4062ac36592eae468e56cfb46a7b00a7985a1 Incident The issue has been fixed and performance has returned to normal. Degraded performance of B2C customer search https://status.snowbee.no/incident/887932 Tue, 05 May 2026 09:21:00 -0000 https://status.snowbee.no/incident/887932#b852a791911d8870bd0caf3d1fec6d8f556e3d2c658f5f2979d3dd228c5e10f2 Incident We have identified the root cause of this issue and a fix is being rolled out. We'll continue to monitor the performance. Degraded performance of B2C customer search https://status.snowbee.no/incident/887932 Tue, 05 May 2026 09:01:00 -0000 https://status.snowbee.no/incident/887932#6ee9a1d0535cea27ce1adac563d4af422142e2d7b9b6677566cda978c29f0f38 Incident Our internal monitoring has diagnosed degraded performance of B2C customer queries in all surfaces. We're investigating this issue. Maintenance: Database cluster maintenance https://status.snowbee.no/maintenance/847258 Wed, 11 Mar 2026 22:22:52 -0000 https://status.snowbee.no/incident/847258#49a9c3f37f2983a3a64dd14ab03f37fcb979beebd8bc410a6d3934f70d8529d1 Maintenance The database cluster will perform automated updates of the underlying database engine during this maintenance window. For small periods of time, SnowBee will be unresponsive and not accept writes and might drop some reads. We expect these periods to last a handful of minutes at most, and the system should quickly recover as the database cluster performs automated updates and restarts. Maintenance: Database cluster upgrade https://status.snowbee.no/maintenance/757649 Tue, 04 Nov 2025 10:52:18 -0000 https://status.snowbee.no/incident/757649#dd6a8d93035c2983973df0d4dc6846c3ee92b770e756a195739b24f80661cf39 Maintenance We expect small amounts of downtime during our next maintenance window, which starts November 09, 2025, 02:00 (UTC+01:00) and lasts for one hour. The downtime is caused by a maintenance version update on our database cluster. We expect the actual real-world downtime to be limited to a few minutes. API is down https://status.snowbee.no/incident/600726 Wed, 11 Jun 2025 07:45:00 -0000 https://status.snowbee.no/incident/600726#fc7ac1f7621eecaefea631d85c2a2a7a03a55a7019bf232d80a29375cf5d267b Incident API recovered automatically after AWS triggered a server shutdown. This is caused by our production environment currently being configured with just a single instance running of the back-end. In the future, we'll have multiple instances running, so that a restart of a single instance does not cause downtime. API is down https://status.snowbee.no/incident/600726 Wed, 11 Jun 2025 07:40:44 -0000 https://status.snowbee.no/incident/600726#754eea05d601139fb9ed31cb650b4c685376158e667e83360fccb3a43a34d435 Incident API went down. API unavailable https://status.snowbee.no/incident/600086 Tue, 03 Jun 2025 23:55:00 -0000 https://status.snowbee.no/incident/600086#5997f5d103076b094280e2fe0516a1bc020369df0e5902cc1781d21ed2a212e2 Incident The API is up, after an automatic recovery by our internal monitoring. To mitigate errors like this in the future, the server cluster in AWS will get full health checks added, and we'll disable Service Connect as it has caused similar issues before. API unavailable https://status.snowbee.no/incident/600086 Tue, 03 Jun 2025 21:33:00 -0000 https://status.snowbee.no/incident/600086#938cbd64e294f54649ed99ae1289c83af3bca8546fcf0382d78c46ec098af64d Incident The API is currently experiencing full downtime for all users.