Configuration changes
-
Compliance systems at financial firms
The Central Bank of Ireland Says Changes to the Maintenance of an Electronic Money Institution's Data Tables Had an Unintended Consequence That Left Its Safeguarding Account Underfunded
In a settlement notice dated October 21, 2026, the Central Bank of Ireland says that after changes made in July 2022, the records behind the report an electronic money institution used to calculate what it had to safeguard "presented incomplete information," and that the firm first took the issue to affect only some currencies.
-
Safety-critical software Medical devices
The FDA Says Updates of GE HealthCare's Monitoring Software May Remove Patients From the Monitoring System and Reset Alarm Settings to Factory Defaults
In an early alert of August 21, 2026, updated on September 3, the FDA says GE HealthCare found during a service update at a facility that some monitored patients "may be discharged (removed)" from its Portrait monitoring system, and that all alarm settings may be reset to factory defaults.
-
Control D Says Its Tests Did Not Check That Data Saved by Its API Stayed in the Format Its DNS Software Reads
In an incident report of October 20, 2026, Control D says an API update of September 16 began saving a setting in a format its DNS software could not read, and that the first save of that kind, 25 days later, stopped DNS for its paid plans at every location for about 54 minutes.
-
IONOS Says a Drift Between Its Central Repository and Live Hardware Settings Went Undetected Before a Configuration Rollout
In a root cause analysis published on its status page on February 25, 2026, IONOS Cloud says a configuration deployment during scheduled maintenance rebuilt device settings from a repository that lacked settings present only on the live hardware, and that, although the change was validated under a four-eyes principle, the rendered output did not provide enough visibility into the discrepancy.
-
LootLocker Says a Replication Process Recovered Normally After a Crash, With No Visible Signal That Data Had Been Dropped
In a postmortem published on May 8, 2026, LootLocker said a short crash of a temporary replication process, eight days before a database migration, dropped batches of data that were not replayed. The process recovered and kept running, so there was no visible signal of the loss until migration day.
