Alternatives to UptimeRobot logo

Alternatives to UptimeRobot

StatusCake, Pingdom, Monitis, Site24x7, and New Relic are the most popular alternatives and competitors to UptimeRobot.
322
84

What is UptimeRobot and what are its top alternatives?

It is all about helping you to keep your websites up. It monitors your websites every 5 minutes and alerts you if your sites are down.
UptimeRobot is a tool in the Website Monitoring category of a tech stack.

Top Alternatives to UptimeRobot

  • StatusCake
    StatusCake

    Monitoring a website is one thing – finding the best way to alert you to downtime another. At StatusCake we give you as many options as possible to decide when & how often you’re contacted. Whether it’s by email, SMS, push notifications for iOS & Android or integration with third party apps including Zapier and PagerDuty – you decide how you want to be alerted and when! ...

  • Pingdom
    Pingdom

    Pingdom is an uptime monitoring service. When problems happen with a site that Pingdom monitors, it immediately alerts the owner so the problem can be taken care of. ...

  • Monitis
    Monitis

    Monitor and manage your websites, servers, networks, cloud systems & applications for performance and reliability. Get your Monitis 15 day free trial now! ...

  • Site24x7
    Site24x7

    Site24x7 is an all-in-one monitoring solution that allows you to monitor every part of your IT infrastructure from Websites to Applications, to Servers (both on-premise and on the cloud) as well as your Network infrastructure. ...

  • New Relic
    New Relic

    The world’s best software and DevOps teams rely on New Relic to move faster, make better decisions and create best-in-class digital experiences. If you run software, you need to run New Relic. More than 50% of the Fortune 100 do too. ...

  • Kibana
    Kibana

    Kibana is an open source (Apache Licensed), browser based analytics and search dashboard for Elasticsearch. Kibana is a snap to setup and start using. Kibana strives to be easy to get started with, while also being flexible and powerful, just like Elasticsearch. ...

  • Grafana
    Grafana

    Grafana is a general purpose dashboard and graph composer. It's focused on providing rich ways to visualize time series metrics, mainly though graphs but supports other ways to visualize data through a pluggable panel architecture. It currently has rich support for for Graphite, InfluxDB and OpenTSDB. But supports other data sources via plugins. ...

  • Sentry
    Sentry

    Sentry’s Application Monitoring platform helps developers see performance issues, fix errors faster, and optimize their code health. ...

UptimeRobot alternatives & related posts

StatusCake logo

StatusCake

121
133
56
Feature Rich Uptime Monitoring, Domain Monitoring, SSL Monitoring and a whole lot more
121
133
+ 1
56
PROS OF STATUSCAKE
  • 14
    Easy to use and reliable
  • 12
    Free tier
  • 6
    Public Reporting
  • 4
    Domain monitoring
  • 3
    Cheaper
  • 3
    SSL Certificate Monitoring
  • 3
    No false positives
  • 3
    Group Notification
  • 2
    Great Customer Support
  • 1
    WhoIs Domain Monitoring
  • 1
    Real Browser Testing
  • 1
    Malware and Virus Scanning
  • 1
    Multiple User Accounts
  • 1
    Mobile App
  • 1
    Full Featured API
