FEC filing system offline 42 to 46 hours; email seen by Reuters cites breach attempt, FEC page gives no cause
The FEC's status page shows its electronic filing system down from the evening of 26 October to 28 October 2026, six days before the midterms. Only an internal email seen by Reuters calls it a breach attempt; no FEC page read names a cause, an actor or whether data was touched.
By Parminder Kumar Sharma · LinkedIn · · 15 min read
Offline for 42 to 46 hours, and the word attack is not on the FEC's own page
The US Federal Election Commission's own status page prints two incidents for its filing systems. The first posts are at 21:29 Eastern time (EDT) on Monday 26 October 2026 for the FECfile+ filing submission outage and at 22:15 EDT for the electronic filing system outage. The page then reports the electronic filing system available at 16:50 EDT on Wednesday 28 October and FECfile+ available at 19:10 EDT the same day. That is 42 hours 35 minutes and 45 hours 41 minutes after the first posts (derived), and six days before the general election on Tuesday 3 November (derived). This briefing rests on the status page, its two incident pages and five other FEC pages and captures, all read in full on 30 October 2026 (from about 15:37 UTC to 15:49 UTC), and on the news reports that carry the rest.
What those FEC pages do not say is why. Neither status incident names a cause, and the FEC's public statements, as reported, say only that the system is offline and that staff are working to restore it. The word intrusion comes from a different place: a report by Reuters, carried by AOL and NBC News, of an email seen by Reuters in which an FEC electronic filings officer told several campaign compliance firms "We have a bad actor attempting to breach FEC systems. As a result, we've had to temporarily shut down our web facing services". That is Reuters's account of an email that this site has not seen and the FEC has not published. It is an attempt described by an officer on the night, not a finding.
The FEC is the operator and the only source for what its systems did, so every statement about the cause, the scope and the data rests on what it chooses to publish. That is not a criticism of the agency. It is the reason this briefing keeps three kinds of statement apart. SecurityWeek put the story in its 30 October roundup in one paragraph and wrote that the system "was restored on October 28"; the status page agrees on the date. The rest of this briefing sets out what each source states, what none of them states, and what a filer should do while the second list is still long.
What is stated and what is not. Sources: FEC status page and incident pages (read 30 October 2026), Reuters via AOL and NBC News (27 October), Newsweek, Nextgov and SecurityWeek. Derived figures are marked.
| Question | Stated, and by whom | Not stated in any source read |
|---|---|---|
| When it went down | FEC status page: first posts 21:29 EDT (FECfile+) and 22:15 EDT (electronic filing) on Monday 26 October. Reuters: down since around 10 p.m. ET. | The moment of the shutdown decision, and what failed first. |
| When it came back | FEC status page: available at 16:50 EDT (electronic filing) and 19:10 EDT (FECfile+) on 28 October. SecurityWeek: restored on 28 October. | A resolved status: both incidents still read as monitoring when read. Whether every service returned. |
| The cause | Reuters, from an internal email: a bad actor attempting to breach FEC systems; web facing services shut down. | Any FEC public statement of cause, the method, or an actor. Newsweek writes that the FEC has not confirmed the attempt. |
| The data | FEC statement: past reports can still be searched. Newsweek quotes an FEC deputy press officer that search of FEC reports was not affected. | Whether any data was read or altered, and whether any pending submission was lost. |
| The deadlines | FEC pages: a 24 hour report period for independent expenditures from 15 October to 1 November; 48 hour notices of contributions from 15 to 31 October. | Any extension or penalty relief on an FEC page read for this briefing. |
| Federal help | Reuters: CISA and the FBI referred questions to the FEC. | Whether either agency is assisting, or was told. |
The timeline the FEC's own page prints
The status page lists the two incidents. The first, FECfile+ filing submission outage, affects the FECfile+ application. The second, electronic filing system outage, affects Efiling, which the page breaks into online web forms, the electronic filing submission system and electronic filing vendor tools. Both open as investigating on Monday evening, and the page shows each marked identified late on the 26th (FECfile+) or at 20:17 EDT on Tuesday 27 October (electronic filing), with a note to see the FEC's electronic filing system outage alert. The Tuesday post reads "The issue has been identified and a fix is being implemented". Reuters reported the same message at around 8 p.m. ET.
There is one more FEC record of the outage itself. An Internet Archive capture of the FEC home page, taken at 03:02 UTC on 28 October (23:02 EDT on 27 October), carries a banner: "FEC's electronic filing system is currently offline:" followed by "We apologize for the inconvenience, and we're continuing to work to resolve the issue" and a link to the incident. The live home page read on 30 October carries no banner, and the FEC's news page (updates) lists nothing after its weekly digest of 23 October, so no FEC news item about the outage was found. When read again at 15:48 UTC on 30 October, the status page listed the Wednesday 28 October row as "Unresolved incidents", naming both. That is the page's own wording for incidents that have not been marked resolved. It does not mean the systems are down: the page shows every component operational.
Nextgov reports a notification email, obtained by its reporter, that said several systems remained offline, "including various filing search features, campaign finance report validation tools, and other feeds and channels". So the outage was wider than the submission step on Tuesday, and the FEC's separate statement that past reports can be searched on its website is a statement about one function. A comparable halt in the US courts is covered in an earlier briefing, US bankruptcy noticing halted since 9 October, where the same question arose: what was down, and what still worked.
Three voices, and what none of them says
Three kinds of source are in play, and they say different things. The status page says outage and offers no cause. The FEC's statement to the press, as printed by Reuters via AOL, reads "At this time, the FEC's electronic filing system is currently offline and our IT staff are actively working to restore service." NBC News, carrying the same Reuters copy, adds that the agency "declined further comment on the outage". The third voice is the internal email Reuters saw, which uses the language of an attack.
Two points follow. First, the attack language rests on one email, relayed by one news agency, and Newsweek writes that the FEC "has not confirmed the attempt or a successful attack" (Newsweek's wording, not an FEC statement). A reader should hold it as reported and not as established. eSecurity Planet makes the same point in its own words: the FEC confirmed the disruption but has not publicly confirmed a successful breach or said whether information was compromised. Second, nothing read says the attempt succeeded. An officer who writes "attempting to breach" and shuts down web facing services is describing a defensive step, and a defensive step is also what an operator would take on a suspicion that turned out to be nothing. The record does not let a reader choose between those.
What the sources do agree on is the boundary. Reuters writes that the FEC does not play a role in administering US elections and that the outage should not affect voters casting ballots; Newsweek and Nextgov say the same. The system that stopped is the one that takes campaign finance reports, so what was lost during the outage is timely public sight of spending, not a vote. Reuters also reports that CISA and the FBI referred questions to the FEC, which is a statement about whom they pointed to, not about whether they are involved.
What the outage landed on: the last minute reporting windows
The FEC's reminder of 13 October says campaign committees must disclose within 48 hours any contribution of $1,000 or more received between 15 and 31 October, and that PACs, party committees and others making independent expenditures that aggregate $1,000 or more for the same race between 15 October and 1 November must file 24 hour reports. The FEC's dates page prints the 24 hour period as 15 October to 1 November for the 3 November election. The outage began on 26 October, which is day 12 of an 18 day window (derived), and the filing system was reported available on 28 October, so it covered 3 of the 18 days of the 24 hour period (derived, counting 26, 27 and 28 October). Reuters reports that the outage prevented organisations from filing the FEC's 24 hour and 48 hour spending reports, which show spending on specific races.
The FEC pages read for this briefing say nothing about an extension or relief. One secondary source does: MultiState, in a post of 28 October, writes that the FEC "has stated it will not impose penalties on late reports affected by the outage as long as filers submit their disclosures within 24 hours of the system being restored". This briefing could not find that statement on any FEC page and has not seen the statement itself, so treat it as unverified until the FEC publishes it. The same post carries a headline and a sentence about AI bots allegedly behind the attack. No source read supports that, and this briefing does not repeat it as a fact.
The practical point stands without the extension. Statutory dates are one thing and the FEC's decision whether to pursue a late filer is another, and a filer who relies on the second without a written source is relying on a rumour. The FEC's own electronic filing overview says to "File as early as possible" and notes that a filer who gets no receipt "should not assume the FEC received their filings". The next section turns those into a list.
Claims in coverage set against the record. Sources: FEC pages and status page (read 30 October 2026); Reuters via AOL and NBC News; Newsweek; MultiState.
| Claim in coverage | What the record establishes | What it does not establish |
|---|---|---|
| The FEC was hacked. | Reuters reports an internal email describing a bad actor attempting to breach FEC systems. | That any attempt succeeded, or that the FEC itself has said so. |
| The system was down from Monday night to Wednesday. | The FEC status page times: first posts 26 October, available 28 October. | Whether every function returned, or when the incidents will be marked resolved. |
| Reports due in the window could not be filed. | Reuters: the outage prevented the 24 hour and 48 hour reports. The FEC's reminder sets the windows. | How many filers, which reports, or whether late filers will be penalised. |
| Filers will not be penalised. | MultiState says the FEC stated this. | Any FEC page or notice saying so, in the pages read. |
| Past filings stayed searchable. | The FEC said search of past reports was not affected. | That nothing else was touched. |
Technical details
None of the FEC pages, and none of the news reports read, prints a technical artifact for this incident: no indicator of compromise, no address, domain, hash, vulnerability, tool, log line or description of how the attempt was made. So there is nothing to hunt for from these sources and no indicator is invented here. The blocks below hold the only machine readable wording the primaries print, the status page entries and the banner, copied as printed, so that a compliance team can match its own logs of the outage against the FEC's clock. Times are Eastern (EDT), as printed.
Monitoring - The electronic filing system is available. A fix has been implemented and we are monitoring the results. Posted Oct 28 , 2026 - 16:50 EDT
Identified - The issue has been identified and a fix is being implemented. Posted Oct 27 , 2026 - 20:17 EDT
Update - We are continuing to investigate this issue. Posted Oct 27 , 2026 - 09:35 EDT
Update - We are continuing to investigate this issue. Posted Oct 27 , 2026 - 02:47 EDT
Update - We are continuing to investigate this issue. Posted Oct 26 , 2026 - 23:08 EDT
Investigating - We are currently investigating this issue. Posted Oct 26 , 2026 - 22:15 EDT
This incident affects: Efiling (Online web forms, Electronic filing submission system, Electronic filing vendor tools).
Update - FECfile+ is available. A fix has been implemented and we are monitoring the results. Posted Oct 28 , 2026 - 19:10 EDT
Update - We are continuing to monitor for any further issues. Posted Oct 28 , 2026 - 17:32 EDT
Monitoring - A fix has been implemented and we are monitoring the results. Posted Oct 28 , 2026 - 16:51 EDT
Update - This issue has been identified. See FEC's electronic filing system outage alert for more information. Posted Oct 27 , 2026 - 20:16 EDT
Update - See FEC's electronic filing system outage alert for more information. Posted Oct 27 , 2026 - 09:36 EDT
Identified - This issue has been identified. See FEC's electronic filing system outage alert for more information. Posted Oct 26 , 2026 - 23:12 EDT
Update - We are continuing to investigate this issue. Posted Oct 26 , 2026 - 23:09 EDT
Investigating - We are currently investigating this issue. Posted Oct 26 , 2026 - 21:29 EDT
This incident affects: FECfile+ application.
FEC's electronic filing system is currently offline:
We apologize for the inconvenience, and we're continuing to work to resolve the issue
The first two blocks are the whole status record. The posts are timestamped, so a filer can show that a submission attempt on the afternoon of 27 October fell inside a stated outage. The email quoted by Reuters, "We have a bad actor attempting to breach FEC systems", is not reproduced in a block because this site has not seen the email, only Reuters's quotation of it.
What to harden, as this site's reading and not an FEC instruction: filers cannot defend the FEC's systems, but they can protect their own submission path. Keep the committee's electronic filing password and its software current (the FEC says to run auto updates when prompted), and keep the treasurer's mailbox, where the receipt emails land, protected with a second factor, because that mailbox is the filer's proof of what was submitted and when.
What filers and campaigns should do, in order
The FEC has published no filer guidance for this outage in the pages read, so the list below combines the FEC's standing guidance (cited) with this site's reading of what the record shows went wrong. It is ranked by how much each step protects a filer from a missed or unprovable submission. No product is recommended.
Take this with you
Ranked checklist for committees, treasurers and compliance firms
- Keep the receipt email for every submission, with its validation number. The FEC says the instant confirmation email is important to keep for the committee's records, and that a filer with no receipt should not assume the report was received.
- File earlier than the deadline, with the FEC's own advice (file as early as possible) as the reason. The 24 hour and 48 hour windows run to 1 November and 31 October, so a notice that can be filed the same hour should not wait.
- Check every filing posted after the restoration. Search the committee's reports in the FEC data pages and confirm that each submission made on or after 28 October appears, with the right amounts and dates, and file an amendment at once if one does not.
- Keep a dated log of every attempt made between 26 and 28 October: the time, the error shown, the person who tried. The FEC status page timestamps give the outage clock, and a log ties the filer's own attempts to it.
- Do not wait for an extension that is not on an FEC page. The only claim of penalty relief found is secondary, from MultiState, and is unverified. If late reports are in the file, ask the FEC's Electronic Filing Office in writing and keep the answer.
- Use official channels only. Watch fec.gov, the news and announcements page and the FEC status page for the outage, and treat any unexpected email, text or call that asks a committee to resubmit, reset a password or send reports another way as suspect. The FEC says emailed reports will not be accepted, so no genuine instruction asks for one. Outages are when phishing about them works best (this site's inference).
- Protect the mailbox that receives receipts and the electronic filing password with a second factor, and limit who can submit, so that a lookalike message cannot be used to file or to read receipts.
- Write down, before the next incident, who files, who checks the status page, and what the fallback is when the system is down. Test it on one 48 hour notice.
None of this needs a product. It needs a copy of each receipt, an earlier hour, and a person whose job it is to read the status page.
If the system that takes the last reports before an election can be offline for about two days with no cause on its own status page, what does your compliance plan say to do in the first hour, and who has the written answer from the agency?
Key facts
Sources
- PrimaryFEC.gov status page: the two incident entries, every component, and the incident history. The primary record of the outage times. Read in fullUS Federal Election Commission (FEC.gov status page)accessed 2026-10-30
- PrimaryIncident page 'FECfile+ filing submission outage': every post from 21:29 EDT on 26 October to 19:10 EDT on 28 October. The primaryUS Federal Election Commission (FEC.gov status page)accessed 2026-10-30
- PrimaryIncident page 'FEC's electronic filing system outage': every post from 22:15 EDT on 26 October to 16:50 EDT on 28 October, and the components affected. The primaryUS Federal Election Commission (FEC.gov status page)accessed 2026-10-30
- PrimaryCapture of the FEC home page at 03:02 UTC on 28 October 2026 showing the banner that the electronic filing system was offline. The FEC's own page as archivedInternet Archive capture of www.fec.govaccessed 2026-10-30
- PrimaryFEC electronic filing overview: file as early as possible, receipt emails, no emailed reports. The FEC's standing filer guidanceUS Federal Election Commissionaccessed 2026-10-30
- PrimaryFEC dates page for 24 and 48 hour reports of independent expenditures, general election 2026: the 24 hour period and the election dateUS Federal Election Commissionaccessed 2026-10-30
- PrimaryFEC Tips for Treasurers, 13 October 2026, 'Last minute disclosure periods reminder': the 48 hour and 24 hour windowsUS Federal Election Commissionaccessed 2026-10-30
- PrimaryFEC news and announcements listing, read 30 October 2026: no item about the outage found after the weekly digest of 23 OctoberUS Federal Election Commissionaccessed 2026-10-30
- Reported byReuters, 27 October 2026, 'Exclusive: Hackers target US FEC system, disrupting campaign finance disclosures days before midterms': the internal email quotation, the FEC statement, the 10 p.m. ET time, CISA and FBI referral. SecondaryReuters, carried by AOLaccessed 2026-10-30
- Reported byNBC News, 27 October 2026, the same Reuters report: the FEC declined further comment. SecondaryNBC News (Reuters copy)accessed 2026-10-30
- Reported bySecurityWeek, 30 October 2026, 'In Other News' roundup: the lead for this briefing and the statement that the system was restored on 28 October. SecondarySecurityWeekaccessed 2026-10-30
- Reported byNewsweek, 27 October 2026: statement of an FEC deputy press officer, and that the FEC has not confirmed the attempt. SecondaryNewsweekaccessed 2026-10-30
- Reported byNextgov, 28 October 2026: a notification email listing other systems offline, including filing search features and validation tools. SecondaryNextgov/FCWaccessed 2026-10-30
- Reported byeSecurity Planet, 28 October 2026: the FEC confirmed the disruption but has not publicly confirmed a successful breach. SecondaryeSecurity Planetaccessed 2026-10-30
- Reported byMultiState, 28 October 2026: the claim that the FEC will not penalise late reports filed within 24 hours of restoration. Unverified, and the post carries unsupported speculation about AI bots. SecondaryMultiStateaccessed 2026-10-30
