System Outages on the Last Day
Filing systems go down, usually briefly and just occasionally on the evening of a deadline. The rules anticipate that, and the relief they offer depends almost entirely on what the filer thought to record while the failure was actually happening.
The rule in short
Most electronic filing regimes provide for extensions or alternative routes where the system is unavailable. Obtaining that relief requires contemporaneous evidence: timestamps of attempts, error messages, screenshots and any official outage notice. It also requires distinguishing a system failure, which usually attracts relief, from a problem at the filer's own end, which usually does not.
An outage on the last day is a solvable problem and a stressful one, and the difference between those outcomes is made in the first ten minutes by whoever thinks to take screenshots.
What usually qualifies as an outage
The filing system being unavailable. A complete failure of the platform, which is the clearest case and is generally announced by the operator.
Partial unavailability. Where submissions can be started and not completed, or where a specific function fails while the rest works.
Failures during scheduled maintenance. Announced maintenance windows that overrun, or that were scheduled without adequate notice.
Authentication failures at the system's end. Where credentials are correct and the platform will not accept them.
Payment gateway failures. Where the fee cannot be processed because the system's payment component is down.
Regional connectivity problems affecting the operator. Rather than problems affecting the individual filer.
Documented degradation. Severe slowness that prevents completion is sometimes treated as unavailability.
Whatever the rule defines. Provisions vary considerably, and some are drafted narrowly enough to exclude anything short of a total failure.
Announced closures of the office. Where a registry is inaccessible for a reason unconnected with technology, the same relief provisions frequently apply and are worth reading together.
What usually does not qualify
The filer's own connectivity. A domestic internet failure is the filer's risk, and it is the commonest rejected explanation.
Device problems. A laptop that will not start, a browser that will not update or a certificate that has expired locally.
Forgotten or expired credentials. Password and multi-factor problems are foreseeable and are treated as such.
Files that are too large. Upload duration is a planning problem rather than a system failure, per what an electronic timestamp records.
Not knowing how to use the system. Unfamiliarity is not unavailability, however genuine the difficulty.
Leaving it too late. An outage lasting twenty minutes only matters to somebody filing in the last twenty minutes.
Payment failures at the filer's bank. Declined cards are a filer-side problem and a frequent one.
Failing to use an available alternative. Where the rules provide another route during an outage and nobody used it.
Waiting for the system to return. A filer who chose to wait rather than to use a permitted alternative has made a decision that will be examined closely afterwards.
| Cause | Relief likely | Evidence needed |
|---|---|---|
| System-wide outage | Yes | Status page, screenshots |
| Partial failure | Often | Error messages, attempts |
| Filer's connectivity | No | — |
| Expired credentials | No | — |
| Large upload overrun | No | — |
Evidence to capture during the outage
Screenshots with visible time. Of the error, the page and ideally a clock, taken at each attempt rather than reconstructed afterwards.
Error messages verbatim. Including any reference or incident number the system generates.
A log of attempts. Times, what was tried and what happened, written as it occurs.
The operator's status page. Official outage announcements are the strongest evidence available and disappear once resolved.
Support contact records. Times of calls or tickets, and whatever was said, which corroborates the account.
Confirmation that connectivity was working. Another site loading, or a test from a second connection, which rules out a filer-side cause.
A second device or connection tried. Which is both good practice and evidence that the problem was not local.
The document ready to file. Showing that it was complete and awaiting submission rather than still being prepared at the time.
File metadata. The saved version of the document carries its own timestamps, which corroborate that it was finished before the deadline rather than afterwards.
Every one of these applications turns on contemporaneous evidence. A status page disappears when the incident is resolved, and an error message nobody captured is an assertion rather than a record.
What to do during an outage
Keep trying at intervals. Both because it may resolve and because the record of repeated attempts matters.
Check the official status information. Which usually confirms whether the problem is general or local.
Try an alternative route. Many systems provide for paper, email or emergency filing during unavailability, on conditions.
Notify somebody. A message to the forum or the operator creates a contemporaneous record of the attempt.
Tell the other side. Particularly where they are expecting the document, since it costs nothing and prevents an argument.
File the moment it recovers. Even at an unsociable hour, because the recovery time will be part of the record.
Do not abandon the attempt. A filer who stopped trying at ten o'clock is in a worse position than one who kept going.
Prepare the application in parallel. If relief is going to be needed, drafting it during the outage itself saves a day.
Agree who decides. A named person with authority to choose between waiting, using an alternative route and filing on paper prevents an hour of discussion during the outage itself.
Afterwards
File as soon as possible. The interval between recovery and filing is the part the filer still controls.
Apply for relief promptly. With the evidence attached rather than described, per seeking relief once the period has expired.
Set out the timeline precisely. Attempt times, error messages, recovery time and filing time, in sequence.
Address the obvious question. Why the filing was being made at that hour, which is asked in almost every one of these applications.
Do not overstate the outage. Operators keep records, and an account contradicted by them is worse than none.
Check the filing was accepted. Post-outage submissions sometimes fail their checks, per a filing rejected for a formal defect.
Record the incident internally. So that the same last-hour practice does not produce the same emergency.
Adjust the habit. The reliable answer to outages is filing earlier, which is the only response entirely within a filer's control.
Keep the evidence with the matter. An outage that affected one filing frequently affected others, and a single preserved record answers the question for every one of them.
Electronic filing regimes generally provide relief where the system is unavailable, and most also provide an alternative route to be used during the failure.
Relief attaches to system-side problems: complete or partial unavailability, authentication failures at the operator's end, payment gateway failures and documented severe degradation.
It rarely attaches to filer-side problems, including domestic connectivity, device failures, expired credentials, oversized uploads and declined payment cards.
The application is decided on contemporaneous evidence: timestamped screenshots, verbatim error messages, a log of attempts, the operator's status page and support contact records.
The only complete answer is filing earlier, because a twenty-minute outage matters exclusively to somebody who left the submission until the final twenty minutes. Where the electronic route is unavailable, the older ones are still there, and they are described in courier, fax and after-hours filing.
Points to carry away
- Rules commonly provide relief for system unavailability.
- Filer-side problems rarely qualify.
- Contemporaneous evidence decides the application.
- Alternative routes frequently exist and are time-limited.
- Filing early removes the issue entirely.
Questions readers ask
Does a filing system outage automatically extend the deadline?
Not automatically in most systems, though many rules provide either an extension or an alternative filing route where the platform is unavailable. Obtaining it generally requires an application supported by evidence, and the strength of that evidence decides the outcome. Some regimes are drafted narrowly enough that only a complete, officially acknowledged failure qualifies, so reading the applicable provision before a deadline evening is worth the few minutes it takes.
What evidence matters most during an outage?
Anything captured while it is happening. Screenshots showing the error with a visible time, verbatim error messages including any incident reference, a written log of attempt times, and the operator's own status page announcement. The status page is particularly valuable and particularly perishable, because it is updated once the incident is resolved. Evidence described afterwards from memory is considerably weaker than the same account supported by images taken at the time.
Does a problem with the filer's own internet connection count?
Generally not. The distinction rules draw is between the system being unavailable and the filer being unable to reach it, and connectivity, devices, credentials and payment cards all fall on the filer's side. That is one reason to check whether other sites load and to try a second connection or device during a failure: it establishes that the problem was not local, which is exactly what the application will need to show.
Sources
- Federal Rules of Civil Procedure — Rule 6(a)(3), Inaccessibility of the Clerk's Officelaw.cornell.edu
- Federal Rules of Civil Procedure — Rule 5(d)(3), Electronic Filinglaw.cornell.edu
- Federal Rules of Appellate Procedure — Rule 26(a)(3), Inaccessibility of the Clerk's Officelaw.cornell.edu
- United States Courts — Electronic Filing (CM/ECF)uscourts.gov
- Federal Rules of Civil Procedure — Rule 6(b), Extending Timelaw.cornell.edu
- Legal Information Institute — Excusable Neglectlaw.cornell.edu
Urban Justice Docket is a publication, not a law firm. This article states general rules and cites its sources; it is not advice about any particular case, and the law differs by state and changes over time.
More in Filing, and When It Counts
A Fee That Blocks a Filing
Many filings require a fee, and where payment is a condition of acceptance a failed transaction prevents the filing entirely. Fee waivers and deferrals exist, take time to obtain, and have their own evidential requirements. The practical protection is arranging payment before the deadline evening and applying for any waiver far enough ahead that its processing time is not the problem.
Amending a Document Already Filed
Amendments fall into categories: clerical corrections, amendments permitted without leave within a window, and amendments requiring permission. The crucial question is whether the amended document is treated as filed on the original date or on the date of amendment, because where a period has expired in the meantime the answer decides whether the new material survives.
Taking a Document Back, and What That Costs
Withdrawing a filed document or a whole claim is available in most systems, sometimes as of right early on and otherwise with permission or consent. The consequences are what matter: protection conferred by the original filing usually ends, limitation continues from where it always was, costs frequently follow, and restrictions on repeat filings can make the decision effectively final.