Nanonets logo

Is Nanonets Down?

SaaSLive status, outages, and incident history

No. Nanonets is up right now.

Every monitored Nanonets system is operational as of September 25, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 18m agoLive · 60s while moving

Know the moment Nanonets breaks

Nanonets is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

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

Official Nanonets status page
How we know: the official Nanonets status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

Nanonets Component Status

The main Nanonets systems on this page. All 5 are operational right now.

5operational
Agents platform
Operational
API
Operational
imgix Content Delivery Network
Operational

2 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Web App, Website.

See all of them free

Component statuses may change independently during partial outages.

Recent Nanonets Outages & Incidents

Incident history from the official Nanonets status page, including resolution updates.

Delayed file processing for models in app.nanonets.comResolved Sep 21, 2026 · 1h 34mResolved

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 --- [2026-09-21T16:55:40.669Z] (resolved) This incident has been resolved. --- [2026-09-21T16:49:50.602Z] (monitoring) A fix has been implemented and we are monitoring the results. --- [2026-09-21T15:52:57.927Z] (identified) The issue has been identified and a fix is being implemented. --- [2026-09-21T15:21:11.469Z] (investigating) We are currently investigating this issue.

Delayed file processing for ILM models in app.nanonets.comResolved Jul 23, 2026 · 59 minResolved

**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 --- [2026-07-23T16:55:01.307Z] (resolved) This incident has been resolved. --- [2026-07-23T16:39:40.657Z] (monitoring) A fix has been implemented and we are monitoring the results. --- [2026-07-23T16:19:52.451Z] (identified) The issue has been identified and a fix is being implemented. --- [2026-07-23T15:55:11.439Z] (investigating) We are currently investigating this issue.

Processing delay on Agent TasksResolved Jun 30, 2026 · -6577 minResolved

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.

Nanonets Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Nanonets incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history49 days observed
Aug 8100.00% average · 1 day with incidentsSep 25

Live Nanonets Outage Reports

Problems reported by engineers using Nanonets. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Nanonets problems reported yet.

Something wrong with Nanonets on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Nanonets

Nanonets publishes a public status page at status.nanonets.com covering 5 components, including API, Web App and Website. PulsAPI tracks Nanonets outages, degraded performance and incident history in real time, alongside the rest of your SaaS stack.

Over the past 30 days, PulsAPI has measured Nanonets uptime at 100.00%. Response times, incident history, and SLA tracking for Nanonets are available on the PulsAPI dashboard.

Nanonets Status FAQ

Is Nanonets down right now?

The verdict at the top of this page comes from the latest poll of the official Nanonets status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

What should I do if Nanonets is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Nanonets recovers.

How do I check Nanonets uptime history?

PulsAPI tracks Nanonets uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Nanonets changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Nanonets outages?

PulsAPI reads the official Nanonets status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual Nanonets components?

Yes. PulsAPI monitors 5 individual Nanonets components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Nanonets goes down?

Yes. Create a free account and subscribe to Nanonets: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Nanonets to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Nanonets problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Nanonets?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Nanonets plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Nanonets with the rest of your stack

2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services