problemranger
Every endpoint matters.
Check HTTP and HTTPS services. Keep response times, status codes, and check history together.
Available nowMEET PROBLEMRANGER A clearer view of your uptime Know before
Know before
your users do.
Stay a step ahead.
From the first slow response to the full incident story. Monitor your services, cut through the noise, and keep your team in the know.
Your infrastructure. Your workspace. Your peace of mind.
ILLUSTRATIVE PROBE NETWORK
Frankfurt selected · sample network Websites, APIs & services Built for distributed probes API-first by design Private workspaces
LESS NOISE. MORE SIGNAL.
Your entire operation.
One clear picture.
Find the signal in seconds. See what’s healthy, understand what changed, and know where to look next.
Acme infrastructure / Overview
Everything is looking good.
A little peace of mind for your infrastructure.
Monitors up24 / 24All systems healthy
Overall uptime99.98%Sample rolling availability
Avg. response time134 msWithin expected range
Active incidents0You’re all clear
Response time · 42 demo checks Sample
Earlier checksLatest check
Production API100.00%
Marketing website100.00%
Checkout service99.94%
All three regions returned HTTP 200.#001
BUILT AROUND YOUR UPTIME
Small details.
A bigger perspective.
Connected tools for the complete journey,
from a check to a confident response.
A second opinion. By design.
Connect independent probes and compare results across regions before declaring an outage.
Connect your probesFrom failure to context.
Track confirmed failures, acknowledge incidents, and follow the timeline through recovery.
Available nowThe right signal. The right person.
A focused incident queue keeps your response visible. Provider delivery and on-call rotations are planned.
Incident queue availableKeep everyone in the loop.
Create a clean service status page from your monitors, with health and incident history.
Available nowFits the way you build.
Create monitors, retrieve results, and manage incidents through the same versioned API the app uses.
Available nowCALM WHEN IT COUNTS
Don’t just spot a problem.
Understand its story.
A failed check is only the beginning. See the evidence, track your response, and keep a clear record of what happened.
Explore incident responseEXAMPLE · CHECKOUT API
Multi-region failure confirmed
Two of three probes report HTTP 503.
Incident opened
Checkout API · high severity
On-call responder notified
Primary escalation policy applied.
Acknowledged
Investigation started by the response team.
Service recovered
Three consecutive healthy checks.
POST /api/v1/monitors
curl "$PROBLEMRANGER_URL/api/v1/monitors" \
-H "Authorization: Bearer $API_KEY" \
-H "Content-Type: application/json" \
-d '{
"workspace_id": "your-workspace-id",
"name": "Production API",
"url": "https://api.example.com/health",
"interval_seconds": 60,
"expected_status": 200
}'AUTOMATION, WITHOUT THE FRICTION
Your monitoring.
In your workflow.
Provision monitors from a deployment pipeline. Pull check results into your own tools. Bring operational context wherever your team works.
Read the API documentationA FEW GOOD QUESTIONS
A little more clarity.
What can I monitor today?
This initial release supports real HTTP and HTTPS checks, persisted history, incident acknowledgement, private workspaces, API keys and service status pages. The demo is clearly labelled and separate from your real monitors.
Are the global probe regions already running?
The globe demonstrates the distributed monitoring model. No named global probe fleet is pre-provisioned. You can register your own independently hosted probe agents; only connected agents appear in the real workspace.
How does sign-in work?
ProblemRanger uses secure, database-backed Google and GitHub sign-in. Workspace membership is verified on the server for every protected operation.
Can I run checks continuously?
Yes, with a connected probe agent. Download the provided Python agent from Documentation and run it on an always-on host. Without a connected agent you can run on-demand checks; the interface does not imply background monitoring is active.
Is this the complete self-hosted edition?
This Hostinger edition uses persistent MySQL storage and database-backed OAuth sessions. Team management, enterprise identity, on-call rotations and notification integrations remain additional work. See the deployment notes for the exact scope.
A little less uncertainty.
A lot more peace of mind.
Give your services the attention they deserve.