# Ninety-day uptime history on the public status page

> Turn on public uptime history so buyers and customers can see the last 90 days of reliability without booking a reassurance call.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/ninety-day-uptime-history-on-the-public-status-page/
- Source: [support.atlassian.com](https://support.atlassian.com/statuspage/docs/display-historical-uptime-of-components/)
- GrowthDex source hub: [Atlassian Statuspage Docs: Display historical uptime of components](/sources/atlassian-statuspage-docs-display-historical-uptime-of-components-suppor/)
- Last checked: 2026-05-29
- Rarity: epic
- Budget: low
- Channels: Brand, Sales, SEO
- Stages: brand trust, enterprise sales, self-serve proof, technical seo
- Key metric: Enabling historical uptime adds a 90-day uptime display on the status page and a full /uptime view.

## Why this can grow

A blank status page during normal weeks does not prove much. Buyers still want to know what the last few months looked like. Statuspage's uptime showcase changes the page from incident-only communication into a running proof surface by showing 90 days of component history and a dedicated uptime page behind it. That helps support during due diligence, but it also helps sales and expansion conversations because the company can point to a live public record instead of making hand-wavy claims about stability.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. For SEO and AI search, I care less about clever keyword tricks and more about clarity. A buyer, crawler, or answer engine should quickly understand who this is for, why it works, what proof backs it, and what page deserves to be cited. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where ninety-day uptime history on the public status page can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Brand and Sales channel.
3. Use the evidence from support.atlassian.com to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

Atlassian Statuspage says enabling historical uptime adds a 90-day uptime display to the main page and a full account on the /uptime page, turning the status page into a sales tool as well as a support tool.

## Adjacent tactics in the same lane

- [Custom docs 404 page with task-led redirects](/growth-ideas/custom-docs-404-page-with-task-led-redirects/) - 2 shared channels, 2 shared stages
- [Customer-facing docs on a brand subdomain](/growth-ideas/customer-facing-docs-on-brand-subdomain/) - 2 shared channels, 2 shared stages
- [ReadMe subdomain redirect after custom-domain cutover](/growth-ideas/readme-subdomain-redirect-after-custom-domain-cutover/) - 2 shared channels, 2 shared stages
- [Help center custom domain before support links spread](/growth-ideas/help-center-custom-domain-before-support-links-spread/) - 2 shared channels, 1 shared stage

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The status page should answer who is affected before support opens](/blog/the-status-page-should-answer-who-is-affected-before-support-opens/) - brand trust, support-led growth, operations

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.