Patlytics Outage History

Patlytics is up right now

Patlytics had 23 outages in the last 2 years totaling 37h 46m of downtime, averaging 0.9 incidents per month.

There were 23 Patlytics outages since February 10, 2025 totaling 37h 46m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: status.patlytics.ai

Major March 31, 2026

Core component of report creation outage

Detected by Pingoru
Mar 31, 2026, 07:30 PM UTC
Resolved
Mar 31, 2026, 07:30 PM UTC
Duration
–
Timeline · 1 update
  1. resolved Mar 31, 2026, 08:32 PM UTC

    Between 3:40 PM ET and 3:50 PM ET, a failure in the report creation pipeline prevented users from creating new reports. Our team identified and resolved the issue at 3:50 PM ET; all report creation functionality has been restored and no data was lost.

Read the full incident report →

Minor March 17, 2026

Elevated error rates for patent imports and report creation

Detected by Pingoru
Mar 17, 2026, 07:55 AM UTC
Resolved
Mar 17, 2026, 08:46 AM UTC
Duration
51m
Affected: Patent InvalidityAI EngineSearch Engine
Timeline · 2 updates
  1. identified Mar 17, 2026, 07:55 AM UTC

    Our underlying provider is temporarily overloaded, we are currently working to address this issue.

  2. resolved Mar 17, 2026, 08:46 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 11, 2026

Elevated Product Search Failures

Detected by Pingoru
Mar 11, 2026, 02:46 AM UTC
Resolved
Mar 11, 2026, 03:54 AM UTC
Duration
1h 7m
Affected: Detection Report
Timeline · 2 updates
  1. investigating Mar 11, 2026, 02:46 AM UTC

    We currently detected elevated failures for Product Search caused by an underlying provider issue. This may result in some Detection Reports and Infringement Portfolio Heatmap returning no products or failing to start downstream claim chart generation.

  2. resolved Mar 11, 2026, 03:54 AM UTC

    This incident has been resolved. Product Search is back to oprational.

Read the full incident report →

Minor March 2, 2026

Critical Platform Dependency Failure

Detected by Pingoru
Mar 02, 2026, 07:12 PM UTC
Resolved
Mar 02, 2026, 07:47 PM UTC
Duration
35m
Affected: Detection ReportPatent InvalidityPatent ProsecutionAWS rds-us-west-2Patent Vault & Intelligence
Timeline · 5 updates
  1. investigating Mar 02, 2026, 07:12 PM UTC

    We are experiencing a critical production issue affecting core system availability. Our engineering team is actively working on mitigation and will provide updates as progress is made.

  2. investigating Mar 02, 2026, 07:12 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Mar 02, 2026, 07:16 PM UTC

    A fix has been deployed to address the incident impacting core services. We are actively monitoring the system to ensure stability.

  4. monitoring Mar 02, 2026, 07:35 PM UTC

    We are actively monitoring the system to ensure stability.

  5. resolved Mar 02, 2026, 07:47 PM UTC

    The issue has been resolved and services are fully restored.

Read the full incident report →

Notice February 27, 2026

Report analysis for the infringement portfolio heat map is degrading

Detected by Pingoru
Feb 27, 2026, 04:56 PM UTC
Resolved
Feb 27, 2026, 06:59 PM UTC
Duration
2h 3m
Timeline · 4 updates
  1. investigating Feb 27, 2026, 04:56 PM UTC

    We are currently investigating this issue.

  2. identified Feb 27, 2026, 05:39 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Feb 27, 2026, 06:24 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Feb 27, 2026, 06:59 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 12, 2026

Degraded Performance Over Various Report Analysis

Detected by Pingoru
Feb 12, 2026, 03:35 PM UTC
Resolved
Feb 12, 2026, 06:18 PM UTC
Duration
2h 43m
Affected: Detection ReportPatent InvaliditySearch Engine
Timeline · 4 updates
  1. monitoring Feb 12, 2026, 03:35 PM UTC

    We are currently experiencing degraded performance on some of our API services due to an ongoing outage with our upstream provider. Requests may fail or experience increased latency. Our team is monitoring the situation and services will recover automatically once the upstream issue is resolved.

  2. monitoring Feb 12, 2026, 04:06 PM UTC

    We are observing signs of recovery for all affected modules. We will continue to monitor success rates.

  3. monitoring Feb 12, 2026, 06:02 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Feb 12, 2026, 06:18 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 16, 2026

Elevated errors from our Detection Report module

