Create your account
Open Get started, complete the available sign-up flow and verify the email address you want to receive alerts at. UpBastion uses Clerk for account authentication. An account has one verified primary email address for monitoring notifications; monitor-specific recipients are not available.
After signing in, open the dashboard. The Monitors page shows your monitors and the form for adding a URL. The public website, documentation and guides can be read without an account.
Add your first monitor
Enter a descriptive name in the Name field, such as “Production homepage”.
Enter the complete public URL in Website URL, including
https://orhttp://.Select Add monitor.
Open the new monitor to view its status, response time, history and incidents.
Use a URL you own or are authorized to monitor. https://example.com/ illustrates the format; replace it with your actual address. The address must resolve publicly and use the default HTTP or HTTPS port. Local networks, credentials in URLs and URL fragments are rejected. Read URL requirements before adding an API endpoint.
Wait for the first observation
A new monitor is due for a check immediately. It stays pending until the worker records a result. Queue load and worker availability affect when that result arrives; adding a monitor does not run a synchronous check in your browser.
Regular checks are scheduled five minutes after a result is saved. If a check fails, the worker schedules a confirmation check after 30 seconds. A second failure opens an incident and queues a downtime email. A single successful check closes an open incident and queues a recovery email. How checks work explains the timing and its limits.
The dashboard refreshes its data about every 30 seconds while open. A dashboard refresh does not cause the worker to check your website.
Confirm that alerts can reach you
Check that your primary account email is verified. If it is not, the dashboard shows a verification notice. It also shows notices when checking or email delivery is temporarily unavailable.
There is no test-email button. For an end-to-end test, use a dedicated endpoint you control, change its response to a failure, wait for confirmation, then restore a successful response. Do this on a test endpoint rather than taking a production site offline. Check email alerts and incident behavior before the test.
What the result means
An Up result means the request received an HTTP 2xx response after any accepted redirects. UpBastion does not render the page, execute JavaScript, inspect response text or test a login, checkout or other user journey. A broken page that returns 200 can still appear up.
Each account can have 10 monitors, including paused monitors. Checks run from one server, with a fixed five-minute interval and a 15-second total request deadline. There are no configurable request headers, request bodies, custom success codes, SMS alerts, Slack integrations or public status pages in the current service.
Continue with creating and managing monitors, or use the guide to choosing useful URLs. For help with your first check, contact UpBastion.