Is Nanonets down?
Last checked 6m agoNo incidents right now.
Nanonets is operational right now. Last checked 6m ago; the most recent incident resolved 7d ago.
Real-time Nanonets status, recent outages, and incident history — pulled directly from Nanonets's official status page at https://status.nanonets.com every 5 minutes. Pingoru tracks 5 Nanonets services and has captured 7 incidents in the last 90 days (98.00% uptime). Get email, Slack, Discord, or webhook alerts the moment Nanonets reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- API
Timeline · 5 updates
- investigating · Jul 23, 2026, 03:55 PM UTC
We are currently investigating this issue.
- identified · Jul 23, 2026, 04:19 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring · Jul 23, 2026, 04:39 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved · Jul 23, 2026, 04:55 PM UTC
This incident has been resolved.
- postmortem · Jul 23, 2026, 05:37 PM UTC
**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
Latest: **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, cus…
-
-
Timeline · 1 update
- 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.
Latest: 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.
-
-
Timeline · 1 update
- 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.
Latest: 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.
-
-
Timeline · 1 update
- 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.
Latest: 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 a…
-
-
Timeline · 1 update
- 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.
Latest: Frontend resources taking time to load causing UI to freeze in loading state. Appropriate CDN fixes were implemented to fix the issue.
-
See the full Nanonets outage history
2 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse Nanonets outage history →Or sign up free to get alerts when Nanonets breaks · 10 free monitors · No credit card
- Started Jul 23, 2026, 03:55 PM UTC · Resolved Jul 23, 2026, 04:55 PM UTC · 59m
- Processing delay on Agent Tasks ResolvedStarted Jun 30, 2026, 12:07 PM UTC · Resolved Jun 25, 2026, 10:30 PM UTC · —
- Processing Delay on Agents ResolvedStarted Jun 30, 2026, 12:03 PM UTC · Resolved Jun 24, 2026, 01:30 PM UTC · —
- Started Jun 29, 2026, 04:30 AM UTC · Resolved Jun 29, 2026, 04:30 AM UTC · —
- Agents UI freezing issue ResolvedStarted Jun 26, 2026, 07:06 AM UTC · Resolved Jun 25, 2026, 01:30 PM UTC · —
- Started May 31, 2026, 07:35 PM UTC · Resolved May 31, 2026, 07:30 PM UTC · —
- Started May 15, 2026, 07:14 AM UTC · Resolved May 14, 2026, 10:00 PM UTC · —