Being advised by a client, friend, or somebody outside your workplace a site is down is, quite frankly, embarrassing. All sites run into trouble from time to time. Murphy’s Law will make certain of that. There are just too many things that may break a web site, from host hardware issues, software issues, programming mistakes, network downtime, and electricity outages. The options are, as they say, endless.
It’s probably not your fault either, but here you are about saving someone’s bacon. What can you do here
Is the Website Actually Down?
This might be obvious, and also a means to toot our own horn, but in SolarWinds® Pingdom® we’ve uptime tracking –your very first line of defense. Since Pingdom is using over 70 worldwide test servers, it’s possible to really get an external perspective on your site –which beats clean your browser, like a monster. Within a moment, Pingdom will confirm if your site is down or not.
If the site is down, be certain that you sit up straight and continue reading. Oh, also it would be suitable to pinch the bridge of your nose and simmer for several seconds–if nothing else than for result. Let your colleagues know you are important.
Related: – 12 Must Have Features for Your Website
Figure Out What the Problem Is
A Lot of things can Violate a Web Site, but Generally, It Is Going to be more of the following reasons:
- Code error
- DNS problem
- Networking issues
- Server issues with your web host
From the Pingdom awake, you will get the main reason behind your own toaster. It is time to check at a few of the most frequent reasons sites return.
HTTP Error 403: Your petition was legitimate, but the host is threatening actions. You may not have the required permissions for a source or might require a consideration of some type.
Packet Loss: This is a system error that may be related to damaged hardware such as a server, network congestion, or another hardware/network capacity bottleneck.
HTTP Error 503: Indicates the hosting isn’t accessible due to scheduled maintenance or due to a temporary overload in visitors. This will probably require support from the hosting provider or your operations staff.
HTTP Error 500: The 500 Internal Server Error is a really typical HTTP status code which means something has gone wrong on the site’s server, however the host couldn’t be more specific on exactly what the specific problem is.
Redirection Error: That really is a 301 or 302 gone poor and happens when you attempt and do a redirect to a HTTPS URL, but the SSL certification for this URL does not match the domain name.
The Pingdom reside map permits you to observe the condition of the net live since it occurs, from the number of outages we have discovered in the previous hour and many frequent error messages into what browsers and devices Web users are employing. Additionally, this is a remarkably useful tool when important outages happen from hosting and CDN suppliers.
Use Your Monitoring Data as Leverage With Your Hosting Provider
Many hosting companies will not be upfront about website issues if you don’t have evidence to back this up. When there’s absolutely no reported status difficulty with your supplier, now you can file a support ticket and also utilize all of the appropriate monitoring data you need from a different third party to prove you’ve got problems.
The earlier you know about a issue, the sooner you are able to repair it. Conversely, if you do not know about a issue, you can not mend it.
Communicate With Your Users Via a Status Page
We can’t overstate the value of this step. Transparency inspires dedication, therefore please think about having a public status pageyour customers will thank you for this. A public standing page is a excellent way to keep users at the loop of everything you are doing at this time and will decrease the influence on your customer care team. And you do have two minutes to log in and upgrade your public status webpage.
- Get a people status page. Hey you’ve one through Pingdom, or in the event that you’d like you can attempt Atlassian Statuspage, SorryApp, or even Cachet.
- Update your status webpage with your applicable status for example’exploring’,’continuing’, and’solved’.
- Update Twitter together with the continuing issue and connect to a status page.
- Ensure that you trap this tweet so that it remains clearly observable. In this way, your customers can see you are alert to the problems and follow upgrades on the webpage. You shouldn’t ever (need to) copy and paste the identical conversation over and over to anyone who requests what’s happening.
- Many standing pages provide users a means to subscribe to upgrades, so once an issue is solved your users will find an email notifying them it is all system proceed.
Conclusion: Wrap Up
In this guide, we just touched onto the surface of everything you could do, and being on the watch for if something goes belly up. But, we just covered a very small subset of items you can perform. If you are a part of a SRE staff somewhere, odds are you are knee-deep from the Apache or even Nginx server, then palms sore from composing orders.
Consider website tracking as cheap insurance from embarrassingly long downtimes. Heck, look at it because your private watchdog which will bark everywhere there’s an problem with your site. Just this puppy speaks and assists you as a site owner to purge, and helps maintain your internet host fair.