How you can check wordpress Performance and Availability Status

Here is wordpress tutorial, how to check wordpress Performance and Availability Status. Yesterday wordpress users faced the issue with fetching the user stats. Yesterday wordpress tweeted on twitter saying.

check wordpress Performance and Availability Status

First Tweet: “WordPress.com experienced a service disruption this morning, but we’re back now. Thanks for your patience.”

After some time they came back with saying following sentenance on twitter

Second Tweet: You can always check the status of your favorite services—including WordPress.com—here: http://status.automattic.com/

Third Tweet: The status page is hosted completely independently so it will stay up if WordPress.com is down.

For checking the WordPress server status you need to check the following site:

http://status.automattic.com/

More details go to following URL:

http://status.automattic.com/9931/135469/WordPress.com

What Automatic is Saying?

Automattic – Sites real-time websites availability and performance status. This site shows if Automattic – Sites sites are down or have performance issues right now, and provides Automattic – Sites uptime and performance history.

This status service is powered by WatchMouse website monitoring service. We will come with more details later.

No More wait for wordpress 3.0

Today Matt announced the wordpress 3.0 launch. WordPress 3.0, is the 13th major release of the software, and contains over 2,700 changes. With this release wordpress is become the world’s most powerful and popular blogging system as well as cms.

I always believe wordpress is great cms for creating the most advanced cms and ecommerce and networking website.  Earlier wordpress mu was designed for Biggest corporate and companies and vast businesses.

What’s new in 3.0? One of the best ways to find out is to try out the new Twenty Ten theme, which shows off many of the release’s (which is also called “Thelonius”) major new features, including custom backgrounds, headers, shortlinks, menus, post types and taxonomies.

WordPress 3.0, the thirteenth major release of WordPress and the culmination of half a year of work by 218 contributors, is now available for download (or upgrade within your dashboard). Major new features in this release include a sexy new default theme called Twenty Ten. Theme developers have new APIs that allow them to easily implement custom backgrounds, headers, shortlinks, menus (no more file editing), post types, and taxonomies. (Twenty Ten theme shows all of that off.) Developers and network admins will appreciate the long-awaited merge of MU and WordPress, creating the new multi-site functionality which makes it possible to run one blog or ten million from the same installation. As a user, you will love the new lighter interface, the contextual help on every screen, the 1,217 bug fixes and feature enhancements, bulk updates so you can upgrade 15 plugins at once with a single click, and blah blah blah just watch the video. :) (In HD, if you can, so you can catch the Easter eggs.)

why wordpress was down for 110 minutes

On 19th Feb 2010 we all faced the wordpress down and that affected the 10.2 million blogs. why wordpress was down for some time on 19th 2010 due to huge amount traffic.

That is really huge amount of blogs and page views missed by wordpress. On that day itself Matt who is founder of wordpress is came up with reason. That is really great relief and news to all bloggers of wordpress.

why wordpress was down
why wordpress was down

As Per Matt:  It appears an unscheduled change to a core router by one of our datacenter providers messed up our network in a way we haven’t experienced before, and broke the site. It also broke all the mechanisms for failover between our locations in San Antonio and Chicago. All of your data was safe and secure, we just couldn’t serve it.

What we’re doing: We need to dig deeper and find out exactly what happened, why, and how to recover more gracefully next time and isolate problems like this so they don’t affect our other locations.

I will update this post as we find out more, and have a more concrete plan for the future.

I know this sucked for you guys as much as it did for us — the entire team was on pins and needles trying to get your blogs back as soon as possible. I hope it will be much longer than four years before we face a problem like this again.