Checking system status…
Loading live status…
Our uptime commitment
Different plans get different SLAs. Here's what we promise to deliver each month.
- Best-effort response
- Standard support queue
- Priority support within 4 business hours
- Service credits if SLA is breached
- 1-hour response, 24/7 paging
- Dedicated success engineer
- Custom SLA on request
SLA percentages exclude scheduled maintenance windows (always pre-announced) and force-majeure events. Full terms in the Terms of Service.
Component status (last 30 days)
Each cell represents one day of operational health. Hover for the date.
Recent incidents
Resolved incidents from the last 90 days. Live incidents are pinned at the top.
No incidents in the last 90 days
If something does go wrong, it lands here within 15 minutes of detection.
Scheduled maintenance
All maintenance is pre-announced at least 48 hours in advance, ideally during low-traffic windows.
No scheduled maintenance
When we plan something — even read-only DB maintenance — it gets posted here first.
Get incident notifications
Subscribe to be emailed when an incident is opened, updated, or resolved. No marketing, no sales emails — incidents only.
One email per incident state change. Unsubscribe in one click.
What each system does
Quick reference for what the components above actually serve.
Public API
Serves dashboard, beacon ingestion endpoints, and customer integrations.
If down: Dashboard becomes read-only; existing protection rules remain in force.
Beacon ingestion
Receives visitor-level events from the t.js tracker on customer sites.
If down: New visitor data isn't recorded for the outage window; protection continues with previous IP/fingerprint state.
Detection engine
Runs scoring, behavioral checks, and IP/proxy lookup against incoming visits.
If down: Scoring pauses for new visits; cached results from the last hour stay valid.
Database
Stores customer accounts, rules, and historical reports.
If down: Reporting may be delayed; live blocking lookups fall back to the read replica.
Background workers
Ad-platform exclusion sync (Google/Meta/Microsoft), email notifications, scheduled reports.
If down: Exclusion-list updates queue and retry; emails delayed but not lost.
Ad-platform APIs
Outbound integration to Google Ads API, Meta Marketing API, Microsoft Ads API.
If down: New exclusions queue locally and sync once upstream recovers (usually within minutes).