Nanonets Status Page

May 14, 2026 · resolved May 14

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.

Apr 28, 2026 · resolved Apr 28

This incident has been resolved.

Apr 9, 2026 · resolved Apr 9

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.

Mar 30, 2026 · resolved Mar 30

This incident has been resolved.

Mar 10, 2026 · resolved Mar 10

On 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 vector database experienced unusually high load due to the query planner selecting a suboptimal execution path for certain queries. This led to elevated database response times and eventually triggered a database restart. As a result, overall system throughput temporarily decreased. Customers may have observed the following effects during this window: * Asynchronous uploads for ILM models experiencing delayed file processing. * Synchronous uploads for ILM models encountering intermittent failures. Only **Instant Learning Models on** [**app.nanonets.com**](http://app.nanonets.com) were affected. Other services and model types remained fully operational. **Resolution:** Our engineering team identified the root cause related to query planning behaviour in the vector database and implemented targeted customizations to ensure the optimal execution path is used. This stabilized database performance and restored normal processing capacity. **Next Steps:** System is stable now and we are actively working on additional database optimizations and long-term improvements to further strengthen system stability and prevent similar issues from recurring. These enhancements will be rolled out in the coming days. We sincerely apologize for the inconvenience caused and appreciate your patience while we worked to resolve the issue. Please feel free to reach out to our support team incase if you have any questions.