DownRightNow Echo
Your users already told us what's broken. Hear it first.
Echo turns real user reports into one clean outage signal for your own product and your competitors. See what is down, where, on which devices and why, through one API, webhooks, or your AI agent.
Free test key, no card needed. REST · Webhooks · MCP
Competitor intelligence
See what's frustrating your competitors' users, live and across their full outage history.
Rich status signal
Know which countries are hit, which issues users face, how many people report them, and on what devices.
Alerts that close the loop
Webhooks fire on outage, degraded and recovered, so you hear when it breaks and when it is fixed.
Built for AI agents
Plug your AI tools straight into live outage data with MCP, with no integration work.
How it works
From a frustrated user to a clear signal in your stack, in three steps.
- 1
Users report what they hit
People tell us what is wrong in their own words: cannot log in, order not placed, payment failing. Each report carries the issue, device and country.
- 2
Echo turns reports into one signal
Reports are grouped by service and compared with independent probes, so you get a state, a top issue and a count, not a pile of tweets.
- 3
You get it where you work
Pull it over REST, receive it by webhook, or just ask your AI agent. Same data, same API key.
One call, the whole picture
Here the crowd says DOWN while the probe still says OK, which is why the response marks the signal as divergent. The status page would have shown green.
curl "https://api.downrightnow.in/v1/status?domain=paynest.com" \
-H "Authorization: Bearer drn_live_..."{
"status": "success",
"data": {
"domain": "paynest.com",
"service_name": "Paynest",
"state": "DOWN",
"probe_state": "OK",
"signals": { "divergent": true },
"top_issue": { "label": "Can't log in", "severity": "down", "count": 214 },
"user_reports_last_15m": 72,
"user_reports_last_24h": 295,
"telemetry": {
"window": "24h",
"devices": [
{ "type": "android", "count": 206 },
{ "type": "ios", "count": 63 },
{ "type": "desktop", "count": 26 }
],
"countries": [
{ "code": "IN", "count": 142 },
{ "code": "US", "count": 61 },
{ "code": "GB", "count": 37 }
]
}
}
}Illustrative example with sample data, not a live capture.
Built for the people who answer to uptime
Engineering & operations
Know before your tickets do
Users notice problems before any monitor fires. Get a webhook when your own service, or a vendor you depend on, starts failing, and again when it recovers.
Ask your agent: “Is anything we depend on having problems right now?”
Marketing & growth
Aim your messaging at their pain
See what your competitors' users are actually frustrated about, then say the opposite: “Never get locked out.”
Ask your agent: “What are my competitors' users complaining about?”
Product & support
Fix what users really hit
Real issue labels and counts show where the friction is. Listening to actual issues, not assumptions, is how satisfaction goes up.
Ask your agent: “What are the top issues users report for our app this week?”
MCP for AI agents
Connect Cursor, Claude, VS Code, and other MCP clients to live outage data with the same drn_live_ key as REST. Setup prompts, JSON configs, and tool reference live in the documentation.
How the data works
What goes into a signal, so you know what you are building on.
Real users, not guesses
Every signal starts with a report from a person who hit a problem, labelled by issue, device and country.
Probes as a second opinion
Echo also checks the service itself. When the crowd says DOWN and the probe says OK, the response flags it as divergent. That is often exactly the failure a status page misses.
Rolling windows
Counts are given for the last 15 minutes and the last 24 hours, so you can tell a fresh spike from a long-running problem.
Clear limits
Usage is metered in API units per day. Go over and you get a clear 429 response, never a silent failure.
Pricing
Two plans. Enterprise includes everything in Pro. Yearly billing saves 15%. All prices in USD; applicable taxes (e.g. GST) added at checkout.
Echo Pro
$199/mo
- Live status, telemetry, MCP
- Webhooks + all-clear (recovered)
- Monitor up to 10 competitor domains
- 50,000 API units / day
$199/mo
USD via Dodo · recurring billing · live API key shown once after checkout
Echo Enterprise
$799/mo
- Everything in Pro
- Up to 50 competitor domains
- Bulk checks + 24h outage timeline
- 250,000 API units / day
$799/mo
USD via Dodo · recurring billing · live API key shown once after checkout
Paid plans renew automatically and are billed in USD; manage billing in your Echo account.
Questions
What is an API unit?
A status request costs 1 unit. A bulk request costs 1 unit per domain it checks. Pro includes 50,000 units a day and Enterprise 250,000.
What happens if I hit the daily limit?
Requests return HTTP 429 with a RATE_LIMITED error and a Retry-After header until the next daily window. Nothing fails silently.
Can I try it before paying?
Yes. The documentation playground gives you a free test key with 50 requests a day for the status and trending endpoints.
What do the webhooks send, and how often?
One POST per event: outage, degraded or recovered. The same event for the same domain is not sent again for 10 minutes, so you do not get paged repeatedly. Pro covers up to 10 competitor domains and Enterprise up to 50.
What is Enterprise adding over Pro?
Up to 50 competitor domains, bulk checks across many domains in one call, a 24-hour outage timeline and 250,000 units a day.
Can I cancel? How does billing work?
Plans renew automatically and are billed in USD. You can switch plan, change interval or cancel anytime from your Echo account.
I have questions about coverage, data freshness, security or invoicing.
Ask us using the form below or email partnerships@downrightnow.in. We reply within 24 hours.
Talk to us
We move quick. Tell us what you want to monitor and we will get back to you within 24 hours.
Prefer email? partnerships@downrightnow.in