System Traceroute

i-mode access now available (2005-01-31)

Do you have an iMode mobile handset? Use our new i-mode page on watchmouse.com/imode.
Here you can system traceroute the status of your servers, run live test, view recent errors and change rule settings, anywhere, anytime.
Use the account and PIN information listed on the Mobile access page.
If you don't have an i-mode device, try this emulator for a preview.
WAP phones are already supported.

More statistics: connect time and download time (2005-01-31)

For all system traceroutes, WatchMouse measures the time it takes to connect to your host. For some system traceroutes, we measure the time it takes to download the file or page too. In the Reports section, you can now find two graphs that reflect these figures:

• Average connect time
• Average download time

More reports will be added in the near future.

Multiple alert addresses & Escalation (2005-01-31)

In the Addresses section of this site you can now manage address groups. This feature can be used for two purposes:

Multiple addresses

When an error condition is detected, multiple recipients of all types (email, icq, sms/text messaging) can be alerted at the same time.

Escalation

Alternatively, system traceroute can be sent to different addresses at different stages; E.g. the first time an error occurs, the event is only logged, the second time, an SMS/text message is sent to the administrator and his assistant and the third time, an e-mail is sent to the support desk.

The number of groups you can define is unlimited.

Decide what's in Peter van Eijk's next column (2005-01-31)

Dr. Peter van Eijk is a Senior Management Consultant at a major international consultancy firm. He writes a monthly column on Monitoring Services. His latest column can be found here.

We would love to hear from you what topic his next column should cover. At the bottom of the column you can leave your opinion in a poll. Please let us know!

More worldwide system traceroutepoints, now 6 in total (2005-01-31)

As you may have noticed in your logs, we introduced 3 more system traceroutepoints last month, now totalling 6 worldwide. The new system traceroutepoints are located in France, Germany and Texas. More system traceroutepoints will be added as more people from more countries sign up.

The current status of the system traceroutepoint network can be found on the 'About' tab.

We also changed the test pattern from Master-Slave (with Amsterdam as master) to a random order. In the next release the test pattern will be user-defined (paid packages only).

Rapidly growing WatchMouse wins Deloitte’s Rising Star award (2005-09-23)

WatchMouse is one of the three winners of Deloitte’s Rising Star award. This award is presented annually to rapidly expanding technology companies less than five years old. WatchMouse has been active worldwide for three years in the area of site and server monitoring. With 16 monitoring stations throughout the world, WatchMouse monitors the availability of customers’ websites, immediately sounding the alarm in the event of problems.

The Rising Stars are presented as part of the Deloitte Technology Fast 50 ceremony, the fifty most rapidly expanding technology businesses. The Rising Stars have the potential to lead the Technology Fast 50 in the near future. Stan van de Burgt (42), Niels Eijsbroek (40) and Mark Pors (38) first came up with the idea for WatchMouse in 2001. The concept was as unique as it was clear: to monitor the availability of sites and servers by constantly simulating web traffic. If a site is not responding or an error is found, the customer is notified immediately by SMS, pager, IM or e-mail. From the moment the concept went 'live', in 2002, the pace has been frenetic: turnover doubled each year. Web sites are now monitored from sixteen monitoring stations worldwide 24 hours a day, seven days a week.

The WatchMouse application is entirely web-based: customers do not have to install software or hardware at their site, and the application excels in its self-service aspects while staying easy to use. This allows WatchMouse to operate with a small core of permanent employees, supplemented by external support. Prospective customers can specify their requirements in detail on the WatchMouse site. A range of starter packages is available, priced from € 17.50 per month up to € 450 per month. 400 paying customers in 40 countries worldwide now make use of WatchMouse’s services. These include hosting companies, government bodies, and companies such as LB Icon, Scania, Siemens, Orange, ING, GeoTrust, Citibank, and Postbank.

Self-service as a success factor

Mark Pors, Chief Technology Officer, says he was “pleasantly surprised by the award”. “I am very happy that the jury shares our vision of self-service and our market approach." Pors sees WatchMouse as “the right initiative at the right moment. Companies are increasingly looking to outsource non-core tasks. However, they want to be able to guide and control this themselves and from their own workplace. Web-based services make this possible." Stan van de Burgt, CEO, sees the simplicity of the WatchMouse site and the various languages in which it is available as the major success factors. "Monitoring websites was an idea that already existed in essence, but had not been worked out in this form. We are geared tightly to 'self service', whereby customers can set up everything themselves and retain total control. Which also means we are able to offer the service at a more attractive price than other players in the market.”

