Patlytics Incident History

1. postmortemAug 27 · 14:20 UTC

   ## What happened On **2026-08-17, between approximately 21:00 and 21:20 UTC**, a routine software update introduced a misconfiguration which incorrectly pinned the execution of a piece of server software to the browser. As a result, loading Patlytics in the browser displayed a generic error screen instead of the application. No data was lost, exposed, or altered, and no background processing \(report generation, analysis jobs, or integrations\) was affected. ## Who was affected The issue affected new page loads only. Users who already had Patlytics open in a browser continued working without interruption for the duration of the window; our usage telemetry shows normal levels of in-session activity throughout the incident period. Users who opened, reloaded, or returned to the application during the roughly 20-minute window would have seen the error screen and been unable to proceed until the fix was applied. The impact was limited to the web interface. API access and asynchronous jobs processing \(including report generation\) were unaffected. ## What we did Internal users were the first to report the issue to our Engineering team and service was restored immediately via roll back. The rollback landed at approximately 21:20 UTC, and normal page loads resumed immediately. ## What we're doing to prevent this from happening again We have made the following changes to our release process and monitoring: * **Automated browser-level testing** for changes that touch application configuration and startup code. Although storybook and unit tests exist, these failed to capture this type of defect. * **Improved monitoring for total page-load failures.** Because the failure occurred before our client-side monitoring could initialize, it produced no error telemetry. We have added independent monitoring that detects a drop in successful page loads directly, so this class of outage is caught by alerting rather than by user report. We hold ourselves to a high standard of reliability, and we apologize for the disruption. Please reach out to your Patlytics contact, or message us through the in-app support widget, with any questions.

Reported by Patlytics on their status page.

1. postmortemAug 27 · 14:15 UTC

   ## What happened From **2026-08-11 21:20 UTC to 2026-08-17 02:01 UTC**, a software update to our Detection Report evidence-gathering process had an unintended side effect: for some reports, when the system tried to find a PDF version of a web page it had crawled, that step could take much longer than expected. When it took too long, the system gave up on that page — and in doing so, it also discarded evidence \(page text and images\) that had already been successfully collected for that page. The report would still finish and be marked as complete, with no error shown. It simply contained less of the underlying evidence than it should have. ## Who was affected This affected 33% of Detection Reports generated during that six-day window. All other reports generated during this period, or generated outside this window, were not affected. ## What we did We identified and fixed the underlying issue on **August 17, 2026**. For every report affected by this issue, we have since generated a new version using the same inputs as the original \(same patent, claims, target company, and search parameters\), and verified that each new version reflects the full set of available evidence. These new versions are now available and supersede the originally affected reports. We recommend relying on the newly generated versions going forward. ## What we're doing to prevent this from happening again We have added automated checks that compare how much evidence a report was expected to gather against how much it actually collected, so that any future shortfall is flagged immediately rather than passing through unnoticed. We are also strengthening our review process for changes to this part of the system going forward. We take the completeness and reliability of our reports seriously, and we apologize for any inconvenience this may have caused. Please reach out to your Patlytics contact, or message us through the in-app support widget, with any questions.

Reported by Patlytics on their status page.