Frequently asked questions
The questions people arrive here with, answered straight. Every claim below is about what the product does today, not the roadmap.
How do I set up monitoring for my server or website?
Sign up at app.yoping.me/signup and the first-run wizard walks you through it: it runs a live first check from both your check regions while you sign up, so you see real results before you finish. From the dashboard you can add up to 10 monitors on the free plan, using any of the five check types: HTTP, keyword, SSL, ping, and TCP. There is no setup guide to read first, because the wizard is the guide. For the day something does go down, the guides section has plain troubleshooting answers for the errors you are most likely to see.
Can I use YoPingMe to track my website uptime every day?
Yes, that is the whole product. Every monitor is checked every 5 minutes, around the clock, from two regions you choose out of five: Frankfurt, Virginia, Singapore, Oregon, and London. An alert goes out by email, webhook, or Slack only when both regions agree your site is down, so a routing blip in one region does not page you. Choosing the regions means a site blocked in one country by design does not raise false alarms. The dashboard keeps 30 days of raw check history, so you can see when each outage started and how long it lasted.
Do I need a credit card to sign up?
No. Signup never asks for a card, and the free plan is free for good, not a trial that expires into a charge: 10 monitors, checks every 5 minutes, email, webhook, and Slack alerts, and 30 days of history. A card only enters the picture if you later choose to upgrade to Pro or Team, and even then each starts with a 14-day free trial.
Is YoPingMe reputable? How do I know I can trust it?
YoPingMe is new, and this site does not pretend otherwise: you will find no customer counts, testimonials, star ratings, or logo walls here, because we refuse to invent them. What you can verify yourself: the free plan costs nothing and needs no card, the signup wizard shows you a live check from both your regions before you commit to anything, the comparison pages say plainly where competitors beat us, and the privacy policy and terms are written in plain language. Then judge the service the honest way: point it at a site you care about and watch a week of real checks.
Is YoPingMe a free UptimeRobot alternative for my business?
Yes, though the terms argument you may have read elsewhere is out of date: in late 2024 UptimeRobot restricted its free plan to personal, non-commercial use, and then lifted that restriction - as of August 2026 their terms permit commercial use on every plan. So for business use the question is fit, not permission. UptimeRobot's free plan has more monitors (50 against 10) and a status page; YoPingMe checks every monitor from two regions you pick and pages you only when both agree, which is the difference you notice at 3am. The full comparison, including the dated terms timeline, is on the YoPingMe vs UptimeRobot page.
How do payments and refunds work on the paid plans?
Paid plans are billed through Paddle, our merchant of record: Paddle runs the checkout, issues the receipt, and is the name on your card statement. Pro and Team start with a 14-day free trial, and after any charge you have a 14-day window to email support@yoping.me for a refund of the most recent payment. The full policy is on the refund policy page. You upgrade from your account page once you are signed in. One honest caveat: changing plan yourself is not available yet, so moving between Pro and Team means emailing support@yoping.me.
Why does YoPingMe say my site is down when it loads fine for me?
Usually one of two things. It can be real: a check runs from more than one region, so a site that is fine from your desk can be unreachable from one of your check regions, which is the whole reason to watch it from more than one place. The other common cause is your own edge. Firewalls, CDNs, and bot protection challenge traffic that does not look like a browser, and our probe is not one: it runs no JavaScript and stores no cookies, so a challenge it cannot solve is recorded as a failed check. The check details show what came back, and a 403, a 429, or a challenge page points at the second cause -how to allowlist the probe has the fix, with Cloudflare worked through.