Nanonets Status Page

Oct 1, 2026 · resolved Oct 2

This incident has been resolved.

Sep 21, 2026 · resolved Sep 21

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

Jul 23, 2026 · resolved Jul 23

**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 document-level instant learning models experienced elevated processing times on [app.nanonets.com](http://app.nanonets.com). The issue was isolated to document-level model processing and did not affect other regions or services. **Impact** Users submitting documents for processing via document-level instant learning models in the US region saw delayed responses and higher-than-normal latency during the incident window. No documents or data were lost, and all queued requests were processed once the issue was resolved. **Root Cause** An internal message-processing component responsible for routing document jobs to our instant learning models encountered a permissions fault that prevented it from passing messages through as expected. This caused jobs to back up in the processing queue, which in turn drove up response times for affected requests. **Resolution** Our engineering team identified the faulty component, corrected the permissions issue, and restored normal message flow. The backlog of queued documents was drained and fully processed shortly after the fix was applied. Service returned to normal operating latency by 16:40 UTC. We sincerely apologize for the inconvenience this caused and we are implementing stricter safeguards to prevent a recurrence

Jun 28, 2026 · resolved Jun 29

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.

Jun 25, 2026 · resolved Jun 25

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.

Is Nanonets down right now?

No — Nanonets is up. All systems operational as of Oct 12, 4:52 AM UTC.

What is Nanonets's current status?

Nanonets: All Systems Operational. Alert24 checks Nanonets's status page continuously and can notify you the moment it changes.

How do I get alerted when Nanonets goes down?

Alert24 monitors Nanonets and 3,700+ other cloud and SaaS providers. When an outage is detected it updates your status page automatically and pages your on-call team — no manual checks. Start free at alert24.net.