Product
Latensy is not just uptime monitoring. It is signal-first monitoring: uptime, latency, incident confirmation, service context, and reporting in one focused workspace.
A real-time overview of infrastructure health.
See 24-hour downtime and degraded time, active incidents, confirmed incidents, and at-risk services in one place. Add a service, add an alert channel, run checks on demand, or resolve an incident without leaving the view. Answer "is anything important happening right now?" in seconds.
Every critical check, organized.
Websites, APIs, cron jobs, feeds, servers, and internal tools listed with status, type, tags, uptime percentage, average latency, last check, last incident, and a response-time trend. Filter by status or tag. Services are not just URLs; they are operational assets with owners and impact.
Latency and degradation, not just up or down.
Response-time trends with average, P95, and max latency per service, high-latency and flapping detection in Mission Control, SLA compliance against a 99.9% target, and TLS and redirect details captured with every check.
Read moreConfirm what matters. Resolve with context.
Consecutive-failure rules per service, confidence levels from suspected to confirmed, severity, cause, duration, and a timeline. Maintenance windows keep planned work from becoming incidents.
Read moreService health your stakeholders can read.
Executive Summary with uptime, incidents, time to detect and recover, impact minutes, and revenue at risk; Impact Report for downtime, degraded time, and affected services; scheduled daily, weekly, or monthly report emails; CSV or JSON export.
Read moreRoute attention to the right people.
Invite your team with owner, admin, member, and viewer roles. Tag services by client, environment, owner, or service type, and mark criticality as revenue, customer-facing, or internal so incidents are ranked by business impact.
The right signal in the right channel.
Alert channels for email, Slack, and webhooks. Send a test alert to any channel before you rely on it. Alerts fire when an incident is confirmed and when it recovers.
Planned work is not an incident.
Schedule maintenance for all services or specific ones. Checks that run inside a window are skipped for incident detection, so your team is not paged for a deploy they planned.
Communicate outward, on your terms.
Public status pages with their own title, description, and URL, listing only the services you choose, with optional 24-hour history, incident messages in Markdown, and upcoming maintenance. Embed SVG status, uptime, or response-time badges anywhere.
Status data where you need it.
A public, rate-limited JSON API returns each status page’s monitors, 24-hour uptime, average response time, incidents, and maintenance windows for your own dashboards and integrations.
Your checks, your data.
Export check results, incidents, and monitor configurations as CSV or JSON for any date range, to share, analyze, or archive beyond the app.
Mission Control on any screen.
Latensy installs as an app on desktop and mobile, so the operating view is one tap away during an incident.
A closer look
Illustrated with example data. The layout, states, and vocabulary are the product's own.
Services
northwind.com
HTTP
Checkout API
REST API
Product feed (EU)
Keyword
Nightly inventory sync
Cron
northwind.com certificate
SSL
Staging API
GraphQL
Services. Status, type, tags, uptime, latency, last check, trend. Filtered to one client.
Northwind Status
Live service status for Northwind Retail
Resolved incident
Checkout API returned errors
Elevated error rates between 14:04 and 14:10 UTC. The upstream payment provider recovered; no orders were lost.
Scheduled maintenance
Database upgrade
20 Jan, 02:00 to 04:00 UTC. Checkout API and Client portal may be briefly unavailable.
Public status page. 24-hour history per service, resolved incidents with a public message, scheduled maintenance.
#ops-alerts
Slack · today
Latensy APP 14:04
Incident confirmed: Checkout API is down
Latensy APP 14:10
Recovered: Checkout API is up
Alert channels
Notifications. Confirmed and recovered alerts in Slack, email, and webhook channels, each testable.
Teams & Tags
38 services · 4 team membersCriticality
Tags
Ranked by impact when something fails
Teams & Tags. Criticality, impact tags, client and environment tags, and the ranking they produce.
Check configuration
Each monitor carries its own interval, request shape, confirmation rule, and business context. Nothing is global by accident.
Heartbeats, badges, and APIInterval and timeout
Per-monitor check interval (5 min on Free, down to 30 s for priority monitors) and request timeout.
Request shape
GET, HEAD, POST, PUT, PATCH, DELETE, or OPTIONS, with custom headers and a request body.
Redirects and TLS
Follow redirects or not; verify certificates or not. Redirect count, final URL, and TLS version are recorded.
Keyword rules
The response must contain, or must not contain, a given string.
DNS expectations
A, AAAA, CNAME, MX, or TXT lookups compared against an expected value.
Expiry windows
Warn N days before a domain expires; set a grace period before a late heartbeat counts as missed.
Confirmation rules
How many consecutive failures open an incident, and how many successes close it.
Business context
Criticality (revenue, customer-facing, internal), an impact tag such as checkout, login, payment, search, or admin, tags, groups, and favorites.
Revenue per minute
Optional. Powers the revenue-at-risk figure in the Executive Summary.
Pause and resume
Pause a monitor during migrations without deleting its history.
Check types
Each monitor has its own interval, consecutive-failure rule, tags, and criticality.
HTTP / HTTPS
Status code, response time, redirects, final URL.
Keyword
Page must (or must not) contain a string.
SSL certificate
Completes a TLS handshake: catches invalid or expired certificates and records the TLS version.
DNS
Resolve a record type and compare the value.
Port (TCP)
Connect to a host and port within a timeout.
Ping
Basic reachability for hosts and devices.
Domain expiration
WHOIS-based expiry date for the registrable domain.
Cron / heartbeat
Your job pings a URL; alert when it goes quiet.
REST API
Authenticated requests, including OAuth token refresh.
GraphQL
Run a query and validate the response.
WebSocket
Open a connection and confirm the handshake.
Database
TCP reachability of the host and port. Credentials are never used.
Add up to 10 monitors on the Free plan, connect an alert channel, and see your first service-health signals today. No credit card required.
