Website report
Visit sitehttps://outages.live/
A free live outage feed for your agents: the official status pages of cloud, AI, and developer providers, merged into one live feed with RSS, a JSON API, and an MCP server.
Audit Full discovery audit·Language English (en)·Response HTTP 200·Served by Cloudflare
Analysed Nov 9, 2026 · 15 categories · 101 passed · 23 warnings · 3 issues · 23 informational
Audit score
F53/100
Needs work
- Agentic
- 73
- SEO
- 56
What we found
3Needs a fix23Could be better101Looks good23Informational- 1.Needs a fix: Server response time: needs fixing. see checkFaster pages help visitors reach your content sooner.
- 2.Needs a fix: HTTP redirects to HTTPS: needs fixing. see checkThese protections reduce risks for your website and its visitors.
- 3.Could be better: Your site details do not match. see checkConsistent names and details help AI assistants recognize your website.
- 4.Could be better: Interactive controls have source labels: needs attention. see checkA usable mobile layout helps visitors read and act on your content.
- 5.Could be better: Images are missing size information. see checkDeclared dimensions keep content from jumping while images load.
Built with 3 technologies· detected stack
Read from the public source and response headers of the sampled pages.
How it fits together
NuxtFramework
CloudflareCDN / edge
- CloudflareCDN / edge
- NuxtFramework
- PlausibleAnalytics
A framework or CDN signal describes the public response, not the origin host or private backend.
Site checks
Every observation from the crawl, grouped by what it describes. Open a row for the evidence and the recommended fix.
Metadata1Could be better10Looks good
100/100Could be better: Meta description lengthDescription is 172 characters, over this audit's 160-character review point (a preview heuristic, not a Google limit).
Could be better · Metadata · Review suggested
Observed evidence
Description is 172 characters, over this audit's 160-character review point (a preview heuristic, not a Google limit).
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. It is there, but weaker than this check expects.
Recommended fix
Front-load the useful summary because Google may generate or truncate snippets by query and device.
Looks good: Page title exists
Looks good · Metadata · Measured on your page
Observed evidence
Title found: "outages.live: A free live outage feed for your agents"
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Title length
Looks good · Metadata · Review suggested
Observed evidence
Title is 53 characters, inside this audit's 15–60 review range.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Title says what the site does
Looks good · Metadata · Measured on your page
Observed evidence
Title "outages.live: A free live outage feed for your agents" says more than the site name.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Meta description exists
Looks good · Metadata · Measured on your page
Observed evidence
Meta description found: "A free live outage feed for your agents: the official status pages of cloud, AI, and devel…"
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Titles unique across pages
Looks good · Metadata · Measured on your page
Observed evidence
All 7 indexable sampled pages have distinct titles.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Show 5 more checks
Looks good: Homepage isn't noindexed
Looks good · Metadata · Measured on your page
Observed evidence
No blocking robots meta tag on the homepage.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Character encoding declared
Looks good · Metadata · Measured on your page
Observed evidence
UTF-8 declared in the Content-Type header and a meta tag.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: HTML5 doctype
Looks good · Metadata · Measured on your page
Observed evidence
HTML5 doctype declared.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No meta keywords tag
Looks good · Metadata · Measured on your page
Observed evidence
No obsolete meta keywords tag.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Valid metadata order in <head>
Looks good · Metadata · Measured on your page
Observed evidence
No invalid element interrupts metadata in <head>.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Indexing16Looks good
100/100Looks good: Single canonical declaration
Looks good · Indexing · Measured on your page
Observed evidence
One canonical declaration found.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Noindex and canonical agree
Looks good · Indexing · Measured on your page
Observed evidence
No conflicting noindex and cross-page canonical instructions.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No meta-refresh redirect
Looks good · Indexing · Measured on your page
Observed evidence
No meta-refresh redirect.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No soft-404 response
Looks good · Indexing · Measured on your page
Observed evidence
No soft-404 pattern on sampled HTTP 200 pages.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Canonical target integrity
Looks good · Indexing · Measured on your page
Observed evidence
Canonical is a valid https URL. Its host is checked by the canonical consistency check.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Sampled URLs have aligned indexability signals
Looks good · Indexing · Measured on your page
Observed evidence
Indexability signals align across 8 sampled URL(s).
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Show 10 more checks
Looks good: robots.txt exists
Looks good · Indexing · Measured on your page
Observed evidence
robots.txt responds with 200.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: robots.txt doesn't block everything
Looks good · Indexing · Measured on your page
Observed evidence
The audited URL is allowed for Googlebot. Most specific matching path; allow wins equal-length conflicts.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Sitemap exists
Looks good · Indexing · Measured on your page
Observed evidence
Sitemap found at https://outages.live/sitemap.xml.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Sitemap parses and lists URLs
Looks good · Indexing · Measured on your page
Observed evidence
Sitemap lists 1474 same-origin URLs.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Sitemap declared in robots.txt
Looks good · Indexing · Measured on your page
Observed evidence
robots.txt declares the sitemap.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Canonical URL set
Looks good · Indexing · Measured on your page
Observed evidence
Canonical set: https://outages.live/
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Canonical is absolute and self-referencing
Looks good · Indexing · Measured on your page
Observed evidence
Canonical is absolute and points at this page.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: www vs apex consistency
Looks good · Indexing · Measured on your page
Observed evidence
Hostname is used consistently (outages.live).
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: URLs are readable slugs
Looks good · Indexing · Measured on your page
Observed evidence
URL slugs are readable (22 sampled).
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Sampled pages expose search-access signals
Looks good · Indexing · Measured on your page
Observed evidence
No restrictive search-access signal on 8 sampled page(s). Actual indexing is not verified.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Content1Could be better9Looks good1Informational
100/100Could be better: Text-to-HTML ratioVisible text is 2.5% of the HTML markup (scripts and styles excluded).
Could be better · Content · Review suggested
Observed evidence
Visible text is 2.5% of the HTML markup (scripts and styles excluded).
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. It is there, but weaker than this check expects.
Recommended fix
Text-to-HTML ratio is not a ranking factor, but a very low value often means deeply nested markup or content that only appears after JavaScript runs. Check the source-content checks before changing anything.
Not measured: ReadabilityFlesch reading ease ≈ 30.
Not measured · Content · Not established
Observed evidence
Flesch reading ease ≈ 30.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
60+ reads easily for most visitors. This is a heuristic, not a rule — technical audiences tolerate denser text.
Looks good: Crawlable content in source HTML
Looks good · Content · Measured on your page
Observed evidence
No recognized empty JavaScript application shell on 8 sampled page(s). The entered page exposes 2003 publisher word(s).
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Homepage content volume
Looks good · Content · Measured on your page
Observed evidence
The audited page has about 2003 words of main content.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No placeholder text
Looks good · Content · Measured on your page
Observed evidence
No placeholder text detected on crawled pages.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No starter-template leftovers
Looks good · Content · Measured on your page
Observed evidence
No starter-template artifacts detected.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Show 5 more checks
Looks good: Title and H1 agree
Looks good · Content · Measured on your page
Observed evidence
Title and H1 share topic words: free, live, outage, feed.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Crawled pages aren't near-duplicates
Looks good · Content · Measured on your page
Observed evidence
No near-duplicate main content among 7 indexable sampled pages.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Outbound references
Looks good · Content · Measured on your page
Observed evidence
6 outbound link(s) present.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Discovery copy is distinct across sampled pages
Looks good · Content · Measured on your page
Observed evidence
No repeated description, H1, or publisher copy across 7 sampled pages.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Structured data5Looks good
100/100Looks good: JSON-LD present
Looks good · Structured data · Measured on your page
Observed evidence
4 JSON-LD block(s) found on the homepage.
Why this matters
Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: JSON-LD parses
Looks good · Structured data · Measured on your page
Observed evidence
All 35 JSON-LD block(s) parse cleanly.
Why this matters
Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Organization or WebSite schema
Looks good · Structured data · Measured on your page
Observed evidence
Identity schema present: WebSite, Organization.
Why this matters
Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Content-specific schema
Looks good · Structured data · Measured on your page
Observed evidence
Content schema found: FAQPage, Event, ItemList.
Why this matters
Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Headings1Could be better6Looks good
91/100Could be better: Element IDs are unique per document41 duplicate ID occurrence(s) across 2 document(s).
Could be better · Headings · Measured on your page
Observed evidence
41 duplicate ID occurrence(s) across 2 document(s).
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. It is there, but weaker than this check expects.
Recommended fix
Give each element a unique id and update fragment links and aria-labelledby references to point to the intended element.
Affected pages (2)
- https://outages.live/
- https://outages.live/live
Looks good: H1 exists
Looks good · Headings · Measured on your page
Observed evidence
H1 found: "A free live outage feed for your agents."
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Single H1
Looks good · Headings · Measured on your page
Observed evidence
Exactly one H1 on the homepage.
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Heading levels don't skip
Looks good · Headings · Measured on your page
Observed evidence
Heading hierarchy is sequential across 6 headings.
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: H1 has real text
Looks good · Headings · Measured on your page
Observed evidence
H1 reads "A free live outage feed for your agents.".
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Headings are descriptive
Looks good · Headings · Measured on your page
Observed evidence
6 headings, averaging 3.7 words — descriptive.
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Content is sectioned with H2s
Looks good · Headings · Measured on your page
Observed evidence
4 H2 section(s) structure the page.
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Images2Could be better2Looks good
69/100Could be better: Width/height attributes50 of 50 visible images lack width and height attributes: claude.svg, codex.svg, cursor.svg, ….
Could be better · Images · Review suggested
Observed evidence
50 of 50 visible images lack width and height attributes: claude.svg, codex.svg, cursor.svg, ….
Why this matters
Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. It is there, but weaker than this check expects.
Recommended fix
Set explicit width and height so the browser reserves the space before the image loads. Without them the page shifts as images arrive, which is what Cumulative Layout Shift measures. next/image sets them for you.
Could be better: Modern image formats34 of 34 raster images are served only as PNG or JPEG: sinch.png, telnyx.png, daytona.png, ….
Could be better · Images · Review suggested
Observed evidence
34 of 34 raster images are served only as PNG or JPEG: sinch.png, telnyx.png, daytona.png, ….
Why this matters
Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. It is there, but weaker than this check expects.
Recommended fix
Serve WebP or AVIF versions, which are usually 25–50% smaller at the same quality. Use <picture> with a WebP/AVIF <source> and the original as fallback, or an image CDN or framework image component that converts automatically.
Looks good: Alt text coverage
Looks good · Images · Measured on your page
Observed evidence
All 50 visible images declare alt attributes (including empty alt for decorative images). Whether each description fits its image needs a human look.
Why this matters
Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Lazy loading
Looks good · Images · Measured on your page
Observed evidence
34/50 images are lazy-loaded.
Why this matters
Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Links6Looks good
100/100Looks good: Internal links resolve
Looks good · Links · Measured on your page
Observed evidence
All 12 sampled internal links return < 400.
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Anchor text is meaningful
Looks good · Links · Measured on your page
Observed evidence
56 of 56 links have descriptive text or labels.
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No dead placeholder links
Looks good · Links · Measured on your page
Observed evidence
No placeholder links on the audited page.
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: External links use rel=noopener
Looks good · Links · Measured on your page
Observed evidence
All target="_blank" links carry rel="noopener".
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Homepage links into the site
Looks good · Links · Measured on your page
Observed evidence
Homepage links to 45 distinct internal pages.
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Same-page links have source targets
Looks good · Links · Measured on your page
Observed evidence
1 same-page fragment link(s) have source targets.
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Mobile1Could be better3Looks good2Informational
76/100Could be better: Interactive controls have source labels5 of 982 source controls lack a detectable name.
Could be better · Mobile · Measured on your page
Observed evidence
5 of 982 source controls lack a detectable name.
Why this matters
Google indexes the phone rendering, so that is the version being graded. It is there, but weaker than this check expects.
Recommended fix
Give each control visible text, a connected label, aria-label or aria-labelledby. Placeholder and neighboring text alone do not name an input. Verify the browser accessibility tree after fixing.
Affected pages (2)
- https://outages.live/
- https://outages.live/providers
Not applicable: Responsive image markupNone of the 50 images use srcset.
Not applicable · Mobile · Measured on your page
Observed evidence
None of the 50 images use srcset.
Why this matters
Google indexes the phone rendering, so that is the version being graded. This check does not apply to the features observed in this sample.
Recommended fix
Serve smaller variants to phones with srcset/sizes (next/image handles this) — mobile users shouldn't download desktop-sized images.
Not measured: No tiny inline font sizesNo sub-12px inline font sizes detected; stylesheet rules and rendered sizes were not measured.
Not measured · Mobile · Not established
Observed evidence
No sub-12px inline font sizes detected; stylesheet rules and rendered sizes were not measured.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Check computed font sizes in a browser across mobile widths.
Looks good: Viewport meta tag
Looks good · Mobile · Measured on your page
Observed evidence
Viewport configured: "width=device-width, initial-scale=1".
Why this matters
Google indexes the phone rendering, so that is the version being graded. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Pinch zoom not disabled
Looks good · Mobile · Measured on your page
Observed evidence
The viewport lets users zoom.
Why this matters
Google indexes the phone rendering, so that is the version being graded. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: ARIA references point to source elements
Looks good · Mobile · Measured on your page
Observed evidence
9 ARIA reference(s) resolve within their source documents. Rendered visibility was not tested.
Why this matters
Google indexes the phone rendering, so that is the version being graded. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Language2Looks good1Informational
100/100Not applicable: hreflang syntaxNo hreflang tags — fine for single-language sites.
Not applicable · Language · Measured on your page
Observed evidence
No hreflang tags — fine for single-language sites.
Why this matters
The declared language tells browsers and assistive tech how to read the page and who it is for. This check does not apply to the features observed in this sample.
Recommended fix
Only add hreflang if you publish the same content in multiple languages/regions.
Looks good: html lang attribute
Looks good · Language · Measured on your page
Observed evidence
Language declared: lang="en".
Why this matters
The declared language tells browsers and assistive tech how to read the page and who it is for. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Declared language matches content
Looks good · Language · Measured on your page
Observed evidence
Declared language (en) matches detected content language.
Why this matters
The declared language tells browsers and assistive tech how to read the page and who it is for. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Branding2Looks good2Informational
100/100Not measured: Web app manifestNo web manifest linked.
Not measured · Branding · Not established
Observed evidence
No web manifest linked.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Optional, but a manifest.json enables install prompts and better mobile integration.
Not measured: Theme colorNo theme-color meta tag.
Not measured · Branding · Not established
Observed evidence
No theme-color meta tag.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Add <meta name="theme-color"> to tint the mobile browser UI to your brand color. Small touch, feels polished.
Looks good: Favicon
Looks good · Branding · Measured on your page
Observed evidence
Favicon declared via <link rel="icon"> (/favicon.svg).
Why this matters
These icons are what appear in browser tabs, bookmarks and search results. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Apple touch icon
Looks good · Branding · Measured on your page
Observed evidence
apple-touch-icon is declared.
Why this matters
These icons are what appear in browser tabs, bookmarks and search results. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Performance
Measured from the audited response and its markup. These are source observations, not field Core Web Vitals.
| Measure | This site | Reading |
|---|---|---|
| Server response time | 1815 ms | Needs a fix: poorThe audit received response headers after 1815 ms from one test location. |
| HTML payload size | 1742 KB | Could be better: needs attentionThe page's HTML is 1742 KB uncompressed. |
| Web fonts don't block text | — | Informational: not applicableNo Google Fonts stylesheet links detected. |
| No render-blocking head scripts | — | Looks good: goodNo synchronous render-blocking scripts in <head>. |
| Inline styles are bounded | 11.9 KB | Looks good: goodInline styles total 11.9 KB. |
| Script/stylesheet count | — | Looks good: good5 total script/style resources — reasonable. |
| HTML served compressed | — | Looks good: goodHTML is compressed with br. |
| Iframe usage | — | Looks good: goodNo iframes. |
| Source HTML weight | 1741.9 KB | Informational: measured source, not transferred bytes1741.9 KB of HTML on the audited page |
From a single automated fetch of the audited page. A quick reading, not a substitute for Lighthouse or field data.
Security
HTTPS, transport security and the response headers the audited pages send.
Needs a fix: HTTP redirects to HTTPSThe http:// version serves content instead of redirecting.
Needs a fix · Security · Review suggestedCritical
Observed evidence
The http:// version serves content instead of redirecting.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. Right now the sampled pages don't provide it.
Recommended fix
301-redirect all HTTP traffic to HTTPS — otherwise you have duplicate origins and users can land on the insecure one.
Could be better: HSTS headerNo active Strict-Transport-Security max-age was observed.
Could be better · Security · Review suggested
Observed evidence
No active Strict-Transport-Security max-age was observed.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. It is there, but weaker than this check expects.
Recommended fix
Add HSTS (e.g. max-age=63072000; includeSubDomains) so browsers never even try HTTP after the first visit.
Could be better: Frame embedding protectionNo frame-embedding restriction was observed (neither CSP frame-ancestors nor X-Frame-Options).
Could be better · Security · Review suggested
Observed evidence
No frame-embedding restriction was observed (neither CSP frame-ancestors nor X-Frame-Options).
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. It is there, but weaker than this check expects.
Recommended fix
Send Content-Security-Policy: frame-ancestors 'self' (or 'none', or a list of partner origins), or X-Frame-Options: SAMEORIGIN. It stops other sites from framing your pages to trick visitors into clicking (clickjacking).
Could be better: X-Content-Type-OptionsX-Content-Type-Options: nosniff is not set.
Could be better · Security · Review suggested
Observed evidence
X-Content-Type-Options: nosniff is not set.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. It is there, but weaker than this check expects.
Recommended fix
Add it — one header, stops MIME-sniffing attacks. Most hosts let you set headers in config (vercel.json, netlify.toml, next.config).
Could be better: Content Security PolicyNo Content-Security-Policy detected.
Could be better · Security · Review suggested
Observed evidence
No Content-Security-Policy detected.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. It is there, but weaker than this check expects.
Recommended fix
Configure an enforced policy for script and resource origins; use report-only monitoring to prepare changes safely.
Could be better: Browser feature permissionsNo explicit restriction on sensitive browser features was observed.
Could be better · Security · Review suggested
Observed evidence
No explicit restriction on sensitive browser features was observed.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. It is there, but weaker than this check expects.
Recommended fix
Disable unused camera, microphone, or geolocation access using Permissions-Policy.
Could be better: Server technology disclosureThe X-Powered-By header advertises "Nuxt".
Could be better · Security · Review suggested
Observed evidence
The X-Powered-By header advertises "Nuxt".
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. It is there, but weaker than this check expects.
Recommended fix
You can remove it (in Next.js: poweredByHeader: false; in Express: app.disable('x-powered-by')). It adds bytes to every response and tells scanners what to probe; it is not a vulnerability by itself.
Not applicable: Declared form submission targetsNo HTML forms were found.
Not applicable · Security · Measured on your page
Observed evidence
No HTML forms were found.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. This check does not apply to the features observed in this sample.
Recommended fix
Check JavaScript-generated form transport separately if present.
Not applicable: Password forms avoid URL submissionNo enabled, named password inputs in sampled HTML.
Not applicable · Security · Measured on your page
Observed evidence
No enabled, named password inputs in sampled HTML.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. This check does not apply to the features observed in this sample.
Recommended fix
Review authentication forms separately when applicable.
Looks good: Site serves over HTTPS
Looks good · Security · Measured on your page
Observed evidence
Site serves over HTTPS.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Referrer policy
Looks good · Security · Measured on your page
Observed evidence
No Referrer-Policy is set, so browsers apply their default, strict-origin-when-cross-origin, which sends only the origin to other sites.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No mixed content
Looks good · Security · Measured on your page
Observed evidence
No insecure subresources detected.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.
Recommended fix
Nothing to do here.
AI answer readiness
Retrieval signals an answer engine relies on: crawler access, clear entities and answers it can quote. These checks do not measure citations or traffic.
Could be better: Entity identity agrees across signalsEntity identity is inconsistent: the declared names differ (og:site_name "outages.live", Organization name "Polylane", WebSite name "outages.live"); Organization url https://polylane.com/ and Organization @id https://polylane.com/ point to a different site than outages.live.
Could be better · AI answer readiness · Measured on your page
Observed evidence
Entity identity is inconsistent: the declared names differ (og:site_name "outages.live", Organization name "Polylane", WebSite name "outages.live"); Organization url https://polylane.com/ and Organization @id https://polylane.com/ point to a different site than outages.live.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
Use one name for the site everywhere it is declared (Organization/WebSite schema, og:site_name, the title) and point identity URLs at this site.
Affected pages (1)
- https://outages.live/
Could be better: Question-style headingsOnly 0% of 48 H2/H3 headings are question-shaped.
Could be better · AI answer readiness · Review suggested
Observed evidence
Only 0% of 48 H2/H3 headings are question-shaped.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
Phrase key subheadings as the questions users actually ask ("How much does X cost?"). This improves the measured question-heading signal; the audit does not guarantee citations.
Could be better: Definitional openingThe opening paragraph doesn't define what the site/topic is: "Every few minutes, outages.live syncs the status pages of the providers your app…"
Could be better · AI answer readiness · Review suggested
Observed evidence
The opening paragraph doesn't define what the site/topic is: "Every few minutes, outages.live syncs the status pages of the providers your app…"
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
"X is a Y that does Z for W" in the first paragraph gives answer engines a liftable definition of you. Write it once, benefit everywhere.
Could be better: llms.txt follows the specAll 260 llms.txt links are bare, with no ": note" after them.
Could be better · AI answer readiness · Published platform rule
Observed evidence
All 260 llms.txt links are bare, with no ": note" after them.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
Add a short note after each link, for example [Pricing](/pricing): plans and limits. The notes tell a retriever which page answers what.
Not measured: Citable facts density229 concrete figures across 2520 words.
Not measured · AI answer readiness · Not established
Observed evidence
229 concrete figures across 2520 words.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Good — keep facts specific and current, and date-stamp them.
Not measured: Question headings have concise answersNo question-shaped H2/H3 headings were available to pair with answer paragraphs.
Not measured · AI answer readiness · Not established
Observed evidence
No question-shaped H2/H3 headings were available to pair with answer paragraphs.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Write the questions your audience asks as H2/H3 headings, then answer each in a concise paragraph immediately below it.
Not applicable: Advertised machine interfaces are inspectableNo OpenAPI interface was advertised by sampled HTML.
Not applicable · AI answer readiness · Measured on your page
Observed evidence
No OpenAPI interface was advertised by sampled HTML.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. This check does not apply to the features observed in this sample.
Recommended fix
An API is optional. Add a service-desc link if you already publish a machine-readable API specification.
Looks good: llms.txt
Looks good · AI answer readiness · Measured on your page
Observed evidence
llms.txt exists (14645 chars of markdown).
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: llms-full.txt
Looks good · AI answer readiness · Measured on your page
Observed evidence
llms-full.txt is published.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: AI crawler access
Looks good · AI answer readiness · Measured on your page
Observed evidence
The audited URL is allowed for evaluated answer-search crawlers.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: FAQ/QA schema
Looks good · AI answer readiness · Measured on your page
Observed evidence
FAQ/QA schema found.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Semantic HTML structure
Looks good · AI answer readiness · Measured on your page
Observed evidence
Semantic structure present: main×1, section×5, header×1, footer×1, aside×1.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Answers lead the section
Looks good · AI answer readiness · Measured on your page
Observed evidence
Paragraphs get to the point without preamble.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Content is chunkable
Looks good · AI answer readiness · Measured on your page
Observed evidence
Paragraphs average 12 words — chunk-friendly.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Freshness signals
Looks good · AI answer readiness · Measured on your page
Observed evidence
dateModified present in schema.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Cites external sources
Looks good · AI answer readiness · Measured on your page
Observed evidence
59 outbound reference(s) across crawled pages.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Consistent brand entity
Looks good · AI answer readiness · Measured on your page
Observed evidence
Brand declared: og:site_name "outages.live" + identity schema.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Description reads as a liftable summary
Looks good · AI answer readiness · Measured on your page
Observed evidence
Meta description works as a standalone summary.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: llms.txt links resolve to this site
Looks good · AI answer readiness · Measured on your page
Observed evidence
llms.txt contains 260 same-origin Markdown link(s).
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Machine-readable provenance signals
Looks good · AI answer readiness · Measured on your page
Observed evidence
Found 4 of 4 machine-readable provenance signal types: author, date, breadcrumb, contact.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Markdown copies of pages
Looks good · AI answer readiness · Measured on your page
Observed evidence
1 of 3 probed URLs returned markdown.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Accept: text/markdown negotiation
Looks good · AI answer readiness · Measured on your page
Observed evidence
The homepage answers Accept: text/markdown with markdown.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
AdSense readinessOptional
Publisher-policy signals, for sites that plan to carry ads. These checks do not affect the overall score or grade, and they do not measure or guarantee AdSense approval.
On its own, this site scores 30/100 for publisher readiness. Ignore this section if you do not run ads.
Needs a fix: Privacy policy pageNo privacy policy page is linked or crawlable.
Needs a fix · AdSense policy · Review suggestedCritical
Observed evidence
No privacy policy page is linked or crawlable.
Why this matters
A publisher review looks for this before it accepts a site. Right now the sampled pages don't provide it.
Recommended fix
Publish an accessible privacy policy that discloses cookies and data use by Google and other third-party ad vendors.
Could be better: Sampled publisher-content coverage1/8 editorial pages expose fewer than 250 publisher words; those 8 pages hold 8206 publisher words in total.
Could be better · AdSense policy · Review suggestedCritical
Observed evidence
1/8 editorial pages expose fewer than 250 publisher words; those 8 pages hold 8206 publisher words in total.
Why this matters
A publisher review looks for this before it accepts a site. It is there, but weaker than this check expects.
Recommended fix
Review whether each page fully serves its purpose. Expand incomplete editorial content with useful information; keep concise navigation and tool pages when they help visitors.
Affected pages (1)
- https://outages.live/live
Could be better: Terms pageNo terms of use page found.
Could be better · AdSense policy · Review suggested
Observed evidence
No terms of use page found.
Why this matters
A publisher review looks for this before it accepts a site. It is there, but weaker than this check expects.
Recommended fix
Consider adding terms that identify the service rules and publisher. This is a transparency heuristic, not an AdSense requirement.
Could be better: About pageNo about page found.
Could be better · AdSense policy · Review suggested
Observed evidence
No about page found.
Why this matters
A publisher review looks for this before it accepts a site. It is there, but weaker than this check expects.
Recommended fix
Add an About page that identifies the publisher, site purpose, and relevant experience. This supports content transparency but is not a standalone AdSense requirement.
Could be better: Contact methodNo contact page or mailto link found.
Could be better · AdSense policy · Review suggested
Observed evidence
No contact page or mailto link found.
Why this matters
A publisher review looks for this before it accepts a site. It is there, but weaker than this check expects.
Recommended fix
Add a working contact route or visible email so users can reach the publisher. This is a trust heuristic, not a published approval rule.
Could be better: Tool pages expose explanatory content1/8 tool-style screen(s) expose fewer than 80 publisher words.
Could be better · AdSense policy · Review suggested
Observed evidence
1/8 tool-style screen(s) expose fewer than 80 publisher words. Google publishes no minimum word count; this is an audit heuristic.
Why this matters
A publisher review looks for this before it accepts a site. It is there, but weaker than this check expects.
Recommended fix
Explain the tool's purpose, inputs, method, limitations, and result interpretation in source HTML. Add useful material, not filler.
Affected pages (1)
- https://outages.live/live
Could be better: Policy pages linked site-wide1/8 crawled pages don't link to the privacy policy.
Could be better · AdSense policy · Review suggested
Observed evidence
1/8 crawled pages don't link to the privacy policy.
Why this matters
A publisher review looks for this before it accepts a site. It is there, but weaker than this check expects.
Recommended fix
Place the privacy link in shared navigation or footer markup so users can reach disclosures from any sampled entry page.
Affected pages (1)
- https://outages.live/live
Not measured: Privacy policy advertising disclosuresA privacy page was not present in the crawl sample, so its disclosures could not be verified.
Not measured · AdSense policy · Not established
Observed evidence
A privacy page was not present in the crawl sample, so its disclosures could not be verified.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Confirm the policy explains cookies or similar storage, Google or advertising vendors, and third-party data use.
Not measured: First-party contact emailNo public contact email was found in the sampled home, About, or Contact pages.
Not measured · AdSense policy · Review suggested
Observed evidence
No public contact email was found in the sampled home, About, or Contact pages.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
A public email is optional. The separate contact-method check covers whether readers have a way to reach the publisher.
Not measured: ads.txtNo ads.txt yet.
Not measured · AdSense policy · Not established
Observed evidence
No ads.txt yet.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
When AdSense provides your publisher entry, publish it exactly at /ads.txt and monitor authorization status in your account.
Not applicable: Article-style content existsNo article/blog-style pages detected among crawled pages.
Not applicable · AdSense policy · Measured on your page
Observed evidence
No article/blog-style pages detected among crawled pages.
Why this matters
A publisher review looks for this before it accepts a site. This check does not apply to the features observed in this sample.
Recommended fix
No action is required solely because articles are absent. For tool or directory sites, make the unique publisher value and explanation crawlable on each relevant screen.
Not measured: Domain age & historyDomain age isn't visible from the site itself.
Not measured · AdSense policy · Not established
Observed evidence
Domain age isn't visible from the site itself.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Do not use age as a content-quality proxy. Verify ownership and account eligibility in AdSense; Google's general eligibility page publishes no domain-age threshold.
Not measured: Latest article has real depthNo article-shaped page was found on this site, so there is nothing to read.
Not measured · AdSense policy · Not established
Observed evidence
No article-shaped page was found on this site, so there is nothing to read.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Publish articles under a path such as /blog/… and list them in the sitemap. This check then reads the newest one.
Not measured: Latest article reads as edited workNo article-shaped page was found on this site, so there is nothing to read.
Not measured · AdSense policy · Not established
Observed evidence
No article-shaped page was found on this site, so there is nothing to read.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Publish articles under a path such as /blog/… and list them in the sitemap. This check then reviews its style signals.
Not measured: Latest article names an author and a dateNo article-shaped page was found on this site, so there is nothing to read.
Not measured · AdSense policy · Not established
Observed evidence
No article-shaped page was found on this site, so there is nothing to read.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Publish articles under a path such as /blog/… and list them in the sitemap. This check then looks for its byline and date.
Looks good: Thin page share
Looks good · AdSense policy · Review suggested
Observed evidence
7/8 editorial pages clear the audit's publisher-content triage threshold.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No ads on non-content screens
Looks good · AdSense policy · Published platform rule
Observed evidence
No Google ad code detected on sampled non-content screens.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Publisher content differs across URLs
Looks good · AdSense policy · Review suggested
Observed evidence
No high publisher-content repetition among 6 substantial sampled page(s).
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Publisher content exists in source HTML
Looks good · AdSense policy · Measured on your page
Observed evidence
No empty client-rendered publisher shell in the crawl sample.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Show 4 more checks
Looks good: No "coming soon" or placeholder pages
Looks good · AdSense policy · Measured on your page
Observed evidence
No "coming soon", "under construction" or lorem-ipsum text on crawled pages.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Site language is AdSense-supported
Looks good · AdSense policy · Measured on your page
Observed evidence
Language "en" is AdSense-supported.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Existing ad scripts
Looks good · AdSense policy · Measured on your page
Observed evidence
No competing ad scripts on the page.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Hosting and infrastructure
Public endpoint facts observed at audit time. A CDN or proxy can conceal the origin infrastructure.
| Hostname | outages.live |
|---|---|
| CDN / edge | Cloudflare |
| IP addresses | 172.67.129.162, 104.21.1.165, 2606:4700:3034::ac43:81a2, 2606:4700:3037::6815:1a5 |
| DNS A | 172.67.129.162 · 104.21.1.165 |
| DNS AAAA | 2606:4700:3037::6815:1a5 · 2606:4700:3034::ac43:81a2 |
| DNS NS | athena.ns.cloudflare.com · miguel.ns.cloudflare.com |
| TLS | TLSv1.3TLS_AES_256_GCM_SHA384 |
| Certificate issuer | Google Trust Services / WE1 |
| Certificate valid until | Jan 30 08:28:11 2027 GMT |
| Certificate validation | Passed |
Website anatomy and diagnostics
Explore links, resources, crawler access and site integrations.
Page architecture
Choose a page to explore its details and connections.
Page content
2003 publisher words
Page structure
html content
Observed discovery
Depth 0 · 7 incoming links
HTTP 200 · 1741.9 KB source
Source interactions
400 controls · 4 unnamed
3 script / 2 stylesheet references
- Canonical declaration
- https://outages.live/
- Schema types
- Organization, WebSite, SearchAction, EntryPoint, DataFeed, DataDownload, FAQPage, Question, Answer
- Outgoing links in sampled graph
- /live · /providers · /outages/algolia-1xzo1u9ikdt · /outages/monday-142fj877ic4 · /outages/ovhcloud-p9c1vr90bp · /outages/scaleway-jb7zqqo3az · /outages/twilio-pdhu197a2z · /outages/cloudflare-1rmptihv97z · /outages/cloudflare-1e9twcfof2k · /outages/hetzner-1ujymm3i0hs · /outages/twilio-iws7ramd9t · /outages/webflow-1dnmz7dzkgh · /outages/deepinfra-1lzw0894vl7 · /outages/twilio-2avgmc4pn9h · /outages/sinch-5vlagjof2t · /outages/twilio-261t6hkut8b · /outages/cloudflare-y3rg17djcf · /outages/cloudsmith-24ooxybhuzm · /outages/crusoe-1y71fx8klj9 · /outages/crusoe-1jufx79wi22 · /outages/launchdarkly-x6veil1h48 · /outages/twilio-9z9jw5e1h0 · /outages/scaleway-1k31qpx6l1u · /outages/cloudflare-295jovg1ehi · /outages/ovhcloud-r0c46h3nib · /outages/scaleway-f4jr0mm9py · /outages/vonage-1stxpd7x60f · /outages/twilio-scghohizxn · /outages/contentful-8doq06zg64 · /outages/moonshot-1541p8492ix · /outages/moonshot-1gx8fmorkm0 · /outages/moonshot-24r7jm219o4 · /outages/deepinfra-25zvpy3tovu · /outages/koyeb-28x1hm76eoi · /outages/deno-28x1hm76eoi · /outages/github-11i4yc7fp1a · /outages/expo-28zrjhpobwt · /outages/codecov-28x1hm76eoi · /outages/circleci-1ly729qfk09 · /outages/netlify-1ly729qfk09 · /outages/blackforestlabs-23eb9urh7so · /outages/ovhcloud-2c9h5ztxvog · /feed.xml · /api/v1/feed · /llms.txt
Routes: / · /live · /providers · /outages · /onepassword · /ably · /adyen · /ai21
Resource origins 3
Resources associated with your website. External resources may belong to the same organization.
- https://outages.live/stylesheet, script, image · 192 references · same origin
- https://plausible.io/script · 8 references · cross origin
- https://static.cloudflareinsights.com/script · 8 references · cross origin
Crawler policy by page
Review crawler access for your pages. Search, training and user-triggered services have different purposes; declared access does not guarantee discovery.
| Crawler / purpose | Page | Policy | Matched directive |
|---|---|---|---|
| Googlebotsearch | / | allowed | allow: / |
| Googlebotsearch | /live | allowed | allow: / |
| Googlebotsearch | /providers | allowed | allow: / |
| Googlebotsearch | /outages/algolia-1xzo1u9ikdt | allowed | allow: / |
| Googlebotsearch | /onepassword | allowed | allow: / |
| Googlebotsearch | /ably | allowed | allow: / |
| Googlebotsearch | /adyen | allowed | allow: / |
| Googlebotsearch | /ai21 | allowed | allow: / |
| bingbotsearch | / | allowed | allow: / |
| bingbotsearch | /live | allowed | allow: / |
| bingbotsearch | /providers | allowed | allow: / |
| bingbotsearch | /outages/algolia-1xzo1u9ikdt | allowed | allow: / |
| bingbotsearch | /onepassword | allowed | allow: / |
| bingbotsearch | /ably | allowed | allow: / |
| bingbotsearch | /adyen | allowed | allow: / |
| bingbotsearch | /ai21 | allowed | allow: / |
| OAI-SearchBotsearch | / | allowed | allow: / |
| OAI-SearchBotsearch | /live | allowed | allow: / |
| OAI-SearchBotsearch | /providers | allowed | allow: / |
| OAI-SearchBotsearch | /outages/algolia-1xzo1u9ikdt | allowed | allow: / |
| OAI-SearchBotsearch | /onepassword | allowed | allow: / |
| OAI-SearchBotsearch | /ably | allowed | allow: / |
| OAI-SearchBotsearch | /adyen | allowed | allow: / |
| OAI-SearchBotsearch | /ai21 | allowed | allow: / |
| PerplexityBotsearch | / | allowed | allow: / |
| PerplexityBotsearch | /live | allowed | allow: / |
| PerplexityBotsearch | /providers | allowed | allow: / |
| PerplexityBotsearch | /outages/algolia-1xzo1u9ikdt | allowed | allow: / |
| PerplexityBotsearch | /onepassword | allowed | allow: / |
| PerplexityBotsearch | /ably | allowed | allow: / |
| PerplexityBotsearch | /adyen | allowed | allow: / |
| PerplexityBotsearch | /ai21 | allowed | allow: / |
| Claude-SearchBotsearch | / | allowed | allow: / |
| Claude-SearchBotsearch | /live | allowed | allow: / |
| Claude-SearchBotsearch | /providers | allowed | allow: / |
| Claude-SearchBotsearch | /outages/algolia-1xzo1u9ikdt | allowed | allow: / |
| Claude-SearchBotsearch | /onepassword | allowed | allow: / |
| Claude-SearchBotsearch | /ably | allowed | allow: / |
| Claude-SearchBotsearch | /adyen | allowed | allow: / |
| Claude-SearchBotsearch | /ai21 | allowed | allow: / |
| GPTBottraining | / | allowed | allow: / |
| GPTBottraining | /live | allowed | allow: / |
| GPTBottraining | /providers | allowed | allow: / |
| GPTBottraining | /outages/algolia-1xzo1u9ikdt | allowed | allow: / |
| GPTBottraining | /onepassword | allowed | allow: / |
| GPTBottraining | /ably | allowed | allow: / |
| GPTBottraining | /adyen | allowed | allow: / |
| GPTBottraining | /ai21 | allowed | allow: / |
| ClaudeBottraining | / | allowed | allow: / |
| ClaudeBottraining | /live | allowed | allow: / |
| ClaudeBottraining | /providers | allowed | allow: / |
| ClaudeBottraining | /outages/algolia-1xzo1u9ikdt | allowed | allow: / |
| ClaudeBottraining | /onepassword | allowed | allow: / |
| ClaudeBottraining | /ably | allowed | allow: / |
| ClaudeBottraining | /adyen | allowed | allow: / |
| ClaudeBottraining | /ai21 | allowed | allow: / |
| Google-Extendedtraining and other Google AI uses | / | allowed | allow: / |
| Google-Extendedtraining and other Google AI uses | /live | allowed | allow: / |
| Google-Extendedtraining and other Google AI uses | /providers | allowed | allow: / |
| Google-Extendedtraining and other Google AI uses | /outages/algolia-1xzo1u9ikdt | allowed | allow: / |
| Google-Extendedtraining and other Google AI uses | /onepassword | allowed | allow: / |
| Google-Extendedtraining and other Google AI uses | /ably | allowed | allow: / |
| Google-Extendedtraining and other Google AI uses | /adyen | allowed | allow: / |
| Google-Extendedtraining and other Google AI uses | /ai21 | allowed | allow: / |
| ChatGPT-Useruser-initiated; robots may not apply | / | allowed | allow: / |
| ChatGPT-Useruser-initiated; robots may not apply | /live | allowed | allow: / |
| ChatGPT-Useruser-initiated; robots may not apply | /providers | allowed | allow: / |
| ChatGPT-Useruser-initiated; robots may not apply | /outages/algolia-1xzo1u9ikdt | allowed | allow: / |
| ChatGPT-Useruser-initiated; robots may not apply | /onepassword | allowed | allow: / |
| ChatGPT-Useruser-initiated; robots may not apply | /ably | allowed | allow: / |
| ChatGPT-Useruser-initiated; robots may not apply | /adyen | allowed | allow: / |
| ChatGPT-Useruser-initiated; robots may not apply | /ai21 | allowed | allow: / |
Advertised APIs and machine interfaces
No supported machine interfaces were advertised in the sampled HTML. An API or MCP server is optional; undiscovered interfaces remain unknown.
Public DNS and TLS endpoint
outages.live · observed · 172.67.129.162, 104.21.1.165, 2606:4700:3034::ac43:81a2, 2606:4700:3037::6815:1a5
- A
- 172.67.129.162 · 104.21.1.165
- AAAA
- 2606:4700:3037::6815:1a5 · 2606:4700:3034::ac43:81a2
- CNAME
- Unavailable for this exact hostname
- NS
- athena.ns.cloudflare.com · miguel.ns.cloudflare.com
- MX
- Unavailable for this exact hostname
- CAA
- Unavailable for this exact hostname
TLS: TLSv1.3
Certificate validation passed for the observed endpoint.
Issuer: Google Trust Services / WE1
Certificate valid until: Jan 30 08:28:11 2027 GMT
PageSpeed measurement
Loading the PageSpeed panel…
Growth resources
Loading growth resources…
Where to take this site next
Follow-on work suggested by the observations above.
- 01
Your top fixes list is the priority order — clear the red items before creating more content.
- 02
Re-run the combined audit after each batch of fixes
Re-run after fixes to see which checks changed; score bands are guidance, not a guarantee of ranking, traffic, or approval.
- 03
Make policy pages, publisher disclosures and substantial content reachable before applying. This audit cannot predict approval.
Apply the recommended fixes
Hand the complete evidence to a coding agent, or take the report with you.
Report notes
- 01This report covers the sampled public pages listed above. Other pages may have different results.
- 02Browser-rendered content, private backend systems and authenticated experiences may require a separate review.
- 03Unavailable observations are identified in the report. Results do not guarantee rankings, citations, security, accessibility or advertising approval.
Pages included in this report
- https://outages.live/
- https://outages.live/live
- https://outages.live/providers
- https://outages.live/outages/algolia-1xzo1u9ikdt
- https://outages.live/onepassword
- https://outages.live/ably
- https://outages.live/adyen
- https://outages.live/ai21