Two of the data pipelines behind recent Incident Report coverage have been failing for days. The DDC capital-projects feed crashed on every run over the past 24 hours — six attempts, six failures — and hasn't completed cleanly in more than two and a half days. Checkbook NYC, the city's spending-transparency feed, has been throwing an HTTP 403 error and hasn't run clean in just under two days.
This matters because it changes what a reader should trust in recent coverage, not because any single published fact is wrong. The DDC and Checkbook streams feed capital-project tracking and city spending data — they are not the same pipeline as DOB's violation and complaint feeds that drove this week's Incident Report stories on job-site injuries, stop-work violations, and OATH hearings. Those DOB feeds have kept running. But a reader relying on this paper's capital-spending or DDC-project context right now is working from a gap, not a complete record, until the feed is restored.
“The DOB complaint and violation feeds that carried this week's Incident Report stories kept running clean — but the feed that's supposed to tell the newsroom when something breaks broke too.”
There's a second problem layered on top: the internal alert that's supposed to flag exactly this kind of outage to the newsroom failed to send on October 11, bouncing with an email-delivery error. That means for at least one day, an outage this significant could have gone unnoticed by anyone checking the usual channel.
None of this changes a number already in print — DOB's complaint and violation data, which carried this week's Incident Report stories, rides a separate pipeline and kept running clean. But it does mean any story leaning on DDC capital-project status or Checkbook NYC spending figures in the next few days should carry a line saying the feed was down when it was reported, until the paper confirms the fix. We'll note here when it's back.