Infrastructure

Built for reliability & compliance

Core customer data is stored in the EU. GDPR compliant by design. Multi-region monitoring uses static egress IPs and can include non-EU probe regions for global uptime verification.

GDPR Compliant
Core customer data stays in the EU
Multi-Region
Monitors run from multiple locations
EU Hosting
Control plane hosted in Germany
Real-Time
30-second check intervals
Simulation Only
Panel dispatches checks to the worker grid
Demo stream
Control Panel
Dispatch Batch #8841

Visual simulation only: scheduler flow is illustrated without sending real network checks.

Tick every 30s
Job assigned Worker pings target Response returns to panel
Worker 1
Assigned: 2 checks · RTT 132ms
Worker 2
Assigned: 1 check · RTT 145ms
Worker 3
Assigned: 2 checks · RTT 420ms
panel/app
Dispatch, ingest, evaluate, alert
Fully connected flow: panel/app dispatches check jobs, workers ping endpoints, and results return directly.
Demo visualization with zero live traffic: no real endpoints are pinged and no real worker checks are triggered.
How checks work in production
1. Job dispatch
panel/app schedules due checks and assigns jobs to available worker regions.
2. Endpoint probe
Workers perform HTTP/TCP checks and collect status code, latency, and packet-loss metadata.
3. Result ingest
Workers send compact check results back to panel/app for rule evaluation and alerting.
4. Data boundary
Core customer data is stored in EU systems. Probe nodes only transmit technical check metadata.
What can leave the EU during non-EU uptime probes
  • Monitor metadata needed to execute checks: URL, method, timeout, interval, thresholds, region assignment.
  • Configured monitor request headers (for example auth header if you set one) sent from the probe to your endpoint.
  • Check result metadata returned to panel/app: status code, latency, packet-loss/degraded state, error string.
What does not leave the EU in this check flow
  • No application event payloads or error stack traces from your product telemetry pipeline.
  • No full response body storage from monitored endpoints in the uptime result payload.

EU Data Residency

Core customer data - error events, configuration, and telemetry - is stored on EU infrastructure located in Germany. Global uptime monitoring can use non-EU probe nodes (for example US-East) that only send technical check metadata back to the EU control plane.

Storage

Error payloads, attachments, and configuration are stored on encrypted infrastructure in the EU.

Database

Structured data is persisted in EU-based databases with daily automated backups.

No Third-Party Transfers

We do not sell, share, or transfer your data to third parties. Transactional emails are the only external service that receives limited metadata.

Monitoring Egress IPs

Uptime checks originate from static IPs. Use these to allowlist Errly in your firewall, WAF, or CDN.

RegionLocationIPv4
EU-CentralGermany91.98.5.251
EU-NorthFinland204.168.215.157
US-EastAshburn, USA178.156.155.91

WAF & Firewall Setup

If your endpoint is protected by a WAF or rate limiter, allowlist the IPs above so checks are not blocked.

Cloudflare WAF

  1. Go to Security → WAF → Custom Rules
  2. Create a rule: skip WAF when ip.src is in the IP list above
  3. Set action to Skip or Allow
  4. Save and verify with a test check

AWS Security Groups

  1. Open your Security Group inbound rules
  2. Add one rule per IP: 91.98.5.251/32, 204.168.215.157/32, 178.156.155.91/32
  3. Allow HTTP (80) and HTTPS (443)
  4. Changes take effect immediately

Custom Headers

  1. All checks send User-Agent: ErrlyBot/1.0 (+https://errly.app)
  2. Add custom headers per monitor for authentication
  3. Example: X-Monitor-Token: your-secret
  4. Configure under monitor settings → Headers

Questions?

If you need help configuring your WAF or firewall to allow Errly monitoring checks, contact us at ···.