Context: Ex parte reexamination (EPR) has become a popular fallback for patent challengers who strike out at the Patent Trial and Appeal Board (PTAB). Unlike an inter partes review (IPR), anyone, not just the original challenger, can request an EPR, and it comes with a much lower bar to get the USPTO to take another look at a patent. U.S. Patent No. 8,234,705 “Contagion Isolation and Inoculation”, covering methods for detecting infected or vulnerable computers and quarantining them from a secure network, has already survived six prior challenges at the PTAB, including from Cisco, Forescout, Hewlett Packard Enterprise, Netskope, Citrix, and Google itself. The patent traces its priority date back to September 27, 2004, and was granted in 2012.
What’s new: The patent owner has petitioned USPTO Director John A. Squires to vacate an EPR order issued against the ’705 patent, arguing that Google filed the reexam on April 8, 2026, using the exact same prior art references from its own IPR petition that the PTAB had denied just months earlier. The petition argues that 35 U.S.C. § 325(d), a provision meant to stop parties from re-litigating issues the Office has already decided, should bar Google from getting a second shot at the same patent through a different procedural door.
Direct impact: If the USPTO Director agrees, the reexam of the ’705 patent would be terminated before it goes any further, closing off Google’s latest attempt to invalidate a patent it has already tried and failed to knock out through an IPR. If the Director declines, the reexam proceeds and Google’s cited prior art gets a full second look, but from that point on Google has no further role in the proceeding. In an EPR, once the request is filed, the requester drops out entirely and it becomes a back and forth between the examiner and the patent owner alone, unlike an IPR where the challenger stays involved throughout.
Wider ramifications: The petition includes a chart showing this is not a one-off move by Google. Since January 20, 2025, Google has filed at least 21 EPRs against patents where a prior IPR had already failed, and in 19 of those, Google itself was the one whose IPR got rejected. More broadly, the petition points to USPTO data showing that between January 2025 and August 2026, just under a third of all reexam requests filed, 425 out of 1,318, involved patents that had already been through an IPR or other post-grant review, covering 714 such proceedings combined. That suggests that the tactic of trying an EPR after an IPR flops is being widely implemented , although Google appears to be the system’s heaviest user.
Why companies are turning to EPRs after IPRs fail
Filing an EPR after losing an IPR is entirely legal, and for a company with Google’s resources, it costs relatively little to take another swing at a patent. IPRs have also gotten tougher to win recently, following rule changes under the current USPTO leadership (October 16, 2025 ip fray article), with IPR petitions hitting a record monthly low in April as those new policies took hold (May 4, 2026 ip fray article), a trend also discussed in ip fray’s recent interview with former USPTO Deputy Director Coke Stewart (August 24, 2026 ip fray article). That shift may be nudging more challengers toward reexams as an alternative path. The tradeoff is that an EPR works very differently from an IPR: a company can actively argue its case throughout an IPR, but once it files an EPR, it loses any say in how the proceeding unfolds. From that point on, it is strictly a back and forth between the patent examiner and the patent owner.
Google’s pattern of EPRs following failed IPRs
| Reexam Control # | Patent # | EPR Filed | Prior IPR(s) |
| 90/015465 | 10,789,626 | Aug 22, 2025 | IPR2024-01269 (Google LLC / Institution Denied) |
| 90/015545 | 9,633,378 | Sep 26, 2025 | IPR2024-01270 (Google LLC / Institution Denied) |
| 90/015546 | 10,262,342 | Sep 26, 2025 | IPR2024-01271 (Google LLC / Institution Denied) |
| 90/015547 | 10,152,734 | Sep 26, 2025 | IPR2024-01272 (Google LLC / Institution Denied) |
| 90/015601 | 11,234,117 | Oct 14, 2025 | IPR2023-00115 (Apple Inc. / Terminated-Settled); IPR2023-00116 (Apple Inc. / Terminated-Settled); IPR2023-00117 (Apple Inc. / Institution Denied); IPR2025-00365 (Google LLC et al. / Discretionary Denial); IPR2025-00366 (Google LLC et al. / Discretionary Denial); IPR2025-00367 (Google LLC et al. / Discretionary Denial) |
| 90/015607 | 11,122,418 | Oct 17, 2025 | IPR2023-00090 (Apple Inc. / Terminated-Settled); IPR2025-00018 (Google LLC et al. / Institution Denied) |
| 90/015735 | 8,271,877 | Dec 1, 2025 | IPR2025-00856 (Apple Inc. / Institution Denied) |
| 90/015906 | 10,789,626 | Jan 26, 2026 | IPR2024-01269 (Google LLC / Institution Denied) |
| 90/015954 | 10,943,058 | Feb 10, 2026 | IPR2025-00857 (Apple Inc. / Trial Instituted) |
| 90/016058 | 6,816,809 | Mar 18, 2026 | IPR2022-01197 (Google LLC / Institution Denied) |
| 90/016123 | 10,541,883 | Apr 2, 2026 | IPR2025-00510 (Linkplay Technology Inc. et al. / Discretionary Denial); IPR2025-01213 (Google LLC / Discretionary Denial) |
| 90/016172 | 9,516,048 | Apr 8, 2026 | IPR2022-00843 (Hewlett Packard Enterprise Company et al. / Institution Denied); IPR2025-01437 (Google LLC / Discretionary Denial) |
| 90/016173 | 8,234,705 | Apr 8, 2026 | IPR2021-00593 (Cisco Systems, Inc. / Terminated-Settled); IPR2022-00081 (Forescout Technologies, Inc. / Terminated-Settled); IPR2022-00084 (Hewlett Packard Enterprise Company et al. / Terminated-Settled); IPR2025-01115 (Netskope, Inc. / Discretionary Denial); IPR2025-01436 (Google LLC / Discretionary Denial); IPR2025-01468 (Citrix Systems, Inc. et al. / Terminated) |
| 90/016189 | 7,069,560 | Apr 17, 2026 | IPR2019-00730 (Google LLC / Terminated); IPR2019-00731 (Google LLC / Final Written Decision); IPR2019-00732 (Google LLC / Institution Denied); IPR2019-00835 (Microsoft Corporation / Final Written Decision); IPR2019-00836 (Microsoft Corporation / Final Written Decision); IPR2019-00837 (Microsoft Corporation / Final Written Decision) |
| 90/016190 | 6,851,115 | Apr 17, 2026 | IPR2019-00728 (Google LLC / Final Written Decision); IPR2019-00729 (Google LLC / Institution Denied); IPR2019-00810 (Microsoft Corporation / Final Written Decision); IPR2019-00811 (Microsoft Corporation / Final Written Decision); IPR2019-00812 (Microsoft Corporation / Final Written Decision); IPR2019-00813 (Microsoft Corporation / Final Written Decision); IPR2019-00814 (Microsoft Corporation / Final Written Decision) |
| 90/016191 | 7,036,128 | Apr 17, 2026 | IPR2019-00733 (Google LLC / Final Written Decision); IPR2019-00734 (Google LLC / Final Written Decision); IPR2019-00735 (Google LLC / Institution Denied); IPR2019-00736 (Google LLC / Institution Denied); IPR2019-00838 (Microsoft Corporation / Institution Denied); IPR2019-00839 (Microsoft Corporation / Institution Denied); IPR2019-00840 (Microsoft Corporation / Institution Denied) |
| 90/016453 | 7,571,014 | Jul 9, 2026 | IPR2026-00021 (Google LLC / Discretionary Denial) |
| 90/016455 | 11,080,001 | Jul 9, 2026 | IPR2026-00020 (Google LLC / Discretionary Denial) |
| 90/016515 | 10,031,715 | Aug 7, 2026 | IPR2025-01590 (Google LLC / Discretionary Denial) |
| 90/019836 | 9,338,140 | Jan 31, 2025 | IPR2024-00213 (Google LLC / Institution Denied) |
| 90/019892 | 8,589,541 | Mar 31, 2025 | IPR2024-00942 (Google LLC et al. / Final Written Decision); IPR2024-00943 (Google LLC et al. / Final Written Decision); IPR2024-00944 (Google LLC et al. / Institution Denied) |
Chart based on data compiled by Bunsow De Mory LLP.
Examiner and counsel
Examiner: David E. England, Art Unit 3992.
Patent owner’s counsel: Bunsow De Mory LLP’s Wayne M. Helge and James T. Wilson.
Counsel served on behalf of Google as third-party requester: Buchanan Ingersoll & Rooney PC’s Patrick C. Keane.
