TrackTik Outage History

Started Sep 30, 2026, 08:06 PM UTC· resolved Sep 30, 2026, 09:52 PM UTC

1. investigating Sep 30, 2026, 08:06 PM UTC

   We are investigating reports of employees being unable to clock in via the Kiosk app. Updates will be provided as more information becomes available. We apologize for any disruption caused.

2. resolved Sep 30, 2026, 09:52 PM UTC

   The issue affecting employees attempting to clock in via the Kiosk app has been identified and is now resolved. We apologize for any disruption caused and thank you for your patience.

Read the full incident report →

Started Sep 18, 2026, 05:57 PM UTC· resolved Sep 23, 2026, 03:29 PM UTC

1. investigating Sep 18, 2026, 05:57 PM UTC

   We are aware of an issue impacting performance for some customers and are actively investigating. Our team is working to identify the root cause and restore normal performance as quickly as possible. We will provide further updates as more information becomes available.

2. monitoring Sep 18, 2026, 06:18 PM UTC

   Performance has returned to normal levels and service should now be operating as expected. We are continuing to monitor the environment closely to ensure stability, but at this time service levels have returned to normal.

3. resolved Sep 23, 2026, 03:29 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 09, 2026, 05:07 PM UTC· resolved Sep 09, 2026, 09:15 PM UTC

1. investigating Sep 09, 2026, 05:07 PM UTC

   We are aware of reports that some clients are currently unable to edit reports within the platform. Our team is actively investigating the issue and working to identify the root cause. We will provide further updates as more information becomes available. We apologize for the inconvenience and appreciate your patience while we work toward a resolution.

2. identified Sep 09, 2026, 05:12 PM UTC

   We have identified the root cause of the issue affecting report editing for some clients. At this time, users may still experience issues when attempting to edit reports while we implement the fix. Our engineering team has developed a hotfix and is currently validating and preparing it for deployment. We are actively working to restore full functionality as quickly as possible and will provide another update once the hotfix has been deployed. We apologize for the disruption and appreciate your patience.

3. monitoring Sep 09, 2026, 06:34 PM UTC

   The hotfix has been deployed and we are currently monitoring the platform to ensure the issue is fully resolved. Users should now be able to edit reports normally. Our team will continue to closely monitor system performance and validate that report editing remains stable across affected environments. If you continue to experience issues, please contact Support and provide details of the report and any error messages encountered. We appreciate your patience while we worked to resolve this issue.

4. resolved Sep 09, 2026, 09:15 PM UTC

   The issue affecting report editing has been resolved. Our monitoring indicates that report editing functionality has returned to normal operation, and no further impact is expected at this time. If you encounter any additional issues with reports, please contact Support with details of the affected user(s), example report(s), and any error messages or unexpected behavior observed so we can investigate promptly. We apologize for the disruption and thank you for your patience.

Read the full incident report →

Started Aug 20, 2026, 01:02 PM UTC· resolved Aug 20, 2026, 03:23 PM UTC

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 →

Started Jul 20, 2026, 05:28 PM UTC· resolved Jul 20, 2026, 07:58 PM UTC

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 →

Started Mar 05, 2026, 08:54 PM UTC· resolved Mar 05, 2026, 08:54 PM UTC

