What shipped, and when.
A paid product should be able to show its work — especially one whose pitch is that nobody sunsets a business model. This is the subset you would notice, in the words you would use. Pricing changes are in here too, at the same size as the features.
-
Grace mode now follows your first payment
Trials without a previous payment now pause when their €9 starting credit runs out. Prepaid accounts that have paid before still receive seven days of free five-minute checks before pausing. Trial grace periods already in progress finish as scheduled. An empty balance does not delete your data; top up or subscribe to resume monitoring.
-
Scheduled-job check-ins now have a usage price
Accepted scheduled-job check-ins now cost €3 per million, with no separate monthly fee per job. They draw from your prepaid balance or your subscription’s included usage budget; the €3 PAYG monthly minimum still applies. Team now supports 100 scheduled jobs and Agency 1,000. Check-ins appear separately from outgoing checks on the usage page.
-
Capture what your page showed during an incident
Enable incident screenshots for HTTP monitors: when a confirmed incident begins and the check received a response, up4 attempts one capture and keeps the image for seven days. PAYG and trials pay €0.005 per successfully stored image; failed or skipped captures are free. Team includes 500 and Agency 2,500 successful images per UTC calendar month, separately from the check budget. No captures run during grace mode, while paused or after the allowance is used up; manual and scheduled captures are unavailable.
-
Give each client a logo for light and dark mode
In agency mode, upload a client logo or import an image from a URL. Add an optional dark-mode version and a compact mark for client lists and switchers, then preview both themes before saving. Reports use the standard logo, so the client’s branding also carries into exported PDFs.
-
Read and export reports in German
Report labels and explanations now follow your English or German app language. PDF and Excel exports also use the matching number format. Shared report snapshots retain the language used when they were created.
-
Set an end time for a monitor pause
Pause a monitor for one hour, 24 hours or until a time you choose. Checks resume automatically when the pause ends, provided monitoring is allowed by your account’s billing and feature settings. For larger changes, queue several bulk actions against the same monitor selection and apply them in sequence.
-
Keep status-page updates in one incident timeline
Post incident updates as a thread with affected components, a message timeline and reusable templates. Edit or backdate messages, and choose whether automatic incident reports publish immediately or wait as drafts. Plan maintenance in its own time zone, with weekly or monthly repeats and subscriber reminders; affected monitors can pause for the window and resume afterwards.
-
Let visitors choose the status updates they receive
Status-page subscribers can choose incidents, maintenance or both, for all components or only the ones they use. Offer updates by email, webhook or feed. Add an incident banner to your own website, use the JSON status summary in an integration or open the page as a wall display; protected pages keep their public feeds, banner and summary closed.
-
Create a branded status page for each client
Upload a logo, a dark-mode variant and a favicon, then choose your page’s accent colour. Give approved email addresses or domains access to a private page through a one-time email code. Duplicate a finished page as an unpublished starting point for another client; domains, access rules, subscribers and updates are not copied.
-
Keep status-page components up to date automatically
Let a section fill itself from monitors, scheduled jobs or a selected group, including new items from the page’s client scope. Add external services using their provider’s Atlassian Statuspage or Instatus feed. Visitors see the source and when it was read; external services do not change your own page’s overall status.
-
Navigate the app from one mobile menu
The mobile side menu brings navigation, account settings and appearance choices together. Open it from the top bar and switch between your Company and client views when agency mode is enabled.
-
See services and scheduled jobs together
The dashboard now brings monitors and scheduled jobs into one overview, with items needing attention and a summary of the past week. Upcoming maintenance, certificate dates and scheduled reports appear alongside it. The monitor and scheduled-job lists also bring status, search and view controls into a more compact layout.
-
Build your status page with a live preview
Create and edit status pages in the same visual editor. Preview your branding and selected monitors or scheduled jobs at desktop and phone widths as you work. New pages are saved as drafts, ready to publish when you are.
-
Follow your scheduled job from its first check-in
The scheduled-job page guides you through adding the check-in URL to your job and shows when the first check-in arrives. Once connected, it brings the next expected run, grace period and recent activity together. Return to the setup instructions whenever the job moves to another server.
-
Receive incident alerts by phone
Connect your own Twilio account to receive phone alerts for monitor incidents, with spoken messages in English or German. Press 1 during the call to acknowledge the incident and stop further escalation. Twilio charges you directly for calls and numbers, including test calls; these costs do not come out of your up4 wallet. Phone alerts do not cover scheduled jobs, recovery messages or comments.
-
Read a monitor’s status and response times in one place
The monitor detail page brings current status, incident context, alert recipients and response-time history together. For HTTP monitors, use the chart legend to show or hide individual request phases alongside the total response time. Your chart selection is remembered in this browser.
-
Choose faster checks during quick setup
Select a 10-second or 30-second interval directly when creating a monitor with quick setup. The longer intervals remain available, so you can choose how often to check without opening advanced setup.
-
Find help without leaving the app
Open Help to find guides for the page you are using, browse the documentation or write to us. The message form keeps your draft when you close the panel, and replies arrive by email.
-
Use up4 in German
Choose German for the customer app, from your first monitor to reports and account settings. Personal emails follow your language preference too, including invitations, sign-in links and account messages.
-
Start with €9 in monitoring credit
New Companies receive €9 in starting credit to try every feature without a card. Checks cost €9 per million executions, and the €3 monthly minimum still applies. How long the credit lasts depends on your usage.
-
Follow along with illustrated guides
Product guides now include annotated screenshots that point to the controls used in each step. Follow the steps for monitors, scheduled jobs, alerts and status pages, and open an image for a closer look.
-
Use a passkey for two-factor authentication
Add a passkey in your security settings and use a supported device or security key to complete the second step of sign-in. Authenticator app codes remain available, and you can keep both options on your account.
-
Show scheduled jobs on your status page
Add scheduled jobs to your status page alongside your services. Visitors can see the current status of monitored backups and other recurring tasks in the same place.
-
A personal alert plan for your first monitor
The first-monitor setup includes a Just me alert plan for your own email address. It follows up every 15 minutes for up to two hours while an incident remains unacknowledged. You can change the plan or choose another alert route.
-
See who was notified about an incident
Incident details bring alert recipients and sending results together. See which notifications were sent, which are still pending and which need attention, without piecing the story together across separate screens.
-
Monitors admit when they have never been checked
A newly created monitor used to show as up before a single check had run — a green light that had measured nothing. It now reads pending until the first result arrives, all the way through to the public status badge. Alongside it: a health advisor that names the eleven ways a setup can be quietly broken (no alert channel, a monitor nobody owns, an interval that outruns the plan budget) and offers to fix each one, plus an honest per-channel status so a channel that has never delivered anything says so.
-
Status pages on your own domain, with the certificate issued for you
Point
status.yourcompany.comat us; we verify the DNS record and provision the certificate. Team includes one domain, Agency ten, and pay as you go adds them from the wallet at €2 a month each. Pages can also be restricted by IP allowlist or access link, so an internal page is protected rather than merely unlisted. -
A new mark
UP with a negative-space 4, across the app, the operator console and this site. Same product, fewer apologies about the old logo.
-
Checker capacity that can grow without us waking up
The worker fleet is now provisioned through an operator-authorised lifecycle across two providers, with capacity alerting and guarded removal. You will not see it, which is the point: it is the machinery that keeps a 10-second interval a 10-second interval when the fleet gets busy.
-
Grace mode: zero balance no longer means dark
Running out of credit used to pause monitoring. Now a 7-day grace period keeps every monitor running at a 5-minute cadence, free of charge, with alerts and status pages live — and the runway warnings that precede it are based on your real burn rate rather than a percentage threshold. Only after those seven days do checks pause, and nothing is ever deleted.
-
One rate for every check type
HTTP, keyword, body, TCP, DNS and ICMP ping checks all cost €9 per million. Previously the meter charged different rates by protocol, which meant the cheapest way to describe our pricing was a table. Now it is a sentence. Non-check meters — alerts, status pages, seats — are telemetry only and cost nothing.
-
The region picker only offers regions we actually run
Checkers now report their own presence, and the picker is built from that signal. It is no longer possible to configure — and be billed for — a region we do not currently serve.
-
Slow is degraded, not down
A response that arrives late is now its own state: recorded, visible on the chart as an amber band, and never a reason to page anyone at 4 a.m. Confirmation is symmetric — three consistent observations in either direction — so a server having a bad minute no longer produces an incident and an apology.
-
Live on upfour.io
Production moved to a three-server split topology in Germany: application, dedicated database and a separate checker box, with only port 443 exposed. The status page deliberately does not run on it.
-
Reports you can hand to a client without editing them
Five report types — executive summary, per-monitor SLA with business-hours masking, downtime ledger with a public verification hash, incident analytics and response time — exportable as CSV, JSON, XLSX or PDF, schedulable by email, and white-label with your logo and domain. Share links freeze a snapshot so the number in the email is still the number three months later.
-
Predictable retention instead of a silent trim
Individual check results live at most 7 days in the primary database, then as rollups and a compressed archive for your plan’s window: 30 days on pay as you go, 90 on Team, 365 on Agency. Reporting reads across both tiers, so a 90-day chart is a 90-day chart.
-
Ping monitoring that is actually ICMP
Ping checks send real ICMP echo requests rather than opening a TCP connection and calling it a ping. Also shipped: a safety layer with a resolve cache, an IANA-reserved-range denylist and per-organization rate limits, because a monitoring service that can be pointed at arbitrary hosts is an amplifier if you let it be.
-
Client accounts
Every monitor, incident, status page, alert plan, playbook and report can belong to a client, partitioned at the database level rather than filtered in the interface. With it: read-only share links that need no account, and client templates so onboarding the next client ends before the kickoff call does.
Older than this list? The product existed before it was worth writing down — status pages, incidents, escalation, on-call and heartbeats all shipped between February and April 2026.
Still shipping. <em>Come and watch.</em>
€9 starting credit · no card