Frequently Asked Questions

Click the "Start Monitoring Free" button on our homepage, enter your name and email address, create a password, then confirm your email via the link we send you. No credit card required for the free plan.

Right after you confirm your email. Once confirmed, a newly added website gets its first check on the next run of its check interval (every 5 minutes on the free plan). Websites added before you confirm your email are saved as inactive — switch them on from the dashboard after confirming.

Our free plan allows monitoring 1 website. Plus allows 10 websites and Professional allows 20 - check our pricing page for details.

We offer three tiers: Starter (free plan with 1 website, 1 automated action per website, checks as often as every 5 minutes), Plus ($9/month: 10 websites, 5 automated actions per website, checks as often as every 2 minutes), and Professional ($19/month: 20 websites, 10 automated actions per website, checks as often as every minute). Plus and Professional can send alerts through your own Telegram bot and watch log files over SSH (Plus: 2 files checked every 15 minutes; Professional: 10 files, as often as every minute). Each tier includes different limits and monitoring frequencies. Check the header menu to see your current plan and usage.

Your website usage is displayed in the user dropdown menu in the header. You'll see a progress bar showing "X/Y websites" where X is your current count and Y is your tier limit. The Subscription page lists the website limit of each plan.

Yes, you can permanently delete your account and all associated data at any time. Go to Profile Settings → Delete Account. This action is irreversible and will remove all your monitored websites, check history, and screenshots.

Click "Forgot Password" on the login page, enter your email address, and we'll send you a password reset link. You can also change your password from the Profile Settings page when logged in.

We accept cryptocurrency payments for premium plans (Plus and Professional). The Starter (free) plan requires no payment information.

Our cryptocurrency payment process is simple and secure:

Yes, you'll need a wallet that supports Binance Smart Chain (BSC) to make payments. We recommend:

Yes! Cryptocurrency payments offer several security advantages:

Payment confirmation typically happens in two stages:

Your subscription activates automatically once the payment is fully confirmed on the blockchain.

However:

• You can cancel your subscription at any time - you'll retain access until the paid period ends
• We offer multi-month discounts to provide better value (up to 15% off for 12 months)
• All payments are clearly shown before you confirm the transaction

Yes! We offer significant discounts for multi-month subscriptions:

Yes, you can switch to another tier at any time by purchasing a new subscription. The new plan activates as soon as the payment is confirmed, and its period starts from that moment — remaining time on your current plan is not carried over. This applies to downgrades too, so you may prefer to wait until your current period ends before buying a lower tier.

You choose the check interval for each website. The shortest interval depends on your plan: Starter: every 5 minutes. Plus: every 2 minutes. Professional: every minute.

Once the number of consecutive failed checks you set for the website is reached (3 by default), we send an alert via your enabled channels (email, Telegram, Slack, Discord, generic webhook). We continue monitoring and notify you when the website comes back online. The Analytics Modal's check log shows exactly when each failed check happened.

We monitor both uptime and response time. Our dashboard displays response times, average response metrics, and an interactive response time chart covering your most recent checks or a date range you pick. You can also view uptime percentages with visual ring indicators for quick status checks.

Yes! When screenshots are enabled for a website, we capture one whenever its status changes and every 6 hours. You can view the screenshot history in the Analytics Modal, allowing you to see how your website looked at different points in time.

Click on any website card to open the detailed Analytics Modal. You'll see: uptime percentage with a visual ring chart, average response time, last check status, short outages, response time history chart, recent checks log with timestamps, and screenshot gallery. By default it covers your most recent 1,000 checks; pick a date range to look at a specific period, or export the data as CSV or JSON.

Absolutely! The dashboard includes a search bar to find websites by URL, and filter buttons to view All, Online, or Offline sites. You can also see statistics overview including total sites, overall uptime, sites online now, and average response time.

Yes! We support monitoring websites protected by HTTP Basic Authentication (standard server auth). You can provide username and password credentials when adding your website. However, form-based login pages (where you fill out a login form) are not currently supported.

Automated Actions allow you to run SSH commands on your server automatically when your website goes down. For example, you can configure it to restart Nginx or reboot the server if downtime persists for more than 5 minutes. This feature helps in self-healing your infrastructure without manual intervention.