CONS OF STATUSCAKE
    Be the first to leave a con

    related StatusCake posts

    Shared insights
    on
    Site24x7Site24x7StatusCakeStatusCake

    What are the comparisons and differences between StatusCake and Site24x7 Services?

    See more
    Pingdom logo

    Pingdom

    2.4K
    1.4K
    579
    Uptime and performance monitoring made easy
    2.4K
    1.4K
    + 1
    579
    PROS OF PINGDOM
    • 224
      Simple and reliable
    • 103
      Monitoring your websites
    • 75
      Easy to use dashboard
    • 65
      Email, text & twitter alerts
    • 43
      Free tier
    • 23
      Performance data
    • 14
      Detailed Reports
    • 11
      Email Reports
    • 9
      Mobile App
    • 9
      Root Cause Analysis
    • 1
      30-day risk free trial
    • 1
      Easy setup
    • 1
      IOS app
    CONS OF PINGDOM
    • 4
      Expensive
    • 3
      UI is incredibly complicated
    • 2
      Hard to set up alerts properly

    related Pingdom posts

    Jerome Dalbert
    Principal Backend Software Engineer at StackShare · | 5 upvotes · 290.4K views

    We currently monitor performance with the following tools:

    1. Heroku Metrics: our main app is Hosted on Heroku, so it is the best place to get quick server metrics like memory usage, load averages, or response times.
    2. Good old New Relic for detailed general metrics, including transaction times.
    3. Skylight for more specific Rails Controller#action transaction times. Navigating those timings is much better than with New Relic, as you get a clear full breakdown of everything that happens for a given request.

    Skylight offers better Rails performance insights, so why use New Relic? Because it does frontend monitoring, while Skylight doesn't. Now that we have a separate frontend app though, our frontend engineers are looking into more specialized frontend monitoring solutions.

    Finally, if one of our apps go down, Pingdom alerts us on Slack and texts some of us.

    See more
    Nikola Yovchev
    Head of Engineering at Relay42 · | 2 upvotes · 130.8K views

    #Datadog #Relay42 #Monitoring

    With Datadog unveiling their Synthetics product (https://www.datadoghq.com/blog/introducing-synthetic-monitoring/), we at Relay42 are considering moving out of Pingdom.

    The rationale is simple:

    • 90% of our monitoring is on Datadog, apart from the external requests. It'd be nice to identify regional issues in one place, so this is great in our monitoring consolidation efforts.

    • The lack of a non-community Terraform provider for Pingdom

    We have yet to get in the beta and test it out but we feel very excited about this announcement.

    See more
    Monitis logo

    Monitis

    13
    5
    0
    A Website performance monitoring platform
    13
    5
    + 1
    0
    PROS OF MONITIS
      Be the first to leave a pro
      CONS OF MONITIS
        Be the first to leave a con

        related Monitis posts

        Site24x7 logo

        Site24x7

        47
        27
        0
        IT Infrastructure monitoring solution
        47
        27
        + 1
        0
        PROS OF SITE24X7
          Be the first to leave a pro
          CONS OF SITE24X7
            Be the first to leave a con

            related Site24x7 posts

            Hi Folks,

            I am trying to evaluate Site24x7 against AppDynamics, Dynatrace, and New Relic. Has anyone used Site24X7? If so, what are your opinions on the tool? I know that the license costs are very low compared to other tools in the market. Other than that, are there any major issues anyone has encountered using the tool itself?

            See more
            Shared insights
            on
            Site24x7Site24x7StatusCakeStatusCake

            What are the comparisons and differences between StatusCake and Site24x7 Services?

            See more
            New Relic logo

            New Relic

            20.8K
            8.6K
            1.9K
            New Relic is the industry’s largest and most comprehensive cloud-based observability platform.
            20.8K
            8.6K
            + 1
            1.9K
            PROS OF NEW RELIC
            • 415
              Easy setup
            • 344
              Really powerful
            • 245
              Awesome visualization
            • 194
              Ease of use
            • 151
              Great ui
            • 106
              Free tier
            • 80
              Great tool for insights
            • 66
              Heroku Integration
            • 55
              Market leader
            • 49
              Peace of mind
            • 21
              Push notifications
            • 20
              Email notifications
            • 17
              Heroku Add-on
            • 16
              Error Detection and Alerting
            • 13
              Multiple language support
            • 11
              SQL Analysis
            • 11
              Server Resources Monitoring
            • 9
              Transaction Tracing
            • 8
              Apdex Scores
            • 8
              Azure Add-on
            • 7
              Analysis of CPU, Disk, Memory, and Network
            • 7
              Detailed reports
            • 6
              Performance of External Services
            • 6
              Error Analysis
            • 6
              Application Availability Monitoring and Alerting
            • 6
              Application Response Times
            • 5
              Most Time Consuming Transactions
            • 5
              JVM Performance Analyzer (Java)
            • 4
              Browser Transaction Tracing
            • 4
              Top Database Operations
            • 4
              Easy to use
            • 3
              Application Map
            • 3
              Weekly Performance Email
            • 3
              Pagoda Box integration
            • 3
              Custom Dashboards
            • 2
              Easy to setup
            • 2
              Background Jobs Transaction Analysis
            • 2
              App Speed Index
            • 1
              Super Expensive
            • 1
              Team Collaboration Tools
            • 1
              Metric Data Retention
            • 1
              Metric Data Resolution
            • 1
              Worst Transactions by User Dissatisfaction
            • 1
              Real User Monitoring Overview
            • 1
              Real User Monitoring Analysis and Breakdown
            • 1
              Time Comparisons
            • 1
              Access to Performance Data API
            • 1
              Incident Detection and Alerting
            • 1
              Best of the best, what more can you ask for
            • 1
              Best monitoring on the market
            • 1
              Rails integration
            • 1
              Free
            • 0
              Proce
            • 0
              Price
            • 0
              Exceptions
            • 0
              Cost
            CONS OF NEW RELIC
            • 20
              Pricing model doesn't suit microservices
            • 10
              UI isn't great
            • 7
              Expensive
            • 7
              Visualizations aren't very helpful
            • 5
              Hard to understand why things in your app are breaking

            related New Relic posts

            Farzeem Diamond Jiwani
            Software Engineer at IVP · | 8 upvotes · 1.5M views

            Hey there! We are looking at Datadog, Dynatrace, AppDynamics, and New Relic as options for our web application monitoring.

            Current Environment: .NET Core Web app hosted on Microsoft IIS

            Future Environment: Web app will be hosted on Microsoft Azure

            Tech Stacks: IIS, RabbitMQ, Redis, Microsoft SQL Server

            Requirement: Infra Monitoring, APM, Real - User Monitoring (User activity monitoring i.e., time spent on a page, most active page, etc.), Service Tracing, Root Cause Analysis, and Centralized Log Management.

            Please advise on the above. Thanks!

            See more
            Shared insights
            on
            New RelicNew RelicKibanaKibana

            I need to choose a monitoring tool for my project, but currently, my application doesn't have much load or many users. My application is not generating GBs of data. We don't want to send the user information to New Relic because it's a 3rd party tool. And we can deploy Kibana locally on our server. What should I use, Kibana or New Relic?

            See more
            Kibana logo

            Kibana

            20.4K
            16.2K
            262
            Visualize your Elasticsearch data and navigate the Elastic Stack
            20.4K
            16.2K
            + 1
            262
            PROS OF KIBANA
            • 88
              Easy to setup
            • 65
              Free
            • 45
              Can search text
            • 21
              Has pie chart
            • 13
              X-axis is not restricted to timestamp
            • 9
              Easy queries and is a good way to view logs
            • 6
              Supports Plugins
            • 4
              Dev Tools
            • 3
              More "user-friendly"
            • 3
              Can build dashboards
            • 2
              Out-of-Box Dashboards/Analytics for Metrics/Heartbeat
            • 2
              Easy to drill-down
            • 1
              Up and running
            CONS OF KIBANA
            • 7
              Unintuituve
            • 4
              Works on top of elastic only
            • 4
              Elasticsearch is huge
            • 3
              Hardweight UI

            related Kibana posts

            Tymoteusz Paul
            Devops guy at X20X Development LTD · | 23 upvotes · 9.7M views

            Often enough I have to explain my way of going about setting up a CI/CD pipeline with multiple deployment platforms. Since I am a bit tired of yapping the same every single time, I've decided to write it up and share with the world this way, and send people to read it instead ;). I will explain it on "live-example" of how the Rome got built, basing that current methodology exists only of readme.md and wishes of good luck (as it usually is ;)).

            It always starts with an app, whatever it may be and reading the readmes available while Vagrant and VirtualBox is installing and updating. Following that is the first hurdle to go over - convert all the instruction/scripts into Ansible playbook(s), and only stopping when doing a clear vagrant up or vagrant reload we will have a fully working environment. As our Vagrant environment is now functional, it's time to break it! This is the moment to look for how things can be done better (too rigid/too lose versioning? Sloppy environment setup?) and replace them with the right way to do stuff, one that won't bite us in the backside. This is the point, and the best opportunity, to upcycle the existing way of doing dev environment to produce a proper, production-grade product.

            I should probably digress here for a moment and explain why. I firmly believe that the way you deploy production is the same way you should deploy develop, shy of few debugging-friendly setting. This way you avoid the discrepancy between how production work vs how development works, which almost always causes major pains in the back of the neck, and with use of proper tools should mean no more work for the developers. That's why we start with Vagrant as developer boxes should be as easy as vagrant up, but the meat of our product lies in Ansible which will do meat of the work and can be applied to almost anything: AWS, bare metal, docker, LXC, in open net, behind vpn - you name it.

            We must also give proper consideration to monitoring and logging hoovering at this point. My generic answer here is to grab Elasticsearch, Kibana, and Logstash. While for different use cases there may be better solutions, this one is well battle-tested, performs reasonably and is very easy to scale both vertically (within some limits) and horizontally. Logstash rules are easy to write and are well supported in maintenance through Ansible, which as I've mentioned earlier, are at the very core of things, and creating triggers/reports and alerts based on Elastic and Kibana is generally a breeze, including some quite complex aggregations.

            If we are happy with the state of the Ansible it's time to move on and put all those roles and playbooks to work. Namely, we need something to manage our CI/CD pipelines. For me, the choice is obvious: TeamCity. It's modern, robust and unlike most of the light-weight alternatives, it's transparent. What I mean by that is that it doesn't tell you how to do things, doesn't limit your ways to deploy, or test, or package for that matter. Instead, it provides a developer-friendly and rich playground for your pipelines. You can do most the same with Jenkins, but it has a quite dated look and feel to it, while also missing some key functionality that must be brought in via plugins (like quality REST API which comes built-in with TeamCity). It also comes with all the common-handy plugins like Slack or Apache Maven integration.

            The exact flow between CI and CD varies too greatly from one application to another to describe, so I will outline a few rules that guide me in it: 1. Make build steps as small as possible. This way when something breaks, we know exactly where, without needing to dig and root around. 2. All security credentials besides development environment must be sources from individual Vault instances. Keys to those containers should exist only on the CI/CD box and accessible by a few people (the less the better). This is pretty self-explanatory, as anything besides dev may contain sensitive data and, at times, be public-facing. Because of that appropriate security must be present. TeamCity shines in this department with excellent secrets-management. 3. Every part of the build chain shall consume and produce artifacts. If it creates nothing, it likely shouldn't be its own build. This way if any issue shows up with any environment or version, all developer has to do it is grab appropriate artifacts to reproduce the issue locally. 4. Deployment builds should be directly tied to specific Git branches/tags. This enables much easier tracking of what caused an issue, including automated identifying and tagging the author (nothing like automated regression testing!).

            Speaking of deployments, I generally try to keep it simple but also with a close eye on the wallet. Because of that, I am more than happy with AWS or another cloud provider, but also constantly peeking at the loads and do we get the value of what we are paying for. Often enough the pattern of use is not constantly erratic, but rather has a firm baseline which could be migrated away from the cloud and into bare metal boxes. That is another part where this approach strongly triumphs over the common Docker and CircleCI setup, where you are very much tied in to use cloud providers and getting out is expensive. Here to embrace bare-metal hosting all you need is a help of some container-based self-hosting software, my personal preference is with Proxmox and LXC. Following that all you must write are ansible scripts to manage hardware of Proxmox, similar way as you do for Amazon EC2 (ansible supports both greatly) and you are good to go. One does not exclude another, quite the opposite, as they can live in great synergy and cut your costs dramatically (the heavier your base load, the bigger the savings) while providing production-grade resiliency.

            See more
            Tassanai Singprom

            This is my stack in Application & Data

            JavaScript PHP HTML5 jQuery Redis Amazon EC2 Ubuntu Sass Vue.js Firebase Laravel Lumen Amazon RDS GraphQL MariaDB

            My Utilities Tools

            Google Analytics Postman Elasticsearch

            My Devops Tools

            Git GitHub GitLab npm Visual Studio Code Kibana Sentry BrowserStack

            My Business Tools

            Slack

            See more
            Grafana logo

            Grafana

            17.9K
            14.3K
            415
            Open source Graphite & InfluxDB Dashboard and Graph Editor
            17.9K
            14.3K
            + 1
            415
            PROS OF GRAFANA
            • 89
              Beautiful
            • 68
              Graphs are interactive
            • 57
              Free
            • 56
              Easy
            • 34
              Nicer than the Graphite web interface
            • 26
              Many integrations
            • 18
              Can build dashboards
            • 10
              Easy to specify time window
            • 10
              Can collaborate on dashboards
            • 9
              Dashboards contain number tiles
            • 5
              Open Source
            • 5
              Integration with InfluxDB
            • 5
              Click and drag to zoom in
            • 4
              Authentification and users management
            • 4
              Threshold limits in graphs
            • 3
              Alerts
            • 3
              It is open to cloud watch and many database
            • 3
              Simple and native support to Prometheus
            • 2
              Great community support
            • 2
              You can use this for development to check memcache
            • 2
              You can visualize real time data to put alerts
            • 0
              Grapsh as code
            • 0
              Plugin visualizationa
            CONS OF GRAFANA
            • 1
              No interactive query builder

            related Grafana posts

            Matt Menzenski
            Senior Software Engineering Manager at PayIt · | 16 upvotes · 1M views

            Grafana and Prometheus together, running on Kubernetes , is a powerful combination. These tools are cloud-native and offer a large community and easy integrations. At PayIt we're using exporting Java application metrics using a Dropwizard metrics exporter, and our Node.js services now use the prom-client npm library to serve metrics.

            See more
            Conor Myhrvold
            Tech Brand Mgr, Office of CTO at Uber · | 15 upvotes · 5M views

            Why we spent several years building an open source, large-scale metrics alerting system, M3, built for Prometheus:

            By late 2014, all services, infrastructure, and servers at Uber emitted metrics to a Graphite stack that stored them using the Whisper file format in a sharded Carbon cluster. We used Grafana for dashboarding and Nagios for alerting, issuing Graphite threshold checks via source-controlled scripts. While this worked for a while, expanding the Carbon cluster required a manual resharding process and, due to lack of replication, any single node’s disk failure caused permanent loss of its associated metrics. In short, this solution was not able to meet our needs as the company continued to grow.

            To ensure the scalability of Uber’s metrics backend, we decided to build out a system that provided fault tolerant metrics ingestion, storage, and querying as a managed platform...

            https://eng.uber.com/m3/

            (GitHub : https://github.com/m3db/m3)

            See more
            Sentry logo

            Sentry

            14.4K
            9.2K
            863
            See performance issues, fix errors faster, and optimize code health.
            14.4K
            9.2K
            + 1
            863
            PROS OF SENTRY
            • 237
              Consolidates similar errors and makes resolution easy
            • 121
              Email Notifications
            • 108
              Open source
            • 84
              Slack integration
            • 71
              Github integration
            • 49
              Easy
            • 44
              User-friendly interface
            • 28
              The most important tool we use in production
            • 18
              Hipchat integration
            • 17
              Heroku Integration
            • 15
              Good documentation
            • 14
              Free tier
            • 11
              Self-hosted
            • 9
              Easy setup
            • 7
              Realiable
            • 6
              Provides context, and great stack trace
            • 4
              Feedback form on error pages
            • 4
              Love it baby
            • 3
              Gitlab integration
            • 3
              Filter by custom tags
            • 3
              Super user friendly
            • 3
              Captures local variables at each frame in backtraces
            • 3
              Easy Integration
            • 1
              Performance measurements
            CONS OF SENTRY
            • 12
              Confusing UI
            • 4
              Bundle size

            related Sentry posts

            Johnny Bell

            For my portfolio websites and my personal OpenSource projects I had started exclusively using React and JavaScript so I needed a way to track any errors that we're happening for my users that I didn't uncover during my personal UAT.

            I had narrowed it down to two tools LogRocket and Sentry (I also tried Bugsnag but it did not make the final two). Before I get into this I want to say that both of these tools are amazing and whichever you choose will suit your needs well.

            I firstly decided to go with LogRocket the fact that they had a recorded screen capture of what the user was doing when the bug happened was amazing... I could go back and rewatch what the user did to replicate that error, this was fantastic. It was also very easy to setup and get going. They had options for React and Redux.js so you can track all your Redux.js actions. I had a fairly large Redux.js store, this was ended up being a issue, it killed the processing power on my machine, Chrome ended up using 2-4gb of ram, so I quickly disabled the Redux.js option.

            After using LogRocket for a month or so I decided to switch to Sentry. I noticed that Sentry was openSorce and everyone was talking about Sentry so I thought I may as well give it a test drive. Setting it up was so easy, I had everything up and running within seconds. It also gives you the option to wrap an errorBoundry in React so get more specific errors. The simplicity of Sentry was a breath of fresh air, it allowed me find the bug that was shown to the user and fix that very simply. The UI for Sentry is beautiful and just really clean to look at, and their emails are also just perfect.

            I have decided to stick with Sentry for the long run, I tested pretty much all the JS error loggers and I find Sentry the best.

            See more
            Tassanai Singprom

            This is my stack in Application & Data

            JavaScript PHP HTML5 jQuery Redis Amazon EC2 Ubuntu Sass Vue.js Firebase Laravel Lumen Amazon RDS GraphQL MariaDB

            My Utilities Tools

            Google Analytics Postman Elasticsearch

            My Devops Tools

            Git GitHub GitLab npm Visual Studio Code Kibana Sentry BrowserStack

            My Business Tools

            Slack

            See more