HyperTrack Status Page

Jul 9, 2026 · resolved Jul 9

Summary On July 9, 2026, beginning at 10:00 UTC, devices attempting to establish or re-establish live connections to the HyperTrack platform experienced failures and delays. Devices that were already connected and tracking were largely unaffected, but newly starting devices experienced delayed or missing location data until service was fully restored at 19:25 UTC. What happened An unexpected surge in load caused a brief database disruption that disconnected a large number of devices at once. The resulting wave of simultaneous reconnection attempts exceeded our connection-handling capacity, which delayed new device connections for the remainder of the window. We deployed a fix at 19:14 UTC, and connectivity was fully restored by 19:25 UTC. Customer impact * Devices starting sessions during the window experienced delayed first location updates — in the worst cases by several hours — and a portion never delivered location data for orders created during the window. * Some orders completed during the window are missing arrival or on-site time data. * Location data for devices that remained connected was captured normally. What we are doing to prevent recurrence * Fixed the configuration that allowed the initial disruption. * Hardened connection handling — bounded requests, timeouts, and load-shedding — so mass reconnections can no longer create a sustained backlog. * Added safeguards that cap and pace surges in load so they can no longer cascade. * Added monitoring and alerting tuned to detect this failure pattern well before customer impact.

Mar 18, 2026 · resolved Mar 19

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.

Feb 3, 2026 · resolved Feb 3

A system update caused an elevated rate of API errors between 15:21 and 15:48 PST ( 23:21 to 23:48 UTC ). The update has been mitigated and the issue is fully resolved. All APIs are operating normally, and we are monitoring closely.

Sep 10, 2025 · resolved Sep 10

# **Summary** During the [incident](https://status.hypertrack.com/incidents/rslmyh4y3yy3) on Friday, September 5th, attackers gained access to our AWS account using a leaked key that had been inadvertently exposed in a JavaScript build. Within minutes, the attackers created concealed backdoor access resources. AWS and HyperTrack cleanup operations removed them, though a few resources initially went undetected. On September 10, attackers used the remaining backdoor resources to access the AWS account used by the HyperTrack platform and launched large-scale crypto-mining operations across multiple non-default AWS regions. The attack used compromised third-party AWS accounts unrelated to HyperTrack. This triggered AWS automated abuse detection, which temporarily restricted account access at 11:56 UTC. After investigation and remediation, AWS restored full account functionality by 18:10 UTC. Importantly, **no customer data or platform systems were accessed**. The incident was contained to crypto-mining activity. # **Timeline** **September 10, 2025 \(Wednesday\)** * **10:51 UTC** - Attacker accessed account resources from third-party compromised AWS accounts. * **10:53 UTC** - Crypto-mining workloads launched in new regions. * **10:57–11:00 UTC** - Multiple regions disabled again to hide activity. * **11:43–11:44 UTC** - Attacker switched between external AWS accounts from a new proxy IP address. * **11:56 UTC** - AWS issued compute resources abuse alert and started shutdown process. * **12:08 UTC** - Services were temporarily restricted. * **12:10 UTC** - HyperTrack engineers started responding to the incident and engaged with the AWS security team. * **15:07 UTC** - HyperTrack engineers removed all crypto mining resources, including all hidden non-default regions. * **18:10 UTC** - AWS security team confirmed restrictions lifted and account access restored. HyperTrack platform started receiving events and processing API requests. # **Next Steps** We recently detected and contained unauthorized access attempts related to leaked CI/CD credentials. Our investigation confirmed that no customer data was accessed and build pipelines for platform code repositories have been hardened. In response to the two incidents, we have taken immediate actions to strengthen our security posture in the coming weeks. Since the first incident, we implemented a code deployment freeze to address necessary steps to harden platform environments. These steps include the following: * **Improve Incident Containment & Remediation** * Multiple meetings with AWS security team members for account status and configuration review. * Continue to monitor CloudTrail for anomalies with alerting enabled. * **Continue Strengthening Identity & Access Measures** * Apply tighter Service Control Policies to limit usage to approved regions. * **Expanded Security Monitoring** * Review and update GuardDuty, Inspector, Security Hub, and IAM Access Analyzer configurations across all accounts and regions. * Configure additional alerting for high-severity findings and account activity to ensure immediate response. * **Implement Governance & Ongoing Improvements** * Aggregate all security findings centrally for faster triage and remediation. * Review Cognito and network configurations to ensure no hidden backdoors exist. * Evaluate AWS Control Tower and additional protections \(WAF, Firewall Manager\) for consistent org-wide governance. Our focus remains on delivering reliable, outstanding value to our customers. We are hardening our platform, strengthening comprehensive monitoring, and implementing industry best practices to prevent the recurrence of incidents. Thank you for your continued trust and patience.

Sep 6, 2025 · resolved Sep 6

### Summary On Friday, September 5 at 23:33 UTC \(16:33 PDT\), one of our AWS accounts was accessed using a set of unauthorized keys. The intrusion was quickly detected, and the compromised keys were revoked within 30 minutes. During this window, the attackers provisioned a large number of expensive compute resources for cryptocurrency mining, which in turn triggered AWS to lock the account. Importantly, there was no unauthorized access to platform resources or customer data. Our investigation determined the root cause: a misconfiguration in our JavaScript build process inadvertently exposed CI/CD environment variables. This led to the leak of a pipeline key, which the attackers exploited. We immediately cleaned up all malicious resources and engaged with AWS in real time to fully restore account functionality. Full traffic was restored at September 6, 7:07 UTC \(12:07 am PDT\) ### Timeline **Sep 06 2025 00:13 UTC:** The outage started at as AWS locked down account‌ **Sep 06 2025 00:18 UTC:** AWS alerts HyperTrack engineering **Sep 06 2025 04:00 UTC:** * HyperTrack engineering completed actions to remove over 3000 EC2 instances and associated resources * HyperTrack engineering reiterates to AWS urgency of reopening full access to the account and turning traffic back on **Sep 06 2025 05:33 UTC:** * AWS confirms case was escalated to Service team to reinstate account. * HyperTrack explains urgency: HyperTrack SDK used in millions of apps, supporting nurses and essential workers **Sep 06 2025 07:07 UTC:** * AWS turned account back on **Sep 06 2025 10:30 UTC:** * HyperTrack engineers continued working with the production resources and handling scale as mobile devices were coming back online after the outage. HyperTrack SDK caches tracking data and thus core pipeline inbound traffic scaled up by a couple orders of magnitude **Sep 06 2025 17:15 UTC:** * HyperTrack engineers continued investigation to understand the source of the leak. The source of the leak was identified to be a misconfiguration in our JavaScript build process.‌ ### Next steps Our team is conducting an in-depth analysis of the incident and is enhancing our security policies and procedures. These updates are designed to reinforce safeguards and ensure the continued safety of customer data.

Is HyperTrack down right now?

No — HyperTrack is up. All systems operational as of Aug 19, 9:39 PM UTC.

What is HyperTrack's current status?

HyperTrack: All Systems Operational. Alert24 checks HyperTrack's status page continuously and can notify you the moment it changes.

How do I get alerted when HyperTrack goes down?

Alert24 monitors HyperTrack and 3,700+ other cloud and SaaS providers. When an outage is detected it updates your status page automatically and pages your on-call team — no manual checks. Start free at alert24.net.