Detected by Pingoru
Jan 16, 2026, 11:25 PM UTC
Resolved
Jan 17, 2026, 01:34 AM UTC
Duration
2h 8m
Affected: Detection Report
Timeline · 6 updates
  1. identified Jan 16, 2026, 11:25 PM UTC

    The issue has been identified and a fix is being implemented.

  2. monitoring Jan 16, 2026, 11:53 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. monitoring Jan 16, 2026, 11:57 PM UTC

    We are continuing to monitor for any further issues.

  4. monitoring Jan 17, 2026, 12:03 AM UTC

    The system is currently recovering. We are actively monitoring performance and will continue to provide updates as progress is made.

  5. monitoring Jan 17, 2026, 12:09 AM UTC

    System performance continues to stabilize. We are closely monitoring all services and will share another update soon.

  6. resolved Jan 17, 2026, 01:34 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 19, 2025

Elevated Error Rates and Degraded Quality for Detection Report Analysis

Detected by Pingoru
Dec 19, 2025, 06:30 AM UTC
Resolved
Dec 19, 2025, 06:30 AM UTC
Duration
–
Timeline · 1 update
  1. resolved Dec 23, 2025, 12:28 PM UTC

    A resource contention issue in our background processing system caused some Detection Report Analysis to queue longer than normal, leading to timeouts before completion. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Minor December 10, 2025

Elevated API Errors: Infringement Service

Detected by Pingoru
Dec 10, 2025, 06:43 AM UTC
Resolved
Dec 10, 2025, 07:32 AM UTC
Duration
49m
Timeline · 1 update
  1. resolved Dec 10, 2025, 09:35 AM UTC

    We were experiencing an elevated level of API errors coming from our Infringement Service between 1:43AM EST and 2:32AM EST. We've remediated the issue and all API is now back to operational.

Read the full incident report →

Notice November 18, 2025

Intermittent access issues affecting Patlytics website

Detected by Pingoru
Nov 18, 2025, 01:52 PM UTC
Resolved
Nov 18, 2025, 05:30 PM UTC
Duration
3h 37m
Affected: Patlytics Customer Dashboard
Timeline · 5 updates
  1. monitoring Nov 18, 2025, 01:52 PM UTC

    We have confirmed that the incident is caused by an issue with one of our third-party service providers. We will provide updates as they become available.

  2. monitoring Nov 18, 2025, 01:53 PM UTC

    We are continuing to monitor for any further issues.

  3. monitoring Nov 18, 2025, 02:33 PM UTC

    We are continuing to monitor for any further issues.

  4. monitoring Nov 18, 2025, 03:08 PM UTC

    A fix has been implemented by the 3rd party service provider and we are monitoring the recovery.

  5. resolved Nov 18, 2025, 05:30 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 17, 2025

We are experiencing degraded service with LLM providers

Detected by Pingoru
Jul 17, 2025, 09:24 PM UTC
Resolved
Jul 17, 2025, 09:36 PM UTC
Duration
12m
Timeline · 2 updates
  1. monitoring Jul 17, 2025, 09:24 PM UTC

    We’re currently experiencing degraded performance for features powered by our AI assistant. This is due to our underlying LLM provider being temporarily overloaded. Our team is actively monitoring the situation and working on mitigation steps, including load balancing and fallback strategies. We’ll keep you updated as soon as service stabilizes. Thanks for your patience! — The Engineering Team

  2. resolved Jul 17, 2025, 09:36 PM UTC

    The incident has been resolved

Read the full incident report →

Minor July 3, 2025

LLM provider overloaded

Detected by Pingoru
Jul 03, 2025, 05:46 PM UTC
Resolved
Jul 03, 2025, 09:13 PM UTC
Duration
3h 27m
Timeline · 4 updates
  1. investigating Jul 03, 2025, 05:46 PM UTC

    We’re currently experiencing degraded performance for features powered by our AI assistant. This is due to our underlying LLM provider being temporarily overloaded. Our team is actively monitoring the situation and working on mitigation steps, including load balancing and fallback strategies. We’ll keep you updated as soon as service stabilizes. Thanks for your patience! — The Engineering Team

  2. identified Jul 03, 2025, 05:46 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Jul 03, 2025, 08:07 PM UTC

    The earlier performance issues caused by our LLM provider being overloaded are now recovering. Most AI-powered features should be working as expected again. We’ll continue to monitor the situation closely and will take further action if needed. Thanks for your patience! — The Engineering Team

  4. resolved Jul 03, 2025, 09:13 PM UTC

    This incident has been resolved.

Read the full incident report →

Major July 1, 2025

LLM Service Degradation Notice