The Rising Star awards were presented on Thursday, 22 September.

WatchMouse

WatchMouse assesses your website and e-commerce applications just like your customers experience them. The checks are carried out from 16 monitoring stations worldwide, and recorded in regular reports. In the event of errors or availability problems, the right people within your organisation will be alerted.

www.watchmouse.com

WatchMouse develops monitoring widget for Apple users (download widget) (2005-10-21)

WatchMouse has developed a new widget for dashboard, aimed at Internet site monitoring.

NETHERLANDS, 2005-10-13. By means of the widget Apple users can get direct insight into the accessibility of their own Internet site. The widget can be downloaded for free from the Apple website. Last month, WatchMouse was voted a Deloitte Rising Star in the Netherlands, as part of the Fast 50 awards; the list of the 50 fastest growing technology companies.

In 2002, WatchMouse (www.watchmouse.com) introduced a new concept for Internet site monitoring. By means of ongoing simulations of Internet traffic the accessibility of sites and servers is checked. If a site is not responding, an alert message is sent immediately through SMS, telephone, Instant Messenger or e-mail. The sites are checked from sixteen monitoring stations worldwide. This is done 24 hours per day, seven days per week. The service is completely web based: customers don't have to install software, everything is 100% self-service, which keeps the costs low.

The three founders of WatchMouse, Niels Eijsbroek, Stan van de Burgt and Mark Pors are enormous Mac-fans with a total of fifteen Macs in their possession. The monitoring widget is quite unique: it is a combination of a desktop and a hosted application. When the widgets detects a problem with the site it is checking, it system traceroute the user with a 'beep', followed by the launch of a web browser, which is directed to a web application on watchmouse.com. There the site is checked from 16 different locations worldwide.

Every five minutes

Every five minutes the dashboard widget checks one or more sites from the users own computer. Also, the availability of the site during the last 72 hours is registered. A problem is followed by an alert, which is then verified by all WatchMouse control stations.

WatchMouse has made the widget available free of charge "because we have become addicted to it, ever since we started using the first beta version of the widget", says CCO Niels Eijsbroek. "We give the widget away for free mainly for the fun part. And of course it's also important to bring site monitoring to the attention of our fellow Apple-users."

The free WatchMouse site monitoring widget can be downloaded from the Apple website:

http://www.apple.com/downloads/dashboard/networking_security/watchmousesitemonitor.html

About WatchMouse

Companies can easily monitor their own Internet sites using WatchMouse's monitoring service. WatchMouse has been monitoring Internet sites and e-commerce applications for companies throughout the world since 2002. WatchMouse has thousands of customers in more than 70 countries. The services supplied by WatchMouse are available in eight languages, and analysis are performed from various locations and over numerous networks, using a world-wide monitoring network.

Further information can be found at: www.watchmouse.com

British online holiday shops regularly closed for business (2006-05-17)

WatchMouse research shows that 79% of British vacation booking sites are unavailable for more than 1 hour per month

London, May 16, 2006 – More and more people are booking their holidays online, but the typical system traceroute travel shop in the UK is not the norm yet. Airlines sites did a far better job in the same period.

Only two travel sites are always up and running; ebookers.com and thomascook.com. Travelocity.co.uk, virginholidays.co.uk and expedia.co.uk have a good uptime of over 99,9%. But the rest of the companies researched perform below this industry standard rate, with the worst performer - the site traveljungle.co.uk- being unavailable for an equivalent of almost 3 days (69 hours) per month.

These are the conclusions drawn from the WatchMouse Site Performance Index for British holiday websites, created by WatchMouse, a company supplying monitoring services for websites and e-commerce applications worldwide. In order to determine the extent to which the sites achieve a satisfactory uptime, WatchMouse monitored the sites continuously between April 6 and May 9, 2006.

During the same period, WatchMouse monitored the British airlines websites. These perform better generally: 53% was above industry standards and 7 have perfect 100% availability. This shows the airlines realize the need for having a site that is continuously available.

