I hate slow websites. They are annoying to use and frustrating to work on. But what does it mean to be “slow”? It used to be waiting for document load. Then waiting for page ready. But with so many asynchronous patterns in use today, how do we even define what “slow” is? The W3C has been working on this with the new Event Timing and Element Timing API, and has defined some new Web Vital metrics to describe the different ways that slow performance can impact a webpage.

On Monday September 28 a multi-hour global Microsoft 365 outage brought down Teams, Office 365 and Outlook leaving many people disconnected. While Microsoft outages are rare, there are a range of possible issues on your network and in your user’s environment that can cause service issues at any time. Knowing quickly when these are happening, and what’s causing them is key to keeping users productive on Microsoft 365.

Legacy generations of networks have predominately provided services with best-effort delivery. While this has worked for voice, text and best- effort broadband services, end users are hampered with buffering, delays, and drops as the demand for feature-rich services continues to grow.

According to a report by Google, mobile users abandon webpages if the load time is more than three seconds. In other words, even a fractionally slower website will lead to a bad user experience and increased bounce rates. Today’s users are more demanding and expect near-instantaneous load times and seamless experiences. If you can’t meet their expectations, they’ll find other websites or applications capable of providing a better experience.

In just 24 hours, tech bloggers and news sites everywhere have been sharing Ivanti's latest acquisition announcement. The news has been picked up by several publications including Redmond Magazine, MarketWatch, TechTarget, WSJ Pro Cybersecurity, and Channel Futures. And while we're delighted to be picked up by so many publications (seriously, we feel like the popular kid at school!), we're glad you've found yourself here on the Ivanti blog!

For today’s tech tip, we’re going to focus on our Endpoint Monitoring Client and two specific use cases: Wi-Fi and application health. With so much of the workforce working remotely, Endpoint Monitoring is an essential tool to help smooth the transition. According to recent research from Gartner, nearly half of US employees will continue to work remotely for at least some of the time post-pandemic.

The whole internet spins across different domains but when we talk about the backbone suite of every organization, MS Office 365, is for sure, one of the biggest contenders. Just like the recent Century Link/Lumen outage, we witnessed another major outage, this time Microsoft O365. This month might as well be considered a bad month for the internet, as we have seen a lot of daily used consumer services getting impacted like Reddit, Pinterest, Google Services, etc.

Another PagerDuty Summit is in the books, and we’re still coming down from the excitement and energy our customers and community showed us over the past week. We made several big announcements over the course of the conference, but none more significant than the AIOps advancements on our digital operations platform. We introduced a number of ways customers can apply machine learning algorithms and automation to a wide range of workflows across the platform.

In today’s IT’s landscape, a variety of tools are available to us to help with root cause analysis process. Leveraging your tools and using them optimally is necessary to any system but it’s important to remember that tools do not have access to all the information available for them to be able to truly solve every problem So to truly get to the true root cause, you need a process that will take us beyond the scope of tools.

Intelligent Medical Objects (IMO) and its clinical interface terminology form the foundation healthcare enterprises need, including effective management of Electronic Health Record (EMR) problem lists and accurate documentation. Over 4,500 hospitals and 500,000 physicians use IMO products on a daily basis. With Honeycomb, the engineering team at IMO was able to find hidden architectural issues that were previously obscured in their logs.