Product updates
Stay up to date with the latest features, improvements, and releases
Uptimer v1.5.0
2026-08-28What's new
- Monitoring is organized around your websites. Each row shows whether that site is OK, still confirming a problem, recovering, or missing data — not just up or down.
- Open a website to see a timeline of what happened: when trouble started, what each location saw, and how status changed over time.
- Add or edit a website monitor in one form — setup stays simple while the product keeps the full picture behind the scenes.
- Slack alerts link straight to the website that needs attention, so you land on the story instead of hunting through menus.
- New API keys show the secret once when created; copy it then — it will not appear again.
Uptimer still starts with straightforward website monitoring, but the product now speaks in incidents and evidence instead of raw check flips. When something looks wrong, you can see whether Uptimer is still confirming, already treating it as a problem, or waiting on missing data — and you can read the history instead of guessing from a single status badge.
Documentation and in-app help were updated to match the new flow. More ways to add custom signals and build advanced rules are planned for the next release.
Uptimer v1.4.0
2026-08-13Features
- A monitor's status is now decided across all of its locations, with a new "Locations Required to Fail" choice — majority (default) or at least one.
- History is now a timeline of incidents — pending, problem, no data, recovering, closed — showing which locations failed and what they reported.
- Slack alerts were rewritten. Each one now says how many of your locations are failing and which, quotes the error the site returned, and links straight to the timeline. Recovery messages say how long you were down.
- The monitor list shows Pending while a problem is being confirmed and Recovering while a site is coming back, so you can see what is happening before an alert arrives.
- Monitoring requests identify themselves as
Uptimer/1.4.0instead ofGo-http-client/1.1, so you can filter them out of your analytics. - Signing out now ends the session at your identity provider too self-hosted OIDC
A single unlucky location used to be able to flip a monitor to Down on its own, and one bad minute could page you. Uptimer now waits for enough locations to agree, holds a problem for two minutes before confirming and alerting, and holds a recovery for two minutes before closing — so blips stay in the history instead of in your inbox. A location that goes silent is not quietly dropped from the vote; it counts as unknown, which is why a half-silent monitor now reads No Data rather than trusting whichever location still answered.
Alerts changed with it. The old message said little more than "Site is down"; the new one tells you how bad it is — "Failing from 2 of 3 locations" is a real outage, one failing location out of three usually is not — and includes the exact error, so you often know the cause before opening anything.
Self-hosted only: workers no longer need a database of their own. worker.db.dsn is still accepted and ignored, so existing configurations keep working — you can delete the setting and drop the second database.
Uptimer v1.3.0 & Python SDK v0.4.0
2026-07-15Features
- Assign regions to a rule when creating or updating it over the REST API — a new "regions" field on the rule payload, matched by region name.
- Python SDK v0.4.0: set regions on rule create/update published to PyPI
Previously a rule created through the API had no region and stayed at No Data (never checked) until someone opened it in the dashboard and assigned one — which blocked fully headless and SDK-driven monitoring. Now an API- or SDK-created rule can be given its regions up front and starts running immediately. Unknown region names return a clear validation error; omit the field for no region.
Instant Check Launch
2025-10-12Features
- Added Instant Check feature with sharable results.
- Introduced Singapore region (SG).
Instant Check enables users to test the availability and HTTP response of a website from multiple geographic regions. After submitting a URL, each region performs an independent check, and results are displayed incrementally as they arrive. The results can be shared through a public link and are stored for 72 hours. The check verifies that the response code is in the 20× range; otherwise, a warning is shown.
Uptimer v1.2.0
2025-09-13Features
- CSS rework with minification and class mapping CSS/JS reduced ~50%
- HTML size reduced through CSS class minification
Fixes
- Fixed paging issue on the rule availability history page.
- UI error messages updated for clarity.
Summary: This update improves site load speed.
- Reduced CSS and JS bundle sizes.
- Fewer HTTP requests for CSS, JS, and font files.
- HTML size reduced through CSS class minification.
Faster load times mean a smoother developer and user experience — aligning with our vision of lightweight, transparent, and reliable tools.
Uptimer (self-hosted) v1.1.0
2025-08-20- Version number displayed alongside project name
- Improved OIDC-to-user mapping (security fix)
- Fixed header spacing issue on the rules list page
Redesign and Python SDK updates
2025-08-19SaaS updates
- Launched public API Officially launched our public API 🚀
- Redesigned pages for improved clarity and navigation Rolled out fully redesigned pages for a smoother experience
Python SDK v0.3.0
- Self-hosted client now requires a base_url
- Introduced cloud client for integration
- Updated documentation for clarity
August 10, 2025 updates
2025-08-10Python SDK v0.2.0
- First public Python SDK version
- Added full rule management (create, update, delete, list)
- New APIs for regions, rules, and workspaces
Uptimer (self-hosted) v1.0.0
- New APIs: rules (CRUD), version, regions, workspaces
- UI supports API key and token management
- Core refactor: app initialization, services, handlers, tests Major core refactor: app initialization, services, handlers, tests
- Refreshed UI
- Optimized performance Fewer SQL queries, parallel API tests
Documentation
- Updated documentation for Uptimer v1.0.0
Documentation - initial launch
2025-06-21- Documentation launched with initial version of Uptimer (v0.2.0)