The number of allowed automated actions depends on your plan:

• Starter: 1 action per website
• Plus: 5 actions per website
• Professional: 10 actions per website

Escalation by duration lets you send an extra notification to a dedicated webhook when downtime exceeds a threshold (e.g. 15 minutes). Useful for integrating with PagerDuty, Opsgenie, or your own incident system: first alerts go to your regular channels; if the site is still down after X minutes, we also POST to your escalation URL with event escalation, downtime minutes, and cause details. Configure it per website under Edit website → Settings (Escalation by duration).

Scheduled actions run on a schedule (e.g. daily at 3:00 or weekly on Sunday), not only when downtime is detected. You can run a webhook (e.g. health ping, backup trigger) or an SSH command (e.g. cache warm-up, log rotate). Configure them per website under Edit website → Scheduled tab: add a name, choose Daily or Weekly + time, and either a webhook URL or SSH command. The system runs due actions every minute.

Maintenance Windows allow you to schedule planned downtime for each website under Edit website → Maintenance. During these periods, we pause checks and alerts, preventing false alarms while you update your infrastructure. You can set one-time or recurring (daily/weekly/monthly) windows.

Yes. When SSL checking is enabled for a website, we track the certificate's issuer, validity, and expiration date. The dashboard and Analytics Modal highlight a certificate that is expiring within your chosen threshold (7 days by default, set under Edit website → Settings) or has already expired. SSL/TLS handshake and certificate errors that make the site unreachable are reported as downtime with the cause "SSL error". When a certificate enters that threshold we send an expiry reminder through all your notification channels, and one final reminder on its last day. A renewed certificate starts the cycle again.

Absolutely. Our Public API gives you full programmatic access to your monitoring data. You can fetch current status, retrieve historical stats (uptime & response time), and even manually trigger checks using the /check endpoint. Create a personal API token on the API Settings page; the API Docs page lists the endpoints.

We’ve designed the app to stay fast even as your data grows:

• Lightweight thumbnails: dashboard cards and screenshot history use small, optimized thumbnails, and load the full HD screenshot only when you open the preview.
• Pre‑aggregated stats: uptime and response‑time metrics for 1/7/30 days are pre‑calculated in the background, so analytics panels open quickly.
• Smarter timelines: response timelines and logs are capped and optimized so you see the last checks instantly without overloading the browser.
• API performance tracking: we internally monitor our own API response times to catch regressions early.

Yes. From the dashboard, remove a site when you no longer need it. Related check data is cleaned up in the background so the UI stays responsive. You can still export historical checks first from Reports & exports if you need a copy.

Public Status Pages give you a dedicated URL (for example /status/your-slug) that shows an overall health headline, each monitored service with 30-day uptime and average response time, a bar of up to 50 recent check outcomes (hover for details), and a recent incidents list for failed checks in the last 7 days. Optional logo, description, and DaisyUI theme (light, dark, or cupcake when set on the page) help match your brand. Visitors never need an account.

Select Status Pages from your account dropdown menu. Click "New Status Page", give it a title and a unique slug (URL), and select the websites you want to display. You can also customize the "Display Name" for each website to make it more user-friendly for your audience.

Yes. Turn off Make this page public when editing the status page. While private, the plain URL /status/your-slug returns “not found” for everyone. You get a secret link that includes a ?k=… key—use the Open link from Status Pages in the app, or copy that full URL to share with your team. Making the page public again clears the key. We also accept your JWT if you request the page with an Authorization: Bearer header (for API or scripted access).

This feature is available for all our subscribers, including the free tier. We believe every user should have the tools to build trust with their audience through transparent uptime monitoring.

Yes. The public page uses an automatic full reload every 60 seconds so viewers see fresh data without refreshing manually. It also shows when the snapshot was built.

On the status page, maintenance windows, temporary pause, and inactive monitoring are called out separately from a hard outage, so visitors understand planned work or disabled checks versus an unexpected failure. The overall banner still reflects real outages on actively monitored services.

We support Email, Telegram, Slack, Discord, and Generic Webhook notifications. You can enable or disable each channel independently from the Notification Settings page. Configure multiple channels to ensure you never miss an alert about your website's status.

