Nanonets Outage History

26 incidents recorded over the last 365 days, 24 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Nanonets status100.00% uptime history

Every Recorded Nanonets Incident

Nanonets incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 1, 2026Service Disruption Due to Google Cloud Outage - app.nanonets.comThis incident has been resolved.5h 1mResolved
Sep 21, 2026Delayed file processing for models in app.nanonets.comOn 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…1h 34mResolved
Jul 23, 2026Delayed file processing for ILM models in app.nanonets.com**Date of Incident:** 23-July-2026 **Region Affected:** US **Duration:** 14:10 UTC – 16:40 UTC **Severity:** Partial degradation \(no data loss\) **Summary** On the date above, customers in the US region using…59 minResolved
Jun 30, 2026Processing delay on Agent TasksOur database was running at capacity due to disk usage surge, this lasted for an hour before we recognized the problem and scaled the database.-6577 minResolved
Jun 30, 2026Processing Delay on AgentsWe 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.-8553 minResolved
Jun 29, 2026Brief Service Unavailability on June 29 for app.nanonets.comBetween 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…0 minResolved
Jun 26, 2026Agents UI freezing issueFrontend resources taking time to load causing UI to freeze in loading state. Appropriate CDN fixes were implemented to fix the issue.-1056 minResolved
May 31, 2026Brief Service Unavailability on June 1 for app.nanonets.comBetween 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…-5 minResolved
May 15, 2026RCA: Performance Degradation for LLM Nano Models on May 14From 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…-554 minResolved
May 2, 2026Scheduled Maintenance: EU & EU-Open Services DowntimeThe scheduled maintenance has been completed.4h 0mScheduled
Apr 28, 2026Elevated 5xx Errors & Timeouts for Instant Learning (LLM Nano)This incident has been resolved.46 minResolved
Apr 10, 2026Intermittent 503 Errors for Subset of Users on app.nanonets.comBetween 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…-1483 minResolved
Mar 30, 2026Delayed file processing for ILM models in app.nanonets.comThis incident has been resolved.21 minResolved
Mar 10, 2026Delayed file processing for all ILM models on app.nanonets.comOn 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…1h 15mResolved
Mar 5, 2026RCA for Processing Delays for Instant Learning Models on app.nanonets.com – 04 MarOn 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…-1357 minResolved
Feb 15, 2026Network Maintenance Notice in US RegionThe scheduled maintenance has been completed.10 minScheduled
Feb 11, 2026Post-Processing Failures Impacting app.nanonets.com ModelsThis incident has been resolved.15 minResolved
Feb 3, 2026Delayed File Processing and Intermittent Failures Across RegionsThis incident has been resolved.22 minResolved
Jan 28, 2026Delayed file processing for all ILM models in app.nanonets.com**Incident Summary** On 28th Jan 03:00 PM UTC, a secondary database migration unintentionally impacted indexes on a small number of core database tables. This led to degraded performance and temporary disruption of…1h 50mResolved
Jan 27, 2026Delayed file processing for models using async api in EU region**Incident Summary** On 27th Jan 17:00 UTC, we experienced elevated load on one of our core LLM processing engines due to a sudden increase in traffic volume. This primarily affected file processing workflows in the…4h 48mResolved
Jan 23, 2026Delayed File Processing in EU & EU-Open RegionThis incident has been resolved.1h 8mResolved
Jan 21, 2026Async file processing & Extract data section file visibility issue for users using app.nanonets.comThis incident has been resolved.35 minResolved
Dec 11, 2025Delay in file processing for Instant learning models in US regionOne 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…1h 55mResolved
Dec 8, 2025IN region OutageThis incident has been resolved.6 minResolved
Dec 3, 2025High Response Times for Instant learning models in US region**Overview** One of our secondary databases experienced connection issues following an unexpected spike in load. This sudden surge placed significant pressure on the database engine, causing request latency to…6h 1mResolved
Nov 8, 2025Failures in some instant learning modelsThis incident has been resolved.2h 13mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Nanonets incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Nanonets Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Nanonets acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Nanonets outage in this window ran 6h 1m, against a mean recovery of 1h 45m. If you depend on Nanonets in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.