UptimePoint Documentation

Welcome to UptimePoint — the all-in-one monitoring platform built for web agencies. This guide will help you set up your account, add your first site, and understand the core concepts.

Creating Your Account

Go to the registration page and fill in your email address, your name, and your agency name. Choose a strong password. Once registered, you'll receive a verification email — click the link to activate your account.

You can start a 14-day free trial on the Solo plan or 7 days on the Team plan — no credit card required.

Adding Your First Site

1. Log in to your dashboard
2. Click "Add site" in the Sites section
3. Enter the full URL (e.g., https://example.com)
4. Select the check types you want to enable (uptime, SSL, domain, DNS, performance)
5. Configure alert thresholds (e.g., alert after 2 consecutive failures)
6. Click "Save" — monitoring starts immediately

The first check results appear within minutes. You'll see the site status (Online / Offline) and detailed metrics for each enabled check type.

Understanding Your Dashboard

Your dashboard is the command center. From here you can:

• Overview — See the global health of all your monitored sites at a glance
• Sites — Manage individual sites, their check types, and alert settings
• Alerts — Configure notification channels and alert contacts
• Reports — Generate PDF reports for your clients
• Team — Invite collaborators and manage permissions
• Settings — Customize your white label, API keys, and account preferences

Navigation Tips

Use the sidebar on the left to move between sections. The top bar shows your organization name and plan. You can switch languages at any time using the language selector.

Uptime monitoring checks your websites at regular intervals to ensure they are online and responding correctly. UptimePoint uses got-scraping for reliable HTTP requests.

How It Works

Every check interval, UptimePoint sends an HTTP request to your site. If the site responds with a success status code (2xx or 3xx), it's marked as online. If it fails to respond or returns an error status (4xx or 5xx), it's marked as offline after the configured number of consecutive failures.

Check Intervals by Plan

Alert Thresholds

You can configure when alerts are triggered:

• Max retries — Number of consecutive failures before alerting (default: 2)
• Check timeout — Maximum wait time for a response (default: 30s)
• Recovery notification — Automatic alert when the site comes back online

HTTP Method & Headers

Each uptime check supports:

• Method — GET (default), HEAD, or POST
• Custom headers — Set authentication tokens, user-agents, etc.
• Expected status — Define which HTTP status codes count as "online"
• Keyword check — Verify that a specific keyword exists in the page HTML

Uptime SLA & Reporting

UptimePoint calculates your site's uptime percentage over selected periods (24h, 7d, 30d, 90d, 1y). This data is used in PDF reports and the dashboard overview. Uptime is calculated as: online checks / total checks × 100.

SSL/TLS certificates are critical for website security and SEO. UptimePoint checks your certificates daily and alerts you before they expire.

Automatic Daily Checks

Every day, UptimePoint connects to your site and inspects the SSL certificate. The following information is collected:

• Issuer — The certificate authority that issued the certificate (e.g., Let's Encrypt, DigiCert)
• Subject — The domain name the certificate is issued to
• Valid from / Valid until — The validity period
• Remaining days — Days until expiration
• Certificate chain — Whether the chain is complete and trusted

Alert Triggers

You will receive alerts at configurable thresholds:

• 30 days before expiry — Informational warning
• 14 days before expiry — Priority warning
• 7 days before expiry — Critical alert
• On expiry — Immediate notification
• On misconfiguration — Self-signed certificates, incomplete chains, hostname mismatches

SSL Configuration Tips

• Use a trusted CA like Let's Encrypt (free) or DigiCert (premium)
• Enable auto-renewal if your hosting provider supports it
• Ensure the certificate chain includes all intermediate certificates
• Use at least TLS 1.2 or higher (TLS 1.0 and 1.1 are deprecated)

Supported Check Types

SSL monitoring is available on all plans. No additional configuration is needed — just enable SSL checks when adding or editing a site.

Never let a domain expire again. UptimePoint monitors your domain registration dates and alerts you well in advance.

WHOIS Checks

UptimePoint performs automatic WHOIS lookups to retrieve your domain's registration and expiration dates. The check runs daily and captures:

• Creation date — When the domain was first registered
• Expiration date — When the domain registration ends
• Registrar — The company where the domain is registered
• Name servers — Current DNS servers
• Registrant contact — Owner information (if not redacted)

Alert Configuration

Configure when you want to be notified:

• 30 days before expiry — Recommended for standard domains
• 14 days before expiry — Urgent reminder
• 7 days before expiry — Critical alert
• On expiry — The domain has expired

Best Practices

• Enable auto-renewal with your registrar whenever possible
• Register domains for multiple years to reduce risk
• Keep your registrant contact email up to date
• Use a dedicated email address for domain registration to avoid missing renewal notices
• Monitor all domains in your portfolio, including those you manage for clients

DNS is the backbone of your online presence. UptimePoint monitors your DNS records to detect configuration errors, unauthorized changes, and potential security issues.

Records Checked

• A / AAAA — IPv4 and IPv6 address records
• CNAME — Canonical name records (aliases)
• MX — Mail exchange records
• TXT — Text records (SPF, DKIM, DMARC, etc.)
• NS — Name server records
• SOA — Start of authority

SPF, DKIM & DMARC

Email authentication records are critical for deliverability. UptimePoint checks:

• SPF — Validates that your SPF record exists and doesn't exceed the 10-lookup limit
• DKIM — Verifies your DKIM signature is properly configured
• DMARC — Checks your DMARC policy (none, quarantine, or reject)

Change Detection

UptimePoint compares DNS records between checks and alerts you when changes are detected. This helps you spot:

• Unauthorized DNS modifications (hijacking)
• Accidental configuration changes
• DNS propagation after planned updates

Alert Configuration

You can set alerts for:

• Missing required records (e.g., SPF, MX)
• Unexpected changes to any record type
• Misconfigured values (e.g., wrong TTL, invalid targets)

Site speed affects SEO rankings, user experience, and conversion rates. UptimePoint integrates with Google PageSpeed Insights to monitor Core Web Vitals and provide actionable optimization suggestions.

Core Web Vitals

Google's Core Web Vitals are a set of metrics that measure real-world user experience:

• LCP (Largest Contentful Paint) — Loading performance. Should be < 2.5s
• FID (First Input Delay) / INP (Interaction to Next Paint) — Interactivity. Should be < 100ms for FID, < 200ms for INP
• CLS (Cumulative Layout Shift) — Visual stability. Should be < 0.1

PageSpeed Reports

Each performance check generates a detailed PageSpeed report including:

• Performance score — 0-100 rating
• Accessibility score — How accessible your site is
• Best practices score — Adherence to web standards
• SEO score — Search engine optimization factors
• Lab data — First Contentful Paint, Speed Index, Time to Interactive, Total Blocking Time
• Opportunities — Specific optimizations with estimated time savings
• Diagnostics — Additional performance information

Configuration

To enable performance monitoring:

1. Go to Admin > Configuration technique > Google PageSpeed
2. Enter your Google PageSpeed API key (get one from the Google Cloud Console)
3. Enable performance checks on individual sites via the site editor

Performance monitoring is available on Solo+ plans.

Interpreting Scores

• 90-100 — Good (green)
• 50-89 — Needs improvement (orange)
• 0-49 — Poor (red)

Get notified immediately when something goes wrong. UptimePoint offers multiple notification channels so you never miss a critical alert.

Notification Channels

Email

Available on all plans. Alert emails are sent to configured contacts. For security, email contacts must be verified via a one-time password (OTP) code, unless the email matches your login email.

SMS (via Plivo)

Available on Solo+ plans. SMS alerts require a Plivo account configured in the admin panel. Each SMS contact must verify their phone number via OTP. SMS credits are consumed per message.

Telegram

Connect your Telegram bot and receive alerts directly in a chat channel. Setup:

1. Create a Telegram bot via @BotFather
2. Get your bot token and chat ID
3. Configure in Alerts section

Discord

Receive alerts in a Discord channel via webhook. Simply enter your Discord webhook URL in the alert configuration.

Slack

Similar to Discord — enter your Slack webhook URL to receive alerts in a Slack channel.

Alert Contacts

Alert contacts are the people who receive notifications. Each contact can have multiple channels (email, SMS, Telegram, etc.). You can add contacts from the Alerts section of your dashboard. Contacts must be verified before they can receive alerts.

Alert Rules

Each alert rule defines when notifications are sent:

• On failure — When a site goes down
• On recovery — When a site comes back online
• On SSL expiry — When a certificate is about to expire
• On domain expiry — When a domain is about to expire
• On DNS change — When DNS records change unexpectedly

Generate professional PDF reports for your clients. UptimePoint's reporting engine creates beautiful, branded documents that demonstrate your agency's value.

Features by Plan

Report Contents

Each PDF report includes:

• Cover page — Client name, report period, agency logo
• Executive summary — Overall health overview
• Uptime graph — Timeline of online/offline events
• SSL status — Certificate validity and expiry
• Domain status — Expiration dates
• Performance scores — Core Web Vitals and PageSpeed results
• Response times — Average, min, max latency
• Incident log — Detailed list of all downtime events

Scheduled Reports

Configure automatic report delivery:

1. Go to Reports in the sidebar
2. Click "Schedule report"
3. Select the client site(s), frequency (daily, weekly, monthly), and recipients
4. The system generates and sends reports automatically via email

Manual Generation

You can also generate reports on demand from the Reports section. Choose the site, date range, and generate a PDF instantly.

Present your reports under your own brand. UptimePoint's white label features let you customize every aspect of the PDF appearance.

Available Customizations

Agency Logo (Solo+)

Upload your agency's logo in PNG, JPEG, WebP, or SVG format. The logo appears on the cover page and header of all PDF reports. Maximum file size: 2 MB.

Colors & Fonts (Team+)

Customize the visual identity of your reports:

• Primary color — Main brand color (used for headers, accents, charts)
• Secondary color — Complementary color
• Font family — Choose the PDF font (Helvetica by default)

Report Footer (Team+)

Add a custom footer to every page of your PDF reports, such as your agency's copyright notice or contact information.

Custom Domain for Report Links (Team+)

Use your own domain for public report links. Instead of uptimepoint.com/reports/..., your links will use reports.youragency.com/.... This requires DNS configuration pointing a subdomain to UptimePoint.

Full White Label (Enterprise)

Complete removal of all UptimePoint branding:

• No "Powered by UptimePoint" on PDFs
• Full custom domain (site-wide)
• Custom email templates (optional)
• Dedicated support and SLA

How to Configure

1. Go to Settings > White label
2. Upload your logo and customize colors/fonts
3. Set your custom domain (Team+)
4. Enable "Hide UptimePoint branding" (Enterprise)
5. Save — new reports will use your branding immediately

Invite your collaborators and manage permissions with granular role-based access control. UptimePoint makes it easy to work together as a team.

Roles & Permissions

Plan Limits

• Free / Solo — 1 user (you)
• Team — Up to 3 members
• Enterprise — Unlimited members

Inviting Team Members

1. Go to Team in the sidebar
2. Click "Invite member"
3. Enter their email address and select their role
4. They'll receive an invitation email with a link to join
5. Once they accept, they can access the dashboard according to their role

Managing Members

From the Team page you can:

• View all current members and their roles
• Change a member's role
• Remove a member from the organization
• Resend invitation emails

The UptimePoint REST API allows you to automate every aspect of your monitoring platform. Integrate with your existing tools, build custom dashboards, and streamline your workflow.

See the API documentation for more details.

API Overview

The API follows RESTful principles. All requests must be authenticated with an API key. Responses are in JSON format.

Authentication

Generate API keys from Settings > API. Each key has a name for identification. Include the key in requests via the Authorization header:

Authorization: Bearer up_api_xxxxxxxxxxxx

Endpoints

• GET /api/v1/sites — List all sites
• POST /api/v1/sites — Create a new site
• GET /api/v1/sites/:id — Get site details
• PUT /api/v1/sites/:id — Update a site
• DELETE /api/v1/sites/:id — Delete a site
• GET /api/v1/sites/:id/status — Get current status
• GET /api/v1/sites/:id/history — Get check history
• GET /api/v1/sites/:id/report — Generate a report
• GET /api/v1/alerts — List alerts
• POST /api/v1/alerts — Create an alert

Rate Limits

API requests are rate-limited to prevent abuse:

• Team — 60 requests per minute
• Enterprise — 300 requests per minute

Availability

The API is available on Team+ plans.

Webhooks allow you to receive real-time HTTP notifications when events occur in your UptimePoint account. Integrate with Slack, Discord, custom applications, or any service that accepts HTTP requests.

How Webhooks Work

When a monitored event happens, UptimePoint sends an HTTP POST request to your configured endpoint URL with a JSON payload containing the event details.

Event Types

• site.down — A monitored site went offline
• site.up — A site recovered and is back online
• ssl.expiring — An SSL certificate is expiring soon
• ssl.expired — An SSL certificate has expired
• domain.expiring — A domain is expiring soon
• domain.expired — A domain has expired
• dns.changed — DNS records changed unexpectedly

Payload Format

{
  "event": "site.down",
  "site_id": "clx...",
  "site_name": "Example Client",
  "site_url": "https://example.com",
  "timestamp": "2026-06-13T12:00:00Z",
  "check_type": "uptime",
  "message": "Site is down (HTTP 500)"
}

Configuration

1. Go to Settings > Webhooks
2. Click "Add webhook"
3. Enter a name for the webhook
4. Enter the target URL (your endpoint that receives POST requests)
5. Select the events you want to subscribe to
6. Save — the webhook is active immediately

Security

You can optionally configure a secret token that UptimePoint sends as an X-Webhook-Secret header, allowing your endpoint to verify that requests are genuinely from UptimePoint.

Availability

Webhooks are available on Team+ plans.

Scheduling a maintenance window

Maintenance windows allow you to schedule periods during which monitoring is suspended for specific sites. This prevents unnecessary alerts when performing planned updates.

• Access : Dashboard → Maintenance Windows
• Required fields : Title, start, end, affected sites
• Recurrence : One-time, daily, weekly, or monthly

Behavior during maintenance

• Checks are automatically suspended for the affected sites
• No alerts are sent (email, Slack, Telegram)
• Planned downtime does not impact your SLA
• Status pages display a "Maintenance in progress" banner
• Each site in maintenance shows a "Maintenance" badge instead of uptime percentage

Recurrence types

• One-time : Single window with specific date and time
• Daily : Repeats every day at the same time (e.g., daily backup)
• Weekly : Repeats every week on the same day (e.g., Sunday maintenance)
• Monthly : Repeats every month on the same date

REST API

Maintenance windows can also be managed via the REST API :

• GET /api/v1/maintenance-windows — List windows
• POST /api/v1/maintenance-windows — Create a window
• GET /api/v1/maintenance-windows/{id} — Details
• PUT /api/v1/maintenance-windows/{id} — Update
• DELETE /api/v1/maintenance-windows/{id} — Delete

See the API documentation for more details.

What is a Heartbeat?

Heartbeats allow you to monitor your scripts, cron jobs, processes and pipelines. You receive an alert as soon as a script fails to execute on time.

Setup

From the Heartbeats dashboard, create a new heartbeat. Copy the generated endpoint URL and include it in your script. On each execution, your script sends an HTTP signal to this URL.

Available Signals

• start : Execution started
• beat : Keepalive during execution (repeated)
• complete : Successful completion
• fail : Script failure

Use these signals for precise lifecycle tracking of your scripts.

Cron Expression

You can optionally provide a cron expression so the system automatically calculates the expected interval between executions.

Status Badge

Each heartbeat has an embeddable SVG badge for your READMEs, dashboards or wikis. The badge URL is: /api/heartbeat/[TOKEN]/badge.svg

REST API

Heartbeats are also manageable via the REST API. See the API documentation for details.

What is an Incident?

An incident is a downtime event affecting one or more of your sites. UptimePoint automatically creates an incident when a site goes DOWN, and automatically resolves it when it comes back UP.

Incident Lifecycle

Automatic Incidents

When a site becomes unreachable, an incident is automatically created with "Investigating" status and the root cause extracted from the error message (e.g. HTTP 403, Timeout, SSL_ERROR).

As soon as the site is back online, the incident is automatically resolved with the total downtime duration calculated. An enriched alert email is sent with the following details:

Manual Incidents

From the Incidents dashboard (icon ), you can manually create incidents for scheduled maintenance, infrastructure outages, or any other event.

Status Pages

Incidents are automatically linked to status pages that include the affected sites. Your visitors will see the complete incident timeline with status badges, root cause, and updates.

Dashboard Features

The Incidents dashboard page provides:

• Search by incident title
• Filters by status, impact, auto/manual origin
• Sort by date (newest / oldest)
• Pagination: 5, 10, or 20 incidents per page
• Actions: resolve, edit, add updates, delete

REST API

Incidents are fully manageable via the REST API. Authenticate with a Bearer token (prefix awm_).

• GET /api/v1/incidents — List incidents (paginated)
• POST /api/v1/incidents — Create an incident
• GET /api/v1/incidents/{id} — Get incident detail with updates
• PUT /api/v1/incidents/{id} — Update incident (status, impact, resolution)
• DELETE /api/v1/incidents/{id} — Delete an incident

See the full API documentation for more examples.

Overview

Browser push notifications display a system-level alert right on the user's screen, even when the UptimePoint tab is closed and the browser runs in the background. It is the fastest channel after SMS, with no per-message cost.

Compatibility

• Desktop: Chrome, Edge, Firefox, Opera (Windows / macOS / Linux)
• Mobile: Android via Chrome/Firefox; iOS 16.4+ only when the site is added to the home screen
• An HTTPS connection is mandatory (already the case in production)
• Each browser on each device is a separate subscription: one account can receive notifications on several devices at once

Step-by-step activation

• Open Settings → Push notifications & Telegram.
• Click "Enable notifications": the browser asks for permission — click "Allow".
• The service worker registers automatically, then your subscription is sent to the server.
• The "Active" badge confirms the operation.

Testing

The "Send test" button triggers an immediate notification on all your subscribed devices. If nothing appears:

• Check that notifications are not blocked at browser level (padlock icon in the address bar) or OS level (Do Not Disturb mode).
• Re-enable notifications: a subscription inactive for a long time (device off, browser reinstalled) is automatically deleted by our servers as soon as it reports expired.

Notified events

• Site DOWN → critical notification linking straight to the monitored site; recovery → green notification
• Missed / recovered heartbeat
• Broken links detected / resolved
• Escalations: every level can target push notifications

Security & privacy

Messages are end-to-end encrypted between our server and the browser's push service thanks to the VAPID keys generated automatically by the platform. The subscription URL is unique per browser and cannot identify the user outside UptimePoint. Clicking a notification opens the monitored site's page directly. To stop everything: "Unlink" for Telegram, or revoke the permission from browser settings.

Official UptimePoint bot

Unlike solutions that require creating your own bot and manually finding your chat ID, UptimePoint ships an official bot: you click, send /start, done.

Administrator setup (once)

• Create the bot with @BotFather on Telegram: run /newbot, keep the provided token.
• Store it in the platform configuration:
  UPDATE "SystemConfig" SET "telegramBotToken"='YOUR_TOKEN' WHERE id='global';
• Register the public webhook (run once on the server):
  npx tsx prisma/register-telegram-webhook.ts https://www.uptimepoint.com
• This command calls setWebhook on Telegram, generates the verification secret and caches the bot username. It is idempotent: safe to re-run.

Linking your account (30 seconds)

• In Settings → Push notifications & Telegram, click "Connect Telegram".
• A t.me/YourBot?start=UNIQUE_TOKEN link opens: just send /start to the bot from Telegram.
• The webhook receives the confirmation, binds your chat ID to your UptimePoint account and deletes the one-time token.
• The "Active" badge appears. Use "Send test" to validate end-to-end.

Messages you receive

• Incidents: site down (with HTTP status and response time when available), recovery with total outage duration
• Heartbeats: missed execution, recovery
• Broken links: detection and resolution
• Escalations: each level can add Telegram as a recipient

Security

• The public webhook verifies the X-Telegram-Bot-Api-Secret-Token header: link forging from outside is impossible.
• Link tokens are single-use and deleted after verification.
• A platform-wide kill switch exists (telegramNotificationsEnabled flag).

Troubleshooting

• Greyed-out button / "unavailable": the admin has not configured the bot token yet.
• Link stays pending: check the webhook registration (re-run the registration command), then send /start again.
• Test fails: the link may have expired on Telegram's side — unlink then link again.

Unlinking

Click "Unlink" to instantly remove the binding and stop all deliveries to your chat. You can re-link anytime with a fresh token.

The principle

An escalation is a chain of notification levels triggered progressively when a site goes down and stays DOWN. Goal: reach the right person at the right time — without waking the whole team over a micro-outage, and without letting a major incident go unnoticed.

How it works in detail

• Trigger: as soon as a site transitions UP → DOWN (uptime check), an escalation "run" starts for every enabled escalation covering that site.
• Level 1: fires immediately (0 delay). Example: notify the on-call technician (email + push).
• Subsequent levels: each fires after its own delay, counted from the start of the outage, while the site remains DOWN. Example: Level 2 after 15 min → tech lead (SMS); Level 3 after 60 min → management (email + SMS + Telegram).
• Recovery: as soon as the site comes back UP, all active runs for that site are closed and every already-reached level gets a "Resolved" notification. Unreached levels are never notified.
• No duplicates: one active run per escalation per site; subsequent outages create new runs.

Creating an escalation

• Escalations dashboard tab → "New escalation".
• Name: free-form (e.g. "Production escalation").
• Affected sites: tick one or more sites, or none to cover the whole fleet.
• Levels: add as many levels as needed. For each level:
  • Delay (minutes before firing, counted from outage start; level 1 is always immediate)
  • Emails: comma-separated list — recipients do not need an account
  • SMS numbers: international format (+1212…), sent through the platform's Plivo configuration
  • Push: notifies every organization member subscribed to browser notifications
  • Telegram: notifies every member who linked their account
  • Every level must contain at least one channel

Real-time monitoring

During an outage, active escalations appear at the top of the page (affected site, current level, start time) with a manual cancel button — useful when the team is already handling the incident and wants to stop further reminders. Every sent notification is logged in the alert history (channel, recipient, type, timestamp).

Pause and deletion

The pause button temporarily disables an escalation without losing its configuration; the engine then ignores new outages entirely. Deletion is permanent and also cleans up run history.

Plan availability

• FREE: unavailable · SOLO: 1 escalation · TEAM: 5 · ENTERPRISE: 10 · ENTERPRISE+: unlimited
• The number of levels per escalation is unlimited; max delay per level is 24 h (1440 min).

Best practices

• Start with 3 levels (immediate / +15 min / +60 min) and adjust based on real incidents.
• Reserve SMS for critical levels only: it is the only usage-based paid channel.
• Use "all sites" for a general on-call, and per-site targeted escalations for critical services.

Overview

Broken link monitoring crawls your site daily to detect links, internal or external, that no longer respond (404 errors, deleted pages, expired domains, and so on). A BFS crawler follows every link found in the HTML and records the failures with their HTTP status code and source page. It complements uptime checks: it does not replace the 1–5 minute uptime monitoring, but runs once a day.

How it works

• Triggered daily by a scheduled job (/api/cron/background-jobs).
• A breadth-first crawler follows <a href> links, using a HEAD request then falling back to GET.
• A 200 ms delay between requests limits the load on your server.
• The result (broken link count, pages crawled, percentage) is stored in the latest check result.

Per-site configuration

• monitorBrokenLinks — enables or disables the scan for the site.
• brokenLinksMaxPages — maximum number of pages to crawl (based on your plan).
• brokenLinksIncludeExternal — includes links pointing to external domains.
• brokenLinksExcludePatterns — regular expressions (one per line) to exclude certain URLs.

Plan limits

• Free: not available
• Solo: 500 pages per scan
• Team: 2,000 pages
• Enterprise: 5,000 pages
• Enterprise+: 10,000 pages

Alerts

• BROKEN_LINKS_DETECTED and BROKEN_LINKS_RESOLVED alerts are sent through the configured channels.
• Enable them in the site's alert configuration (the broken links detected / resolved fields).

Manual scan ("Check now")

The "Check now" button does not run the full crawl (too slow). On a site's Broken Links card, use the "Scan now" button for a quick scan capped at 50 pages, with no delay between requests.

Best practices

• Exclude highly dynamic areas (search pages, carts, comment sections).
• Limit the number of pages to avoid saturating a large site.
• Prioritize internal links first: they hurt SEO the most.

Overview

A status page is a public page that displays the real-time state of your sites at a dedicated URL (/status/slug). It is the ideal transparency tool to reassure your customers during an outage: your sites are shown with an availability badge, a history, and ongoing incidents.

Creation and sharing

• Create a page from the dashboard (Dashboard → Status Pages) and pick a slug.
• The page is published by default and available to everyone at https://your-domain/status/slug.
• A JSON API (/api/status/slug) exposes the same data for your own tools.

Page content

• Monitored sites with an availability badge (Online / Offline) and a 30-day percentage.
• Availability history (24h, 7 days, 30 days, 90 days).
• Ongoing and past incidents (with timeline and updates).
• Optional heartbeats (pulse + last ping) when added to the page.

Customization

• White label: custom colors, logo and name (Enterprise / Enterprise+).
• Custom domain: serve the page from your own domain (Enterprise+).
• Built-in templates, site groups, badges and widgets to embed in your site.
• Password protection (Enterprise+), analytics (GA) and custom CSS (Enterprise+).

Advanced features

• Subscribers: visitors can subscribe to receive status alerts.
• Noindex: control the page's search engine indexing.
• Automatic incidents: an incident detected on an included site is displayed automatically.

Plan limits

• Free: 1 page
• Solo: 10 pages
• Team: 100 pages
• Enterprise and Enterprise+: unlimited

Best practices

• Link to your status page from your footer and support emails.
• Show incidents with their status to reduce support tickets during an outage.

Overview

The security of your account relies on several layers: strong passwords, login attempt detection, two-factor authentication (2FA), account suspension, and secure password reset.

Two-factor authentication (2FA)

• Adds an extra layer of protection to sign-in, on top of your password.
• Enable 2FA from your account settings (Settings → Security).
• At sign-in, an additional code is required after your password.

Attempt detection & reCAPTCHA

• After several failed sign-ins (configurable threshold, 3 by default), a reCAPTCHA is shown.
• The reCAPTCHA key is configured by the administrator (Admin panel → Configuration).

Forgot password & reset

• From the sign-in page, use Forgot password?.
• A single-use reset link (valid for 1 hour) is sent by email.
• Choose a strong password and do not reuse it elsewhere.

"Remember me"

• The "Remember me" checkbox extends your session on the device.
• Without it, your token is invalidated after 24 hours.
• Use it only on trusted devices.

Account suspension

• An account can be suspended by the administration (with a recorded reason).
• Suspended accounts lose access to the application; reactivation is up to the administrator.

Best practices

• Enable 2FA and use a password manager.
• Never share your 2FA code or your password.
• Make sure you are on https://uptimepoint.com before entering your credentials.

Overview

The referral program rewards you for every new user you bring to UptimePoint. You share your unique referral link, and as soon as the referred person becomes an eligible customer, you receive a credit.

Your referral code

• Every account has a unique code in the form UP-XXXXXXXX.
• You will find it in your Referrals area of the dashboard.
• Your personal link looks like https://uptimepoint.com/register?ref=YOUR_CODE.
• A code's public page (/referral/code) presents the offer and the sign-up button.

When is the reward granted?

• By default, the reward is granted when the referred person makes an eligible payment.
• A 30-day cookie associates the person with your code from their arrival.
• The reward is a day credit (30 days by default) applied to your subscription.

Reward types

• Day credit: adds days to your subscription period.
• Percentage credit: credit proportional to the amount paid by the referred person.
• The type and values are configured by the administrator.

Tracking

The Referrals dashboard shows your links, clicks, your referrals, and granted rewards. Notifications and emails keep you informed when a new reward is awarded.

Best practices

• Share your link on social networks, your newsletter, and your email signature.
• Explain the benefit rather than sharing the link alone: a personal recommendation converts better.

30-Day Money-Back Guarantee

UptimePoint offers a 30-day money-back guarantee on eligible paid subscriptions. If you are not satisfied for any reason, you can request a refund within 30 days of your initial paid subscription. No specific reason is required.

How to request a refund

• Contact UptimePoint Support (contact@uptimepoint.com).
• Provide the email address associated with your account and your subscription details.
• Have your invoice or payment identifier ready to speed up verification.

Eligibility conditions

• The request is made within 30 days of the initial paid subscription.
• The purchase can be verified.
• The account has not been involved in fraudulent or abusive activity.

Renewals

• The guarantee applies to the initial paid subscription, not recurring renewals.
• Processed renewals are generally non-refundable, except as required by law.
• To avoid a charge, cancel your subscription before the next billing date.

Cancellation vs refund

• Cancelling prevents future charges but does not automatically generate a refund.
• After cancellation, access to paid features remains active until the end of the paid period.

Processing

• Once approved, the refund is processed through the payment provider used.
• Displaying on your account may take several business days depending on the provider.
• Partial refunds may be granted at UptimePoint's discretion.

The refund policy page

The full /refunds page details the official policy, special cases (partial refunds, fraudulent transactions) and contact information.

UptimePoint offers flexible pricing plans for agencies of all sizes. Choose the plan that fits your needs and upgrade or downgrade at any time.

Plan Comparison

Free Trial

New accounts get a free trial:

• Solo — 14 days trial with full Solo features
• Team — 7 days trial with full Team features

No credit card is required to start your trial. When the trial ends, you can subscribe to continue using the service.

Payment Methods

We accept the following payment methods:

• PayPal — Pay with your PayPal account or credit/debit card via PayPal
• ZyndPay — Pay with USDT (TRC20) cryptocurrency

Billing Cycles

• Monthly — Billed every month
• Yearly — Billed once a year (save ~20%)

Changing Plans

• Upgrade — Instant. You're charged the prorated difference.
• Downgrade — Takes effect at the end of your current billing cycle.

Enterprise Plan

The Enterprise plan is not available for self-subscription. Contact us for a custom quote tailored to your agency's needs.

How do I change my plan?

Go to Settings > Billing. You can upgrade at any time — the change takes effect immediately with prorated billing. Downgrading takes effect at the end of your current billing cycle.

Can I try before buying?

Yes! The Solo plan offers a 14-day free trial and the Team plan offers a 7-day free trial — no credit card required. You get full access to all features during the trial period.

What happens when my trial expires?

Monitoring stops for all sites. Alert notifications and scheduled reports are suspended. Your data (sites, configurations, history) is preserved for 30 days. Subscribe to a paid plan to resume service.

How are payments handled?

We accept PayPal (credit/debit cards via PayPal) and ZyndPay (USDT TRC20). Subscriptions can be monthly or yearly. Yearly billing saves approximately 20%.

Can I use my own domain?

Yes. The Team plan includes a custom domain for public report links. The Enterprise plan includes a fully custom domain with complete white label (no UptimePoint branding anywhere).

How do I add team members?

Go to Team in the sidebar and click "Invite member". Enter their email and select a role. They'll receive an invitation email. Available on Team+ plans.

What monitoring types are supported?

UptimePoint supports: Uptime (HTTP/HTTPS), SSL/TLS certificate checks, Domain expiration monitoring, DNS record monitoring (SPF, DKIM, DMARC, A, CNAME, MX, TXT), and Performance (Core Web Vitals via Google PageSpeed).

How is uptime calculated?

Uptime percentage = (successful checks / total checks) × 100. A check is successful if the site responds with a 2xx or 3xx HTTP status code within the configured timeout.

What is the difference between Solo and Team?

Team adds multi-user access (up to 3 members), API access, webhooks, customizable PDF reports (colors, fonts, custom domain), 90-day history, and priority support. Solo is for single users who need basic PDF reports with their logo.

How do I contact support?

Use the contact form or email support@uptimepoint.com. We typically respond within 24 hours on business days.

Is there a mobile app?

UptimePoint is fully responsive and works on mobile browsers. Native mobile apps for iOS and Android are planned for future releases.

How do I set up SMS alerts?

SMS alerts require a Plivo account configured by the admin. Once configured, add a contact with a phone number and verify it via OTP. SMS alerts are available on Solo+ plans.