Detected by Pingoru
Jul 01, 2025, 08:52 PM UTC
Resolved
Jul 02, 2025, 12:36 AM UTC
Duration
3h 43m
Affected: Detection ReportPatent InvalidityPatent ProsecutionPatent Vault & Intelligence
Timeline · 3 updates
  1. investigating Jul 01, 2025, 08:52 PM UTC

    We’re currently experiencing degraded performance for features powered by our AI assistant. This is due to our underlying LLM provider being temporarily overloaded. Our team is actively monitoring the situation and working on mitigation steps, including load balancing and fallback strategies. We’ll keep you updated as soon as service stabilizes. Thanks for your patience! — The Engineering Team

  2. monitoring Jul 02, 2025, 12:03 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jul 02, 2025, 12:36 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical June 27, 2025

LLM provider connection degraded

Detected by Pingoru
Jun 27, 2025, 10:48 PM UTC
Resolved
Jun 27, 2025, 11:14 PM UTC
Duration
26m
Affected: Detection ReportPatent ProsecutionAI Engine
Timeline · 3 updates
  1. investigating Jun 27, 2025, 10:48 PM UTC

    We’re currently experiencing an issue affecting multiple modules, including but not limited to Detection Report, Infringement, and Invalidity. Our engineering team is actively working on a fix. We’ll provide updates as soon as possible—thank you for your patience.

  2. investigating Jun 27, 2025, 11:14 PM UTC

    The earlier issue affecting modules such as Detection Report, Infringement, and Invalidity has been fully resolved. All modules are now functioning normally. Thank you for your patience!

  3. resolved Jun 27, 2025, 11:14 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 13, 2025

Degrading experience on our platform

Detected by Pingoru
Jun 13, 2025, 11:00 AM UTC
Resolved
Jun 13, 2025, 11:00 AM UTC
Duration
–
Timeline · 1 update
  1. resolved Jun 13, 2025, 11:52 AM UTC

    During a brief period, our systems experienced a database issue that prevented new changes and updates from being saved. Access to existing information was unaffected. The underlying issue has been resolved, and all services are now operating normally. We apologize for any inconvenience this may have caused.

Read the full incident report →

Major June 5, 2025

Intermittent database connection issues

Detected by Pingoru
Jun 05, 2025, 07:00 AM UTC
Resolved
Jun 05, 2025, 07:00 AM UTC
Duration
–
Timeline · 1 update
  1. resolved Jun 06, 2025, 06:42 PM UTC

    We've experienced intermittent database connection issues that impacted application performance and service usage. The incident was detected via elevated error rates and resolved shortly after. The total duration of the incident was from 2:48PM PT to 3:50PM PT. Since, our service is back to operational.

Read the full incident report →

Minor May 19, 2025

Partial throttling of the patent search functionality

Detected by Pingoru
May 19, 2025, 06:17 PM UTC
Resolved
May 19, 2025, 07:42 PM UTC
Duration
1h 25m
Affected: Patent Vault & IntelligenceSearch Engine
Timeline · 4 updates
  1. investigating May 19, 2025, 06:17 PM UTC

    This impacts several dependent features, including but not limited to: bulk patent upload, adding patents to vaults, and certain components of the infringement.

  2. investigating May 19, 2025, 07:41 PM UTC

    We are continuing to investigate this issue.

  3. monitoring May 19, 2025, 07:42 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved May 19, 2025, 07:42 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 25, 2025

Elevated error on platform login

Detected by Pingoru
Mar 25, 2025, 06:35 PM UTC
Resolved
Mar 25, 2025, 07:25 PM UTC
Duration
49m
Affected: Patlytics Customer DashboardAuth0 User Authentication
Timeline · 4 updates
  1. identified Mar 25, 2025, 06:35 PM UTC

    We've observed elevated errors on our platform login. We are looking into the issue

  2. identified Mar 25, 2025, 06:37 PM UTC

    The root cause has been identified by our downstream provider. We continue to working with our provider to remediate the issue.

  3. monitoring Mar 25, 2025, 07:14 PM UTC

    Our downstream provider has implemented a fix and have an early sign of recovering. We continue to working with them to monitor the progress.

  4. resolved Mar 25, 2025, 07:25 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 10, 2025

Prior art search engine degradation

Detected by Pingoru
Feb 10, 2025, 08:16 PM UTC
Resolved
Feb 11, 2025, 05:01 AM UTC
Duration
8h 45m
Affected: Search Engine
Timeline · 3 updates
  1. identified Feb 10, 2025, 08:16 PM UTC

    We are experiencing degradation of our prior art search service. We are working on remediating the issue.

  2. monitoring Feb 10, 2025, 10:19 PM UTC

    A remediation fix has been implemented. We are monitoring.

  3. resolved Feb 11, 2025, 05:01 AM UTC

    This incident has been resolved.

Read the full incident report →