In the world of a site reliability engineer (SRE), failure is not only an option, but also expected. Systems, web applications, servers, devices, etc., are all prone to performance issues and unexpected outages at some point. It is an unavoidable fact. These unexpected failures can lead to huge revenue losses,
In one of our previous articles, we discussed what an SRE is, what they do, and some of the common responsibilities that a typical SRE may have, like supporting operations, dealing with trouble tickets and incident response, and general system monitoring and observability. In this article, we will take a
A site reliability engineer, or SRE, is a role that that encompasses aspects of both software engineering and operations/infrastructure. It also encompasses a strategy and set of practices and principles across service offerings and is closely tied to DevOps and operations. The term site reliability engineering first came into existence
Serverless. It’s likely you’ve already come across this term somewhere, but what exactly does it mean? Well, to start, serverless, or serverless computing, doesn’t really mean there aren’t servers involved, because there are, rather it refers to the fact that the responsibility of having to manage, scale, provision, maintain, etc.,
SaaS businesses are built upon the simplicity of computing, storage, and networking they provide to their users. Web and mobile applications provided by SaaS businesses are meant to be straight forward to consume for users. However, it’s important to deliver an excellent experience to your users who rely heavily on
A Content Delivery Network (CDN) is a collection of distributed nodes, called edge servers, connected to the same origin servers and placed local to the users’ location. If you are using a CDN, your website content is delivered to the user from the nearest edge server to their location. Without
Dotcom-Monitor has detected that Reddit.com has gone down on 3/10/2016 around 8:30 PM CST, returning a 503 error “all of our servers are busy right now”. This seemed to be a complete outage from all locations around the US until approximately 9:05 PM CST.
Can your Customers Reach Your Website? You may have been aware that a large DNS provider, Neustar UltraDNS experienced an extended outage on Thursday 10/16/2015 which caused many of the largest websites in the world to be unavailable for over an hour and a half. Recent large scale internet
October 15: Neustar UltraDNS Outage October 15, 2015 – Neustar UltraDNS Down – Dotcom-Monitor is tracking a Neustar UltraDNS outage at this time. The UltraDNS outage appears to have started at approximately 4:00 pm CST. The UltraDNS issue resulted in (as it should) error alerts to clients. Monitoring that does not cache DNS
UPDATE: It appears that the Gimp website registration expired and so the DNS resolution was automatically “parked” by the registrar. Once they were aware of this, the Gimp site admins re-registered the site for another 5 years, then the site was pointed back to the original content servers, but there
© 1998-2024 Dotcom-Monitor, Inc. All rights reserved.
