Live chat
Use the chat bubble in the bottom-right corner of this site or inside the Checkly app. Enter and verify your email to start a conversation with the support team.
Best for: Questions while you are in the product
Support
Stuck on a check, have a billing question, or found a bug? Pick the channel that fits and we will take it from there.
Use the chat bubble in the bottom-right corner of this site or inside the Checkly app. Enter and verify your email to start a conversation with the support team.
Best for: Questions while you are in the product
Reach the Checkly support team directly. This is the right place for anything tied to your account.
Best for: Account, billing, and technical questions
support@checklyhq.comGuides, concepts, and the full API and CLI reference. Most questions are answered here first.
Best for: Setup, configuration, and how-tos
Read the docsAsk questions, share what you are building, and learn from other Checkly users and the team.
Best for: Quick questions and best practices
Join the Slack communityLive platform status and incident history. Subscribe to get notified about incidents and maintenance.
Best for: Checking whether Checkly itself is affected
status.checklyhq.comPropose an idea, add context, and vote on requests from other Checkly users. Product reads every entry.
Best for: Ideas and product feedback
feedback.checklyhq.comThe more context a support request carries, the fewer round trips it takes. If you can, include the following when you email us.
The email address on the account and the name or ID of the affected check, check group, or resource.
A direct link to a failing or unexpected check result from the Checkly app is the fastest way for us to see what you see.
Timestamps (with timezone, UTC preferred) and the run location or private location.
What you expected to happen, what happened instead, and whether it reproduces every time.
Error output, screenshots, and the relevant check configuration or CLI construct. Redact secrets before sending.
Enterprise plans add a support layer on top of everything above.
Found a security vulnerability? Please do not post it publicly. Follow our security response process instead.