# 2026-09-20: New Status Page

**URL:** <https://forum.codefloe.com/t/2026-09-20-new-status-page/187>\
**Category:** Announcements\
**Tags:** changelog\
**Created:** [September 20, 2026, 9:12am UTC](https://forum.codefloe.com/t/2026-09-20-new-status-page/187 "2026-09-20T09:12:00Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![codefloe](https://forum.codefloe.com/user_avatar/forum.codefloe.com/codefloe/32/42_2.png) [@codefloe](https://forum.codefloe.com/u/codefloe)\
**Post date:** [September 20, 2026, 9:12am UTC](https://forum.codefloe.com/t/2026-09-20-new-status-page/187/1 "2026-09-20T09:12:00Z")

</div>

We’ve migrated our [Status Page](https://status.codefloe.com/) from [Gatus](https://github.com/TwiN/gatus) to a self-hosted [OpenStatus](https://www.openstatus.dev/) instance.

Besides a more appealing UI, this gives us the following:

- Ability to store uptime information longer than 30 days (up to 2 years)
- Multiple monitors per endpoint. Openstatus hosted version would even allow a worldwide coverage; we have to use our own servers.
- Automated event posting: both for regular maintenance events like server reboots and discovered service degradations (e.g. if error rates (5xx responses) accumulate or latency exceeds a certain threshold)
- Ability to subscribe via multiple methods (RSS, JSON, Email, etc.)

 ![image](https://cdn.forum.codefloe.com/original/1X/9ab48d2b3f4a997ddf8c3f2d78ab72e0a113c38b.png)

As a bonus, we also set up monitors for other Forges (GitHub, GitLab and Codeberg), so users have (yet) another source for their uptime monitoring and their performance can be evaluated for a longer period (all of them don’t store uptime information for such a long time, e.g. Codeberg only shows the last 14 days).