Is Nanonets down?

Last checked 7m ago
Current status
Nanonets is up

No incidents right now.

Official status page: https://status.nanonets.com · Polled every 5 minutes · 4 components tracked

Nanonets is operational right now. Last checked 7m ago; the most recent incident resolved 13d 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 4 Nanonets services and has captured 6 incidents in the last 90 days (97.64% uptime). Get email, Slack, Discord, or webhook alerts the moment Nanonets reports a new incident — free for 5 monitors, no credit card.

Users who monitor Nanonets also follow these AI services: Tungsten Automation EMEA Together AI Hugging Face Laserfiche Observe.AI Quest Retell AI Braintrust Cerebras Modal View all 6,000+ providers
Nanonets uptime 97.64% uptime · past 90 days
Mon Wed Fri
MarAprMayJun
Less More

Recent outages & incidents

Past 90 days
  1. Resolved
    Started May 31, 2026, 07:35 PM UTC · Resolved May 31, 2026, 07:30 PM UTC
    Timeline · 1 update
    • resolved · May 31, 2026, 07:35 PM UTC

      Between 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 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 are reviewing the incident and strengthening our deployment and validation processes to further reduce the likelihood of similar occurrences. We apologize for the inconvenience and appreciate your patience.

    Latest: Between 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 u…

  2. Resolved
    Started May 15, 2026, 07:14 AM UTC · Resolved May 14, 2026, 10:00 PM UTC
    Timeline · 1 update
    • resolved · May 15, 2026, 07:14 AM UTC

      From 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 worked with the provider to stabilize the service and performance has since recovered. As an additional preventive measure, we are introducing stronger fallback mechanisms to route requests to more accurate backup models during such events. We apologize for the inconvenience caused and appreciate your patience.

    Latest: From 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 wit…

  3. Resolved 46m
    Started Apr 28, 2026, 05:16 AM UTC · Resolved Apr 28, 2026, 06:02 AM UTC
    API
    Timeline · 3 updates
    • 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.

    • 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.

    • resolved · Apr 28, 2026, 06:02 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  4. Resolved
    Started Apr 10, 2026, 07:13 AM UTC · Resolved Apr 09, 2026, 06:30 AM UTC
    Timeline · 1 update
    • 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.

    Latest: 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 t…

  5. Resolved 21m
    Started Mar 30, 2026, 01:41 PM UTC · Resolved Mar 30, 2026, 02:03 PM UTC
    API
    Timeline · 3 updates
    • investigating · Mar 30, 2026, 01:41 PM UTC

      We are currently investigating this issue.

    • identified · Mar 30, 2026, 01:52 PM UTC

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

    • resolved · Mar 30, 2026, 02:03 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

Outage history

Past 90 days · 5 incidents View full outage history →