Frequently asked questions

MrVampCruz Uptime is an uptime monitoring service for websites, APIs, databases, and servers. Create a free account, add monitors, get email, in-app, and optional Telegram alerts when something goes down (and when it recovers), track incidents and history, and optionally publish public status pages. Built by Altaaf Hamod (MrVampCruz).

Individuals and teams who need reliable checks with clear plan limits — from a free starter tier to paid plans with multi-region checks, SSL/domain monitoring, teams, custom status URLs, and more. See Pricing for what’s on each plan today.

Altaaf Hamod, known online as MrVampCruz — a software engineer based in Mauritius. MrVampCruz is a personal brand, not a registered company.

The platform page at /status shows the live health of MrVampCruz’s own services. You can also enable your own public status page(s) at /status/your-link and choose which monitors appear. Teams can have their own status pages too.

No. The Free plan starts without a card. Paid plans check out through PayPal when you upgrade.

On the Pricing page. Plans and feature comparison load live from the API, with a monthly/yearly toggle. Prices are composed from features, so always check /pricing for current totals.

Yes. The Free plan starts without a card and includes a starter set of monitors, groups, one region per monitor, email and in-app alerts, limited incident/history retention, and a public status page. Paid features (for example faster checks, SSL/domain monitoring, custom HTTP options, custom status URLs, and teams) and exact Free limits are listed on Pricing and on your account plan.

Paid plans can be billed every month or once a year. Features are the same either way — yearly is just charged annually (usually at a better price). Use the Monthly / Yearly toggle on Pricing to compare.

Paid plans may include trial days before the first PayPal charge. Cancel before the trial ends to avoid being charged. Trials are limited to one per identity (including email, PayPal payer details, and related fingerprints) — including after account deletion — to prevent abuse.

Paid upgrades use PayPal checkout and subscriptions. Manage payment methods in PayPal when payments are enabled. You can cancel at period end from Billing, or unlink PayPal (you move to Free). To ask for a refund, open a request in Support Desk after reviewing the refund conditions and rules — refunds are not guaranteed and depend on those terms (and any legal requirements).

Your subscription may become payment-failed or past-due and paid features can be restricted until PayPal payment is restored. Teams you manage can freeze while the Manager’s plan or payment is unresolved.

Whatever currency is shown on Pricing for each plan when you subscribe. Confirm there before checkout.

Available types (each may be locked to your plan): HTTPS, Keyword, Ping, Port, API, UDP, DNS, SSL, Domain expiry, and Heartbeat. HTTPS/Keyword/API need a URL; host-based types need a hostname; Heartbeat gives you a push URL to call from your service.

By default, HTTP status codes 200–399 count as up. Redirects are followed (up to a small limit). Paid plans can define custom “up” status codes, use methods beyond HEAD, send custom headers/body, and attach Basic, Digest, or Bearer auth.

It behaves like an HTTP check but also requires a configured string to appear in the response body. The check uses a method that returns a body so the keyword can be scanned.

Both open a TCP connection to a host. Port monitors require an explicit port. Host monitors check reachability via TCP connect (defaulting to port 443 if unset) — they are not ICMP ping.

Intervals run from 15 seconds up to 24 hours: every second until 1 minute, then every minute until 1 hour, then every hour until 24 hours. Your plan sets the fastest allowed interval (Free is typically 5 minutes). Paid plans can lower that minimum — see Pricing.

Each monitor can be probed from one or more checker regions so you catch outages that only appear in certain parts of the world. Free typically allows 1 region per monitor; paid plans can allow more (sometimes unlimited). Exact caps are on Pricing. Available regions also depend on which checker nodes are online.

Timeout depends on your plan’s Custom timeout setting. If the plan sets a fixed value (e.g. Free at 10 seconds / 10000 ms), you can’t change it. If Custom timeout is enabled with no fixed value, you can set 1–60 seconds per monitor.

The check succeeded but was slower than your degraded threshold, or only some regions are down (a partial outage). Full down means the check failed or timed out.

Yes. Groups help filter and organize your monitor list. How many groups you get depends on your plan — Free has a small cap; paid plans allow more. See Pricing for current limits.

Each monitor can send email, in-app, and Telegram notifications (email and in-app on by default; Telegram after you connect the bot). You are notified when a region opens a downtime incident and again when it recovers. Team monitors notify the relevant team members — Telegram only if that person connected the bot.

Open Settings → Telegram → Connect Telegram. That opens our bot @mrvampcruz_uptime_bot (MrVampCruz Uptime). Tap Start to link your chat. Then enable “Telegram alerts” on each monitor you want. You can Send test, Disconnect in Settings, or use /unlink in the bot. Telegram is optional and run by Telegram — delivery depends on their service.