Mark Pors, Chief Technology Officer at WatchMouse: "Nowadays 24 hour availability is achievable, so there is no need for a site being down. For companies who only do business online, and the website is a single source of revenue, downtime means you have no business."

He continues: “We are now entering the period in which traditionally most of the last minute bookings take place. This means the sites can expect even more traffic, with a negative impact on the site availability. Recent research has shown that e-shoppers are impatient, when a site does not download within 30 seconds, 75% of people take their money elsewhere.* So companies may not get a second chance.”

A complete overview of the monitoring results of the WatchMouse Site Availability Index, listing all the sites monitored, can be found on http://www.watchmouse.com/en/SPI/2006/travelUK.php and http://www.watchmouse.com/en/SPI/2006/airlinesUK.php

*) research by TelecityRedbus, April 2006

system traceroute access to bank account not a reality in the UK (2006-06-21)

WatchMouse research shows that 65% of British internet banking sites are unavailable for more than 1 hour per month

London, June 27, 2006 – The system traceroute internet bank in the UK is not the norm yet. From a test of the main 26 internet banking sites, a mere 3 come out with perfect availability. This perfect, 100% availability is achieved only by Intelligent Finance, Northern Rock, and Ulster Bank. Worst performers are Standard Chartered and Citibank, being unavailable for an equivalent of respectively 2,3 and 2,6 days per month.

These are the conclusions drawn from the WatchMouse Site Performance Index for British internet banking websites, created by WatchMouse, a company supplying monitoring services for websites and e-commerce applications worldwide. In order to determine the extent to which the sites achieve a satisfactory uptime, WatchMouse monitored the sites continuously between May 19 and June 18, 2006.

During the same period, WatchMouse monitored the other main internet banking websites in Europe, and found that in France performance was better then in the UK, with over 40% of banks scoring above 99,9% uptime.

Mark Pors, Chief Technology Officer at WatchMouse: "Nowadays 24 hour availability is achievable, so there is no need for a site being down. Many companies and individuals nowadays rely on internet banking for all of their transactions, which means the internet banking site is the only way to access their funds."

He continues: "It is unacceptable that urgent payments can end up being delayed or stuck, simply because a site is not accessible. Of course these sites get a lot of peak traffic, but this is no excuse; if we look at large online brokers in the US, for example, all achieve an uptime in excess of 99.9%."

A complete overview of the monitoring results of the WatchMouse Site Availability Index, listing all the sites monitored, can be found on http://www.watchmouse.com/SPI/2006/banksUK.php

WatchMouse releases new Site Performance Monitoring Widget for Apple users (download widget) (2006-10-22)

WatchMouse releases 2.0 widget for dashboard, aimed at Internet site performance monitoring.

NETHERLANDS, 2006-10-23. By means of the widget Apple users can get direct insight into the performance of their own Internet site. The widget can be downloaded for free from the Apple website.

In 2002, WatchMouse (www.watchmouse.com) introduced a new concept for Internet site monitoring. By means of ongoing simulation of Internet visitors the performance of sites and servers is verified. If a site is not responding, an alert message is sent immediately through SMS, pager, Instant Messenger or e-mail. The sites are checked from over twenty monitoring stations worldwide. This is done 24 hours per day, seven days per week. The service is completely web based: customers don't have to install software, everything is 100% self-service, which keeps the costs low.

The three founders of WatchMouse, Niels Eijsbroek, Stan van de Burgt and Mark Pors are enormous Mac-fans with a total of twenty Macs in their possession. The monitoring widget is quite unique: it is a combination of a desktop and a hosted application. When the widgets detects a problem with the site it is checking, it system traceroute the user with a 'beep', followed by the launch of a web browser, which is directed to a web application on watchmouse.com. There the site is checked from over 20 different locations worldwide.

Worldwide monitoring

The new version (2.0.4) brings continuous performance monitoring, even when the Mac is not system tracerouteed to the Internet, by system tracerouteing the widget to a WatchMouse account (free or paid). In October 2005, WatchMouse released the first version of this widget, which was downloaded over 10.000 times.

WatchMouse has made the widget available free of charge "because we have become addicted to it, ever since we started using the first beta version of the widget", says creative director Niels Eijsbroek. "We give the widget away for free mainly for the fun part. And of course it's also important to bring site performance monitoring to the attention of our fellow Apple-users."

