Frequently Asked Questions

Yes! The free plan includes 3 monitors with 5-minute check intervals, email alerts, and basic status pages. No credit card required. Perfect for side projects and learning the ropes.

• UptimeRobot Solo ($7-8/mo): Only 10 monitors (Free tier gives 50!)
• Better Stack ($269/mo): Enterprise pricing for indie features
• OpsPulse Pro ($9/mo): 20 monitors, Telegram alerts, smart thresholds, no per-seat pricing

We built OpsPulse because existing tools either nickel-and-dime you or assume you're a Fortune 500 company.

No. All plans include unlimited team members. We think per-seat pricing for uptime monitoring is ridiculous — your cofounder shouldn't cost extra.

Yes. Upgrade or downgrade instantly. When you upgrade, you're prorated for the remaining days. When you downgrade, the new rate applies next billing cycle.

Traditional monitoring alerts on every failed check. If your server hiccups for 30 seconds, you get 3 emails. We use consecutive failure thresholds (default: 2 failures before alerting) and alert deduplication to eliminate 98% of false positives without missing real incidents.

Yes. All HTTP(S) monitors check SSL certificate validity and expiration. You'll get alerted 30 days before cert expiry — no more surprise "Your connection is not secure" warnings.

Currently we support HTTP/HTTPS endpoints and TCP port monitoring. Ping (ICMP) support is on the roadmap. If you need something specific, let us know — we prioritize based on user demand.

A public page showing your service health in real-time. When things break, users check there instead of emailing support. You can customize the title, logo, and accent color to match your brand. Included free on all plans.

Yes! Full REST API for managing endpoints, retrieving uptime data, and integrating with your CI/CD pipeline. API documentation →

• Email: All plans
• Telegram: Pro and Team plans
• Discord: Via webhooks (Team plan)
• Slack: Via webhooks (Team plan)
• Custom webhooks: Team plan (integrate with anything)

Three ways:

1. Consecutive failure threshold: Only alert after N failures (default: 2)
2. Alert deduplication: Same incident = one alert, not ten
3. Severity routing: Critical → SMS/Telegram, Warnings → Email digest

Most users see a 90%+ reduction in alert volume without missing real incidents.

Email alerts: under 10 seconds. Telegram/push: under 5 seconds. We monitor our own monitoring (yes, recursively) and maintain 99.9% alert delivery success rate.

Multiple regions for redundancy. Primary checks originate from North America (East + West coast) with European backup nodes. Multi-region monitoring ensures we catch provider-specific outages.

• Free: 5 minutes
• Pro: 1, 2, 3, or 5 minutes
• Team: 30 seconds to 5 minutes

For most use cases, 1-minute intervals are plenty. Sub-minute checks are overkill unless you're running high-frequency trading systems.

Yes. Add basic auth credentials or custom headers in the endpoint settings. We store credentials encrypted and never log sensitive values.

We target 99.9% uptime for our monitoring infrastructure. Our own status page is at status.orionapps.org (meta, we know). Historical uptime is published monthly.

About 2 minutes. Create account → Add endpoint → Done. No credit card for free plan. See our 5-minute setup guide for the full walkthrough.

Yes! Bulk CSV import supports up to 100 endpoints at once. Template provided in the dashboard. Most users migrate from UptimeRobot/Pingdom in under 10 minutes.

Email support for all plans (response within 24h, usually faster). We're a small team, which means you talk to actual developers who built the product — not a ticket queue.

Yes! Public status pages are included free on all plans. Show real-time system status to your users with customizable branding, title, logo, accent colors. Learn more at /status-pages.html.

Yes. No contracts, no cancellation fees, no guilt trips. Your data is exported on request. We'd rather earn your retention than lock you in.