SYNTHETICS
HTTP Monitoring and TLS Certificate Checks
Check whether a public service responds as expected before waiting for a customer report. Review actual check history and connect observed failures with incident investigations.
Guided pilot scope · Reviewed 2026-10-16. No production AI diagnosis, automatic infrastructure/DDL remediation or compliance certification is offered.
Configure a real endpoint check
Create an HTTP or HTTPS monitor with GET or HEAD, expected status, interval, timeout and optional literal response text. Run an immediate probe, then review scheduled results. Production uses actual requests; browser demos are labelled illustrations.
Read timing and certificate evidence
Results include observed DNS, TCP, TLS, first-byte and total timings where stages complete. HTTPS checks report verified certificate information and remaining days; failed stages remain unknown.
A failed request or assertion marks the check down. History helps distinguish a failure from missing or stale observations. Displayed uptime is the share of retained successful checks, not a time-weighted SLA.
Connect checks to incident response
The first failed check creates a linked incident, subsequent failures reuse it, and recovery resolves it. The investigation workspace can show relevant check results. Enabled alert channels receive best-effort failure/recovery and certificate-expiry notifications.
Use IncidentOps separately for configured responder paging and acknowledgement. Notification delivery alone does not prove a human response.
Worker and network boundaries
Checks run from one deployed worker location. Public HTTP/HTTPS destinations are supported; private-network probes, custom authentication headers, browser journeys and a regional fleet are unavailable. Redirects are not followed.
Intervals range from 15 seconds to 24 hours. Response and concurrency limits apply. Test your final URL and expected response; check history cannot certify global availability or service uptime between observations.
Frequently asked questions
Does Spekra check from several countries?
The current production adapter uses one deployed worker location. It does not provide a managed multi-region probe fleet.
Can I check an internal database or private endpoint?
This synthetic adapter blocks private and reserved network destinations. Database monitoring uses separate supported collectors and network configuration.
Are status pages publicly hosted?
The current status preview is authenticated. A publicly hosted customer status portal is not implemented.
Evaluate your own workflow
Start with supported sample or staging infrastructure and agree on a success measure. Contact the operator to arrange a pilot. This static website does not create accounts or send invitations automatically.
Request a guided pilot →