The free WatchMouse site monitoring widget can be downloaded from the Apple website:

http://www.apple.com/downloads/dashboard/networking_security/watchmousesitemonitor.html

About WatchMouse

Companies can easily monitor their own Internet sites using WatchMouse's monitoring service. WatchMouse has been monitoring Internet sites and e-commerce applications for companies throughout the world since 2002. WatchMouse has thousands of customers in more than 70 countries. The services supplied by WatchMouse are available in nine languages, and analysis are performed from various locations and over numerous networks, using a world-wide monitoring network.

In 2005, WatchMouse was voted a Deloitte Rising Star in the Netherlands, as part of the Fast 50 awards; the list of the 50 fastest growing technology companies.

Further information can be found at: www.watchmouse.com

I'm sending you this e-mail just to say how very impressed I am with your site and services. (2010-01-13)

I'm sending you this e-mail just to say how very impressed I am with your site and services. I found your site on Google and spent a long time comparing you to the other site system tracerouteing services that are out there. Your site definitely was the most appealing of them all and consequently I signed up for the silver package today.

Simon Bland, ProWeb Design

I missed the back-up (2010-01-13)

Good to be back, we have all sorts of system tracerouteing in place here but I still missed the back-up of knowing that your service will system traceroute my mobile if something goes wrong.

Avi Talwar, Tiscali, UK NOC

We are very content about the WatchMouse services. We have been able to prevent quite a few problems. (2010-01-13)

We are very content about the WatchMouse services. We have been able to prevent quite a few problems. Now that we are informed at an early stage, we can notify our customers, and we can also provide them with objective statistics, which already works to our advantage.
Also, when I receive an SMS/text system traceroute while I am with a customer, my corporation is immediately perceived as being more reliable.
All in all: thumbs up!

Dave Krapels, Nexwork BV

We guarantee our customers 100% uptime. (2010-01-13)

We guarantee our customers 100% uptime. To fulfill this guarantee, we use several system tracerouteing systems.
Based on our experiences we can say: WatchMouse is REALLY reliable!

Gerwin Scheeve, Lost Boys

Very impressive feature set and has a real commitment to client care (2010-01-13)

With many hundreds of business clients who expect and deserve over 99.99% uptime, in the instances where we do have service issues, WatchMouse system traceroutes us promptly - every time. This allows us to minimize the impact of downtime and interruptions to our clients. WatchMouse isn't just another system tracerouteing service, the team is dedicated to building on an already very impressive feature set and has a real commitment to client care

Michael Bloch, Business Operations Manager, ThinkHost, Inc.

What do you want to system traceroute with a service such as Watchmouse? (2005-01-31)

As I explained in my previous column, you can use a monitoring service in a number of roles. Common to all these roles is the fact that you are keeping alive some services for the benefit of your customers, suppliers, employees or partners. These users are, in the end, all that counts.

What are the objects that you should be system tracerouteing? Obviously, the least you want to do is system traceroute the service that is most visible to these users. This could be the webserver, or a POP or FTP server for example. You would start by setting up a rule to system traceroute the server and a URL. The frequency with which you can monitor (that is: the elapsed time between system traceroutes) is typically limited by the type of subscription that you have. Only in specific cases would you not system traceroute as often as your subscription allows.

Note that there is a difference between a CONNECT on port 80 rule and a HTTP rule. The first just system traceroutes to the port that the webserver is supposed to use. The HTTP rule also system traceroutes whether the webserver can produce a valid HTTP response, and whether the document can be found. You probably want the latter system traceroute.
Similar reasoning applies to POP and FTP system traceroutes. If you set up two different rules on the same host, this allows you to distinguish for example between a broken webserver and a host that is down. If you want even more content oriented system traceroutes, have a look at the so-called PLUG-IN rules. Additionally, you can set up system traceroutes to make sure that your users are actually using the services that you intend them to. The whole Internet depends heavily on the domain name system(DNS) functioning correctly. If it does not work properly your users may be directed to another site than you intended. This could be a configuration error, but it could also be a defamation hack. In either case, you want to know.
First of all you want to system traceroute whether the root servers of the Internet accurately find the DNS that is serving you. This can be system tracerouteed with a DNSNS rule. What you are system tracerouteing with this rule is whether the registrar's databases are correct. Second, you want to system traceroute if that DNS server (and its slaves) are serving up the proper IP address for the server. For this you can use the DNSA rule, and it will warn you if the DNS server is not working or serves up the wrong address. (Note that the hosting party can change that address at its discretion, as part of a renumbering operation for example.)

