Nanonets Outage History

Nanonets is up right now

Nanonets had 24 outages in the last 2 years totaling 29h 28m of downtime — averaging 1 incident per month.

There were 24 Nanonets outages since October 20, 2025 totaling 29h 28m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.nanonets.com

Notice October 1, 2026

Service Disruption Due to Google Cloud Outage - app.nanonets.com

Detected by Pingoru
Oct 01, 2026, 07:46 PM UTC
Resolved
Oct 02, 2026, 12:48 AM UTC
Duration
5h 1m
Timeline · 4 updates
  1. investigating Oct 01, 2026, 07:46 PM UTC

    Some of our models are seeing intermittent failures due to an ongoing issue with Google Cloud Platform (GCP). We're investigating, working with GCP, and applying mitigations to reduce the impact. We'll post another update sooner if anything changes. We apologize for the disruption

  2. monitoring Oct 01, 2026, 09:34 PM UTC

    Error rates have dropped after we made some configuration changes. Services are partially restored, and some requests may still fail intermittently. We're continuing to work on full recovery and will keep you posted with further updates

  3. monitoring Oct 01, 2026, 09:36 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Oct 02, 2026, 12:48 AM UTC

    This incident has been resolved.

Read the full incident report →

Major September 21, 2026

Delayed file processing for models in app.nanonets.com

Detected by Pingoru
Sep 21, 2026, 03:21 PM UTC
Resolved
Sep 21, 2026, 04:55 PM UTC
Duration
1h 34m
Affected: API
Timeline · 5 updates
  1. investigating Sep 21, 2026, 03:21 PM UTC

    We are currently investigating this issue.

  2. identified Sep 21, 2026, 03:52 PM UTC

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

  3. monitoring Sep 21, 2026, 04:49 PM UTC

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

  4. resolved Sep 21, 2026, 04:55 PM UTC

    This incident has been resolved.

  5. postmortem Sep 21, 2026, 05:35 PM UTC

    On 21st September 2026 between 15:00 UTC and 16:30 UTC, some customers experienced delayed document processing and intermittent request failures across multiple models. The cause was an internal resource-accounting component in our model gateway that entered a repeated retry loop. This exhausted connection capacity on the affected service and caused a subset of processing nodes to restart, slowing throughput. We identified the root cause and applied a configuration change that resolved the issue, with service returning to normal by 15:30 UTC and most files were processed before 16:30 UTC. A permanent fix to the underlying component is being rolled out, along with additional monitoring to detect this condition earlier. We sincerely apologize for the inconvenience this caused and we are implementing stricter safeguards to prevent a recurrence

Read the full incident report →

Major June 29, 2026

Brief Service Unavailability on June 29 for app.nanonets.com

Detected by Pingoru
Jun 29, 2026, 04:30 AM UTC
Resolved
Jun 29, 2026, 04:30 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Jun 29, 2026, 04:41 AM UTC

    Between 04:21 AM UTC and 04:25 AM UTC on June 29th, app.nanonets.com experienced a brief service disruption, during which the application was unavailable. The issue was caused by an unexpected error encountered during backend infrastructure operations, resulting in a temporary interruption of service. The issue was identified and resolved promptly, and all services have been fully restored. We apologize for the inconvenience and appreciate your patience.

Read the full incident report →

Notice June 25, 2026

Processing delay on Agent Tasks

Detected by Pingoru
Jun 25, 2026, 10:30 PM UTC
Resolved
Jun 25, 2026, 10:30 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Jun 30, 2026, 12:07 PM UTC

    Our database was running at capacity due to disk usage surge, this lasted for an hour before we recognized the problem and scaled the database.

Read the full incident report →

Major June 25, 2026

Agents UI freezing issue

Detected by Pingoru
Jun 25, 2026, 01:30 PM UTC
Resolved
Jun 25, 2026, 01:30 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Jun 26, 2026, 07:06 AM UTC

    Frontend resources taking time to load causing UI to freeze in loading state. Appropriate CDN fixes were implemented to fix the issue.

Read the full incident report →

Notice June 24, 2026

Processing Delay on Agents

Detected by Pingoru
Jun 24, 2026, 01:30 PM UTC
Resolved
Jun 24, 2026, 01:30 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Jun 30, 2026, 12:03 PM UTC

    We observed processing delay on tasks in Agents Platform for a couple of hours caused by architectural changes introduced by our team to increase observability of our platform.

Read the full incident report →

