Loading…

UPG Monitor
Sign in

Uptime monitoring

Know the second
something breaks.

UPG Monitor checks your URLs and APIs every minute. When something changes, you know before your users do.

Get startedSign in

Setup in minutes, no complex onboarding.

  • Checks every 60 s
  • Email alerts on transition
  • Public status pages
Live monitors4 / 5 up
api.production112ms
99.97%
app.production88ms
99.81%
auth.service—
97.40%
cdn.assets14ms
100.0%
db.replica31ms
99.92%
Last checked 23 s ago · 60 s interval
Monitor overview
auth.serviceDown

https://auth.example.com/health

GETEvery 1 minTimeout 10sSSL on
Check log
TimeCodeResponse
10:23 PM5031245 ms
10:21 PM503987 ms
10:18 PM0—
9:41 PM5031102 ms
8:55 PM200108 ms
Recent activity8 events
8 events
✓
Recoveredapi.production

api.production.example.com

2m

×
↓
Went downauth.service

auth.service.example.com

14m

×
✓
Recoveredapp.production

app.production.example.com

1h

×
↓
Went downauth.service

auth.service.example.com

1h

×
✓
Recoveredcdn.assets

cdn.assets.example.com

3h

×
✓
Recovereddb.replica

db.replica.example.com

5h

×
  • Checks every 60 s
  • Email alerts on transition
  • Public status pages

Why it matters

Downtime is silent until it’s too late.

01

Your users know before you do.

By the time a complaint lands in your inbox, many more visitors have already bounced. The gap between outage and awareness is where you lose people.

02

Every minute has a measurable cost.

Downtime during peak hours means failed checkouts, dropped signups, and lost payments — happening in real time while you’re looking at something else.

03

Recovery starts with awareness.

You can’t fix what you don’t know is broken. The faster the alert reaches you, the faster your users get back on track — and the less damage there is to explain.

A look inside

From overview to detail

01Dashboard
DashboardAll operational

Total

5

Up

4

Down

1

•

api.production

Up

api.example.com

100%112ms2m ago
•

auth.service

Down

auth.example.com

97%—2m ago
•

cdn.assets

Up

cdn.example.com

99%14ms2m ago
5 monitors · 4 up · 1 down
02Dashboard → auth.service
Monitor overview
auth.serviceDown

https://auth.example.com/health

GETEvery 1 minTimeout 10sSSL on

97.4%

Uptime

1.2 s

Avg resp

3

Incidents

✓

SSL

Check log
TimeCodeResponse
10:23 PM5031245 ms
10:21 PM503987 ms
10:18 PM0—
9:41 PM5031102 ms
8:55 PM200108 ms
03Recent activity
Recent activity8 events
8 events
✓
Recoveredapi.production

api.production.example.com

2m

×
↓
Went downauth.service

auth.service.example.com

14m

×
✓
Recoveredapp.production

app.production.example.com

1h

×
↓
Went downauth.service

auth.service.example.com

1h

×
✓
Recoveredcdn.assets

cdn.assets.example.com

3h

×
✓
Recovereddb.replica

db.replica.example.com

5h

×
Last 7 days of status changes
01

Continuous checks

Every monitor runs on a 60-second cycle. HTTP status codes, response times, and SSL — checked without gaps.

02

Transition alerts

Notifications fire exactly once per state change — no spam when a service is flapping. Up is quiet; down is loud.

03

Public status pages

Each monitor gets a shareable status page. Give your team or customers a live view — no login required.

04

Early warning alerts

Detects sustained response-time slowdowns before they become outages. Learns each site’s normal baseline, then sends one warning when latency stays well above normal across several checks; the episode only ends after a clear recovery, so your inbox is not flooded by repeat alerts.

UPG MonitorSign in →