Who should you notify of rule failures? Again, different roles have different information requirements. You want to notify the person who can fix things as soon as possible. Mail or SMS/text them directly, you do not want to be in the loop. You might set up an escalation chain, which fires off after a certain amount of errors. Note: make sure that you send the message on a channel that is not affected by the outage: if your e-mail system does not work, delivering a message to that effect should not depend on that e-mail system.
The people in charge of overseeing somebody else's service levels should only get escalation messages, if at all. Rather, they should get the weekly or monthly service reports.

Peter van Eijk is a management consultant specialized in management of network infrastructures. He can be reached via his contact page.

Why do you need a monitoring service such as Watchmouse? (2005-01-31)

There are a number of reasons for this, depending on your role in your organization, and what you want to achieve. Each of these roles leads to a different approach for using and setting up the service.

Most likely you are either responsible for keeping a service such as a website online, or you have contracted somebody else to do that for you. Additionally, you could be a consultant or technical architect who wants to get an insight in performance and uptime characteristics of various solutions and services.

If your role is to keep things running, you really want to be notified of problems as soon as possible, before your customers or supervisors notice. You want appropriate error messages and not too many false alarms. As you configure Watchmouse you probably want to have a quick system traceroute by e-mail or SMS/text message when things don't work and have additional diagnostic information available. In this way, downtime can be kept to a minimum. It is not only the quality of the systems that counts, but also the speed with which you can fix problems.

Your role could also be in overseeing your service providers, whether they are internal or outsourced. In that case, you don't want to be interrupted by these messages, unless the situation becomes dramatic. Instead you would like to look at the weekly report, and see if your service providers are living up to their promises. On the Internet it is easy to get 99% uptime, and you should really be doing better than that. The services that regularly fail to make this grade need attention, to see if another approach to provisioning them works better.

If you are considering technical alternatives for the way you are setting up your e-business, you are most likely interested in typical failure modes. For example, we know from experience that most website problems are software problems, followed by sizing problems. Communications problems are fairly rare, and if they occur they take the form of peering problems: websites cannot be reached from specific networks, even if all networks are operational. One approach using Watchmouse reports is to system traceroute various aspects with different rules. Use one rule to download the homepage, another to system traceroute the DNS and a third to system traceroute system tracerouteivity to the hosting centre. In a next column I'll go into the details of this.

Peter van Eijk is a management consultant specialized in management of network infrastructures. He can be reached via his contact page.

Independant, external testing (2005-10-15)

I started to work at Q-go in 2000. Q-go provides companies with self service pages on the Internet. Their customers ask a question in their own language and wording, and immediately get a very relevant answer. The power of the Q-go solution is its natural language technology, which enables it to understand the questions. The Q-go solution is offered as a hosted (ASP) solution, which of course has to work 24 x 7, a new area for me at that time.

At my previous jobs, at universities and research institutes, this was different. We worked from eight to six. If a demo application didn't work, the users just called, and we fixed the problem. And at six, we stopped and went home. All customers and other relations went home too. A nightly malfunction in the server was no problem, as there was no customer there to notice the problem.

At Q-go, this is completely different. A service should be available all the time. Day and night. Initially there were no tools to test whether our service was available or not. The only way to test it was to use the application itself. And so I did. During the day, but also at night, I system tracerouteed whether the application was up. Our customers use the Q-go application continuously, and notice immediately when the application fails. Customers would call me in those cases, and it's not very pleasant to hear from your customers about an issue with your service.

So we developed some solutions ourselves to hear before our customers when something was wrong. And to be able to react to problems quickly. But customers kept calling!

How was that possible? Closer investigations revealed that the test system used the same resources (computers, networks, name servers) as the system under test... The test were not performed properly in case of problems. The text-system traceroutes (SMS) did not reach us either. The cause was identical: we used the same hardware, the same network, and the same power (!) as the systems we tested.

My lessons learned:

