Nanonets Outage History

Nanonets is up right now

There were 7 Nanonets outages since February 3, 2026 totaling 3h 1m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.nanonets.com

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 10, 2026

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

Detected by Pingoru
Apr 10, 2026, 07:13 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 March 30, 2026

Delayed file processing for ILM models in app.nanonets.com

Detected by Pingoru
Mar 30, 2026, 01:41 PM UTC
Resolved
Mar 30, 2026, 02:03 PM UTC
Duration
21m
Affected: API
Timeline · 3 updates
  1. investigating Mar 30, 2026, 01:41 PM UTC

    We are currently investigating this issue.

  2. identified Mar 30, 2026, 01:52 PM UTC

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

  3. resolved Mar 30, 2026, 02:03 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 10, 2026

Delayed file processing for all ILM models on app.nanonets.com

Detected by Pingoru
Mar 10, 2026, 02:43 PM UTC
Resolved
Mar 10, 2026, 03:58 PM UTC
Duration
1h 15m
Affected: API
Timeline · 5 updates
  1. investigating Mar 10, 2026, 02:43 PM UTC

    We are currently investigating this issue.

  2. identified Mar 10, 2026, 03:19 PM UTC

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

  3. monitoring Mar 10, 2026, 03:34 PM UTC

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

  4. resolved Mar 10, 2026, 03:58 PM UTC

    This incident has been resolved.

  5. postmortem Mar 10, 2026, 04:50 PM UTC

    On March 10 between 1:10 PM and 3:30 PM UTC, we experienced a service degradation that impacted Instant Learning Models \(ILM\) on [app.nanonets.com](http://app.nanonets.com/). **Impact**: During this period, our vector database experienced unusually high load due to the query planner selecting a suboptimal execution path for certain queries. This led to elevated database response times and eventually triggered a database restart. As a result, overall system throughput temporarily decreased. Customers may have observed the following effects during this window: * Asynchronous uploads for ILM models experiencing delayed file processing. * Synchronous uploads for ILM models encountering intermittent failures. Only **Instant Learning Models on** [**app.nanonets.com**](http://app.nanonets.com) were affected. Other services and model types remained fully operational. **Resolution:** Our engineering team identified the root cause related to query planning behaviour in the vector database and implemented targeted customizations to ensure the optimal execution path is used. This stabilized database performance and restored normal processing capacity. **Next Steps:** System is stable now and we are actively working on additional database optimizations and long-term improvements to further strengthen system stability and prevent similar issues from recurring. These enhancements will be rolled out in the coming days. We sincerely apologize for the inconvenience caused and appreciate your patience while we worked to resolve the issue. Please feel free to reach out to our support team incase if you have any questions.

Read the full incident report →

Major March 5, 2026

RCA for Processing Delays for Instant Learning Models on app.nanonets.com – 04 Mar

Detected by Pingoru
Mar 05, 2026, 09:37 AM UTC
Resolved
Mar 04, 2026, 11:00 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Mar 05, 2026, 09:37 AM UTC

    On 04th March between 11:00 AM and 1:10 PM UTC, we experienced a service degradation that affected Instant Learning models hosted on app.nanonets.com During this time window, the secondary database serving part of the processing workload experienced unusually high load. This temporarily reduced our overall processing capacity to approximately 50%. As a result Asynchronous uploads may have experienced increased response times and delayed file processing. Synchronous uploads may have encountered intermittent failures. Only Instant Learning models on app.nanonets.com were affected. Other model types and other regions remained fully operational. Our engineering team identified the source of the elevated database load and implemented corrective actions to stabilize the system. Processing capacity was restored and services returned to normal by 1:10 PM UTC. We are implementing additional optimizations to improve database performance and resilience. These improvements will be deployed over this week and will not require any downtime. We sincerely apologize for the inconvenience caused and appreciate your patience while we worked to resolve the issue. Please feel free to reach out if you have any questions.

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 →

Looking to track Nanonets downtime and outages?

Pingoru polls Nanonets's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Nanonets reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Nanonets alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Nanonets for free

5 free monitors · No credit card required