Upcron Docs

Uptime Monitors

Monitor your websites, APIs, and services with HTTP checks and get instant alerts when they go down.

Uptime monitors continuously check the health of your web services by sending HTTP requests at regular intervals. When a monitor detects that your service is down or responding with unexpected status codes, it automatically creates an incident and sends you alerts.

Uptime monitors are perfect for monitoring websites, APIs, health check endpoints, and any HTTP-accessible service.

Creating Your First Monitor

1

Navigate to Monitors

In your Upcron.io dashboard, go to the Monitors section within your project.

2

Add New Monitor

Click "Create Monitor" and fill in:

  • Monitor Name — A descriptive name (e.g., "Production API")
  • URL — The endpoint to monitor (e.g., https://api.example.com/health)
  • Project — Select the project this monitor belongs to
3

Configure Settings

  • HTTP Method — GET, POST, PUT, PATCH, DELETE, or HEAD
  • Valid HTTP Codes — Which status codes indicate success (default: [200])
  • Basic Authentication — Username/password if your endpoint requires it
  • Active Status — Enable or disable the monitor
4

Save and Start Monitoring

Click "Create Monitor" to save and start monitoring immediately.

Monitor Configuration

HTTP Methods

Choose the appropriate HTTP method for your endpoint:

  • GET — Most common method for health checks and status endpoints
  • POST — Useful for APIs that require data submission to check health
  • HEAD — Lightweight option that only checks headers without downloading the full response

Valid HTTP Status Codes

Configure which HTTP status codes should be considered successful responses:

// Standard Web Service
[200]

// API with Multiple Success Codes
[200, 201, 202]

// Service with Redirects
[200, 301, 302]

Common status code combinations

  • Web pages: [200]
  • APIs: [200, 201, 202]
  • CDN/Proxy services: [200, 301, 302]

Basic Authentication

For endpoints that require basic HTTP authentication, enable the option in your monitor configuration, enter your credentials (encrypted and stored securely), then save and verify.

Credentials are encrypted and stored securely. Never share your monitor configuration files with sensitive authentication data.

Monitor Status

Up (Active)

Monitor is active and the last check was successful.

Down

Failure detected — incident created and alerts sent.

Inactive

Monitor is disabled and not performing checks.

Unknown

Not checked yet or status is being determined.

Best Practices

Choose the Right Endpoints

Monitor endpoints that are critical to your service functionality:

# Good endpoints to monitor
https://api.example.com/health
https://example.com
https://api.example.com/status

# Avoid monitoring
# Internal admin pages
# Endpoints with side effects
# Pages that require user interaction

Organize with Projects

  • Production — Critical production services
  • Staging — Development and testing environments
  • Third-party — External services you depend on
  • Infrastructure — Database, cache, and infrastructure endpoints

Use Descriptive Names

Choose clear, descriptive names: "Production API Health Check", "Website Homepage", "Payment Gateway Status" — not "Monitor 1" or "Test".

Dashboard Overview

Your monitor dashboard shows:

  • Current Status — Up/Down status for each monitor
  • Uptime Percentage — Calculated uptime over time
  • Last Checked — When the monitor was last verified
  • Incident Count — Number of incidents in the last 30 days
  • Response Time — Average response times

Uptime is calculated as: (Successful checks / Total checks) × 100

Troubleshooting

Monitor shows down but service is actually up
  • Check if your valid HTTP codes include the status your service returns
  • Verify the URL is correct and accessible from external networks
  • Check if basic authentication credentials are correctly configured
  • Ensure your service isn't blocking Upcron.io's monitoring requests
Getting too many false positive alerts
  • Add additional valid HTTP status codes (like 301, 302 for redirects)
  • Consider monitoring a more stable endpoint (like /health instead of /)
  • Check if your service has intermittent issues that need addressing
Basic authentication not working
  • Verify the username and password are correct
  • Test authentication manually with curl
  • Check if your service requires additional headers
  • Ensure the authentication endpoint matches your monitor URL