Bubobot supports multiple monitoring types including:
A monitoring interval is the frequency at which we check your endpoints. For example, a 30-second interval means we check your service every 30 seconds.
We offer the market's shortest monitoring intervals, starting from 20 seconds, allowing you to detect and respond to issues faster than ever. You can customize these intervals based on your needs and service level.
We monitor your systems from multiple global locations to provide accurate, region-specific insights. Check our coverage at https://docs.bubobot.com/configuration/worker-ip-locations
Bubobot queries WHOIS data daily to track domain expiration dates and registrar information changes.
We support all major TLDs including .com, .net, .org, .io, country codes, and new gTLDs. If WHOIS data is publicly available, we can monitor it.
WHOIS privacy doesn't hide expiration dates - only contact information. Bubobot can still track expiration even with privacy protection enabled.
Yes, each domain monitor can have its own custom alert timing configured independently.
Absolutely. Bubobot monitors domains regardless of where they're registered - GoDaddy, Namecheap, Cloudflare, or any other registrar.
Expiration tracking alerts you before certificates expire. Validation monitoring continuously checks certificate chain integrity, revocation status, and encryption strength to catch issues immediately.
Yes, Bubobot monitors all certificate types including wildcards, multi-domain (SAN), and single-domain certificates.
Yes, unless you customize the alert timing. You can disable specific warning stages or set custom periods per certificate.
Absolutely. Bubobot monitors certificates from any Certificate Authority including Let's Encrypt, DigiCert, Sectigo, and others.
Currently, each monitor tracks one keyword condition (presence or absence). Create multiple monitors to track several keywords on the same URL.
Yes. Bubobot searches for keywords in any HTTP response body including JSON, XML, HTML, and plain text.
Currently, keyword monitoring uses exact string matching. Regex support is on our roadmap based on user feedback.
Yes. Use custom HTTP parameters to configure authentication headers, cookies, or bearer tokens to monitor keyword presence on protected pages.
Any TCP port from 1-65535. Common examples include SSH (22), FTP (21), SMTP (25), custom application ports, or any service listening on TCP.
Bubobot tests ports from external locations. If your firewall blocks external connections to specific ports (as it should for security), monitoring won't work. This is by design - we test what external users/services would experience.
Currently, only TCP port monitoring is supported. UDP monitoring is on our development roadmap.
Port monitoring confirms TCP connectivity. For application-level health checks, combine with HTTP monitoring to verify the service is responding correctly.
Add a single HTTP request to your Bubobot heartbeat URL at the end of your script. Works with curl, wget, Python requests, Node.js fetch, or any HTTP client.
If your script fails before reaching the heartbeat URL call, Bubobot won't receive the heartbeat and will alert you when the expected interval is exceeded.
Yes. Each heartbeat monitor has independent interval configuration down to the second.
No. Heartbeat monitoring requires only a simple HTTP request - one line of code in your existing scripts.
The dedicated Authorization tab supports Bearer tokens, API keys, Basic Auth, and custom authentication schemes. You can also configure authentication through custom headers if needed.
No hard limit on parameter count. You can add as many URL parameters, headers, and body fields as needed for your API monitoring requirements.
Bubobot AI collects response time data for 14 days to understand your application's normal behavior patterns, including daily cycles, weekly patterns, and typical variability before activating anomaly detection.
Threshold-based anomaly detection works immediately. AI-powered detection requires 14 days of historical data to establish accurate baselines.
Start with 80% sensitivity for balanced detection. Lower values (20-50%) only catch significant deviations, while higher values (85-95%) are more sensitive to minor changes.
You may need to retrain the AI model when your application undergoes major changes (infrastructure upgrades, traffic shifts, new features). Bubobot will prompt you when retraining is recommended.
Bubo AI assists with feature explanations, configuration guidance, troubleshooting steps, best practices, and navigating Bubobot's interface. It's trained on our complete documentation and help resources.
Bubo AI is trained exclusively on verified Bubobot documentation and updated regularly. For complex account-specific issues, it will recommend contacting our support team.
Yes. The AI Assistant is available to all Bubobot users on both free and pro plans.
Bubobot shows the complete HTTP response in monitoring logs. You can verify your parameters, headers, and body are being sent correctly by reviewing the response data.
Yes. You can use either a Bubobot subdomain (yourname.bubobotstats.com) for quick setup or configure a custom domain (status.yourcompany.com) for complete brand ownership.
Public pages are accessible to anyone with the URL, ideal for customer-facing communications. Private pages require authentication, perfect for internal system status that shouldn't be publicly visible.
No, you can not.
Customize your company logo, name, address, email, color themes (light/dark), page titles, domain settings, and add Google Analytics tracking for visitor insights.
No, white-label features and custom domains require a Pro plan.
Yes. Bubobot can automatically create incidents on your status page when monitoring alerts are triggered. You can also manually create incidents for issues not directly tied to monitors or for more complex multi-service outages.
Subscribers receive email notifications when incidents are created, updated, or resolved. You can also schedule maintenance announcements in advance, and subscribers will receive notifications before, during, and after the maintenance window.
Incident history is retained indefinitely, allowing you to maintain complete records for post-mortem analysis, compliance reporting, and tracking service reliability trends over time. You can configure how many days of incidents are displayed on your public status page (default: 30 days).
Smart Silencing evaluates each alert against your configured rules (business hours, service tiers, maintenance windows) and dynamic contexts (active incidents, deployment status, system load). Alerts are only silenced when multiple conditions indicate low urgency or expected behavior.
No. Critical service alerts, production environment issues, and high-severity incidents bypass silencing rules. You configure service criticality tiers to ensure important alerts always reach your team regardless of other silencing conditions.
Yes. Bubobot analyzes your alert patterns and suggests rules based on recurring low-priority alerts, auto-resolved incidents, and historical alert handling patterns. You review and approve all suggestions before they're applied.
Need help? Contact us at [email protected] and our team will assist you with any questions or issues.
Yes, we provide API access that will allow third-party users to integrate with Bubobot. Check the API docs at https://docs.bubobot.com/api
A monitor run occurs each time our system checks your endpoint or service. The total number of monitor runs is calculated by:
For example:
Monitor runs accumulate across all your active monitors and their respective workers.
Our pricing is based on monitor runs - each time our system checks your endpoint counts as one monitor run. Important to note:
You can estimate costs using the calculator at https://bubobot.com/pricing/calculating.
We offer flexible plans with annual subscriptions available at a 20% discount. Our pricing is transparent with no hidden fees.
Yes, you can easily upgrade or downgrade your plan as your needs change. We offer flexible scaling options to accommodate your growing monitoring requirements without long-term commitments.
Yes! We offer a generous free tier that includes your first 150,000 monitor runs completely free. This allows you to thoroughly test our platform and scale your monitoring needs without initial costs.
Bubobot is a SaaS monitoring platform designed to keep your systems up and running. We offer comprehensive monitoring tools to give you full visibility and control over your system's health.
Getting started with Bubobot is simple:
For detailed instructions on setting up specific monitors and configuration options, visit our documentation at https://docs.bubobot.com/
Bubo Assistant is your AI chatbot that simplifies Bubobot management. It allows you to create and manage monitors, configure integrations, and handle incidents using your own language.
Anomaly Detection identifies unusual system behavior before it escalates into incidents. Unlike traditional monitoring that relies solely on fixed thresholds, our detection system analyzes performance patterns over time to spot changes that may indicate problems. This proactive approach helps prevent downtime by alerting you to subtle changes in response times and status code patterns.
When creating or editing a monitor, select the Anomaly Detection tab and choose between two powerful options:
With either option, you can customize when alerts trigger by setting what percentage of checks must exceed limits and for how long.
Bubobot provides two key notification settings:
These settings help reduce noise and ensure accurate incident reporting. You can customize both periods based on your monitoring needs.
Setting up integrations is straightforward:
Escalation policies help ensure critical alerts are never missed. They allow you to:
For example, if the primary responder doesn't acknowledge an alert within a specified time, it automatically escalates to the next level of support.
Bubobot integrates with numerous notification channels like Slack, Telegram, Discord, or PagerDuty. For critical notifications, we also support SMS alerts and phone calls.
For the complete list of integrations and setup guides, visit our documentation at https://docs.bubobot.com/integrations/integrations-messaging
Status pages allow you to transparently communicate your system's health with your users. You can display real-time status of your monitored services, planned maintenance, and incident history.
You can customize your status page with:
Check our documentation for complete customization options.
Yes, you can set up a custom domain for your status page (e.g., status.yourcompany.com).
Yes, Bubobot supports team collaboration. You can invite team members, assign roles, and manage permissions from your account settings.
For detailed instructions on team management and available roles, visit our documentation at https://docs.bubobot.com/user-team/invite-members-to-a-team
Team members can help manage monitors, respond to alerts, and configure integrations based on their assigned roles. Check our documentation for the complete list of roles and their capabilities at https://docs.bubobot.com/user-team/invite-members-to-a-team