Uptrends pricing has three tiers. Core starts from $42 a month and checks uptime every 2 minutes, Pro starts from $60 and checks every minute, and Enterprise is custom priced and is the only tier that checks every 30 seconds. Core includes 10 users and 240 SMS credits, Pro 25 users and 600. The page prints two figures per plan without saying which is yearly, and it never states how many monitors a plan includes, because every monitor spends credits. Figures are from the Uptrends pricing page, read in November 2026.
That last point is what makes Uptrends hard to budget. You cannot read a monitor count off the page, so the real cost depends on how many credits your checks burn. This guide lays out what is printed, what is not, how the credit costs stack up for common setups, and when a flat plan is the cheaper way to get the same uptime alerts.
Uptrends pricing by plan
| Limit | Core | Pro | Enterprise |
|---|---|---|---|
| Price a month | From $42 and from $46 (both printed) | From $60 and from $66 (both printed) | Custom |
| Fastest uptime check | 2 minutes | 1 minute | 30 seconds |
| Users | 10 | 25 | Unlimited |
| SMS credits | 240 | 600 | 1,200 |
| Public status pages | 10 | Unlimited | Unlimited |
| Data retention | 180 days | 365 days | 730 days |
| API and transaction checks | Not available | Yes | Yes |
| Support | Ticket | Ticket and live chat | Priority |
Source: Uptrends pricing. The header says annual billing carries a 10% discount, and each plan shows two "from" prices. They are not exactly 10% apart, so which is the yearly figure is not clear from the page. Ask for a written quote before you plan around either one. A 30-day trial with full Enterprise access and no credit card is offered, which is the safest way to count real credit use.
How the Uptrends credit model works
Every monitor type costs credits. An uptime monitor is 6 credits, an API step is 15, and a browser monitor or a transaction step is 50. Each plan includes a base number of credits, and the page does not print how many, so the plan price alone does not tell you what you can monitor. Extra credits are sold as bundles. The credit table on the page shows two unlabeled figures per cell, so we do not quote bundle prices here.
What you can say with certainty is the ratio. One browser check spends the credits of more than eight uptime checks, so a team that adds a login journey to a plain uptime setup changes the cost a lot more than a team that adds ten more URLs. That is fair if you need browser tests. It is a surprise if you thought you were buying URL checks.
What the interval ladder means for plain uptime checks
The interval is a plan limit, not a setting. A Core account cannot check faster than every 2 minutes. At that rate a site that fails right after a check can go unnoticed for almost 2 minutes, and a confirmation retry adds more. Pro halves that, and 30-second checks sit on Enterprise only. For a store or a SaaS login page, the gap between detecting a failure in 30 seconds and in 2 minutes is the difference between a short blip and a ticket from a customer.
| Tool and plan | Fastest check | Price | Monitors |
|---|---|---|---|
| Uptrends Core | 2 minutes | From $42 a month | Set by credits |
| Uptrends Pro | 1 minute | From $60 a month | Set by credits |
| Uptrends Enterprise | 30 seconds | Custom | Set by credits |
| AlertPing Starter | 60 seconds | $24 a month billed yearly ($49 monthly) | 20 |
| AlertPing Team | 30 seconds | $29 a month billed yearly ($59 monthly) | 100 |
AlertPing prices are on its pricing page. A year of Team is $348, which is less than twelve months of Uptrends Pro at the lower printed figure ($720), and it checks twice as often with second-region confirmation before anyone is paged.
Who should pay for Uptrends, and who should not
A digital experience team that records login and checkout journeys, wants real browser waterfalls and checks from hundreds of cities has a real use for Uptrends, and the credit system is the cost of that depth. Our Uptrends alternative page says plainly that we do not sell those features.
A team that wants to know when a URL, an API or a port stops answering is paying for a suite it does not use. It also lands on a slower clock than it expected. For that team, a flat plan that confirms the outage from a second region and pages through escalation chains costs less and checks faster. If you also compare against other suites, the Checkly alternative page prices an API-first tool the same way. Slow detection is also a search problem: a site that times out repeatedly can lose crawl frequency, and teams that watch rankings with an outside tool such as seomake for tracking search visibility can match a dip to an outage window.
Questions buyers ask
How much does Uptrends cost per month?
Uptrends Core starts from $42 to $46 a month and Pro from $60 to $66, depending on the billing view, since the page prints both numbers without a label. Enterprise is custom. Core covers 10 users and 240 SMS credits, and Pro covers 25 users and 600. Your final bill depends on the credits your monitors use.
Does Uptrends have a free trial?
Yes. Uptrends offers a 30-day trial with full Enterprise access and no credit card. During the trial you can switch to any plan. It is the best way to measure how many credits your uptime, API and browser checks actually spend before you commit to a year.
Can Uptrends check every 30 seconds?
Only on Enterprise. Core checks uptime every 2 minutes and Pro every minute. Enterprise is custom priced, so 30-second detection means a sales conversation. AlertPing checks every 30 seconds on Team, $348 a year, and every 60 seconds on Starter.
What is a cheaper Uptrends alternative for uptime monitoring?
A flat plan priced per plan, not per credit. AlertPing Team covers 100 monitors, 15 members, escalation chains, 300 SMS alerts a month and status pages for $348 a year. It does not do browser or transaction monitoring, so keep Uptrends if you rely on those.