Meldingen & Alerts
Real-time monitoring voor Nederlandse infrastructuur. Receive instant notifications the moment your services go down, so your team can act before customers notice.
Notification Channels
Five channels. Zero delays.
StatusBewaker pushes alerts through every major platform your DevOps and SRE teams already use. Configure one or combine multiple channels for redundancy — you decide what "instant" means for your organization.
Slack
Post alerts directly into a dedicated channel or trigger a thread for incident response. Supports rich formatting with check result details, response time graphs, and direct links to the StatusBewaker dashboard. Integrates with Slack's notification system so on-call engineers get paged immediately.
Microsoft Teams
Send adaptive card messages to Teams channels with color-coded severity badges. Teams alerts include the monitored endpoint, last known uptime percentage, and a one-click "Acknowledge" button that logs the incident in StatusBewaker's timeline. Works seamlessly with Teams shift schedules for on-call rotation.
Structured HTML alerts delivered to individual inboxes or distribution lists. Each e-mail contains a summary table of all failing checks, expected recovery SLA, and a link to the live status page. Supports digest mode — receive one consolidated report every 15 minutes instead of per-event noise.
SMS
Short, actionable text messages sent via Twilio to any mobile number. Ideal for critical-tier services where seconds matter. SMS alerts include the service name, the type of failure (HTTP error, timeout, SSL expiry), and a short URL to the incident page. Rate-limited to prevent alert fatigue during prolonged outages.
Webhooks
Fire a POST request to any HTTPS endpoint with a JSON payload containing the full check result, timestamp, and severity level. Connect to PagerDuty, Opsgenie, Zabbix, or your own internal incident management system. Webhooks include a retry mechanism with exponential back-off to ensure delivery even if your receiving service is temporarily unavailable.
Configuration & Escalation
Set up alerts that match your response workflow
Every check in StatusBewaker can be paired with a custom alert policy. Define who gets notified, when, and how — then watch the escalation ladder in real time.
Downtime Detection
Checks run from probes in Amsterdam, Rotterdam, and Frankfurt. A service is marked down only after consecutive failures across at least two probe locations, eliminating false positives from single-node probe outages. Detection intervals start at 30 seconds for critical checks and scale to 5 minutes for low-priority endpoints.
Escalation Policies
Build multi-tier escalation chains: start with a Slack notification to the on-call engineer, escalate to SMS after 5 minutes if unacknowledged, and page the infrastructure manager after 15 minutes. Each tier is configurable per check or per service group, and escalation timers pause automatically during declared maintenance windows.
Maintenance Windows
Schedule recurring or one-off maintenance periods to suppress alerts during planned deployments. Maintenance windows can be set per check, per group, or globally. When a window opens, StatusBewaker continues monitoring and logging results — it simply halts notification delivery until the window closes.
Recovery Notifications
When a service comes back online, StatusBewaker sends a recovery alert through the same channels that received the initial downtime notification. The recovery message includes total downtime duration, the number of failed checks, and a link to the post-incident report. You can also configure a quiet period to prevent rapid alert/recovery cycles from flooding your channels during flapping events.
Every organization handles incidents differently. StatusBewaker's alert engine is designed to fit your process — not the other way around. Start with a single Slack channel and one critical check, then expand as your monitoring matures.
Meldingen & Alerts
Real-time monitoring voor Nederlandse infrastructuur. Receive instant notifications the moment your services go down, so your team can act before customers notice.
Notification Channels
Five channels. Zero delays.
StatusBewaker pushes alerts through every major platform your DevOps and SRE teams already use. Configure one or combine multiple channels for redundancy — you decide what "instant" means for your organization.
Slack
Post alerts directly into a dedicated channel or trigger a thread for incident response. Supports rich formatting with check result details, response time graphs, and direct links to the StatusBewaker dashboard. Integrates with Slack's notification system so on-call engineers get paged immediately.
Microsoft Teams
Send adaptive card messages to Teams channels with color-coded severity badges. Teams alerts include the monitored endpoint, last known uptime percentage, and a one-click "Acknowledge" button that logs the incident in StatusBewaker's timeline. Works seamlessly with Teams shift schedules for on-call rotation.
Structured HTML alerts delivered to individual inboxes or distribution lists. Each e-mail contains a summary table of all failing checks, expected recovery SLA, and a link to the live status page. Supports digest mode — receive one consolidated report every 15 minutes instead of per-event noise.
SMS
Short, actionable text messages sent via Twilio to any mobile number. Ideal for critical-tier services where seconds matter. SMS alerts include the service name, the type of failure (HTTP error, timeout, SSL expiry), and a short URL to the incident page. Rate-limited to prevent alert fatigue during prolonged outages.
Webhooks
Fire a POST request to any HTTPS endpoint with a JSON payload containing the full check result, timestamp, and severity level. Connect to PagerDuty, Opsgenie, Zabbix, or your own internal incident management system. Webhooks include a retry mechanism with exponential back-off to ensure delivery even if your receiving service is temporarily unavailable.
Configuration & Escalation
Set up alerts that match your response workflow
Every check in StatusBewaker can be paired with a custom alert policy. Define who gets notified, when, and how — then watch the escalation ladder in real time.
Downtime Detection
Checks run from probes in Amsterdam, Rotterdam, and Frankfurt. A service is marked down only after consecutive failures across at least two probe locations, eliminating false positives from single-node probe outages. Detection intervals start at 30 seconds for critical checks and scale to 5 minutes for low-priority endpoints.
Escalation Policies
Build multi-tier escalation chains: start with a Slack notification to the on-call engineer, escalate to SMS after 5 minutes if unacknowledged, and page the infrastructure manager after 15 minutes. Each tier is configurable per check or per service group, and escalation timers pause automatically during declared maintenance windows.
Maintenance Windows
Schedule recurring or one-off maintenance periods to suppress alerts during planned deployments. Maintenance windows can be set per check, per group, or globally. When a window opens, StatusBewaker continues monitoring and logging results — it simply halts notification delivery until the window closes.
Recovery Notifications
When a service comes back online, StatusBewaker sends a recovery alert through the same channels that received the initial downtime notification. The recovery message includes total downtime duration, the number of failed checks, and a link to the post-incident report. You can also configure a quiet period to prevent rapid alert/recovery cycles from flooding your channels during flapping events.
Every organization handles incidents differently. StatusBewaker's alert engine is designed to fit your process — not the other way around. Start with a single Slack channel and one critical check, then expand as your monitoring matures.