Go to Notification Settings from the header menu, click "Generate Link Code", and send the /link command it shows to @up2ame_bot. Once connected, you'll receive instant alerts when your websites go down or come back online.

Yes, on the Plus and Professional plans. Alerts then come from your company's bot instead of @up2ame_bot, to a private chat, a group or a channel.

1. Create a bot with @BotFather (or use an existing one) and copy its token.
2. Open the bot and press Start, or add it to your group (as an admin for a channel).
3. In Notification Settings → Telegram → Your own bot, paste the token and the chat ID. Find chats lists chats that recently messaged the bot.
4. Press Verify & save. We post a confirmation message to the chat to make sure it works.

The token is encrypted at rest. We only send messages: we never change your bot's webhook or commands. If your plan ends, alerts fall back to @up2ame_bot.

First, check your notification settings in your account. If everything appears correct, use the Contact form and we will help troubleshoot the issue.

No. Alert messages use a standard format that includes the website, its status, and the probable cause. Custom message templates are not supported.

An alert is sent once the website fails the number of consecutive checks you set for it (3 by default, configurable per website). How long that takes depends on the check interval: with 1-minute checks and the default of 3, that is about 3 minutes. Requiring several consecutive failures keeps one-off glitches from triggering alerts.

Yes! Click the theme toggle button in the header to switch between Light and Dark themes. The theme preference is saved to your browser and applies across all pages including authentication pages (Login, Signup, Password Reset). The system automatically detects your OS theme preference on first visit.

Simply click on any website card in your dashboard. This opens the Analytics Modal showing comprehensive data: uptime percentage ring chart, average response time, last check status, response time history chart, recent checks table with timestamps, and screenshot gallery. You can scroll through all the data in one convenient view.

You can stop checks in two ways:

• Active / Inactive toggle: turns monitoring off until you turn it back on. The site stays in your list; no checks run while inactive.
• Temporary pause (dashboard): use the pause control on a site card to silence checks for a short period (default length is configurable under Edit website → Settings). Checks resume automatically when the pause ends, and the card can show how long pausing remains.

Use inactive for longer “off” periods; use pause for quick maintenance windows without forgetting to re-enable monitoring.

The circular ring shows the uptime percentage of the website's last 60 checks, with the exact percentage shown next to it. Green (≥98%) means excellent uptime, yellow (90-97%) indicates some issues, and red (<90%) shows significant downtime. The center dot uses the same color, or gray when monitoring is inactive.

We have monitoring nodes located in Russia. This ensures reliable monitoring for websites in the region.

We monitor all standard HTTP status codes. Green indicators for 200 (OK), yellow for 3xx redirects (301, 302), and red for errors (4xx, 5xx). The dashboard displays color-coded status bars showing the history of all checks, making it easy to spot patterns.

We only send a downtime alert after several consecutive failed checks (3 by default, adjustable per website). Failures that recover before that are recorded as short outages instead of triggering an alert.

Check history (response times and status codes) is kept for 30, 90, or 180 days depending on your plan; screenshots are kept for 6 months. The analytics modal shows your most recent 1,000 checks by default, and you can pick a date range to look at any period within your retention window.

Yes. We internally track the performance of our core monitoring APIs (e.g. dashboard and analytics endpoints) and store response times per route.

These internal metrics help us detect slowdowns or regressions early, so we can keep the app fast and responsive even as we add new features.

Our dashboard provides a comprehensive overview of your infrastructure:

• Overall Uptime: Your success rate across all sites over each site's last 60 checks.
• Response Timeline: An interactive chart showing status and latency for recent checks.
• Real-time Status: Instant filter for All, Online, or Offline sites.

Data retention depends on your plan tier:

• Starter: 30 days of history
• Plus: 90 days of history
• Professional: 180 days of history

Open Reports & exports from your account menu. The page has two separate tools:

• Executive PDF reports (Plus and Professional): set a title, date range, and whether to include all your websites or only the ones you select. Each run creates one shareable PDF (uptime, incidents, metrics). Completed reports can be downloaded from the list; the list is paginated (10 reports per page). If generation fails, the status shows Failed with a short error summary so you know it did not complete.
• Export check history (all plans): pick one monitored site, optional start/end dates (or leave both empty to export all stored checks for that site — exports can be large), and CSV or JSON. This is raw check data for Excel, BI tools, or backups — not the same as a PDF summary.