Notice May 31, 2026

Brief Service Unavailability on June 1 for app.nanonets.com

Detected by Pingoru
May 31, 2026, 07:30 PM UTC
Resolved
May 31, 2026, 07:30 PM UTC
Duration
—
Timeline · 1 update
  1. resolved May 31, 2026, 07:35 PM UTC

    Between 12:53 AM IST and 01:00 AM IST on June 1, app.nanonets.com experienced a brief service disruption, during which the application was unavailable. The issue was caused by an unexpected error encountered during backend infrastructure operations, resulting in a temporary interruption of service. The issue was identified and resolved promptly, and all services have been fully restored. We are reviewing the incident and strengthening our deployment and validation processes to further reduce the likelihood of similar occurrences. We apologize for the inconvenience and appreciate your patience.

Read the full incident report →

Major May 14, 2026

RCA: Performance Degradation for LLM Nano Models on May 14

Detected by Pingoru
May 14, 2026, 10:00 PM UTC
Resolved
May 14, 2026, 10:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved May 15, 2026, 07:14 AM UTC

    From 22:00 UTC to 23:15 UTC on May 14th, we observed performance degradation in the oneshot service affecting LLM Nano models. The issue was primarily caused by a network issue with our GPU service provider. Our team worked with the provider to stabilize the service and performance has since recovered. As an additional preventive measure, we are introducing stronger fallback mechanisms to route requests to more accurate backup models during such events. We apologize for the inconvenience caused and appreciate your patience.

Read the full incident report →

Major April 28, 2026

Elevated 5xx Errors & Timeouts for Instant Learning (LLM Nano)

Detected by Pingoru
Apr 28, 2026, 05:16 AM UTC
Resolved
Apr 28, 2026, 06:02 AM UTC
Duration
46m
Affected: API
Timeline · 3 updates
  1. investigating Apr 28, 2026, 05:16 AM UTC

    We are currently investigating an issue affecting our GPU service provider infrastructure, which is causing elevated 5xx errors and timeouts for Instant Learning models using LLM Nano. Our team is actively working with the provider to identify and resolve the underlying network issues. We will share further updates as soon as we have more information.

  2. monitoring Apr 28, 2026, 05:37 AM UTC

    We’ve temporarily routed LLM Nano traffic to LLM Mini, a more stable, accurate and higher-capacity variant, to mitigate errors. File processing should now be faster and more reliable while we continue working on resolving the underlying issue.

  3. resolved Apr 28, 2026, 06:02 AM UTC

    This incident has been resolved.

Read the full incident report →

Major April 9, 2026

Intermittent 503 Errors for Subset of Users on app.nanonets.com

Detected by Pingoru
Apr 09, 2026, 06:30 AM UTC
Resolved
Apr 09, 2026, 06:30 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Apr 10, 2026, 07:13 AM UTC

    Between 7:19 UTC and 7:29 UTC, a subset of users experienced intermittent 503 errors when accessing app.nanonets.com. A backend node went down and was replaced by a new node. Due to a DNS caching issue, traffic for some users could not be routed to the new node, resulting in failed requests. Other users were unaffected. The issue was identified and resolved by updating the load balancer configuration to ensure proper traffic routing. Preventive measures have been put in place to avoid recurrence.

Read the full incident report →

Minor February 11, 2026

Post-Processing Failures Impacting app.nanonets.com Models

Detected by Pingoru
Feb 11, 2026, 09:10 AM UTC
Resolved
Feb 11, 2026, 09:26 AM UTC
Duration
15m
Affected: API
Timeline · 3 updates
  1. investigating Feb 11, 2026, 09:10 AM UTC

    We are currently investigating this issue.

  2. monitoring Feb 11, 2026, 09:15 AM UTC

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

  3. resolved Feb 11, 2026, 09:26 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 3, 2026

Delayed File Processing and Intermittent Failures Across Regions

Detected by Pingoru
Feb 03, 2026, 03:13 PM UTC
Resolved
Feb 03, 2026, 03:35 PM UTC
Duration
22m
Affected: API
Timeline · 3 updates
  1. identified Feb 03, 2026, 03:13 PM UTC

    One of our GPU service provider is facing issues. We are working on resolving the issue with them.

  2. monitoring Feb 03, 2026, 03:22 PM UTC

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

  3. resolved Feb 03, 2026, 03:35 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 23, 2026

Delayed File Processing in EU & EU-Open Region

