HyperTrack Outage History

HyperTrack is up right now

HyperTrack had 9 outages in the last 2 years totaling 12h 57m of downtime — averaging 0.4 incidents per month.

There were 9 HyperTrack outages since August 6, 2024 totaling 12h 57m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.hypertrack.com

Notice March 19, 2026

Elevated API Errors

Detected by Pingoru
Mar 19, 2026, 04:30 AM UTC
Resolved
Mar 19, 2026, 04:30 AM UTC
Duration
Timeline · 1 update
  1. resolved Mar 18, 2026, 10:07 PM UTC

    A platform deployment caused an elevated rate of API errors between 21:08 UTC to 21:47 UTC. New systems were provisioned to mitigate the issues. API degradation is fully resolved. All APIs are operating normally, and we are monitoring closely.

Read the full incident report →

Critical September 10, 2025

System outage

Detected by Pingoru
Sep 10, 2025, 12:08 PM UTC
Resolved
Sep 10, 2025, 06:15 PM UTC
Duration
6h 6m
Affected: Cloud serviceOrdersNearbyGeofencesGeotagsDashboardOps DashboardOrder tracking viewsWebhooks
Timeline · 5 updates

Read the full incident report →

Major September 6, 2025

Platform outage

Detected by Pingoru
Sep 06, 2025, 12:48 AM UTC
Resolved
Sep 06, 2025, 07:19 AM UTC
Duration
6h 30m
Affected: Cloud serviceOrdersNearbyGeofencesGeotagsDashboardOps DashboardOrder tracking viewsWebhooks
Timeline · 4 updates

Read the full incident report →

Minor April 28, 2025

Platform degradation and elevated errors

Detected by Pingoru
Apr 28, 2025, 04:00 AM UTC
Resolved
Apr 28, 2025, 03:30 AM UTC
Duration
Timeline · 1 update
  1. resolved Apr 28, 2025, 04:00 AM UTC

    Due to underlying database conditions, we are experiencing degraded platform performance and elevated errors. Team is currently investigating and troubleshooting.

Read the full incident report →

Notice April 10, 2025

Performance degradation

Detected by Pingoru
Apr 10, 2025, 02:31 AM UTC
Resolved
Apr 09, 2025, 07:30 AM UTC
Duration
Timeline · 1 update
  1. resolved Apr 10, 2025, 02:31 AM UTC

    We experienced degraded performance in one of our databases. This has caused elevated response times and timeouts in parts of our service from 12:22 am to 12:50 am UTC.

Read the full incident report →

Notice April 2, 2025

ETA Processing Issue

Detected by Pingoru
Apr 02, 2025, 06:27 PM UTC
Resolved
Apr 01, 2025, 08:00 PM UTC
Duration
Timeline · 1 update
  1. resolved Apr 02, 2025, 06:27 PM UTC

    Less than 5 % of ETA calculations were behind for up to one hour between April 1, 20:00 UTC and to April 2, 00:00 UTC due to a processing issue.

Read the full incident report →

Major September 10, 2024

Orders API Incident – Small Segment of Customers Impacted

Detected by Pingoru
Sep 10, 2024, 06:30 AM UTC
Resolved
Sep 10, 2024, 06:30 AM UTC
Duration
Timeline · 1 update
  1. resolved Sep 11, 2024, 06:07 AM UTC

    We identified a bug in the Orders API implementation that caused an issue with workers' devices switching logic. As a result, a segment of customers using Orders API is affected. Starting at Sep 10, 2024, 6:16:22 AM UTC, The bug impacted certain tracked orders where device tracking was inadvertently stopped before order was completed. The issue has been resolved at Sep 10, 2024, 4:38:07 PM UTC, and our team is closely monitoring to ensure full system stability.

Read the full incident report →

Notice August 6, 2024

Webhook Degradation

Detected by Pingoru
Aug 06, 2024, 10:34 PM UTC
Resolved
Aug 06, 2024, 05:30 PM UTC
Duration
Timeline · 1 update
  1. resolved Aug 06, 2024, 10:34 PM UTC

    A significant increase in traffic caused delays in webhook delivery of up to 30 minutes. This issue started at 10:30 UTC and was resolved by 19:30 UTC. We’ve upgraded our infrastructure to handle similar traffic spikes in the future, ensuring more stable and timely webhook processing.

Read the full incident report →