1. monitoring Mar 05, 2026, 08:54 PM UTC

   Mar 5, 15:54 EST Resolved - The issue affecting multi-page PDF previews in the Post Order section is now resolved. Google has fixed the underlying API disruption, and the document viewer is back to normal operation. Thank you for your patience. Mar 5, 12:21 EST Identified - We have identified the root cause of the PDF preview issue. The document viewer relies on a third-party API provided by Google, which is currently experiencing a service disruption. As this is an external issue, we do not have an immediate ETA for a resolution, but we are monitoring their progress closely. Please rest assured that your data is safe and all document pages are stored securely in our system. Mar 5, 11:30 EST Update - At this time, we are still investigating the issue affecting the Post Order section of the application where only the first page of multi-page PDFs is being displayed in the viewer. Where available, users can download the document directly to their device to view all pages. We are aware that some uses (such as those in the Guard portal) may not have download permissions, and we are working to restore the preview functionality as our highest priority. No data loss has occurred; all uploaded documents remain complete in our system. Thank you for your patience as we work towards a fix. Mar 5, 10:46 EST Investigating - We are currently investigating an issue affecting the Post Order section of the application. Some clients have reported that when viewing multi-page PDF documents via the in-app document viewer, only the first page is being displayed. Our team has confirmed that there is no data loss; all uploaded documents remain complete in our system. We are actively investigating the underlying cause, and we will share updates as more information is available.

Read the full incident report →

Started Feb 19, 2026, 08:25 PM UTC· resolved Feb 19, 2026, 08:25 PM UTC

1. monitoring Feb 19, 2026, 08:25 PM UTC

   Feb 19, 15:25 EST Resolved - The fix for the Schedule Preparation tool has been successfully deployed across all regions. Users are now able to assign employees to unpublished shifts as expected. We have verified that the issue is resolved and will continue to monitor performance to ensure ongoing stability. Thank you for your patience while we worked to resolve this. Feb 19, 15:05 EST Monitoring - A fix has been developed and is currently being deployed across all regions. We are monitoring the platform to ensure that the Schedule Preparation tool is functioning correctly and that employee assignments are saving as expected. Users should see the issue resolved as the update reaches their specific region. Feb 19, 14:44 EST Identified - We have identified the root cause affecting the Schedule Preparation tool. A fix has been developed and is currently being prepared for deployment. Feb 19, 14:37 EST Investigating - We are currently investigating reports of an issue affecting the Schedule Preparation tool. Users may experience errors or find themselves unable to save employee assignments to unpublished shifts. This may prevent schedulers from finalizing staff assignments for future periods. Our engineering team is currently investigating the root cause and working toward a resolution. We will provide further information as soon as more details or a timeline for a fix become available.

Read the full incident report →

Started Jan 29, 2026, 06:39 PM UTC· resolved Jan 29, 2026, 06:39 PM UTC

1. monitoring Jan 29, 2026, 06:39 PM UTC

   Jan 29, 13:39 EST Resolved - This incident has been resolved, thank you for your patience. Jan 29, 08:08 EST Update - Services are operational, however, we are currently processing a backlog of pending email and SMS reports at this time. Our U.S. clients may continue to experience delivery delays - we are monitoring the queue to ensure full stabilization. If you continue to experience issues once the backlog is cleared, please contact our Support Team. Jan 28, 16:12 EST Monitoring - Services are returning to normal, and a backlog of pending reports is currently being processed - some clients may continue to experience delays in receiving email and SMS notifications. We are continuing to monitor the system closely as it catches up and will provide further updates. Jan 28, 09:56 EST Identified - We have identified the cause and are currently monitoring the service as it recovers. Some US-based clients may continue to experience delays in receiving email and SMS reports while the system processes the backlog. We will provide updates as they become available and once service is fully stabilized. Jan 28, 08:59 EST Investigating - We are aware of an issue preventing reports from being sent via email and SMS for clients on Infrastructure 4. Our team is treating this with the highest priority and is actively working on a resolution.

Read the full incident report →

Started Jan 12, 2026, 07:10 PM UTC· resolved Jan 12, 2026, 07:10 PM UTC

