5 possible Takeover scenarios

Posted on July 3rd, 2017 by Damien Jordan in Monitoring

WebSitePulse Takeover Service
It is always good to know that someone is going to take care of your website when it goes down. We as a website and server monitoring service offer such a feature and it is called Takeover.
Our "Takeover" service lets you leave detailed instructions that we will follow in case of a detected downtime. If you want to know more about how to enable and configure the takeover feature, you may want to check out this article - Handling Downtime and Outages.
To get a better idea of what instructions you can leave, here are 10 possible takeover scenarios that a lot of our customers have configured.

1. Calling a list of designated contacts
A list of designated people can be provided that we will start contacting once an issue with one of your monitored targets is detected, e.g. escalation scheme:
After the second consecutive failure, call John at +1 222 333 4444
If John is not available, call Jeff at +1 333 444 5555
If Jeff is not available, call Mary at +1 444 555 6666

We will start calling the people on the list until we reach one of the contacts and we report the problem. We can also send a text message or leave a detailed voice mail if requested.

2. Contacting the web hosting provider and submitting a ticket
The hosting provider support URL is required, as well as the username and password for logging in. Once we receive the takeover notification, we will open the hosting provider’s website, log in to your account, create a ticket and communicate with their support staff until the issue is resolved. We will then send you a detailed report describing our actions and how the issue was handled by the hosting provider's support team. Here is an example:
In case my target is down and my website is not opening, please submit a ticket to my hosting provider.
www.hostingprovider.com
Username: user1
Password: Pass1
Go to Support -> Tickets -> Submit a ticket
You should get a response in 30 minutes. If this is not the case, send a follow up e-mail or call them.

3. Manually rebooting the server
In addition to the aforementioned scenario (scenario 2), we can also log in your hosting provider's control panel and manually reboot the server or restart individual running services if the option is available, e.g.:
www.hostingprovider.com
In case my target is down and my website is not opening, please reboot my server.
Username: user1 Password: Pass1
Go to Servers -> Select Server 001 -> Perform a power cycle After the reboot, if the server has still not recovered, we can either submit a ticket or contact you for further instructions.

4. SSH to a server
Our 24/7 support team is highly trained and we can follow more complex takeover instructions, including establishing a SSH connection and perform various action on it. Please be as descriptive and thorough as possible in the instructions that you leave. If a SSH connection is not possible due to the nature of the failure, we can still contact you, submit a ticket or call your hosting provider.

5. Custom instructions
Not finding a suitable takeover scenario for your needs above? We are very flexible and we will be able follow and execute your custom takeover instructions. Make sure that you contact us first if the instructions you are about to submit require the use of specialized software or require additional information in any way as we want to make sure that we are fully prepared for action when the target goes down.

Do you have any other takeover scenario ideas and thoughts? Please share them in the comment section below.

Or maybe you have some questions or concerns regarding our services? Feel free to call us at +1 888 977 8573 or just drop us a line to support@websitepulse.com and we will be glad to assist you.

Read more...

Instagram is down

Posted on April 24th, 2017 by Damien Jordan in Monitoring, Performance Reports

Instagram is down

If you were not able to log in your Instagram account recently or you were not able to view or like any of the photos of the people you follow - you are not alone. Instagram experienced major server issues, which started at around 1:30PM ET. We detected the problem in the first minutes of the occurrence. The site was intermittently returning 503 - Internal Server Error, 5xx errors or it was timing out after 30 seconds.

Read more...

Amazon AWS S3 outage

Posted on March 1st, 2017 by Websitepulse in Monitoring, Industry News

Amazon AWS S3 outage

 

Read more...

The Free Website Test Tools by WebSitePulse

Posted on May 31st, 2016 by Websitepulse in Monitoring

WebSitePulse Free Test Tools

The Free Website Test tools by WebSitePulse allow you to test a server, website or network as a one-time thing, without having to create a monitoring target. We have tried to keep them as simple and easy to use as possible. Here is a quick guide to how each test can help you.

Read more...

Handling Downtime and Outages

Posted on May 30th, 2016 by Damien Jordan in Monitoring

Is your site down? We all have experienced outages and downtime and we all know that this has quite a negative impact on our business and reputation. Unfortunately, downtimes and outages cannot be completely avoided, but can be quickly detected, thus minimizing the negative effects. All we need is a very good tool, which will help us identify even the shortest server overloads or network glitches.

First of all you have to be prepared to handle the situation. Knowing the configuration specifics of your website / server / third party hosting panel is crucial if the problem is on your side and can be fixed by you. There are times when you will not have control over the situation as the issue is with a major upstream provider, but being notified immediately about it gives you the chance to contact the provider and let them know that there is a problem. Using our services gives you another option – our Takeover feature. It allows you to leave detailed instructions that our support team will follow in case of a detected failure. You might want us to contact your hosting provider and report the problem, give us credentials to SSH to your server and manually reboot it (if possible), etc.

Read more...