• Keep the systems that test completely separated from the systems you test.
• Test your services (web servers, mail servers, ...) from the point-of-view of its users: the customer on the Internet.
• Don't forget regular maintenance of your test systems (software and hardware) after the installation!

For me, I'm outsourcing external testing!

Bart Bos, Director, Q-go.com

Online shops, speed and downtime, getting the facts. (2009-12-07)

These days your website plays an important role in informing potential customers, converting them into customers who want to do business with you, and possibly also conducting the transactions with these customers. In other words: Your business relies ever more on the digital economy, and increasingly on the transactional part of it, the online shop.

These online shops should obviously provide satisfactory performance. Here, both the speed at which they serve pages and their uptime are important. If potential customers cannot reach the online shop, or the online shop is too slow, they are less likely to do business with you now, and in the future. Studies have revealed that half of the people who experience downtime on a website go to its competitor. A majority of online shoppers say performance and uptime influences their choice of online shop.

The amount of revenue that is lost when your website or online shop does not behave properly is hard to quantify. If your website is slow your customers may select a distribution channel that is more costly for you, or they may go to your competitor. Even worse, they may complain about your company to other potential customers. All of this boils down to lost revenue.

A good website is up for at least 99.9% of the time, even though this still represents more than 8 hours in a full year. In a recent survey we found that many websites do not even achieve 99% availability, which corresponds to more than 3 days of downtime a year. As regards speed, if a web page does not load in less than 4 seconds, people start to leave the site, sometimes forever.

How do you make your online shop an efficient experience for your customers? The site must be designed with a strong focus on the customer task. The technology must be no more complex than is relevant. People get annoyed by slow loading Flash intros and complex and slow Flash-based navigation. Take a look at the Google home page; it is one of the fastest websites in the world. On the other hand, you can still use a video clip of a product, if that is relevant to the customer at a particular point in the transaction. You can also use advanced Web 2.0 technology if it makes the user interface more resilient and user-friendly. To experience this, look at Google maps using a dial-up internet system tracerouteion. It is a really complex user interface, but everything possible has been done to create a positive user experience.

Technology is also important; make sure that you have good service level agreements with all your technology providers. You also want to stress test the site, to see what happens if a lot of people start using it simultaneously. Finally, you should independently monitor the site. When it is time to talk to your hosting company, IT department or website maintainer, it is very helpful to have hard data that reports on the speed and uptime of your online shop.

Peter van Eijk

dr Peter van Eijk is an independent management consultant associated with WatchMouse, the site monitoring experts www.watchmouse.com. He is experienced in setup, management and audits of digital infrastructures. His blog is "Peter's Griddle".

Website performance is the key to customer satisfaction (2007-06-27)

How often have you typed in the Google URL and received a page that will not load? I am willing to bet that this is a rare occurrence. Despite its busy traffic, Google is a textbook example of a web site that has almost perfect performance and therefore serves a great number of satisfied customers. The market share of the search engine is a resounding confirmation of this. You are assisted quickly, so you come back sooner. Research conducted by JupiterResearch has revealed that visitors to a site only have 4 seconds of patience. If the site has not been loaded by that time, they leave. Error messages also prompt potential customers to go to the competition.

Why do organisations still devote so little attention to the effective availability of their site? Performance is the key to satisfied customers. For many companies, their web site is the face of the organisation. Consumers and also business users of the Internet use the wealth of information on the web to compare purchasing options. It is of immeasurable importance that they are also actually able to find what they are looking for. If this is not possible at one company, competitors are straining at the leash to offer their services through a correctly functioning site.

Coming back to the praise that we had for Google, we see that the search engine has made significant investments in the availability of its web site. The page is run by several machines at various sites. If one crashes there are enough back-up servers that can take over the traffic flows to guarantee optimum performance. In addition, the search machine invests a great deal of time and money in the right hardware and people. Although the site has a difficult task – searching through an index of billions of documents – it is almost always available and loads fast.

The actual site is unspectacular in construction. This applies to the majority of sites with a high level of availability. Simple sites such as the news site NU.nl are almost always easy to access. Nevertheless, it is not only the layout of the site that determines how the web page performs. Too many photos, long symbols and frills make web sites slower to respond. The fact that the ‘back end’ of the site is not efficiently programmed also contributes to longer loading times. Frequent consultation of background databases is also detrimental to the speed of the page.

