Incident report
-
GitHub Says Copilot Code Review Could Not Build a Review for Some Customers but Reported That the Job Had Completed Successfully
In its availability report for September 2026, dated October 14, GitHub says a change to the service that runs Copilot code reviews began sending the full copy of the results only for some customers, and that the missing review results "were not detected due to lack of monitoring."
-
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.
-
Surveypal Says a Production Release Was Deployed but Only Partially Applied, and Automations for Submitted Events Did Not Trigger Correctly
In an incident report posted on its status page on April 13, 2026, Surveypal said a production release of April 10 "was deployed but only partially applied." Part of its infrastructure kept running an older version, automations for submitted events did not trigger correctly, and some customers experienced missing automation triggers. The release was fixed on April 13.
-
dbt Labs Says a Bug Made a Pipeline Stop Recording Run Results Without Triggering Any Visible Errors
In a write-up on its status page, dbt Labs says a bug introduced during a planned infrastructure update caused a new data pipeline to stop recording run results "without triggering any visible errors," while its API stayed up and served stale data.
