We are observing intermittent timeouts when calling the /v1/orders endpoint in production. The issue started around 04 Feb 2026, and affects approximately 3–5% of total API calls.
Steps to Reproduce
Trigger the GET /v1/orders?status=pending API.
Monitor API latency via Application Insights.
Occasionally, the request exceeds 30 seconds and fails with a timeout.
Expected Behavior
API should return results consistently within < 5 seconds.
No intermittent timeout failures should occur.
Actual Behavior
Response time spikes to > 30 seconds.
API intermittently returns timeout errors.
Logs show increased DB query latency during the same timeframe.
Logs / Error Messages
2026-02-04T11:23:14Z ERROR TimeoutError: Request exceeded 30000ms
Query execution took 28954ms for query: SELECT * FROM Orders WHERE status='pending'
Impact
Affects customer experience for live orders.
Causes retries in backend service → higher API usage → cost impact.
Environment
Environment: Production
API Version: v1
Database: Azure SQL
Region: Central India
Possible Root Causes (Hypothesis)
Increased DB load during peak hours.
Slow query execution due to missing index.
Connection pool saturation on backend service.
We are observing intermittent timeouts when calling the /v1/orders endpoint in production. The issue started around 04 Feb 2026, and affects approximately 3–5% of total API calls.
Steps to Reproduce
Trigger the GET /v1/orders?status=pending API.
Monitor API latency via Application Insights.
Occasionally, the request exceeds 30 seconds and fails with a timeout.
Expected Behavior
API should return results consistently within < 5 seconds.
No intermittent timeout failures should occur.
Actual Behavior
Response time spikes to > 30 seconds.
API intermittently returns timeout errors.
Logs show increased DB query latency during the same timeframe.
Logs / Error Messages
2026-02-04T11:23:14Z ERROR TimeoutError: Request exceeded 30000ms
Query execution took 28954ms for query: SELECT * FROM Orders WHERE status='pending'
Impact
Affects customer experience for live orders.
Causes retries in backend service → higher API usage → cost impact.
Environment
Environment: Production
API Version: v1
Database: Azure SQL
Region: Central India
Possible Root Causes (Hypothesis)
Increased DB load during peak hours.
Slow query execution due to missing index.
Connection pool saturation on backend service.