هر مسیر را مانیتور کن. با اطمینان هشدار بده.
پروب‌های مستقل روی چند شبکه نتیجه‌ها را با هم ترکیب می‌کنند تا اختلال یک مسیر به‌اشتباه به‌عنوان قطعی کامل اعلام نشود.
Your monitoring workspace
Manage monitors, incidents, provider coverage, public status pages and alerts from one workspace.
Talk to a real person
Need help with onboarding, monitoring or incident diagnosis? Contact support directly.
Everything required to investigate real outages
Not just a red/green badge. The platform records when an incident started, when it recovered, how long it lasted, what failed, and how the request was spent across DNS, TCP, TLS and transfer stages.
HTTP / HTTPS
Status ranges, response-time thresholds, SSL/TLS, redirects, response headers and endpoint health.
Ping / ICMP
Reachability and latency for routers, servers, IPs and hosts that do not expose HTTP.
TCP / Port
Verify SSH, SMTP, databases and custom services by connecting to the actual TCP port.
Content assertions
Confirm expected text is present or absent and validate response headers for critical pages or APIs.
A monitoring report should answer “what happened?”
Each monitor has filtered incident history, paginated check logs, uptime by range, downtime duration and detailed error classification. Planned maintenance can suppress checks so deployments do not pollute SLA history.
Start monitoring in three steps
Add a monitor
Choose HTTP, Ping, TCP or Keyword and configure the interval and failure rules.
Connect Bale
Each user connects their own Bale chat once. No hard-coded personal Chat ID is required.
Investigate & communicate
Review incidents, detailed timings and public status pages, then act before customers report the outage.
پروب‌های مستقل، رخدادهای تأییدشده و هشدارهای اشتباه کمتر.
Workerها را روی ارائه‌دهنده‌های مختلف اجرا کنید، شواهد را مرکزی ترکیب کنید و فقط وقتی اختلال معتبر است هشدار بفرستید.