The site returns 200 and the customer still cannot pay. Every few minutes Uptimo walks the path you earn from in a real browser: login, cart, delivery details, payment gateway. When a step fails, you get a recording of the run, a screenshot of that step and the full HAR file. Before the first customer calls.
No card required · Set up in fifteen minutes · Cancel any time
Tools that only check whether an address responds measure the least important thing. The home page almost always works. The money is lost further down: at login, in the cart, at the payment gateway.
The form returns an error, but the server answers 200. Monitoring stays quiet and the complaint arrives by e-mail two hours later.
Nobody knows which step, which browser or what time. Half a day goes into reproducing something that already happened.
The contract says 99.9%. Nobody can show what it really was, or subtract the planned maintenance window.
No escalation and no acknowledgement: either the whole company gets an SMS at 3 a.m., or the only person notified happens to be asleep.
The first reminder of the expiry date is the browser warning shown to a customer.
An agency with thirty sites clicks through the same configuration thirty times, without roles and without separating clients.
The same scenario every few minutes, always the same way. If it passes, you know a customer will pass too. If it fails, you have the full material for a fix before anyone has time to report the problem.
Three screens where you will spend 95% of your time with Uptimo. The rest of the panel exists so that you do not have to look at it.
Availability, response time, open incidents and expiring certificates: the last ones we read ourselves from every monitored https address, with issuer and expiry date. Wall mode turns the same view into one readable from across the room, with an audible alarm on a new failure.
The morning review takes ten seconds instead of a tour of five tools.
Replays the given steps in a real browser (Playwright): go to, click, fill in, wait, check text. You describe the scenario in plain sentences (“click the ‘Add to cart’ button”) and we run them on your own page, showing the result of every step with a screenshot BEFORE anything is saved.
You monitor the sales process, not just the presence of a server.
A payment failure shows up within minutes, not after the daily sales report.
On a failed run it saves a recording, a screenshot of every step and a full log of network requests.
You do not have to reproduce the failure. You watch it.
Shorter time to repair, measurable as the MTTR shown on the dashboard.
HTTP, HTTPS, full page with resources and HAR analysis, DNS, ping (IPv4 and IPv6), TCP port, IMAP and SMTP mail server, certificate expiry, scenario, and heartbeat: a cron job, backup or queue pings your address, and no signal in time means an outage.
One tool instead of three: the network layer, the application and the business process.
Fewer licences, one on-call rota, one incident history.
We read the expiry date and the issuer of the certificate from every monitored https address, without creating a separate check. As many days before the end as you set, a message goes to the recipients of that service.
The only outage visible a month ahead stops depending on somebody's memory.
You do not lose a day of sales to a browser warning about an insecure connection.
Push notifications to your phone, e-mail, Slack, Microsoft Teams, SMS and any webhook with your own headers and message template. Conditions for failure, recovery and a problem that is still going on.
The alert reaches the right person (including whoever is on call in the rota, with day and night layers and a calendar), and the “I am on it” acknowledgement stops the next steps. On an incident, one click asks AI for the likely cause and what to check first.
Night-time wake-ups only when they are really needed. When many services fail at once you get one mass-outage summary instead of dozens of alerts.
Counts availability, downtime, number of incidents and MTTR. A weekly or monthly report goes out by e-mail per group.
The conversation about service level rests on a measurement, not on an impression.
An argument in negotiations with a client and with a hosting provider.
A planned break mutes alerts, and excluding the period from SLA is a separate decision. One window covers many services and groups, and the chosen recipients get an e-mail announcement with an Outlook or Google invitation at a chosen moment before the start, a reminder at start and a note when done. A monthly calendar shows what was, what is running and what is coming. Recurring work (daily, on chosen weekdays, on a day of month) is set up once as a series, and the windows and announcements are created automatically.
No need to choose between quiet nights and an honest report.
The report stays credible also for the client who reads it.
Four roles (Owner, Administrator, Member, Observer), service groups, a record of who changed what. We create accounts on your request. Each person receives a message and sets their own password; we never send passwords by e-mail.
A client or the management board gets visibility without the right to change settings.
An agency serves many clients from one account, without mixing data.
The whole monitoring configuration as a file, secrets excluded. Done on request.
Copying a set of checks for the next client takes a minute, not an hour.
The cost of adding a client stops growing linearly.
The scenario walks the whole path: product page, add to cart, delivery details, on to the gateway. A text check at the end confirms it really is an order, not an error page with status 200.
E-mail address and password. No card and no call with a salesperson.
Paste addresses and pick a check type. The first results appear within a minute.
Pick the steps from a list: go to, fill in, click, check text. No code.
Channels, conditions, escalation order and quiet hours. You schedule the SLA report once.
Uptimo for Android is a companion to the account you already monitor. You set everything up in the web panel; the phone has one job: to tell you first when something breaks and let you judge the situation without opening a laptop.
The app requires an Uptimo account. Monitoring is configured in the web panel, not in the app.
HTTP, DNS, ping and TCP checks are cheap for us, so their limits are generous. The browser is what costs. That is why the number of scenarios and the interval differentiate the plans. SMS has its own allowance, because it is the only channel priced per message; once it runs out, alerts continue by e-mail and the allowance renews every month. Net prices, in Polish zloty (PLN).
Launch offer: 50% off the first year
The first 100 companies to buy a plan pay half the list price below for the whole first year when billed annually. With monthly billing the discount is 25% for the first 6 months. The terms are attached to the account, so ending the offer for new customers changes nothing for them. After that the list price applies, the one you can see right here: we are not hiding it from you.
One site, one person
Free with no time limit. Sensible monitoring of a single site.
A company with a few addresses, no scenarios
first year (50% off), then PLN 23
The full set of alert channels, without the browser.
A small company with one sales site
first year (50% off), then PLN 79
The first scenario and the full set of alert channels.
A company for which downtime means lost revenue
first year (50% off), then PLN 199
Full process monitoring plus accountability for every incident.
Maintaining many sites for many clients
first year (50% off), then PLN 499
One panel, many clients, a separate report for each of them.
A separate instance, your own check location (an agent inside your network as a Docker image on Linux, outbound traffic only), individually agreed limits, a contractual SLA and support with a defined response time. For organisations that must monitor resources unreachable from the public internet or have compliance requirements.
Net prices in PLN. Monthly or annual billing, VAT invoice. Change or cancel the plan at any time, with no notice period.
The browser scenario is not an add-on in the most expensive plan, it is the core of the product. The alternative is a tool that confirms the server is up at the very moment the cart has stopped working.
Video, a screenshot of every step and HAR are created on their own, only on failure. Nobody has to remember to switch recording on, or wait for the bug to happen again in front of a witness.
SLA counted to the second, with a clear distinction between silencing alerts and excluding a period from the calculation. The report goes by e-mail in the language of the recipient's organisation.
The instance runs on a server in Germany (netcup), inside the European Economic Area. Secrets in the database are encrypted with AES-256-GCM, the session lives in an httpOnly cookie, and scenarios run in an isolated process with no access to the application keys.
Your blocking question is not here? Write to us. We reply the same working day.
Free tools check whether an address responds. That is useful, but it only catches total outages. Uptimo adds a layer above: it walks the path you make money on and, on failure, leaves a recording and a HAR file. If your downtime costs less than a few hundred zloty a month, stay with the free tool, and take our Solo plan, which is free as well.
No. The Solo plan is free with no time limit, and the 14-day trial of the paid plans does not require a card. You enter payment details only when you decide to stay.
Adding HTTP, DNS or certificate checks takes fifteen minutes. The first checkout scenario usually takes an hour, mostly to walk the path and confirm the steps are stable. There is nothing to install on your side: you set up nothing and maintain nothing.
No. You pick the steps from a list: go to an address, fill in a field, click, wait for an element, check text. That covers login, cart, contact form and search. You can also describe the scenario in plain sentences: the builder runs them on your page and shows a table with the result of every step, screenshot included. You only save what worked in front of you.
In the European Union: the application and the database run on a server in Germany (netcup), and this website separately, on OVHcloud hosting in Poland. Data leaves the European Economic Area only when you deliberately trigger it: the scenario description when generating steps with AI, and the alert text to Slack or Teams if you configure them. The full list is in the privacy policy. Secrets (channel passwords, integration keys) are encrypted with AES-256-GCM, the session lives in an httpOnly cookie with SameSite=Strict, and failure artefacts are available only through a short-lived token limited to a single check. The database has an automatic backup, verified after every dump.
In the standard plans, from one location in the European Union. We do not pretend to run a network of a hundred probes. For monitoring a business process, frequency and scenario fidelity matter, not the number of cities. Additional or private locations are part of a dedicated instance.
We do not block private addresses. That is a deliberate decision, because monitoring your own network is a normal use. For it to work, though, the resource must be reachable from our location. If it is not, you need a dedicated instance on your side of the network.
File import is supported for our own export format. When migrating from another tool, we move the list of checks together with you during onboarding. Usually it is one meeting.
Yes, from the Start plan up. Enable it in the panel (Status page) and pick the services to show. The page is public, no login, at an address in the Uptimo domain, with your logo: service state, 90-day availability, ongoing and past outages and planned maintenance. State comes from monitoring, not by hand. You can also show it on your own domain, e.g. status.yourcompany.com: enter it in the settings, add a CNAME record at your DNS provider, and we issue the certificate ourselves.
Yes, in every plan. Next to a service you switch on “Status via API” and get a tokenised address that returns JSON without login, with the same state as the panel: up, down, paused, pending, plus the last check and the start of an ongoing outage. It fits an office wall board, a ticketing system or your own script. Short documentation with an example response sits next to the switch.
You write to us and the plan runs until the end of the paid period. No notice period and no retention call. We will prepare a copy of your configuration for download; just ask for it before the period ends.
Create an account, build one scenario and leave it for a day. If it finds nothing, that is great: you will know it from a measurement, not from hope.
No card required · Set up in fifteen minutes · Cancel any time
We want to count visits to learn which content is useful. This uses Google Analytics and cookies. Without your consent we collect nothing. The site works the same either way. Details in the privacy policy (in Polish).