Inbound Monitoring

Monitor Apps Behind Firewalls with Push-Based Heartbeats

Traditional monitoring can't reach your internal services. Inbound monitoring flips the script - your apps send heartbeats to us. If we don't hear back, you get alerted. No firewall rules needed.

Start Free Monitoring Learn More
Unique Feature

The Problem with Traditional Monitoring

Most monitoring services work by actively checking your endpoints from the outside. But what about services that can't be reached from the public internet?

Traditional (Pull-Based)

  • Monitoring service tries to reach your app
  • Requires public IP or open firewall ports
  • Can't monitor internal services
  • Requires VPN tunnels for private networks
  • Complex setup for NAT environments

Inbound (Push-Based)

  • Your app sends heartbeats to StatusNow
  • Works through any firewall (outbound HTTPS)
  • Perfect for internal services
  • No VPN or firewall changes needed
  • Works on any network with internet access

Firewall-Friendly

Uses outbound HTTPS connections only. If your server can reach the internet, it can send heartbeats to StatusNow.

Zero Configuration

No firewall rules, no port forwarding, no VPN tunnels. Just add a simple HTTP call to your application.

Cron Job Monitoring

Perfect for monitoring scheduled tasks. Send a heartbeat after each successful run - if the heartbeat doesn't arrive on schedule, you're alerted.

IoT & Edge Devices

Monitor devices on cellular networks, behind CGNAT, or in remote locations. Anywhere with internet access works.

How It Works

  1. Create an Inbound Monitor: Set up a new monitor in StatusNow and choose "Inbound" type. You'll get a unique heartbeat URL.
  2. Set the Expected Interval: Tell us how often your app should check in (e.g., every 5 minutes, every hour, once a day).
  3. Add Heartbeat to Your App: Make a simple HTTP request to your heartbeat URL from your application.
  4. Get Alerted: If we don't receive a heartbeat within the expected timeframe, you're notified immediately.

Integration Examples

# Bash / Cron Job
curl -X POST https://statusnow.dev/api/heartbeat/YOUR_UNIQUE_ID

# At the end of your backup script:
./backup.sh && curl -X POST https://statusnow.dev/api/heartbeat/YOUR_UNIQUE_ID
// Node.js
const axios = require('axios');

// After successful operation
await axios.post('https://statusnow.dev/api/heartbeat/YOUR_UNIQUE_ID');
# Python
import requests

# Send heartbeat after task completion
requests.post('https://statusnow.dev/api/heartbeat/YOUR_UNIQUE_ID')
// C# / .NET
using var client = new HttpClient();
await client.PostAsync("https://statusnow.dev/api/heartbeat/YOUR_UNIQUE_ID", null);

Perfect Use Cases

Cron Jobs & Scheduled Tasks

Monitor backup scripts, data sync jobs, report generators

Internal APIs & Services

Backend services not exposed to the internet

IoT Devices

Sensors, gateways, edge computing devices

VPN-Protected Systems

Corporate networks, staging environments

Background Workers

Queue processors, batch jobs, data pipelines

On-Premise Software

Customer-hosted installations behind firewalls

Why This Matters

Most monitoring services assume your applications are publicly accessible. But modern infrastructure often includes:

  • Internal microservices that communicate over private networks
  • Background workers processing queue messages
  • Scheduled tasks running on isolated servers
  • IoT devices on cellular or restricted networks
  • Customer-hosted software behind corporate firewalls

Inbound monitoring solves all of these. If your code can make an outbound HTTP request, you can monitor it with StatusNow.

Start Monitoring in Minutes

No firewall changes. No VPN tunnels. Just add one line of code and start monitoring immediately.

Ready to Monitor Behind Your Firewall?

Start monitoring your internal services, cron jobs, and IoT devices with push-based heartbeat monitoring.

Start Free Monitoring See All Features