Public status page · Autessa Status Page
90-day uptime history
Autessa Status Page shows 90 days of uptime history for every component as a row of daily bars. Each bar is colored by the worst status that component had that day, and hovering or focusing a bar shows the date and the incidents or maintenance behind it.
The problem it solves
Trust is built over months, not minutes
Prospects and customers judge reliability by the track record, not today's green light. A visible history, quiet days and bad days alike, shows you are open about problems and gives people the context they need: was that a one-off, or does it happen every week?
What you get
- 90 daily bars per component, oldest on the left, today on the right.
- Each day takes the worst status of any incident or maintenance that touched that component that day.
- Hover a bar, or reach it with the keyboard, to see the date and up to three events from that day.
- Every bar has a spoken label, such as "November 3, 2026: Partial outage" or "no incidents".
- A one-line summary under each row: "No incidents in 90 days" or "4 of 90 days with an incident or maintenance".
- Ongoing incidents color every day up to today; scheduled and canceled maintenance never color a day.
How it works
How does 90-day uptime history work?
Incidents and maintenance are posted
Each one names the components it affects and how badly.
Days are worked out on the server
For every component, each of the last 90 days takes the worst status of the events that overlapped it, from start to resolution (or to now, if still open).
The bars are drawn
Green for quiet days, then amber, orange, red or blue for the worst thing that happened.
Visitors explore
Hovering or tabbing to a bar shows the date and the titles of that day's events, each with its status dot.
Every option
How a day gets its color
| Option | What it does |
|---|---|
| Window | The last 90 days, counted in whole days. |
| Source | Incidents and maintenance that list the component as affected. |
| Incident days | The severity picked for that component on the incident: Degraded performance, Partial outage or Major outage. |
| Maintenance days | Under maintenance, for windows that started (In progress or Completed). |
| Not counted | Maintenance that is only Scheduled or was Canceled. |
| Several events in a day | The worst status wins, and every event is listed in the day's details. |
| Hidden components | No bars are shown for components hidden from the page. |
Permissions
Who can do what?
| Who | Can |
|---|---|
| Visitors | Read and explore every component's 90-day history. |
| Staff in Status Admin | Shape the history by how they report incidents and maintenance and which components they mark as affected. |
Connected
How it connects to the rest of Status Page
FAQ
Questions about 90-day uptime history
How far back does the uptime history go?
90 days per component on the front page. Older incidents remain on the monthly history page.
Does changing a component's status by hand show in the history?
No. The bars come from incidents and maintenance. A quick manual status change without an incident does not color a day, so post an incident when you want the record to show it.
How is uptime shown?
As daily bars across 90 days, with a count of the days that had an incident or maintenance, so customers see the real track record at a glance.
100% customizable, code and all
Make Autessa Status Page fully your own.
Use it out of the box, then change anything. Ask Autobot, Autessa’s AI builder, for a new field, screen, report, workflow or agent and it builds it into your copy of the app. Or open the code and edit it yourself. Nothing is locked: the app, its data and its code are yours.
Start free and make it yours