October 9th, 2025
Monthly update

We’ve been busy shipping! Here’s a roundup of the new features and improvements we introduced over the last month.
We redesigned the check overview page to get you to what matters, faster. This update also introduces a new feature: Error Groups. While still in beta, they already make it much easier to see which errors occurred over time, how often, and in which locations.

Next to Error Groups, we added the following tweaks and updates:
Quicker and clearer filters for date, status and retries. Shave off three clicks to get to that annoying randomly failing check.
A distilled and easier-to-scan list of alerts and possible alert notifications.
An updated locations list to scan performance by location.
…plus dozens of small quality-of-life improvements that make this page smoother and snappier to use.
API checks now support TCP dumps and traceroute reports to help debug network-level issues. On checks that fail due to network errors, you’ll now see:
TCP Dumps: Capture raw packet data and download it as a .pcap file (e.g. for Wireshark). Great for starting an investigation in case of an error, such as incomplete TCP/TLS handshakes or delayed packets.
Traceroute reports: Trace the full path your request takes across the internet, including latency and packet loss at each hop. Pinpoint where packets drop or latency spikes.
We’d love your feedback: should these tools be available in other check types? Are there other debugging features you’d like us to add? Drop in a comment below or ping us in the community Slack 🙂
As part of Playwright Check Suites, we’ve launched a brand new pw-test command that supports both Checkly and Playwright flags. The npx checkly pw-test command runs Playwright tests with Checkly monitoring features, and reuses the Playwright CLI arguments. This command automatically records test sessions without requiring the --record flag.

npx checkly pw-test {checkly flags} -- {playwright flags}
npx checkly pw-test -- --project="firefox"
npx checkly pw-test --create-check -- --project="firefox"Test and create Playwright Check Suites from your local repository using pw-test. Learn more in our docs.
Check session trigger API: You can now programmatically run checks on demand, equivalent to clicking Schedule now in the UI.
POST /v1/check-sessions/trigger – Start an ad-hoc session for all activated checks matching the provided filters
GET /v1/check-sessions/{checkSessionId} – Retrieve the status and results of a running or completed session
GET /v1/check-sessions/{checkSessionId}/completion – Wait for a session to finish and return final results
Learn more in our API docs.
Single retries: A new SINGLE_RETRY strategy has been added for simple use cases such as Uptime Monitors. Learn more.
Network retries: After announcing network retries as a UI feature a few weeks back, they are now available in the CLI, Terraform, and Pulumi providers. Learn more.
New IP ranges: We’ve increased the list of IP addresses we use to run checks. The API endpoints are already updated with the new IPs, but if you manually manage an allowlist of Checkly IP ranges, make sure to include the new ones. We will begin migrating to the new IP addresses on October 15th.
→ us-east-1 (N. Virginia) new IP ranges:
173.208.3.141
209.50.250.200
209.50.250.199
2607:f5b7:1:135:5::/112
2607:f5b7:3:e:1::/112
2607:f5b7:3:e:2::/112
→ us-west-1 (California) new IP ranges:
23.19.66.246
23.19.45.129
23.19.66.245
2607:f5b4:1:12:d::/112
2607:f5b4:1:12:c::/112
2607:f5b4:1:1c:2::/112
→ eu-west-2 (London) new IP ranges:
23.19.59.129
23.106.239.101
23.106.239.174
2a0d:3003:b666:a00a:2::/112
2a0d:3003:b666:a006:12::/112
2a0d:3003:b666:a005:7::/112
Alert Escalation Reminders: Escalation reminders now respect the alert channel set at the check level. Previously, reminders could be sent via a group’s channel even when group-level overrides were disabled.
Got feedback? We’d love to hear from you!
You can share your feedback on our feedback hub or connect via the Checkly community Slack.
Happy monitoring!