PulseDeck

loading live data · checked 22d ago · probes ~1m

Everything I ship,
monitored in public.

PulseDeck is a status page I built and operate like production: a scheduled prober checks my sites around the clock, stores every result in git, and files an incident automatically when something goes down.

How it worksSource code

All systems operational

Snapshot data · checked 22d ago · probes ~1m (measured)

last probe 28 Sept 2026, 4:18 pm

Incident log

Services

bundled snapshot

Portfolio

Operational

faizanxbuilds.github.io

90.00% uptime · 30d446 ms avg

GREET Teacher Training College

Operational

greetteachertrainingcollege.in

100.00% uptime · 30d1228 ms avg

DeployWatch

No data yet

faizanxbuilds.github.io/DeployWatch/

collecting data—

GitHub API

Operational

api.github.com/zen

100.00% uptime · 30d754 ms avg

Google Edge

Operational

www.google.com/generate_204

100.00% uptime · 30d551 ms avg

Don't take my word for it

10 checks recorded over 23 days. The last few probe times, straight from the data this page renders:

  • 28 Sept 2026, 4:18 pm
  • 28 Sept 2026, 4:17 pm
  • 28 Sept 2026, 4:16 pm
  • 28 Sept 2026, 4:16 pm
  • 28 Sept 2026, 4:15 pm
  • 28 Sept 2026, 4:14 pm
  • 28 Sept 2026, 4:13 pm
  • 28 Sept 2026, 4:12 pm
Workflow runs ↗Probe commits ↗Raw probe data ↗

Why a status page?

Anyone can claim “I know monitoring.” This page is the receipts: real probes, real latency numbers, real incident history — running on a schedule, with the pipeline visible in the repo. It’s the same loop I’d run on day one as a Cloud/DevOps engineer: observe → alert → investigate → document.

See the pipeline behind this page →