Farm payment and loan systems at the U.S. Department of Agriculture have been down for days, and some were still failing on Friday, November 20. The department has not publicly confirmed a breach. Its under secretary now calls the trouble a “cyberthreat,” a shift from the explanation officials first gave.
What the USDA has confirmed so far
The disruption began on Monday, November 16, when multiple applications went offline. That account comes from reporting by Nextgov/FCW and Government Executive, as summarized by Cynoteck, which cited people familiar with the matter and an internal email.
The email came from Chris Rottler, acting assistant chief information officer for the Farm Production and Conservation Business Center. It said the department's Cybersecurity and Privacy Operations Center had “uncovered a security incident,” according to Yahoo News and Newscord.
The sequence so far looks like this:
| Date | What was reported |
|---|---|
| Monday, November 16 | Multiple USDA applications go offline |
| Thursday, November 19 | A technical bulletin warns of intermittent outages through the week |
| Friday, November 20 | Fordyce calls the incident a “cyberthreat”; a farm group cited by ABC says the disruption is in its fifth day |
The dates and the broad impact are consistent across reports. What caused the outage is not. The USDA has not resolved that question on the record.
Which farm payment and loan tools are down
Reports say the affected applications include the financial tools that handle payments between USDA and farmers. Those tools reportedly include programs tied to crop insurance and loss coverage, along with the applications staff use to check loan and aid status, according to MLQ.ai and Nacionale News.
Employees also reported trouble with the Farm Service Agency's loan software and with ProTracts, a Natural Resources Conservation Service program that releases payments to farmers for conservation work, according to PoliAlert's summary of NBC News reporting.
Staff were reportedly told to “proceed with caution and don't do any critical work.” That instruction suggests the problem reached well beyond a single portal.
The reports do not say how many farmers are affected. For a producer waiting on a loan decision or a conservation check, that is the most important missing detail, and the department has not released it.
Why resetting database passwords may explain the length of the outage
According to Cynoteck's account, the response included resetting all database passwords in every environment. Resetting credentials is a standard containment step, but it carries a cost. Every application that depended on those credentials had to restart, and that restart reportedly produced days of outages.
That trade-off matters for anyone trying to judge how serious the outage is. A team that moves quickly to lock down access can still leave public-facing services unavailable for days. It also helps explain why the department's own bulletin warned of problems through the week instead of promising a single fix.
Was the USDA hacked? What officials have said
Readers searching whether the USDA was hacked will find conflicting signals. Early on, department officials described the problems as routine. Richard Fordyce, under secretary for farm production and conservation, did not acknowledge a breach and blamed outages on updates. Earlier, he told DTN, “We will occasionally have outages sometimes because there's updates,” a quote carried by Newscord.
On Friday, Fordyce told reporters at a Kansas City event that the incident was a “cyberthreat,” not a “software update,” according to The Fence Post. He reportedly said no data was lost because the department's cybersecurity protections worked. Another report quotes him saying “there was no Personally Identifiable Information” exposed, per PoliAlert.
NBC News, citing two former USDA officials, reported that hackers broke into the system that handles farmer payments. NBC also described this as the first known case in the wider wave of outages caused by an outside actor. Whether that account can be confirmed on the record is not yet clear.
Here is where the record stands. The USDA has not publicly confirmed a breach or named the affected systems. No one has said who carried out the intrusion, and officials have not said whether any data was taken. Fordyce's account moved from updates to a cyberthreat within days, and the department has not explained that change. Without details, farmers cannot judge whether their own records are at risk.
How the USDA incident fits a wider run of outages
The same day Fordyce made his remarks, a Government Accountability Office report found that USDA and FDA had not fully implemented several federal cybersecurity requirements for the food and agriculture sector, according to Yahoo News. The timing puts the outage next to a finding about the department's own cyber readiness, which makes a vague explanation harder to accept.
The USDA is not the only name in the cluster. Yahoo News reported that the wider run of disruptions began with a Microsoft Outlook outage, and that the NSA, JPMorgan Chase, Bank of America, Apple and United Airlines also reported problems, per Yahoo News. A separate report said the federal government considers the cyber incidents unrelated, per Fox 8.
For now, the USDA case should be read on its own. The sources do not show a shared cause, and officials say the incidents are separate. That position is hard to test from outside, so it does not settle whether the outages share an attacker.
USA 24 has covered a different case: a vendor-related leak that exposed customer data tied to JPMorgan, Visa and Mastercard. Abrigo's Sageworks platform has also been offline since October 30, with the cause still unconfirmed, as USA 24 reported. Neither case is tied to the USDA outage in the sources.
Farmers and ranchers who depend on USDA loans, crop insurance and commodity or conservation payments are the most directly affected. Former officials told NBC the outage came days before a key enrollment deadline, per PoliAlert. Farm lenders, agricultural advisers and food-sector businesses that rely on USDA data may face their own uncertainty.
Ryan Marquardt, vice president of the Iowa Farmers Union, told ABC News, “USDA needs to explain what happened.” The group said it knew only what had been shared publicly, per ABC News.
What farmers should do now
Until the department confirms the status of its systems, farmers and their advisers can protect themselves with a few steps. These are general precautions, not guidance issued by the USDA.
- Call your local Farm Service Agency or NRCS county office to confirm the status of any pending payment or loan.
- Keep written records of every submission, confirmation number and deadline, along with the date and the name of anyone you spoke to.
- Treat unsolicited calls, emails or texts offering “urgent” USDA payment fixes as suspicious. Scammers often exploit outages like this one.
- Do not share Social Security numbers or banking details through unverified channels. Use phone numbers from official agency pages, not numbers in a message.
What to watch next
Fordyce said, according to ABC News, “Most systems should be back online by close of business today, and if not, we'll work on that over the weekend.” That gives farmers a concrete test. If loan or payment tools still fail on Monday, November 23, the outage will have outlasted the department's own timeline.
Other questions to track include whether the USDA confirms a breach and names the affected systems, whether any data was taken, how many farmers are affected, and whether any payments slipped. The NBC account also needs on-record confirmation before it can be treated as established. The department's response to the GAO findings will show whether food and agriculture cyber gaps get attention beyond this outage.
The answers will come from the department. Pressure to provide them grows with each day the tools stay dark. A confirmed breach would shift the story from an outage to a question of exposure. Continued silence would leave producers who depend on these payments to work out their own risks.




