Kestrel Uptime is a fictional company we audit; names of other companies are replaced
SAYLENT · THE SUMMARY · 10 Sept 2026 · SNAPSHOT (single run)
Recommended in 0 of 11 scored answers, and mentioned in 0 of 11. First move: Unblock the AI crawlers your buyers' engines depend on.
In the 4 answers to questions that name you, the engines back you in 1.
In the 8 head-to-head answers, the engines name you in 4 and recommend you in none.
Every number opens its receipt: the exact saved answer it came from.
This run: 24 asked · 23 answered · 1 engine failure · 11 scored. How to read the numbers: every count here is out of the scored answers, the what-to-buy and problem questions, one answer per question and engine. Branded and head-to-head questions are counted separately and labelled wherever they appear.
The quotes in this report are verbatim outputs the named AI engines (gpt-5.4 · claude-sonnet-4-6 · gemini-3.6-flash · sonar) generated on the dates shown, in response to Saylent's standardized prompts. They document what each AI said. They are not statements of fact by Saylent, and AI systems can state inaccurate things about real companies.
Measured across ChatGPT, Claude, Gemini, Perplexity on 10 Sept 2026: 24 asked · 23 answered · 1 engine failure · 11 scored.How we measure →
How engines could describe you: Reduces false alarms through multi-region agreement before paging · Customers learn about outages from status page, not support queue · Automatically updated status pages that never disagree with reality · Automatic escalation and acknowledgement tracking · Deploy markers and response time trends on alerts · +1 more
You lose every head-to-head answer: 0 of 8 recommend Kestrel Uptime. Upcheck owns the share of voice: 17 mentions to your 3. One gate is costing you: robots: PerplexityBot, blocked. blocking removes perplexity citation eligibility within hours-days
Recommended in 0 of 11 scored answers. One draw per question and engine on this profile, so this is a count, not a measured range.
Your gap is buyers ask what to buy. The engines don't surface you at all there. Click a stage to read those answers.
What we found · your 3 moves
Each engine builds its answers from a different corner of the web. The counts are citations on this run. The sources you have to win are the ones the engines already trust.
answers from a scattered mix of sources.
builds answers from best-of listicles.
builds answers from best-of listicles.
builds answers from best-of listicles.
45% of the pages behind these answers are best-of listicles. You appear on 0 of the 5 we could verify.
The divergence that matters: Claude leans on best-of listicles: where you're absent.
11 pages cited · 5 listicles · 3 comparisons · 3 other pages. You appear on 0 of the 11. 6 of them sit on a rival's own domain.
Upcheck is on 9 of the 11 pages behind these answers we could verify; you're on 0.
4 pages 2+ engines trust: you're absent from all 4. Two or more engines cite each one. A listing here moves several engines at once.
| Cited× | Source | You | Competitors on page |
|---|---|---|---|
| 9 | 11 Best Uptime Monitoring Tools in 2026 (Ranked & Compared) - Upcheck Knowledge Hub listiclegemini×3perplexity×2claude×4upcheck.example | Rival's own site (Upcheck) | Upcheck, Beacon Uptime |
| 6 | 5 Best Uptime Monitoring Tools in 2026 listicleclaude×3perplexity×3fastbeacon.example | Rival's own site (Beacon Uptime) | Upcheck, Beacon Uptime |
| 5 | 10 Best Uptime Monitoring Tools for 2026 - Livecheck listicleclaude×3gemini×1perplexity×1livecheck.example | ABSENT | Upcheck, Beacon Uptime |
| 4 | The 7 Best Uptime Monitoring Tools in 2026: I Tested Each | Umberhollow listicleclaude×1gemini×2perplexity×1umberhollow.example | ABSENT | Upcheck, Beacon Uptime |
| 4 | Plans & Pricing | Upcheck otherchatgpt×4upcheck.example | Rival's own site (Upcheck) | Upcheck |
| 3 | Beacon Uptime vs Upcheck: A Complete Comparison for 2026 | Beacon Uptime Community comparisonclaude×1gemini×1perplexity×1beacon-uptime.example | Rival's own site (Beacon Uptime) | Upcheck, Beacon Uptime |
| 3 | The 11 Best Website Uptime Monitoring Tools Compared (2026) listicleclaude×2perplexity×1brighthollow.example | ABSENT | Upcheck, Beacon Uptime |
| 3 | beaconuptime vs Upcheck: 2026 Comparison — Quiethollow comparisonclaude×1gemini×1perplexity×1quiethollow.example | ABSENT | Upcheck |
| 3 | Cost-effective alternative to beaconuptime | Upcheck comparisongemini×1perplexity×2upcheck.example | Rival's own site (Upcheck) | Upcheck |
| 2 | Pricing | Beacon Uptime otherchatgpt×2beacon-uptime.example | Rival's own site (Beacon Uptime) | Beacon Uptime |
| 2 | Silverhollow – Pricing otherchatgpt×2silverhollow.example | ABSENT | — |
5 of the 6 questions have a single page that beats you: the one page the engines read instead, where a listing moves the answer. The other 1 either name you already or spread across too many sources to point at one.
| Q | Question | The page beating you | Engines | Rivals on page |
|---|---|---|---|---|
| q01 | What is the best Uptime monitoring and status pages for small engineering teams without dedicated monitoring staff? | 10 Best Uptime Monitoring Tools for 2026 - Livecheck livecheck.example | 3 | Upcheck, Beacon Uptime |
| q02 | Top Uptime monitoring and status pages options in 2026 — which do you recommend? | 10 Best Uptime Monitoring Tools for 2026 - Livecheck livecheck.example | 3 | Upcheck, Beacon Uptime |
| q14 | How do I solve: learning about outages from customers instead of monitoring? Which tools or providers help? | 10 Best Uptime Monitoring Tools for 2026 - Livecheck livecheck.example | 3 | Upcheck, Beacon Uptime |
| q09 | Kestrel Uptime vs Upcheck — which is better for small engineering teams without dedicated monitoring staff? | The 7 Best Uptime Monitoring Tools in 2026: I Tested Each | Umberhollow umberhollow.example | 3 | Upcheck, Beacon Uptime |
| q10 | Beacon Uptime vs Upcheck: which would you pick for small engineering teams without dedicated monitoring staff? | beaconuptime vs Upcheck: 2026 Comparison — Quiethollow quiethollow.example | 3 | Upcheck |
Entity clarity
Claude confused you with a different ‘Kestrel Uptime’ in 2 answers (an entity-clarity problem).
Gemini confused you with a different ‘Kestrel Uptime’ in 2 answers (an entity-clarity problem).
Perplexity confused you with a different ‘Kestrel Uptime’ in 1 answer (an entity-clarity problem).
| Question ID | Question | Verdict by engine |
|---|---|---|
| q01 | What is the best Uptime monitoring and status pages for small engineering teams without dedicated monitoring staff? “For small engineering teams without dedicated monitoring staff, my default recommendation is: Best overall: Beacon Uptime
It’s the strongest all-in-one option if you want uptime checks, alerting, incident ” | Perplexity · no answer |
| q02 | Top Uptime monitoring and status pages options in 2026 — which do you recommend? “As of September 10, 2026, my practical shortlist is: 1. Beacon Uptime — best overall for most software teams 2. Upcheck — best budget-friendly all-rounder 3. Boardline Broadcastpage — best enterprise” | |
| q09 | Kestrel Uptime vs Upcheck — which is better for small engineering teams without dedicated monitoring staff? “If by “Kestrel Uptime” you mean Kestrel’s incident-response / platform-engineering automation product, then for a small engineering team without dedicated monitoring staff…” | |
| q10 | Beacon Uptime vs Upcheck: which would you pick for small engineering teams without dedicated monitoring staff? “For small engineering teams without dedicated monitoring staff, I’d usually pick Beacon Uptime. ([beacon-uptime.example](https://beacon-uptime.example/pricing?utm_source=openai)) Why: teams like that usually don’t just n” | |
| q14 | How do I solve: learning about outages from customers instead of monitoring? Which tools or providers help? “The fix is not “buy one monitoring tool.” It’s to build a detection stack so you learn about failures before customers do: 1. External synthetic checks for uptime and critical flows 2. Internal telem” | |
| q18 | What is Kestrel Uptime? Is it any good? “I couldn’t find a well-established, clearly documented product called “Kestrel Uptime” by that exact name. Search results were mostly unrelated “Kestrel” products, plus a couple of status/monitoring pages, which suggests it may be a very new,…” |
absent: not in the answer at all · compared: named in a comparison, not recommended · neutral: named without a steer · recommended: the engine tells the buyer to pick you · dismissed: named and ruled out · no answer: the call returned nothing
1 of the 24 calls returned no answer (an engine error or an empty response), so they are counted nowhere below.
5 answers are about a different company that shares your name. Everything mined from them carries a badge below, and Entity clarity above explains them.
Tone in the 8 answers that name you, across every question type: positive ×1 · neutral ×4 · negative ×3 (5 of those 8 are about a different company that shares the name Kestrel Uptime (see entity clarity).)
Where you land in the answer: named first ×4 · named early ×2
Mentioned but framed weakly: 2 answers (a mention that doesn't sell you is rented ground).
What the engines say about Kestrel Uptime, grouped by how it lands with a buyer. We show what was said; we don't guess what's true. A false claim is a fix-worthy finding.
Counted over every answer this run collected, scored or not: an answer counts when it lists, compares or recommends the name. The summary's “of 11” counts scored answers only.
| Brand or competitor | Share of mentions | Mentions |
|---|---|---|
| Upcheck | 17 | |
| Beacon Uptime | 15 | |
| Boardline Broadcastpage | 5 | |
| Pingwatch | 5 | |
| Statusly | 5 | |
| Fastbeacon | 4 | |
| Quickstatus | 4 | |
| Kestrel Uptime | 3 | |
| Beacon Live | 2 | |
| Escalytics | 2 | |
| Falconware AI | 2 | |
| Hawkeye Monitor | 2 | |
| Perchfeed's Talonqueue (message queue) | 2 |
In the 17 answers that skip you, these rivals keep appearing, and here's the engines' stated reason why.
Engines make you the default for: teams with multi-step incident remediation, repetitive cloud/CI/CD/ops work, or need for AI-assisted operational workflows, Wants on-call rotation, richer incident handling, or more structured team workflows.
When a buyer fits a specific profile, the engines steer them to a rival. Here's the segment, the rival, and the engines' stated reason.
+5 more rivals were steered a single segment each: see the stored answers.
204 citations to 94 domains across 21 of the 23 answers. The most-cited domain type is blog / editorial: 76 of them (37%).
Domains the answers cite when they name a rival and not you (non-branded questions only), where we did not find you on any page we read. Ranked by how many of those answers cite them. A listing, review or mention here is the off-site move with the most receipts behind it.
Cited in 4 answers that name Beacon Uptime, Upcheck and 11 others and not you, across 3 engines and 2 questions. We read 1 page on it: Upcheck and Beacon Uptime are there, you are not.
Cited in 3 answers that name Beacon Uptime and Upcheck and not you, across 3 engines and 1 question. We read 1 page on it: Upcheck is there, you are not.
Cited in 3 answers that name Beacon Uptime, Upcheck and 6 others and not you, across 2 engines and 2 questions.
Cited in 3 answers that name Upcheck, Beacon Uptime and 6 others and not you, across 2 engines and 2 questions. We read 1 page on it: Upcheck and Beacon Uptime are there, you are not.
Cited in 3 answers that name Beacon Uptime, Statusly and 10 others and not you, across 2 engines and 2 questions. We read 1 page on it: Upcheck and Beacon Uptime are there, you are not.
| Domain | Type | Citations | Skip you | Name you | ChatGPT | Claude | Gemini | Perplexity |
|---|---|---|---|---|---|---|---|---|
Rival's site | Rival's site | 2412% | 12 | 5 | 4 | 6 | 5 | 9 |
Rival's site | Rival's site | 147% | 7 | 1 | 1 | 5 | 1 | 7 |
Rival's site | Rival's site | 105% | 8 | · | 6 | 2 | 1 | 1 |
Blog / editorial | Blog / editorial | 63% | 4 | 1 | · | 3 | 1 | 2 |
Docs / help | Docs / help | 63% | 1 | 3 | · | 3 | 1 | 2 |
Other | Other | 52% | 2 | 1 | · | 2 | 2 | 1 |
Blog / editorial | Blog / editorial | 42% | 3 | 1 | · | · | 1 | 3 |
Blog / editorial | Blog / editorial | 42% | 3 | 2 | · | 1 | 2 | 1 |
Blog / editorial | Blog / editorial | 42% | 2 | 1 | · | 1 | · | 3 |
Rival's site | Rival's site | 42% | 1 | 3 | 1 | · | 2 | 1 |
Answers naming each brand, split by engine. You count when the judge found you in the answer; a rival counts when the answer lists it among the options it prefers. Open a count for the answers behind it.
| Brand | Named in | Recommended | ChatGPT | Claude | Gemini | Perplexity |
|---|---|---|---|---|---|---|
Upcheck | · | 5 | 4 | 5 | 3 | |
Beacon Uptime | · | 6 | 3 | 3 | 3 | |
Kestrel Uptime | 1 | 2 | 2 | 2 | 2 | |
Boardline Broadcastpage | · | 3 | 1 | 1 | · | |
Pingwatch | · | 2 | 1 | 1 | 1 | |
Statusly | · | · | 3 | 1 | 1 | |
Fastbeacon | · | 1 | 1 | 1 | 1 | |
Quickstatus | · | 2 | 1 | 1 | · | |
Escalytics | · | 1 | · | · | 1 | |
Falconware AI | · | · | 1 | 1 | · |
Counted once per question and engine, over the answer this report shows. A domain's type comes from a short public rule list (hover a type to see the rule that fired); set your own with sources.domainTypes in saylent.config or the brand's run options in the app.
We read saylent-kestrel.vercel.app's robots.txt on 10 Sept 2026: PerplexityBot is blocked. blocking removes Perplexity citation eligibility within hours-days
2 fail · 3 warn · 2 info · 16 pass of 23 checks
Both rows are true for PerplexityBot and ClaudeBot: your server answers us, and robots.txt tells the crawler not to ask. The crawler obeys robots.txt, so the page is never fetched.
| Status | Check | Detail |
|---|---|---|
| fail | robots: PerplexityBot | blocked. blocking removes Perplexity citation eligibility within hours-days |
| fail | JSON-LD Organization | No Organization schema found on any crawled page. Engines can't resolve who you are. |
| warn | robots: ClaudeBot | blocked. feeds future Anthropic model weights; blocking is a legitimate choice |
| warn | JSON-LD Product | No Product schema found on crawled pages. |
| warn | JSON-LD FAQPage | No FAQPage schema found on crawled pages. |
| info | robots: Google-Extended | not mentioned. Note: it is a Gemini-training opt-out token only, not a crawler. |
| info | live-fetch caveat | IP-verifying CDNs may treat our test differently than real bots; your server logs are ground truth. |
| Status | Check | Detail |
|---|---|---|
| pass | robots: GPTBot | allowed |
| pass | robots: OAI-SearchBot | allowed |
| pass | robots: Claude-SearchBot | allowed |
| pass | robots: Bingbot | allowed |
| pass | robots: ChatGPT-User | allowed |
| pass | robots: Claude-User | allowed |
| pass | robots: Perplexity-User | allowed |
| pass | live fetch as OAI-SearchBot | HTTP 200 |
| pass | live fetch as ChatGPT-User | HTTP 200 |
| pass | live fetch as Claude-SearchBot | HTTP 200 |
| pass | live fetch as PerplexityBot | HTTP 200 |
| pass | live fetch as GPTBot | HTTP 200 |
| pass | live fetch as ClaudeBot | HTTP 200 |
| pass | content coverage | Every non-branded question has a matching page (threshold 0.45). |
| pass | homepage entity clarity | "Uptime" appears in the first 800 chars. |
| pass | freshness | No page titles carry years older than 2025. |
Evidence weight is the number on each card. Each fix family starts from a fixed base (crawler access 9.5, a coverage hub 9.0, a source pitch 8.5, wrong claims and entity confusion 7.0, missing schema 5.5, stale titles 4.0). The two source families are re-scored from where this run's citations actually come from, and a pitch gains 0.1 for every citation the target page already has, up to half a point. Higher means more of this run's evidence points at it.
Honest time-to-impact: days–2 weeks (bots recrawl quickly once allowed)
# Allow AI answer-engine crawlers that drive buyer discovery # Add the following lines to your robots.txt file. # Lines beginning with # are comments and are ignored by crawlers. # --- AI answer-engine crawlers (explicitly allowed) --- User-agent: OAI-SearchBot Allow: / User-agent: ChatGPT-User Allow: / User-agent: Claude-SearchBot Allow: / User-agent: Claude-User Allow: / User-agent: PerplexityBot Allow: / User-agent: Perplexity-User Allow: / # --- Optional: uncomment the block(s) below if you also want to allow # training/indexing crawlers (separate from answer-engine access). # Review your content licensing position before enabling. # # User-agent: GPTBot # Allow: / # # User-agent: ClaudeBot # Allow: / # # User-agent: Google-Extended # Allow: / # ---
3-Step Verification Checklist
Step 1 — Confirm the live file is correct
https:///robots.txt directly in a browser or run:curl -s https:///robots.txt | grep -A2 "PerplexityBot\|OAI-SearchBot\|Claude-SearchBot"
Allow: / and no preceding Disallow: / that would override it.allowed for a representative URL.Step 2 — Check your CDN's AI-bot traffic toggle
⚠️ A robots.txt Allow directive is irrelevant if your CDN returns a 403/429/503 before the crawler ever reads the file.
Step 3 — Verify access in your server logs
robots.txt.grep -E "OAI-SearchBot|ChatGPT-User|Claude-SearchBot|Claude-User|PerplexityBot|Perplexity-User" /var/log/nginx/access.log
Why this matters: Evidence shows that blocking PerplexityBot removes citation eligibility from Perplexity's answer engine within hours to days — the same logic applies to every answer-engine crawler listed above. Buyers increasingly discover and evaluate products through AI-generated answers; being uncrawlable means being invisible at that moment.
Honest time-to-impact: hours–days (Perplexity) → 2–4 weeks (Claude) (typical range)
To: [email protected] Subject: Addition suggestion for "5 Best Uptime Monitoring Tools in 2026"
Hi,
Disclosure: We represent Kestrel Uptime and are pitching our own product for inclusion.
Your listicle is cited frequently by AI assistants recommending uptime tools — which is exactly why we'd love a spot on it.
Kestrel Uptime belongs on this list because it automatically keeps status pages in sync with live monitor state, so customers learn about outages from your status page instead of flooding your support queue — a problem free-tier tools don't solve.
Where budget-friendly all-rounders win on price, Kestrel wins on trust: no manually updated status pages, no reality gaps, no support noise.
You can evaluate it directly at saylent-kestrel.vercel.app.
Happy to provide screenshots, a trial account, or any detail that helps.
The Kestrel Uptime team
Honest time-to-impact: hours–days (Perplexity) → 4–8 weeks (Gemini) (typical range)
Honest time-to-impact: hours–days (Perplexity) → 4–8 weeks (Gemini) (typical range)
Honest time-to-impact: hours–days (Perplexity) → 4–8 weeks (Gemini) (typical range)
Honest time-to-impact: hours–days (Perplexity) → 4–8 weeks (Gemini) (typical range)
Same playbook as the pitches above: reuse those drafts, swapping in each outlet's angle and the contact channel listed in the evidence. No separate draft is needed — the pitches above ARE the template for these outlets.
Honest time-to-impact: hours–days (Perplexity) → 2–4 weeks (Claude) (typical range)
Honest time-to-impact: 2–6 weeks (typical range)
Paste-ready JSON-LD for the schema types missing on saylent-kestrel.vercel.app: Organization, Product, FAQPage. Fields come only from your brand model — verify any value marked TODO-VERIFY before shipping; never publish an invented fact.
Organization (add to your homepage <head>):
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Kestrel Uptime",
"url": "https://saylent-kestrel.vercel.app",
"description": "Kestrel Uptime — Uptime monitoring and status pages"
}
</script>Product (add to your main product page):
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Product",
"name": "Uptime monitoring from four global regions",
"brand": {
"@type": "Brand",
"name": "Kestrel Uptime"
},
"url": "https://saylent-kestrel.vercel.app",
"category": "Uptime monitoring and status pages"
}
</script>FAQPage (add to a page that answers buyer questions; replace the TODO-VERIFY answer with a real, sourced sentence):
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is Kestrel Uptime?",
"acceptedAnswer": {
"@type": "Answer",
"text": "TODO-VERIFY: one-sentence description of Kestrel Uptime (Uptime monitoring and status pages)."
}
}
]
}
</script>What this is: the answers 4 AI engines gave to your buyers' questions, the pages those answers were built from, and what we found on each. This run: 24 asked · 23 answered · 1 engine failure · 11 scored. Every number above opens its stored receipt.
1 of the 24 calls returned no answer (an engine error or an empty response), so they are counted nowhere below.
The two labels in the header: the profile is the question set (smoke is the short sample set, full is the complete one), and the judge is who scored the answers (cross-family means every answer was judged by a model from a different provider family, which lowers self-preference bias; single-family means one provider served every role).
What this is not: a guarantee, a ranking factor list, or a delta. One run is a snapshot. We label it. Movement is measured set-vs-set on the same frozen questions, and if nothing moved yet, we say so.
What we won't do: scrape AI apps against their terms, invent "AI search volume", sell you an llms.txt file, or show a before/after gap that's really just luck. Full methodology →
Run this on your own brand
Saylent is the open-source audit of what AI assistants say about your brand, with the receipts. The method is documented at yotambraun.github.io/saylent and every line of it is readable at github.com/yotambraun/saylent.
npx saylent audit <your domain>