On the first failed check for a monitor and region. Recovery closes the incident with a duration. Cause and error details are stored. Older resolved incidents may be pruned when you exceed your plan’s incident cap.

Retention depends on your plan: incident count, check history days, and status-report days. Older resolved incidents and raw history may be pruned when you exceed those caps. Exact numbers are on your plan and the Pricing comparison — they can differ by plan and change over time.

No. The current & past incidents section is for paid plans. Public pages can still show uptime bars for recent days when the page is enabled.

No. Paid SSL & domain monitoring detects certificate errors and can remind you before SSL certificates or domains expire (configurable days ahead).

A paid option to define which HTTP statuses count as up (for example 200–299,301,304). Anything outside that list opens an incident. Without it, the default 2xx–3xx (or a single expected code) applies.

Supported methods include HEAD, GET, POST, PUT, PATCH, DELETE, OPTIONS, and QUERY. Free monitors are limited to HEAD (keyword checks use a body-capable method when needed). Paid plans unlock the full set.

Yes on paid plans with Custom request — headers plus a form or JSON body. Those options are stripped or unavailable on Free.

Yes — Basic, Digest, or Bearer credentials can be stored on the monitor and sent with each check.

Yes. Each monitor can use auto, IPv4, or IPv6 resolution.

/status is the platform/operator status page. Your own pages (and team pages) live at /status/{slug} once enabled and linked to monitors.

It depends on your plan. Free includes a small number of pages and public services; paid plans allow more (sometimes unlimited). Limits follow your current plan — check Pricing for the live comparison.

Paid plans with Custom status page URL can pick a readable slug (lowercase letters, numbers, hyphens; reserved names blocked). Free pages use a generated ID (s-…); Free may regenerate that link a few times per month.

Yes. Monitors can hide the target and optionally show public “extra info” text instead of the raw URL or hostname.

Personal pages start disabled until you turn them on in Settings (or Team settings for team pages). The platform root /status for the operator stays available separately.

Yes. Managers own team status pages and can assign team monitors to them. Members cannot change page assignments. Team page limits count against the Manager’s plan.

No. Team features are off on Free. Paid plans that include Teams unlock teams, members, team leads, shared monitors, and team joins — with limits that depend on the plan. See Pricing for which plans include teams and what the caps are.

Manager (owner and billing authority), Team Lead (TL — can manage members; only the Manager invites TLs), and Member. Permissions for adding/editing/deleting monitors and viewing or purging audits are granted per member.

Managers (and TLs for member invites) send an email invite link that expires after about 24 hours. Existing users sign in and accept; new users register, verify email, then join via /accept-invite.

The Manager’s. Shared monitors, team seats, and team status pages count against the Manager’s plan. Ownership transfer moves billing and limits to the new Manager.

If the Manager exceeds plan limits or loses team features (downgrade or payment issue), the team freezes: management locks, monitors stop ticking for that team, and non-managers are suspended from managing. There is a grace period (about 30 days); if still frozen after that, the team can be purged. Fixing the Manager’s plan or payment can thaw the team.

Yes — Manager only, and not while frozen. The target must have enough plan capacity. Transfer is confirmed with password and a short-lived email OTP. After the first transfer, the team slug may be renamed once, then locked.

Sign up with name, email, username, and password. You’ll receive a verification email (valid about 24 hours). Unverified emails cannot sign in until verified.

Passwords must be 8–256 characters and include an uppercase letter, a lowercase letter, and a number.

Yes from Settings. Email change and account deletion use password plus email verification codes. Deletion cancels an active PayPal subscription when integrated. Some archives or identity fingerprints may remain for anti-abuse, billing, or legal compliance.

Account sign-in is email/username and password. PayPal is used for billing and checkout, not as a general login provider for the app.

An essential httpOnly session cookie keeps you signed in. Theme and notification preferences may use browser storage. If your browser blocks storage (private mode), the site still works — preferences just may not persist.

Account profile, hashed passwords, monitor configuration and check telemetry, incidents, notification metadata, PayPal billing attributes when you subscribe, security logs/IPs, and — if you connect Telegram — your Telegram chat ID and username for delivering alerts. Trial-abuse fingerprints may be retained. Details are in the Privacy Policy.

No. Data is shared with processors you need for the service (such as PayPal, hosting, email, and Telegram when you connect the bot) and with advisers or authorities when required — not sold for third-party marketing.

The service is operated from Mauritius. Infrastructure and processors may be in other countries. See /privacy for the full policy.

Retention follows your plan (incident count, history days, status reports, audits). Free has no personal audit log. Older raw checks may be rolled into daily aggregates.

Email altaafhamod@mrvampcruz.com (Altaaf Hamod / MrVampCruz). Full documents: /privacy and /terms. The service is not directed at children under 16 (or the local minimum age).