The news feed.

Posted by WAU on October 4, 2017
Hi All,

Apologies for the intermittent downtime over the past hour or so. One of the datacenters we work with experienced a full power failure taking our servers and upstream equipment with it.

We pride ourselves on having near perfect uptime so this is a real blow. We take care to only work with providers that can provide redundancy for every possible system and will be working with our vendors to see why the UPS systems didn't kick in as expected.

Thanks for bearing with us.
Posted by on April 8, 2017
We received some complaints from users that were receiving a false positive notification for their sites, this was a false positive and the issue has been rectified, our sincere apologies for any problems this may have caused.
Posted by on July 18, 2016
There has been a problem with one of our partners that has, regrettably, resulted in links on publisher sites being rewritten and redirected. We have disabled the affected code until this is fully resolved. All features work as intended and without issue, the only thing missing is the what's being copied stats, once the issue is resolved these will be back. has worked with Tynt since 2009 to bring you stats about the top phrases and images that were being copied off of your site, they provide a great service and we were able to work with them to provide a small subset of what they provide to users.

Recently, we got some publisher complaints that links on their sites were being redirected through the domain This immediately raised red flags as our widgets are specifically tailored to ensure the publishers site is never modified in any way. Once we determined that the affected code was coming from the Tynt copy and paste stats JavaScript code we immediately disabled the code in all widgets, and it remains that way as of this posting. We will re-enable the copy and paste stats as soon as we have resolved the issue with our partner.

If you see any redirects, empty your browser cache and reload the page, browser cached versions of the widget code may still load the affected code. Also, if you've copied the widget Javascript code to your own server, please point it back to the original location (ie.,,,, or so that you ensure you are not loading an old version of the widget code.

Please contact us if you are experiencing any problems.

Once again, apologies to all of our affected publishers, we are here to help and absolutely want to make sure our widgets provide the best service possible and that includes never manipulating your page content.
Posted by on April 19, 2016
TL:DR; hosted sites (does not affect .org/self hosted sites) widgets were broken, now they are fixed.

A few days ago it was brought to our attention that widgets on hosted sites were no longer functioning and displaying an incorrect concurrent user count.(if you run your own install of WP on your own server this wouldn't have affected you).

What happened was that, in the latest update to the platform, the Photon functionality was turned on by default. Photon retrieves images embedded in your blog once and then hosts them off of Wordpress' servers to speed up blog serving time by reducing the number of locations your browser has to look for image assets. While this is a great feature in most cases it causes a problem for services like where we rely on the blog users loading the widget image from our servers so that they can be counted in the stats. With Photon proxying our widget images no one was getting counted in the stats for sites hosted on as the end users never requested the widget images from us directly.

We've been working with Automattic (the fantastic company behind Wordpress) over the past few days to find a solution that allows widgets to continue functioning on hosted blogs, and I'm happy to report that there is a solution now in place that allows the widget to work properly once again!

You shouldn't need to make any changes to your widget code, but if you are seeing a lot of "Unknown" users in the readers list on your stat pages you might want make a very small change to your widget code to serve the widget off of https and not http.

Example, if your widget code looks like:

<a href="">
    <img src="" width="81" height="29" border="0" title="Click to see how many people are online" />

Change it to:

<a href="">
    <img src="" width="81" height="29" border="0" title="Click to see how many people are online" />

The only difference is the  http  in the img tag has been converted to  https .

As always, if you have any questions don't hesitate to contact us.
Posted by on June 26, 2014
We've had a number of different widget codes over the years and as such we like to make sure our long time users update their codes to ensure they are getting the best performance possible from the widgets on their site.

About 3 years ago we converted the Javascript code from the traditional synchronous (sync) style to the newer asynchronous (async) style. The async version has the advantage of never blocking loading of page elements on your site, which would have been possible with the sync version.

Although the async code has been available for many years we are still seeing lots of sites using the sync version, so we'd like to provide this message to assist users in determining what sort of code they are running.

If the widget code installed on your site looks something like the following code you are using the old sync version and we recommend you convert to the async version. Note: the code below is an example only, it shows a dummy site identifier (123456789012) and is for the small widget, the other types have slightly different formats.

<script type="text/javascript" src=""></script>
<script type="text/javascript">WAU_small('123456789012')</script>

If your code looks something like the following (again, this is an example, it will vary from widget style to widget style) then you are using our async code and all is good :)

<script id="_wau3b8">var _wau = _wau || []; _wau.push(["small", "123456789012", "3b8"]);
(function() {var s=document.createElement("script"); s.async=true;

We'd be happy to help you convert the code on your site to the async version if you are still using the sync version, feel free to <a href="">contact us</a>.

If you need a new widget code, just grab one from <a href="">the showcase</a> to ensure you have the latest code!