Upcron Docs

Upcron Monitoring Bot

Technical identification and behavior of the automated HTTP probes used by Upcron.io uptime monitoring.

This page describes the bot that performs customer-initiated uptime checks on behalf of Upcron.io subscribers. It is not a search engine, content crawler, or AI training bot.

Operator

Service Upcron.io
Product Uptime monitoring & heartbeat tracking (SaaS)
Contact [email protected]
Dashboard app.upcron.io

Bot identification

User-Agent Upcron/1.0 (https://upcron.io)
Bot type Direct / intermediary uptime monitor (private checks on behalf of paying customers)
Protocol HTTPS HTTP(S) health checks only

What the bot does

Upcron.io runs scheduled HTTP probes against URLs that customers explicitly configure in their account. Each monitor defines a single target URL, HTTP method, expected status codes, optional authentication headers, and check frequency (typically every 30–300 seconds per monitor).

  • Sends one HTTP request per scheduled check to the configured URL
  • Records response status code, latency, and TLS/connection timing for the customer dashboard
  • Opens an incident and notifies the customer when checks fail according to their monitor rules
  • May run the same check from multiple geographic zones when the customer enables multi-zone monitoring

What the bot does not do

  • Does not crawl websites or follow internal links beyond configured redirect limits
  • Does not index, cache, or republish page content
  • Does not access URLs that were not added by a Upcron.io customer
  • Does not perform bulk scanning, vulnerability testing, or denial-of-service traffic
  • Does not impersonate end users or bypass paywalls

Request behavior

Methods GET, HEAD, POST, PUT, PATCH, DELETE (as configured per monitor)
Frequency Per-monitor interval chosen by the customer (minimum plan-dependent; typically ≥ 30 s)
Timeout 10 seconds per check (default)
Redirects Follows up to 5 redirects when enabled on the monitor
Request body Only when the customer configures a POST/PUT/PATCH monitor with a custom body
Authentication Optional HTTP Basic Auth or custom headers set by the customer for their own endpoints

Monitoring zones

Probes originate from the zones below. Customers choose which zones apply to each monitor. Multi-zone checks run in parallel; aggregate status follows a configurable consensus threshold.

Zone ID Location Infrastructure
eu-nbg1 🇩🇪 EU — Nuremberg, Germany Hetzner (primary control plane)
eu-fra1 🇩🇪 EU — Frankfurt, Germany AWS Lambda
eu-west-1 🇮🇪 EU — Ireland AWS Lambda
us-east-1 🇺🇸 US East — Virginia AWS Lambda
us-west-2 🇺🇸 US West — Oregon AWS Lambda
ap-southeast-1 🇸🇬 Asia Pacific — Singapore AWS Lambda
ap-northeast-1 🇯🇵 Asia Pacific — Tokyo AWS Lambda
ap-south-1 🇮🇳 Asia Pacific — Mumbai AWS Lambda
sa-east-1 🇧🇷 South America — São Paulo AWS Lambda

Remote zone workers receive signed instructions from Upcron.io infrastructure and perform the outbound HTTP check locally. Egress IP addresses are cloud-provider managed and may change; checks are initiated only for registered customer monitors.

Allowing Upcron on your site

If you protect your origin with a firewall or bot management product, you can allow our monitoring traffic by:

  • Permitting the User-Agent Upcron/1.0 (https://upcron.io)
  • Allowlisting probe traffic from the zones your monitors use (contact [email protected] for current egress details)
  • Creating a monitor only for URLs you intend to be checked

Related documentation