Detected by Pingoru
Jan 23, 2026, 05:55 PM UTC
Resolved
Jan 23, 2026, 07:04 PM UTC
Duration
1h 8m
Affected: API
Timeline · 4 updates
  1. investigating Jan 23, 2026, 05:55 PM UTC

    We are currently investigating this issue.

  2. identified Jan 23, 2026, 06:25 PM UTC

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

  3. monitoring Jan 23, 2026, 06:48 PM UTC

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

  4. resolved Jan 23, 2026, 07:04 PM UTC

    This incident has been resolved.

Read the full incident report →

Major January 21, 2026

Async file processing & Extract data section file visibility issue for users using app.nanonets.com

Detected by Pingoru
Jan 21, 2026, 08:58 AM UTC
Resolved
Jan 21, 2026, 09:34 AM UTC
Duration
35m
Affected: APIWeb App
Timeline · 3 updates
  1. investigating Jan 21, 2026, 08:58 AM UTC

    We are currently investigating this issue.

  2. monitoring Jan 21, 2026, 09:07 AM UTC

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

  3. resolved Jan 21, 2026, 09:34 AM UTC

    This incident has been resolved.

Read the full incident report →

Major December 11, 2025

Delay in file processing for Instant learning models in US region

Detected by Pingoru
Dec 11, 2025, 07:56 AM UTC
Resolved
Dec 11, 2025, 09:52 AM UTC
Duration
1h 55m
Affected: API
Timeline · 4 updates
  1. investigating Dec 11, 2025, 07:56 AM UTC

    We are currently investigating this issue.

  2. monitoring Dec 11, 2025, 09:30 AM UTC

    Our sync API is now operating normally. For async uploads, most results are already available and any remaining pending results will be processed within the next few minutes as we clear the backlog. Our team is addressing the issue on priority. We sincerely apologize for the inconvenience caused.

  3. resolved Dec 11, 2025, 09:52 AM UTC

    This incident has been resolved.

  4. postmortem Dec 12, 2025, 07:45 AM UTC

    One of our core processing services experienced an unexpected surge in load, which slowed down parts of our system and led to a backlog in processing. Our engineering team identified the underlying bottleneck and implemented fixes to stabilize performance. We are also rolling out improvements to make our platform more resilient to sudden spikes in usage. We sincerely apologize for the inconvenience caused.

Read the full incident report →

Critical December 8, 2025

IN region Outage

Detected by Pingoru
Dec 08, 2025, 07:52 AM UTC
Resolved
Dec 08, 2025, 07:59 AM UTC
Duration
6m
Affected: APIWeb AppWebsite
Timeline · 3 updates
  1. investigating Dec 08, 2025, 07:52 AM UTC

    Service Disruption on https://in.nanonets.com US and EU regions are not affected

  2. identified Dec 08, 2025, 07:58 AM UTC

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

  3. resolved Dec 08, 2025, 07:59 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 8, 2025

Failures in some instant learning models

Detected by Pingoru
Nov 08, 2025, 06:33 PM UTC
Resolved
Nov 08, 2025, 08:46 PM UTC
Duration
2h 13m
Affected: APIWeb AppWebsite
Timeline · 4 updates
  1. identified Nov 08, 2025, 06:33 PM UTC

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

  2. monitoring Nov 08, 2025, 08:04 PM UTC

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

  3. monitoring Nov 08, 2025, 08:04 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Nov 08, 2025, 08:46 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical October 20, 2025

Service Disruption Due to Global AWS Outage

Detected by Pingoru
Oct 20, 2025, 09:11 PM UTC
Resolved
Oct 20, 2025, 09:43 PM UTC
Duration
32m
Affected: APIWeb App
Timeline · 4 updates
  1. identified Oct 20, 2025, 09:11 PM UTC

    On 20th Oct, a global AWS outage impacted one of our feature flag service providers, resulting in intermittent failures for some of our models. The issue originated from the provider's infrastructure dependency on affected AWS regions, which caused disruptions in feature flag evaluations within our system. Our engineering team promptly identified the root cause and implemented mitigation measures to restore functionality. We are continuously monitoring the situation and working with our partners to ensure full stability. We apologize for the inconvenience caused and appreciate your patience and understanding.

  2. monitoring Oct 20, 2025, 09:28 PM UTC

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

  3. monitoring Oct 20, 2025, 09:29 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Oct 20, 2025, 09:43 PM UTC

    This incident has been resolved.

Read the full incident report →