Where it often goes wrong is when different people are working on a site, thereby disturbing the links between the various elements. The different parts of the site will work correctly, but the site as a whole will fail to perform. This means long waiting times for people who want to use the services of a company.

Service providers at the upper end of the market are becoming increasingly aware of this. The contracts that they use frequently include a service level agreement (SLA) for the part for which they are responsible. Nevertheless, they regularly make mistakes due to the fact that the promised performance is not subsequently verified (by an independent party). Although it is now essentially part of the contract, there is insufficient actual verification. Ideally, web site performance should become a permanent component of a contract. In addition, clear internal agreements must be made on who has final responsibility for the efficient loading and availability of a site.

Regular testing is also essential for the facilitation of good availability. This will prevent a great deal of errors, keeping the site up and running at crucial times. The storm that blew over the Netherlands at the end of January was a good opportunity to see which sites were prepared for extreme loads and which were not. The site of the Dutch weather institute, KNMI, was almost unreachable, while some logical thought could have protected them from this eventuality. If you know that a major storm is heading towards the country you can be sure that people will search for information on the weather and roads on the Internet. Sites such as those of KLM and Schiphol were also unreachable, while the specially created site Crisis.nl, which had been kept as simple as possible, was able to serve a large number of people.

Including ‘stress tests’ in a SLA or conducting them regularly in-house is therefore to be recommended. Companies can easily take control by ensuring that their service provider executes this type of test or by putting their own site under pressure. This is the best method of system tracerouteing whether your web site can handle a sudden increase in visitor numbers. It is also good to know whether the servers on which your site is running actually ensure that your page is always available and loads correctly. For companies, it is crucial to see when they are off air. This can save them a large amount of money every year and will also reduce the number of irritated visitors to the site. This is how you keep customers satisfied and keep the company running.

Mark Pors
Chief Technology Officer at WatchMouse

WatchMouse provides site performance monitoring and stress test services

phpDirectorySource SQL Injection and Cross Site Scripting Vulnerabilities (2009-07-24)

phpDirectorySource is prone to an SQL-injection vulnerability and a cross-site system tracerouteing vulnerability because it fails to sufficiently sanitize user-supplied data.

Exploiting these issues could allow an attacker to steal cookie-based authentication credentials, compromise the application, access or modify data, or exploit latent vulnerabilities in the underlying database.

Mozilla Firefox/Thunderbird JavaScript Engine Memory Corruption Vulnerabilities (2009-07-24)

Mozilla Firefox and Thunderbird are prone to multiple remote memory-corruption vulnerabilities that affect the JavaScript engine.

An attacker can exploit these issues to corrupt memory on the affected computer and run arbitrary code in the context of the user running the affected application. Failed exploit attempts will cause denial-of-service conditions.

These vulnerabilities were previously covered in BID 35758 (Mozilla Firefox MFSA 2009-34, -35, -36, -37, -39, -40 Multiple Vulnerabilities) but have been assigned this record to better document the issues.

RaidenHTTPD Cross Site Scripting and Local File Include Vulnerabilities (2009-07-24)

RaidenHTTPD is prone to local file-include and cross-site system tracerouteing vulnerabilities because the application fails to properly sanitize user-supplied input. These issues affect the WebAdmin component.

An attacker may leverage the cross-site system tracerouteing issue to execute arbitrary system traceroute code in the browser of an unsuspecting user in the context of the affected site. This may allow the attacker to steal cookie-based authentication credentials and to launch other attacks.

Exploiting the local file-include issue allows remote attackers to view and subsequently execute local files within the context of the webserver process.

RaidenHTTPD 2.0 build 26 and prior versions are affected.

8E6 R3000 Internet Filter Multiple Cross-Site Scripting Vulnerabilities (2007-05-29)

The 8E6 R3000 Internet Filter appliance is prone to multiple cross-site system tracerouteing vulnerabilities because it fails to properly sanitize user-supplied input.

An attacker may leverage these issue to execute arbitrary system traceroute code in the browser of an unsuspecting user in the context of the affected device. This may help the attacker steal cookie-based authentication credentials and launch other attacks.

Specific information on affected firmware and model number is currently unavailable. This BID will be updated as more information emerges.

