Frequently Asked Questions
Uptime monitoring without blind spots
Technical FAQ
Answers to operational, configuration, and integration questions from our platform engineering team.
How often is my website checked?
By default, UptimeGuard executes health checks every 60 seconds. Business and Enterprise tiers support 30-second intervals. Checks are distributed across 12 global probe locations, including Frankfurt, Seoul, and Northern Virginia, to guarantee geographic redundancy and accurate latency metrics.
What exactly counts as a downtime incident?
An incident is logged when a target returns a non-2xx HTTP status code, fails to establish a TCP handshake within 10 seconds, or triggers a custom keyword mismatch. Transient 502/503 errors lasting under 30 seconds are automatically grouped into a single incident to prevent alert fatigue and ensure accurate MTTR calculations.
How can I change the monitoring interval?
Navigate to Dashboard > Monitors > [Your Monitor] > Settings. Adjust the "Check Frequency" dropdown to your desired interval. Changes propagate within 2 minutes across all probe nodes. Note that reducing intervals below 60 seconds consumes additional monthly credits based on your current subscription tier.
How are SSL certificate expirations handled?
UptimeGuard validates the TLS handshake on every scheduled check. Automated warnings trigger at 30, 14, and 7 days before expiration. We automatically track certificates issued by Let's Encrypt, DigiCert, and Sectigo without requiring manual certificate pinning or extra configuration.
What notification channels are supported?
We support PagerDuty (v2 API), Slack (webhooks and native app), Microsoft Teams, direct email, and SMS via Twilio. Webhook payloads deliver structured JSON containing status, response time, and probe location. Microsoft Teams integration requires OAuth2 authorization for secure channel posting.
Still looking for an answer? Check our full integration guides or contact engineering support.