Overall UXE Score
7.79
Assessed by the editors · −0.1 vs season average

- Recognition
- Featured
- Recognized
- 30 Sept 2026
- How it got here
- Chosen by the editors
- Studio
- OpenStatus
- Assessed as
- Product Experience
- Platforms
- Web
01/Overview
An uptime monitoring service with 91 of its 127 interactive controls measuring under 24 pixels on the short side.
Ninety-one of 127 controls under 24 pixels — 72% of everything clickable on the page. Most of it is the status timeline, which is built from one narrow bar per day, and each bar is a target. On a status page, those bars are how you find the outage.
Twenty-three contrast failures alongside, and three landmark problems. Nothing critical.
3.32 seconds to largest paint on 1.1 MB over 63 requests, with a layout shift of 0.000 and a skip link present. 1,598 words across nineteen headings, and the live status page is embedded on the marketing page rather than screenshotted — which is the right way to sell a status page.
Patterns observed
- No consent dialog on first visit
- Client
- In-house product
- Audience
- Teams who want a status page they can host themselves
- Industry
- Developer Tools
- Platforms
- Web
- Status
- Live
- Markets
- Worldwide
- Languages
- 1 — English
02/Honors
Recognized by the editors.
Recognition
Featured
Meets the UXE standard. Earns a public profile, a badge and a place in the quarterly awards.
Conferred by the editors on 30 Sept 2026 · minimum UXE 7.0
Awards
None. The quarterly awards are decided among projects their makers entered, and nobody entered this one — the editors chose it, assessed it and conferred the recognition above. If OpenStatus’s team would like it entered and considered for a season, entering is free.
03/Editors’ verdict
In the editors’ words.
“Seventy-two per cent of the controls are under 24 pixels, and most of them are the daily bars you click to find the outage.”
The UXE editors
Selected and assessed by the editors
04/Score breakdown
How the editors scored it.
- Overall UXE Score−0.1 vs Q3 2026 average
- 7.79
- Strongest criterionInformation Architecture
- 8.2
- Assessed bytheir own scores, signed
- The editors
- Measured30 Sept 2026
- On the live product
- 8.0−0.2
Usability
Can people complete what they came to do — efficiently, confidently and without error?
Editors’ noteThe live status page is embedded rather than screenshotted, which is the right demonstration.
- 8.2+0.3
Information Architecture
Is content organized, labeled and navigable in the way people actually think?
- 8.2−0.1
UI & Consistency
Is the visual language coherent and purposeful across every screen and state?
- 8.0+0.2
Interaction & Feedback
Does every action respond clearly, promptly and meaningfully?
- 7.2−0.3
Performance
Does it feel fast — perceived and measured — on real devices and networks?
Editors’ note3.32 s to largest paint on 1.1 MB over 63 requests, layout shift of 0.000.
- 6.9−0.9
Accessibility
Can everyone use it, including people relying on assistive technology?
Editors’ noteNinety-one of 127 controls measure under 24px — most of them the one-bar-per-day status timeline. Twenty-three contrast failures.
- 8.0−0.1
Learnability
How quickly does a first-time user become a confident one?
Scores are the editors’ own — this product was selected rather than entered, and the verdict is signed. Ticks mark the Q3 2026 average across 161 recognized projects.
05/Screens
2 screensThe product, screen by screen.


06/Accessibility & performance
Built for everyone, on any device.
Accessibility
Assessed here
Audited by the UXE editors (axe-core 4.10 over the loaded page, plus manual checks), September 2026
6.9
Measured
- Pinch zoom is not blocked
- No horizontal scrolling at the assessed viewport
- 7 landmark regions, and a page language declared as en
- A skip link was found
- 2 prefers-reduced-motion rules in the stylesheet
Known gaps
- 26 automated violations in one pass — 23 serious, 3 moderate
- Elements must meet minimum color contrast ratio thresholds (23 elements, serious)
- Main landmark should not be contained in another landmark (1 element, moderate)
- Document should not have more than one main landmark (1 element, moderate)
Performance
1 of 4 within budget
Chrome headless at 1440×900, throttled to Slow 4G (1.6 Mbps down, 150 ms round trip) with 4× CPU slowdown. Three cold loads, each in a fresh browser context with the HTTP cache disabled; the median is reported. 30 September 2026.
7.2
Measured
| Metric | Measured | Budget |
|---|---|---|
| Largest Contentful Paint | 3.32 s (over budget) | ≤ 2.5 s |
| First Contentful Paint | 3.32 s (over budget) | ≤ 1.8 s |
| Cumulative Layout Shift | 0 (within budget) | ≤ 0.10 |
| Page weight | 1.1 MB (over budget) | ≤ 1 MB |
Within budget Over budget
07/Credits
The people who made it.
Studio
OpenStatus
An open-source uptime monitoring and status page service, developed in public.
- Recognized
- 1
Team
Individual credits are published when the team submits them. This profile was compiled by the editors, so it names the company and nobody else.
Check it yourself
- Client
- In-house product
- Industry
- —
Built with
→/More from the showcase
Whole seasonMore from the showcase.

8.87
UXE

8.83
UXE

8.76
UXE