The following updates were released to the Kentik platform for Synthetics during July 2026.
Features
- Save returns you where you started: Saving in the synthetic test wizard now returns you to the page you came from — test results, a dashboard, or elsewhere — instead of always redirecting to the tests list.
- Synthetic credit calculator: A new tool estimates monthly synthetic test credit usage across 16 test types, with numeric quantity inputs, formatted totals, a calculation details view, and print-to-PDF export. Test intervals were aligned with the portal's supported options, including 2-minute and 10-minute intervals, transaction tests restricted to 5-90 minutes, and clarified one-minute minimum billing for private-agent ping, DNS, flow, and matrix tests.
Bug Fixes
- Bulk delete of synthetic tests: Deleting multiple tests at once now works, with clear success and failure counts.
- Disabled filter groups are ignored: Disabled synthetics filter groups were still being compiled into queries, silently returning zero rows.
- Path view on shared URLs: Trace and tracee views now load through shared links instead of returning a 403.
- Health timeline across mixed test frequencies: The synthetic tests page now aggregates results in a frequency-aware way, giving consistent data density across test periods. Default pagination changed from 100 to 25 results per page.
- Distinct colors for adjacent BGP bands: Reachability stacked bands now use an adjacency-aware, deterministic color scheme, kept consistent between the Reachability and Route Viewer views, so neighboring bands never share a color.
- Web test uploads in UA mode: Waterfall and screenshot data now upload correctly, after region codes for the current production clusters were mapped to the right portal domains.
- "New" label expiry consistent across time zones: The New badge on the Synthetics Tests menu link previously expired at different times depending on whether a user was in UTC or local time.
- Removing a test no longer leaves orphaned records: Deleted tests previously left records behind that could raise false alerts after a restart.