We’re constantly working to optimize the MyGeotab platform to ensure it remains fast, reliable, and focused on the data that provides the most value to your fleet. As part of this effort, we are updating how the platform handles low-level system information, known as debug data.

The DebugData API was originally designed as an internal tool for Geotab engineers to diagnose device firmware behavior. Over time, we’ve found that approximately 70% of these records are internal diagnostics with no meaningful use case for external integrators. By reducing the volume of this internal data, we expect to see improved database performance across the platform.

New 14-day retention window Starting in Q2 2026, MyGeotab will transition to a rolling 14-day retention window for all debug data. This change applies to both the MyGeotab UI and the API. While the report in the UI and the API endpoints themselves will remain fully functional, they will now be scoped to provide the most recent two weeks of information.

Managing historical data and offline devices For the vast majority of users, this change will have no operational impact, as most troubleshooting and data pulls occur in near-real-time. However, it is important to note two specific scenarios:

• API Integrations: If you have a custom integration that requires debug data older than 14 days, you will need to begin storing that data locally as it is collected.
• Offline Devices: If a device is offline for more than two weeks, any debug data backfilled from that offline period will fall outside the retention window and will not be stored in MyGeotab.

These updates are scheduled for a gradual two-week rollout during Q2 2026. If you have a critical use case not served by existing APIs, please reach out to your Partner or Geotab representative to discuss supported alternatives.