For web agencies and freelancers
Website monitoring for web agencies
A client site can return an error while the rest of your portfolio looks healthy. Keep its uptime checks, certificate warnings, and incident history together so your team can find the affected service and decide what to do next.
Organize monitoring around each client
Create a group for each client or service, then add HTTP monitors for the public website and API checks for important endpoints. Keep certificate expiry and scheduled jobs as separate monitors: a responding homepage does not prove that either is healthy. Use separate workspaces when ownership and access need a stronger boundary. Within a workspace, roles and object access control which monitors a teammate can view or manage. Shared workspaces require two-factor authentication for Owner and Admin roles.
Investigate the affected location
A CDN route or regional network can fail while other locations still reach the site. Upteno retains each observation, including status, response time, and available diagnostics. The configured trusted-location agreement and consecutive-cycle rules determine when a state change becomes an incident. Start with locations relevant to the client and review the confirmation settings. More confirmation can reduce reactions to transient failures, but it can also delay an alert. A blocked or incomplete check is not proof that a website is down.
Set up the first client
1. Run the free website check on a public URL. Review the report, then use its monitoring action to carry that target into account setup. 2. In the workspace, group related monitors and configure their intervals, locations, expected responses, and confirmation rules. 3. Connect and test each recipient contact. Configure notification policies and planned maintenance, then review notification history after a state change.
Keep the client informed
Use incident history to explain what was observed and when recovery was confirmed. Scheduled reports and status pages help communicate the service state without forwarding raw alerts. Status pages can be public, password-protected, or workspace-private. Public and password-protected pages are shareable by link but excluded from search indexing. Review the page visibility before sharing it with a client.
What this workflow does and does not cover
Upteno checks public targets. It does not run a browser checkout journey or prove that every visitor can complete a purchase. Pair HTTP or API assertions with heartbeat signals for the jobs you depend on. The service is a free public beta with no service-level agreement. Confirm that its documented behavior fits each client commitment before relying on it as an operational channel.