New! Pingdom status plugin for WordPress

Do you run a web service or hosting company? Do you like transparency? Then this might be of interest to you.

Service status blogs are becoming increasingly common these days and are usually very appreciated by users. Look no further than Twitter’s famous status blog, or the Google Apps status page. Status blogs (or “status pages”, depending on approach) may look and work differently, but they all serve the same purpose, informing users about service issues.

Now it’s easier than ever before if you want one, or want to make your existing status blog even better.

Making it easy to create a powerful status blog

To make it really easy for companies to offer a comprehensive status blog, we are now releasing a free Pingdom status plugin for WordPress. Using this plugin you can combine Pingdom’s monitoring with the world’s most widespread blogging platform.

What the Pingdom status plugin adds to your blog:

  • A public status page. It creates a page on your WordPress blog which shows the current status (up or down) of the sites and servers you monitor with Pingdom.
  • Monitoring history. Users can drill down and view detailed uptime and response time history for each monitored item.
  • Make all or just some results public. You can select to make all your monitoring results public, or just some of them. Often companies have additional monitoring set up that may not be directly relevant to their users.
  • Grouping. You can create groups of monitored items and name them, for example “web servers,” “database servers,” “websites,” etc. This makes it easy for you to categorize the results for your users.
  • Default or custom design. The plugin comes with an attractive default styling, but you can modify it as much as you like, for example by adding your own colors and branding, etc.

All you need is a Pingdom account and a WordPress blog. Once you have that, setting up the plugin won’t take more than five minutes.

To get started, just follow the plugin installation instructions. All settings are done inside the standard WordPress admin control panel, in the Plugins section.


Here is an example of what the main status page looks like:

Pingdom status page for WordPress

In the above case we have created a group named “Websites.” You can of course have multiple groups.

By clicking on any of the monitored items, users can drill in and examine its status history:

Uptime and response time history in the Pingdom status plugin for WordPress

Final notes

This plugin was designed for self-hosted WordPress blogs (i.e. using the software). It won’t work for blogs hosted on the service.

Also, a small but important thing to keep in mind: Host your status blog separately. If your main site or service goes down, you still want your status blog to be accessible.

And in case you missed the link to the plugin, here it is again:

We hope you will find it useful.

About Pingdom:

In case you arrived here not familiar with Pingdom, we offer a service that monitors websites and servers for our users, sending alerts if errors are detected, and providing a control panel where our users can examine their monitoring history and troubleshoot problems. We have tens of thousands of users, ranging all the way from large corporations to hobbyist webmasters. You can read more about our features at

Pingdom has paid monitoring packages starting at $9.95 per month, but also a free trial for monitoring one site.


  1. To bad it doesn’t work, I’m getting the following error when trying to activate the plugin:

    Plugin could not be activated because it triggered a fatal error.

    Parse error: syntax error, unexpected $end in /usr/local/www/ on line 1136

    I installed the plugin automatically with the plugin browser.

  2. The plugin doesn’t activate, with fatal errors about missing include files.

    Your lines
    `require_once(ABSPATH . ‘wp-content/plugins/PingdomStatus/…`
    assume the content dir is always in the same place, and the plugin directory is always PingdomStatus (which it isn’t when you use the auto-install).

    Try `plugin_basename( dirname( __FILE__ ) .’/file_to_include’`

  3. Ok, everyone. Thank you for the quick feedback. The problem with auto-install should now have been fixed (we’ve tested it, and it works fine). Apologies for the inconvenience.

    We’ve uploaded a version 1.1.1 to WordPress now that properly supports the auto-install feature in addition to manual install.

    If you run into any problems, remove the old install before you install the new one.

    1. @Dan Knights: It’s supposed to work right away, right after you’ve synched the first time. If you have a brand new Pingdom account, though, the graphs won’t have much to work with since you have almost no monitoring history (i.e. the graphs show one month, and if your account is hours old, there’s not much to show on that scale).

    1. @Dan Knights: Please send an email to support -at- and we’ll have a look at it and see if we can help. Don’t forget to include a URL to your status blog.

    1. @Kumar: Sounds strange. Please send an email to support -at- explaining your problem a little more in detail (including a URL if possible) and we’ll see what we can do to help.

  4. I receive an error when I click at “Public checks” in the WordPress Plugin Settings.

    Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 75 bytes) in /var/www/vhosts/domain/subdomains/subdomainname/httpdocs/wp-content/plugins/pingdom-status/php/doctrine/Doctrine/Record.php on line 714

    1. @Tobias: Very strange. Would you mind emailing support -at- with some more information? For example if you’re experiencing this on any of the other settings pages? Plus, what Pingdom account you’re using. Please do that, and we’ll see if we can find out what’s happening.

  5. My website has been hanging when it loads. So I ran the index file through strace and found it to hang when calling this file: /home/newlifel/public_html/wp-content/plugins/pingdom-status/php/data_layer/generated/BasePingdomPsResponseTime.php

    Why does it cause the site to hang for roughly 5 seconds? What is this script doing? I thought the plugin only displayed the data already on Pingdom servers to display the graphs and charts.

    Any assistance would be helpful. I can’t justify the site hanging for 5 seconds while the page loads.

    See for yourself:

    1. @Donnie: We’d need to look closer at that. Please send this and as much other information as you can about your blog’s setup to support -at- pingdom dot com and we’ll handle it from there. (This blog isn’t exactly ideal for support issues. 😉 )

Leave a Reply

Comments are moderated and not published in real time. All comments that are not related to the post will be removed.required