Operations | Monitoring | ITSM | DevOps | Cloud

As part of our big deploy that added ping and TCP monitoring, we’ve also shipped a small, but often requested feature: you can now choose the frequency of the check we run. By default, we check your website for uptime every minute. The Lighthouse check runs daily. Using our new feature, you can now, for instance, choose that the uptime check should run every 2 minutes, and the Lighthouse check every 5 days. You can choose the frequency at the settings of the check.

API gateways are often viewed as the centralized entry point for client HTTP requests in a distributed system. They act as intermediaries between clients and backend services, managing API request routing, load balancing, rate limiting, access control, and traffic shaping across multiple backend services. This API management is vital for many services and products, but many organizations can put too much stock in it.

Snowflake’s scalable architecture, minimal latency, advanced analytics, simplified data handling, flexible pay-as-you-go model, and always-on security make the data cloud a top choice for many businesses. You can also purchase Snowflake resources on demand or upfront. But if you struggle to control your Snowflake costs, you’re not alone. With the help of this guide, you’ll know how to manage your Snowflake costs better.

Every week, we hear about new AI breakthroughs. AI models write code, create videos, or analyze data in ways we couldn’t imagine just months ago. But there’s a gap: While most companies have adopted AI tools, the majority of employees still don’t use AI in their everyday work. As a manager, you see AI’s potential to change how your team works. Yet your employees struggle to figure out how AI fits into their daily tasks.

What if your Node.js application suddenly froze during peak hours? Imagine thousands of users trying to log in, make payments, or send messages; instead, they’re stuck waiting. Every second feels like a countdown to frustration, churn, and bad reviews. The truth is, Node.js is powerful but unforgiving. It runs on a single-threaded event loop, meaning just one poorly optimized task or slow dependency can bottleneck your entire app. When performance slips, it affects every customer simultaneously.

Modern applications rely heavily on external services to function properly. From payment processors to CDN providers, these external dependencies can significantly impact your ability to meet Service Level Agreements. Understanding how external dependencies affect SLAs is crucial for maintaining reliable services and managing customer expectations.

Microservices architecture offers tremendous benefits for scalability and flexibility, but it also introduces new failure modes that can quickly spiral out of control. When one service fails in a distributed system, the impact can cascade across services like dominoes falling, creating widespread outages that affect your entire application. Understanding how these cascading failures occur and implementing the right defensive patterns is crucial for building resilient microservices.

With Apple’s OS 26 release, IT admins using Apple Business Manager (ABM) or Apple School Manager (ASM) have a great new tool in their toolbelt: device migration. This makes switching devices between MDM platforms much easier, with minimal disruption for end users. Here, we’ll unpack what you need to know, and how ABM device migration makes it incredibly easy to switch to Ivanti Neurons for MDM.

When a website goes down, the failure often feels like a black box. Visitors see a spinning wheel, a cryptic error code, or a blank page. For the people responsible for keeping that site online, the first question is always the same: what broke? The truth is that there is no single way a website “goes down.” Instead, a request from a browser passes through multiple steps—DNS resolution, TCP connection, TLS negotiation, and HTTP response. Each step depends on the ones before it.

The great return to the office is in full swing, but the office doesn't look like it used to. Today's enterprise is a fluid entity, with employees collaborating across home offices, corporate headquarters, and geographically dispersed branch locations. This has elevated the branch office from a simple satellite to a critical hub of productivity and innovation.