Locus Outage History

Locus is up right now

Pingoru has recorded 16 incidents for Locus: 0 in the last 12 months and 0 in the last 90 days.

Source: health.locus.sh

16incidents recorded
0last 12 months
0last 90 days
–typical duration

Incidents, newest first

Major January 14, 2025 Order Creation Issue | IN –

Started Jan 14, 2025, 03:10 PM UTC· resolved Jan 14, 2025, 03:10 PM UTC

  1. resolved Jan 14, 2025, 03:10 PM UTC

    On 2025-01-14T20:40:51.865+0530, order creation was impacted in SolutionIQ on the IN stack due to files exceeding the row limit of 11,000, causing orders not to be processed. The issue was resolved by processing failed orders in batches and adding alerts for future occurrences.

Read the full incident report →

Major December 19, 2024 TDMS callback issue | IN –

Started Dec 19, 2024, 06:33 AM UTC· resolved Dec 19, 2024, 06:33 AM UTC

  1. resolved Dec 19, 2024, 06:33 AM UTC

    On 19/Dec/24, there was an issue affecting TDMS on the IN stack where callbacks for shipments were not sent due to incorrect tour ID formats. The problem has been resolved by rolling back the problematic change and coordinating manual interventions for affected shipments.

Read the full incident report →

Major December 19, 2024 Tracking Tour ID Null Issue | IN 7h 38m

Started Dec 19, 2024, 02:37 AM UTC· resolved Dec 19, 2024, 10:15 AM UTC

  1. resolved Dec 19, 2024, 08:32 AM UTC

    On 2024-12-19T14:02:37.220+0530, TDMS experienced an issue where tracking tour IDs were set to null, impacting dispatch assignments due to a bad commit. This issue was resolved by 2024-12-24T10:10:15.808+0530.

Read the full incident report →

Major December 16, 2024 Auto Assign Error and Unmasking Contact Details | NV –

Started Dec 16, 2024, 10:14 AM UTC· resolved Dec 16, 2024, 10:14 AM UTC

  1. resolved Dec 16, 2024, 10:14 AM UTC

    On 2024-12-16T15:44:51.984+0530, the auto-assign error and unmasking of contact details impacted the TrackIQ component in the NV stack due to missing obfuscation logic in task-related APIs, leading to a compliance breach. The issue was resolved by 2024-12-17T14:34:18.303+0530 after implementing the necessary logic to maintain data obfuscation.

Read the full incident report →

Major December 12, 2024 Vehicle Pro-Assign Plans Dispatch Issue | IN –

Started Dec 12, 2024, 03:12 PM UTC· resolved Dec 12, 2024, 03:12 PM UTC

  1. resolved Dec 12, 2024, 03:12 PM UTC

    On 2024-12-12T20:42:58.164+0530, Tour Dispatch Management System (TDMS) was impacted on the IN stack due to a bug in vehicle pro-assign plans dispatch, where empty tours were being dispatched erroneously. The issue was resolved by correcting the handling of the type field to avoid dispatching empty tours.

Read the full incident report →

Minor November 27, 2024 Order Status Update Delays | NV –

Started Nov 27, 2024, 04:04 PM UTC· resolved Nov 27, 2024, 04:04 PM UTC

  1. resolved Nov 27, 2024, 04:04 PM UTC

    On November 27, 2024, there was an issue with the Tecor and Xpedigo carrier integrations where switching to an older implementation to reduce alerts caused new tracking information from them to be ignored silently, impacting order status updates. The incident was resolved by manually updating order statuses and ensuring that SMS notifications were appropriately managed.

Read the full incident report →

Major November 27, 2024 Invoice Posting Issue | IN –

Started Nov 27, 2024, 07:01 AM UTC· resolved Nov 27, 2024, 07:01 AM UTC

  1. resolved Nov 27, 2024, 07:01 AM UTC

    On 2024-11-27T12:31:42.503+0530, a 5XX error occurred during invoice posting due to internal API endpoints being used instead of public ones on the IN stack. This issue prevented clients from accessing necessary APIs. The root cause was related to API endpoints being restricted to internal use. The issue has been resolved and service is restored.

Read the full incident report →

Major November 22, 2024 Dispatch shipment error too many requests | IN –

Started Nov 22, 2024, 01:24 PM UTC· resolved Nov 22, 2024, 01:24 PM UTC

  1. resolved Nov 22, 2024, 01:24 PM UTC

    On 2024-11-22T18:54:12.618+0530, Tour Dispatch Management System (TDMS) on the IN stack experienced an issue with rate-limiting internal API calls, causing a 'Too many requests' error. Rate limits were adjusted to a higher threshold, mitigating client-facing impacts and restoring full operations.

Read the full incident report →

Minor November 14, 2024 Help & Support Ticket Creation Failure | NV, IN –

Started Nov 14, 2024, 06:56 AM UTC· resolved Nov 14, 2024, 06:56 AM UTC

  1. resolved Nov 14, 2024, 06:56 AM UTC

    On 2024-11-14T12:26:59.264+0530, the Help & Support ticket creation from the dashboard failed due to an outdated Freshdesk API key in the secrets manager, affecting NV and IN stacks. Resolution was achieved by updating the API key.

Read the full incident report →

Major November 11, 2024 OrderIQ Orders Status Issue | IN –

Started Nov 11, 2024, 07:43 AM UTC· resolved Nov 11, 2024, 07:43 AM UTC

  1. resolved Nov 11, 2024, 07:43 AM UTC

    On 11/Nov/24 at 1:13 PM IST, the OrderIQ component on the IN stack experienced an issue where orders were incorrectly moving to PARK status after a tour was discarded. This was due to a faulty process that caused tours not to generate automatically, impacting operations. The issue was mitigated by a temporary update to the TDMS API.

Read the full incident report →

Minor November 11, 2024 TDMS Tour Dispatch Issue | IN –

Started Nov 11, 2024, 07:31 AM UTC· resolved Nov 11, 2024, 07:31 AM UTC

  1. resolved Nov 11, 2024, 07:31 AM UTC

    On 2024-11-11T13:01:15.404+0530, the TDMS component in the IN stack allowed dispatch of tours with zero orders. This was due to a case where a tour was created from DIQ. The issue was identified and resolved with the latest release. The component is fully operational post-resolution.

Read the full incident report →