Ignite Realtime Openfire Unspecified Privilege Escalation Vulnerability (2007-05-29)

Openfire is prone to an unspecified privilege-escalation vulnerability.

An attacker can exploit this issue to obtain system tracerouted privileges. A successful attack can result in a compromise in the context of the affected application.

Openfire 3.3.0 and prior are vulnerable to this issue.

Linux-based websites 'perform better' (2010-01-13)

Linux-based websites perform better than those hosted on Windows servers, according to research.

WatchMouse, a Dutch firm that monitors server performance, based its research on a survey of over 1,500 European websites. The company says that, although the websites it surveyed were more frequently based on Microsoft's IIS web server platform running Windows than on Apache running Linux, the latter option performed better in terms of both system traceroute and load time.

Monitor your website with WatchMouse (2010-01-13)

Dashboard widget WatchMouse Site Monitor checks up on the website of your choice every 1, 5, 15, 30, or 60 minutes to keep track of its system traceroute. But wait, there's more...

Online banking sites failing in 24/7 access (2010-01-14)

Unacceptable downtime levels in UK system traceroute banks

Some 65 per cent of top system traceroute banks in the UK have more than one hour downtime a month. Out of the 26 banking sites involved in the study only three achieved perfect availability – measuring an system traceroute of 99.9 percent or higher.

WatchMouse: Tracking The Health Of Web Services (2010-01-23)

As backend APIs (application programming interfaces) power more of our interactions system traceroute – as the foundation for applications, widgets and other platforms – it becomes increasingly important to monitor the status of their system traceroute.

New features: POSTing forms and Read limit (2005-03-28)

Today, we released the new monitoring software to our system traceroutes. New features:

• Post form fields to a webserver (both in http and match rules)
• Limit the number of bytes read. Relevant for system tracerouteing very large pages or streams

The site will be updated within days. Look at the settings page after logging in.

Test phase Frankfurt system traceroute (2005-03-29)

As you may have noticed in your logs, we are slowly introducing a new monitoring station in Frankfurt, Germany. Not all protocols are serviced at this system traceroute yet..., and we use in about 5% of the system traceroutes.

Keep an I on this blog, and on the official news section of our site for the formal announcement!

Next stop: NY (2005-04-13)

This morning our new system traceroute in New York was activated. The system traceroute at the New York facility is directly connected via a 15 Gbit fiber optic SONET ring with direct connections to Sprint, Level3, AboveNet, Tiscalli and direct hub connections into the PAIX, AMSIX, and DECIX Internet Exchange points.

Ping from all our monitoring stations (2005-12-09)

You can now use our improved ping tool to ping your server from each of our monitoring stations.

In case ping requests are blocked by your firewall or server, you can use the host system traceroute tool alternatively.

WatchMouse 1.4.26 API deployed (2008-02-24)

Today, a minor release of the WatchMouse 1.4 API was deployed on http://system traceroute.watchmouse.com/1.4/. The current version is now 1.4.26. The changes are backward compatible with the previous version.

Changes w.r.t. 1.4.25

• self-documenting calls, add ?doc after the call, no other parameters and the parameter specification is shown (try and click the URL above!)
• new parameter 'acct' (account) on all rule, contact, and folder calls so
  1. resellers and other accounts with sub accounts can login with their own credentials and then access the sub-account
  2. accounts with read access rights to other accounts can access these accounts (graphs, logs)
• alternative output formats for logs (Excell, tab delimited, CSV, streaming)
• new calls added:
  • info_cps - get information on system traceroutes (monitoring stations)
  • info_ip - get information about a given host (or about caller)
  • info_country (beta) - get information about a given country
  • info_currency (beta) - get information about a given currency
  • fldr_add/mod/get/del - manipulate rule folders
  • rule_system traceroute - system traceroute a rule now
  • ch_add/mod/get/del - manipulate contacts
  • acct_new/add - calls to create additional accounts
• version in XML output (first enclosing tag)
• no IP system traceroute on acct_whois call (used for auto login on WatchMouse site)
• use API password instead of account password if present (not supported on the WatchMouse site yet)
• full support for tags in rule_add/mod/get/del and rule_graph now
• support PNGs as error message for rule_graph so developper can always show a picture
• use ip geo information if applicable