Uptime Monitoring

Bleemeo's uptime monitoring supports HTTP/HTTPS for websites and APIs (with custom headers, status code validation, and response body checks), TCP for any port-based service (databases, custom applications), ICMP (Ping) for basic host reachability and latency, and DNS for domain resolution validation. For HTTPS monitors, we also automatically check SSL certificate validity and expiration dates.

Bleemeo performs uptime checks every 30 seconds from each selected monitoring location. This sub-minute frequency ensures you detect outages almost immediately, minimizing the time between an issue occurring and your team being notified. The check frequency is the same across all protocols (HTTP, HTTPS, TCP, ICMP, DNS).

Yes, Bleemeo supports private probes. You can use any Glouton agent installed on your servers as a monitoring probe, allowing you to monitor URLs and services accessible only from your internal network. This is perfect for monitoring internal APIs, staging environments, intranet applications, or services behind firewalls. You can have unlimited private probes connected to your account.

Bleemeo operates monitoring probes from 7 global locations: Paris (France), Milan (Italy), Spain, Stockholm (Sweden), and Frankfurt (Germany) in Europe, plus Singapore in Asia and Ohio (USA) in North America. By default, European probes are enabled. You can select which locations to monitor from based on where your users are located.

An alert is raised when the majority of your selected probes fail to reach the service, preventing false positives from network routing issues. Notifications can be sent via email, SMS, or webhooks. You can also integrate with Slack, PagerDuty, OpsGenie, Microsoft Teams, and other notification platforms. Alert rules are customizable to match your incident response workflow.

For all HTTPS monitors, Bleemeo automatically tracks SSL certificate expiration. You'll receive a warning alert 20 days before expiration and a critical alert 10 days before expiration. We also monitor domain name expiration via WHOIS lookups (where available), with the same 20/10 day warning thresholds. This gives you ample time to renew certificates and domains before they impact your users.

Yes, Bleemeo offers advanced validation options. For HTTP/HTTPS monitors, you can specify: expected response codes (e.g., only 200, or any 2xx), text that must be present in the response body, text that must be absent (to detect error pages), and custom HTTP headers for authentication or API versioning. This ensures the check validates not just availability, but correct functionality.

Yes, Bleemeo tracks response time (latency) from each monitoring location on every check. You can view response time graphs in the monitor dashboard to identify performance degradation, compare latency across geographic locations, and set up alerts when response times exceed your thresholds. Historical latency data is retained for trend analysis and SLA reporting.

Bleemeo provides detailed uptime statistics and SLA reports for your monitored services. The dashboard shows current status, response time trends, and historical availability percentages. You can track your services against internal SLA targets and generate reports for stakeholders. Our monitoring infrastructure itself is designed for high availability with redundant probes.

Yes, Bleemeo is well-suited for API monitoring. You can monitor REST APIs using GET, POST, and PUT methods, add custom HTTP headers for authentication (API keys, Bearer tokens), validate response codes and response body content, and track response times. Combined with multi-location monitoring, this gives you a comprehensive view of your API's global availability and performance.