Introduction
Your is-pro.dev subdomain may host critical services — a portfolio, API, or business site. When it goes down, you need to know immediately. Uptime monitoring services track your subdomain's availability, response time, and SSL certificate status, alerting you when something goes wrong. This guide covers setting up free monitoring using UptimeRobot, Better Stack, or the built-in is-pro.dev monitoring tools, configuring alerts, and creating a public status page.
Prerequisites
- An is-pro.dev subdomain with a live service (website, API, or application)
- An account on UptimeRobot or Better Stack (free tier)
- Access to your notification channels (email, Slack, Discord, or SMS)
Step 1: Choose a Monitoring Service
Several free monitoring services offer reliable uptime tracking. UptimeRobot monitors 50 URLs on the free tier at 5-minute intervals, with alerts via email, SMS, Slack, Discord, and webhooks. Better Stack (formerly Better Uptime) offers 10 monitors on the free tier with status pages, incident management, and a 3-minute check interval. Both services check your subdomain from multiple global locations and report response times. The is-pro.dev platform also provides built-in monitoring for registered subdomains, tracking DNS resolution, SSL status, and HTTP response codes. For most users, one of these free services provides sufficient coverage.
Step 2: Configure Monitors for Your Subdomain
In your chosen monitoring service, create a new monitor. Set the monitor type to "HTTP" or "HTTPS" for web services. Enter your full subdomain URL: https://yourname.is-pro.dev. Configure the check interval — UptimeRobot free tier offers 5-minute checks, which balances coverage with API usage limits. Set the timeout (typically 30 seconds) and select the monitoring locations closest to your target audience. For APIs, configure the monitor to check a specific endpoint and expect a particular HTTP status code (e.g., 200 OK) or keyword in the response body. Add monitors for all critical subdomains — one for your main site, one for your API, and one for your status page.
Step 3: Set Up Alert Notifications
Configure alert contacts in your monitoring service. For email alerts, add your primary email address. For faster response, set up Slack or Discord webhook integrations — paste the webhook URL from your Slack or Discord channel into the monitoring service's integration settings. This posts instant notifications when downtime is detected. For SMS alerts, UptimeRobot offers 50 SMS credits per month on the free plan. Better Stack offers push notifications via their mobile app. Configure alert thresholds: "Down" after 2 consecutive failed checks to avoid false alarms from transient network issues. Set up "Up" notifications so you know when the service recovers.
Step 4: Monitor SSL Certificate Status
SSL certificate expiration is one of the most common causes of unexpected downtime. Configure your monitoring service to check SSL certificate validity and expiration date. Both UptimeRobot and Better Stack include SSL monitoring in their HTTP checks. Set a warning threshold — get notified 30, 14, and 7 days before certificate expiration. For is-pro.dev subdomains with Cloudflare proxied mode, Cloudflare's Universal SSL certificates renew automatically, so manual renewal is not needed. For DNS-only records with self-managed Let's Encrypt certificates, monitoring is essential because Certbot auto-renewal can fail if ports are blocked or the ACME challenge fails.
Step 5: Create a Public Status Page
A public status page lets your users check if your service is experiencing issues without contacting you. Better Stack offers a free status page with the ability to mark incidents and show uptime history. Create a status page listing all your monitored services. Customize it with your branding and subdomain (e.g., status.yourname.is-pro.dev). Better Stack hosts the status page on their domain or you can point your status subdomain to it via a CNAME record. Configure the status page to automatically update when monitor status changes — green for operational, yellow for degraded, red for downtime. Add an incident history log so users can see past outages and their resolution times.
Step 6: Review Monitoring Data and Improve Reliability
Review your monitoring dashboard regularly. Look for patterns: does your subdomain become slow or unresponsive at certain times of day? Do SSL checks fail after specific events? Use the response time data to identify performance bottlenecks. If your monitoring service provides multi-location checks, compare response times from different geographic regions — high variance may indicate CDN configuration issues. Set up weekly or monthly uptime reports to track trends. Use the insights to improve your infrastructure: add caching, optimize database queries, or upgrade hosting if response times degrade consistently. Higher uptime builds trust with your users and improves SEO.
Best Practices
- Monitor from multiple geographic locations to catch regional outages
- Set up redundant notification channels (email + Slack + SMS) so you never miss an alert
- Include a health check endpoint in your application that returns database and cache status for deeper monitoring
- Keep your status page URL separate from your main service so it stays accessible during outages
Conclusion
Uptime monitoring is essential for any service you care about. Free tools like UptimeRobot and Better Stack provide reliable monitoring, instant alerts, and public status pages for your is-pro.dev subdomains. Combined with SSL monitoring and a status page, you can detect and respond to issues before they impact your users significantly.
FAQ
How often should I check my subdomain?
For most services, a 5-minute check interval is sufficient. Critical production services may benefit from 1-minute checks, which typically require a paid plan.
Can I monitor non-HTTP services like game servers?
Some monitoring services support TCP and port checks, which work for game servers, SSH, and other non-HTTP services. UptimeRobot's free tier includes TCP monitoring.
What is a good uptime target?
99.9% uptime (about 8.7 hours of downtime per year) is a reasonable target for most personal projects. Commercial services should aim for 99.99% (52 minutes of downtime per year).
FAQ
Is DevOps setup free on is-pro.dev?
Yes, all subdomains on is-pro.dev include free DNS management and SSL certificates.
How long does DNS take to propagate?
Cloudflare typically propagates DNS changes within seconds to a few minutes globally.
Can I use this for commercial projects?
Yes, is-pro.dev subdomains can be used for personal and commercial projects within our fair use policy.