How It Works

This site answers one question: is UVLe down right now. The answer comes from a single repeated measurement, so most of "how it works" is knowing exactly what that measurement sees and what it misses.

---

The check

Our server sends a GET request to https://uvle.upd.edu.ph/ about every 30 seconds, the same request your browser makes when you open UVLe. Each interval gets a few seconds of random jitter so the checks land slightly off-rhythm. A check records three things: the HTTP status code (we expect 200), the response time in milliseconds, and whether the request errored or timed out. It gives up waiting after 60 seconds.

Three buckets

• 🟢 Operational — answered 200 in under 7 seconds
• 🟡 Degraded — answered 200 in 7 seconds or more
• 🔴 Down — any other status code, a connection error, or a timeout

The 7-second line came from actually using UVLe during deadline weeks. Past that point a page feels broken even when it eventually loads, which is usually what's happening when the whole college submits at 11:58 PM.

The big answer

The Oo / Hindi / Mabagal on the homepage reflects the single most recent check. One failed check flips it to Oo; the next successful one flips it back. It's twitchy on purpose, since "right now" is the question you came to ask.

The 24-hour chart

Each bar is one hour, roughly 120 checks. Two things matter for reading it:

• Uptime is weighted. Operational checks count fully, degraded checks count 75%, down checks count zero. An hour where UVLe crawled scores below a clean hour even though every request technically succeeded.
• Each bar is a timeline. Checks are grouped into chronological runs of the same status, so a 10-minute outage shows as a red slice in the middle of the bar instead of disappearing into an average.

The response time in the tooltip is the hour's average. Gray bars are hours where our server wasn't watching.

Incidents

The first failed check opens an incident, and it stays open, counting consecutive failures, until a check succeeds. Every outage gets a start, an end, and a duration. "UVLe was down for 23 minutes last night" is a measurement we can pull up.

Freshness

The server recomputes the dashboard every 15 seconds and your browser refetches it every 30 while the page is open. What you see is at most about 45 seconds behind reality.

What this can't tell you

We check from one server in one location, so a network problem between us and UP Diliman looks identical to UVLe being down. We also only test that the front page loads. Logging in, opening a course, uploading a file — those can all break while our check stays green.

This is an independent student project. It has no affiliation with UP or the ILC, and the official announcements remain the record. We just measure the front door, every 30 seconds, around the clock.