Standard HTTP(S) and TCP health checks execute every 60 seconds. Paid Professional and Enterprise tiers support 30-second and 15-second intervals respectively. DNS resolution checks and ICMP ping probes default to 120-second intervals. Reducing intervals below 15 seconds requires a dedicated probe allocation and is subject to network throttling safeguards.
FAQ - StatusBewaker Docs
Real-time monitoring voor Nederlandse infrastructuur
Overview
Monitoring Architecture & Policies
StatusBewaker provides deterministic uptime tracking for Dutch enterprises, government portals, and cloud-native applications. Our probe network operates across three EU regions to guarantee sub-second latency measurements and GDPR-compliant data handling.
This section covers technical specifications regarding check intervals, false positive mitigation, and data retention. For custom SLA configurations or API rate limit adjustments, contact our infrastructure team at ops@statusbewaker.nl.
Technical Q&A
Frequently Asked Questions
What are the default check intervals for HTTP, TCP, and DNS probes?
How does the platform prevent false positive downtime notifications?
StatusBewaker employs a quorum-based validation model. A critical incident is only dispatched when a minimum of three independent probes (e.g., Amsterdam, Rotterdam, Frankfurt) register consecutive failures within a 90-second sliding window. Transient TLS handshake drops, 502 Bad Gateway responses, or rate-limited 429 errors are categorized as degraded states and trigger informational webhooks rather than SMS/PagerDuty escalations.
What is the data retention policy for uptime logs and performance metrics?
Raw check payloads and response headers are stored in our primary PostgreSQL cluster for 90 days. Aggregated uptime percentages, latency percentiles (p50, p95, p99), and certificate timelines are retained indefinitely in our TimescaleDB instance. Historical datasets older than 24 months are archived to AWS S3 Glacier Deep Archive and remain queryable via the REST API with a maximum 48-hour retrieval SLA.
How are monitoring datasets handled during GDPR right-to-erasure requests?
Upon receiving a deletion request, customer-specific monitoring configurations, webhook endpoints, and team member credentials are purged within 72 hours. Historical uptime telemetry is anonymized at the aggregate level to preserve statistical integrity for public status pages, while all personally identifiable information and raw response bodies are permanently wiped from active and backup storage systems.
Do you provide audit-ready exports for ISO 27001 or SOC 2 compliance?
All plans include automated CSV and JSON exports for the preceding 365 days. Enterprise customers receive monthly PDF compliance reports detailing probe distribution, mean time to detection (MTTD), and mean time to resolution (MTTR). API access supports programmatic retrieval using HMAC-SHA256 request signing, with IP allowlisting and role-based access control (RBAC) enforced at the gateway level.