Every failed check is tagged with a probable cause, which you can see in the Analytics Modal and in alert messages. Examples include:

• DNS resolution failed
• SSL/TLS handshake or certificate error
• Request timed out / connection failed
• Server error (5xx) or Page not found (404)
• Required keyword missing in the page body

This helps you quickly understand whether an incident is caused by DNS, SSL, networking, application errors, or unexpected content changes.

Short outages are brief downtimes that recovered before the main alarm fired. We only send the main "site down" alert after several consecutive failed checks (e.g. 3). If your site failed 1 or 2 checks and then came back, that counts as a short outage — no alert, but we record it.

In the Analytics Modal and on the dashboard you'll see "Short outages: X in 24h" (and in 7 days). You can also enable Unstable work detection in Edit website → Settings: choose Manual (e.g. alert when 10 short outages in 2 hours) or Auto (intelligent) — the system learns your normal pattern from the last 14 days (mean and variance) and flags when the last 24h is statistically above that baseline (e.g. mean + 1.5× standard deviation or above the 95th percentile). When flagged, the site shows an "Unstable" badge and the reason in analytics.

Yes! We support Incoming Webhooks for both Slack and Discord. Simply create a webhook in your channel settings and paste the URL into your Notification Settings in our dashboard.

Yes. In Notification Settings, enable Generic Webhook and enter your endpoint URL. We send a POST request with a JSON payload for every alert and recovery. Events include website_down, website_restored, keyword_missing, ssl_alert, performance_warning and log_match. The payload includes the site URL, message, severity, and meta (status_code, response_time_ms, cause_code, cause_summary) so you can automate workflows in Zapier, IFTTT, or your own services.

This per-website setting (under Edit website → Settings) controls how often we send repeated alerts while a website remains offline. You can adjust this to avoid alert fatigue or ensure critical issues are constantly highlighted. The shortest interval depends on your plan: 60 minutes on Starter, 30 on Plus, and 5 on Professional.

Automated Actions allow our system to automatically execute SSH commands on your server when downtime is detected. For example, you can set it to restart Nginx or clear a cache if a site stays down for more than 5 minutes.

Security is our top priority. Passwords and private keys are encrypted at rest and are never shown again after you save them. We recommend an SSH private key for a dedicated user that has only the rights your commands and log files need.

Open Servers & Logs from the account menu. Add each server once (host, port, user, password or private key) and press Test connection. Auto-actions, scheduled SSH actions and log monitors then simply pick that server, so you never paste credentials twice, and changing a password updates every action at once.

Available on Plus (2 log files, checked every 15 to 60 minutes) and Professional (10 log files, as often as every minute). We connect to your server over SSH on a schedule, read only the lines added since the last check, and alert you when lines contain a word or match a regular expression, for example error|fatal|out of memory in /var/log/nginx/error.log.

• Choose how many matching lines in one check trigger an alert, and a quiet period between alerts.
• Alerts go to all your channels (email, Telegram, Slack, Discord, webhook event log_match) with the matching lines.
• Log rotation is detected automatically. Any plain-text file your SSH user can read works.
• Test shows the last lines of the file and marks the ones that would match.

Yes! There is a "Test Run" button in the Action Manager. It allows you to execute the command manually and see the full output from your server to ensure everything is configured correctly.

Yes. Auto‑Fix (SSH Actions) can be targeted to specific root causes. For each action you can select one or more triggers (multi-select): e.g. only on server errors (5xx) and timeout, or only DNS errors. Leave all unchecked for "Any downtime."

• Only on server errors (5xx) – e.g. restart your app or web server.
• Only on DNS errors – e.g. hit your DNS or infrastructure automation.
• Only when a required keyword is missing – e.g. trigger a redeploy if the page content is wrong.

Configure this in Edit website → Auto-Actions under "When this happens."

We typically respond to messages sent through the Contact form within 24 hours.

No. Support is provided through the Contact form, and we reply by email. Our Telegram bot only sends monitoring alerts.

We welcome feature suggestions! Send them via the Contact form. We regularly review user feedback for future updates.