1. monitoring Jan 12, 2026, 07:10 PM UTC

   Jan 12, 14:10 EST Resolved - The incident affecting Infra3 and European infrastructure has been resolved. All services are operating normally at this time. Thank you for your patience, and we apologize for any inconvenience caused. Jan 12, 12:33 EST Monitoring - The issue affecting TrackTik Infra3 and European infrastructure has been mitigated, and services are currently stable. We are continuing to monitor all infrastructure and will address any issues quickly should they occur, while completing follow-up updates for clients. Thank you for your patience. Jan 12, 12:12 EST Identified - We have identified an issue affecting TrackTik on Infra3 and European infrastructure and are actively working to resolve it. Updates will be shared as they become available. Thank you for your continued patience as we work to fix this for affected clients. Jan 12, 12:05 EST Investigating - We are aware of an ongoing issue with TrackTik and investigating with the highest priority, we will post updates as soon as possible. Thank you for your patience.

Read the full incident report →

Started Nov 18, 2025, 03:10 PM UTC· resolved Nov 18, 2025, 03:10 PM UTC

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 →

Started Oct 27, 2025, 12:30 PM UTC· resolved Oct 27, 2025, 12:30 PM UTC

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 →

Started Oct 21, 2025, 02:49 AM UTC· resolved Oct 21, 2025, 02:49 AM UTC

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 →

Started Jan 31, 2025, 09:31 PM UTC· resolved Jan 31, 2025, 10:19 PM UTC

1. identified Jan 31, 2025, 10:01 PM UTC

   We detected a service-impacting incident at 4:30 PM ET, in the US-West region (California) which our team is actively addressing. The impact is limited to customers in the West coast region of the continental US. The service is in the process of recovering and is expected to resume shortly.

2. monitoring Jan 31, 2025, 10:14 PM UTC

   The platform has been restored, and we are actively monitoring the recovery process.

3. resolved Jan 31, 2025, 10:19 PM UTC

   This incident is resolved.

Read the full incident report →

Started Dec 16, 2024, 08:22 PM UTC· resolved Dec 16, 2024, 08:29 PM UTC

1. investigating Dec 16, 2024, 08:22 PM UTC

   Customers on US West infrastructure may experience problems loading their portals. We are currently investigating the issue.

2. investigating Dec 16, 2024, 08:24 PM UTC

   We are continuing to investigate this issue.

3. resolved Dec 16, 2024, 08:29 PM UTC

   Our services are now operating normally.

Read the full incident report →

Started Dec 09, 2024, 10:08 PM UTC· resolved Dec 09, 2024, 10:26 PM UTC

1. investigating Dec 09, 2024, 10:08 PM UTC

   We are currently investigating reports of 502 Bad Gateway errors for clients on Infr3.

2. investigating Dec 09, 2024, 10:20 PM UTC

   We are continuing to investigate this issue.

3. resolved Dec 09, 2024, 10:26 PM UTC

   502 Bad Gateway errors have been resolved.

Read the full incident report →

Started Nov 21, 2024, 12:43 PM UTC· resolved Nov 21, 2024, 01:52 PM UTC

1. identified Nov 21, 2024, 12:43 PM UTC

   We have identified a significant issue affecting the DNS service for the EU domain. Our team has taken corrective actions, and the service is now in the process of being restored. The restoration will occur gradually across different regions. This means some users may experience normal service sooner than others, depending on how quickly the changes propagate through the global DNS network.

2. monitoring Nov 21, 2024, 01:27 PM UTC

   DNS propagation is underway, and portals should now be accessible in most, if not all, regions. This delay occurs due to the DNS propagation process, during which DNS information is updated across the internet. The duration of this delay may vary depending on your internet provider. You can try clearing your browser cache or restarting your phone to prompt a refresh.

3. resolved Nov 21, 2024, 01:52 PM UTC

   The DNS has been successfully propagated across all regions, and the service is functioning normally. If you are still having trouble accessing your portal, consider clearing your browser cache or flushing your computer's DNS. Additionally, restarting your phone may help trigger a refresh.

Read the full incident report →

Started Nov 15, 2024, 04:00 AM UTC· resolved Nov 15, 2024, 04:00 AM UTC

1. resolved Nov 15, 2024, 04:29 AM UTC

   A partial disruption occurred for a few minutes for customers on our Asia infrastructure.

Read the full incident report →