TrackTik Outage History

TrackTik is up right now

TrackTik had 9 outages in the last 2 years totaling 4h 51m of downtime — averaging 0.4 incidents per month.

There were 9 TrackTik outages since October 20, 2025 totaling 4h 51m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.tracktik.com

Major August 20, 2026

Unable to View or Create Geofences

Detected by Pingoru
Aug 20, 2026, 01:02 PM UTC
Resolved
Aug 20, 2026, 03:23 PM UTC
Duration
2h 21m
Timeline · 5 updates
  1. investigating Aug 20, 2026, 01:02 PM UTC

    We are currently investigating an issue where some users may be unable to view existing geofences or create new geofences within the platform. Our team is actively working to identify the root cause and restore full functionality as quickly as possible. We will provide additional updates as more information becomes available. We apologize for the inconvenience and appreciate your patience.

  2. investigating Aug 20, 2026, 01:18 PM UTC

    We have identified the cause of the issue affecting the ability to view and create geofences. Our team is actively working on a fix. Users may continue to experience issues with geofence visibility and creation until the update has been fully deployed. We will provide another update once the solution is in place and will continue to monitor the situation until it is fully resolved.

  3. identified Aug 20, 2026, 01:18 PM UTC

    The issue has been identified and a fix is being implemented.

  4. monitoring Aug 20, 2026, 02:44 PM UTC

    The fix for the geofence issue has been deployed, and we are currently monitoring the system to confirm that the issue affecting the ability to view and create geofences has been fully resolved. We appreciate your patience and apologize again for the disruption. We will provide another update once monitoring is complete.

  5. resolved Aug 20, 2026, 03:23 PM UTC

    The hotfix has been successfully deployed, and the issue affecting the ability to view and create geofences is now resolved. We apologize for any disruption and appreciate your patience while we worked to restore full functionality.

Read the full incident report →

Minor July 20, 2026

TrackTik Canada - Service Disruption

Detected by Pingoru
Jul 20, 2026, 05:28 PM UTC
Resolved
Jul 20, 2026, 07:58 PM UTC
Duration
2h 29m
Affected: TrackTik Canada
Timeline · 3 updates
  1. identified Jul 20, 2026, 05:28 PM UTC

    We're currently investigating an issue affecting Action Queue processing in Canada. You may experience issues with exports not running, payroll processing, invoice generation, notification delays, or any other Action Queue-dependent functionality.

  2. monitoring Jul 20, 2026, 06:01 PM UTC

    The issue impacting the TrackTik Canada Action Queue has been mitigated, and services are currently stable. We are continuing to monitor services and will address any issues quickly should they occur. Thank you for your patience.

  3. resolved Jul 20, 2026, 07:58 PM UTC

    The issue affecting the TrackTik Canada Action Queue has been resolved. All services are operating normally at this time. Thank you for your patience, and we apologize for any inconvenience caused.

Read the full incident report →

Minor November 18, 2025

TrackTik Unaffected by Cloudflare Issues

Detected by Pingoru
Nov 18, 2025, 03:10 PM UTC
Resolved
Nov 18, 2025, 03:10 PM UTC
Duration
Timeline · 1 update
  1. monitoring Nov 18, 2025, 03:10 PM UTC

    Nov 18, 10:10 EST Resolved - Cloudflare has fixed earlier widespread issues. We maintained full stability throughout the incident, and all TrackTik and Trackforce services are confirmed to be operating normally. Nov 18, 09:25 EST Monitoring - Due to Cloudflare outages affecting numerous sites today, we want to let our clients know TrackTik, GuardTek and Silvertrac remain operational and unaffected. The Trackforce corporate marketing website is affected and we are monitoring the situation closely for updates.

Read the full incident report →

Minor October 27, 2025

US West Service Disruption

Detected by Pingoru
Oct 27, 2025, 12:30 PM UTC
Resolved
Oct 27, 2025, 12:30 PM UTC
Duration
Timeline · 1 update
  1. monitoring Oct 27, 2025, 12:30 PM UTC

    Oct 27, 08:30 EDT Resolved - The issue impacting the US West instance has been resolved. Some users experienced latency and timeouts due to elevated traffic conditions on Sat. Oct 25 and Sun. Oct. 26., 2025. Mitigation steps were applied, and service performance has returned to normal with no further delays observed. Thank you for your patience while we worked to restore stability. Oct 26, 21:42 EDT Monitoring - We have identified the source of the issue impacting the US West instance and have implemented mitigation measures. Our team is now monitoring the service to ensure stability. Oct 26, 20:44 EDT Investigating - We are currently investigating intermittent connectivity and login issues affecting the US West instance. Some users may experience problems signing in, submitting reports, or conducting tours in the Mobile Guard App and web portal. Our engineering team is actively working to restore full service.

Read the full incident report →

Minor October 21, 2025

AWS

Detected by Pingoru
Oct 21, 2025, 02:49 AM UTC
Resolved
Oct 21, 2025, 02:49 AM UTC
Duration
Timeline · 1 update
  1. monitoring Oct 21, 2025, 02:49 AM UTC

    Oct 20, 22:49 EDT Resolved - AWS has resolved the outage and reports all services are back to normal. Any temporary effects on TrackTik services should now be resolved Oct 20, 18:12 EDT Update - TrackTik customers may experience limited effects from the ongoing AWS outage. You may also still have delays when trying to reach our team via phone or chat, however, our email and web forms remain unaffected. Our teams are actively monitoring AWS updates and resolution timelines. Oct 20, 14:04 EDT Monitoring - Our customers may experience limited effects from the ongoing AWS outage. You may also encounter delays when trying to reach our team via call or chat. Our teams are actively monitoring AWS updates and resolution timelines.

Read the full incident report →