Operations | Monitoring | ITSM | DevOps | Cloud

The internet is the lifeblood of our modern world. With over 5.4 billion users globally, it connects us to friends, family, information, and opportunities. But what if the internet suddenly disappeared? What would be the cost of shutting down the internet? Internet outages, while thankfully rare, can have devastating consequences. To highlight these, we’ve delved deep into the economic impact of internet disruptions, analyzing real-world cost data to reveal just how staggering the effects can be.=

Today’s IT teams are facing a greater demand for services than ever before, and often doing so with increasingly limited resources. This inevitably leads to one of the most common yet challenging decisions corporate IT leaders must face throughout their career: should we keep this in-house, or should we outsource it? Understanding the nuances of the MSP vs internal IT debate is the first step to making an informed choice for your business.

One service can’t connect to another (or can’t establish a database connection) – underneath this simple definition, there can be two very different conditions. First – we may have a service process down. In this case, the Kernel stack is operational, so we are getting the packet back, indicating the connection was refused. Second – when network flow is completely disrupted due to connectivity issues, firewall, or a node being completely down.

Monitoring network traffic (which is defined as the data moving across your network at a given time) is important for any business looking to maintain a fast and efficient network. Automating network traffic monitoring and analysis with the support of a tool can help IT teams reduce downtime, identify the causes of bottlenecks, boost the efficiency of troubleshooting efforts, and more.

I was just asked how to troubleshoot an HTTP Error 500.19 - Internal Server Error when trying to launch an ASP.NET Core website on IIS. I have seen this error too many times for both ASP.NET and ASP.NET Core so decided to write a blog post about at least one, obvious, fix. The problem happens when deploying the ASP.NET or ASP.NET Core website to IIS and getting the following error message in the browser.