Operations | Monitoring | ITSM | DevOps | Cloud

Progress Wins at the Network Computing Awards

Progress has been named a winner at this year's Network Computing Awards, earning industry recognition for its ongoing commitment to innovation and delivering real-world value to customers. A standout event in the UK technology calendar, the Network Computing Awards celebrate organizations and solutions that are driving measurable impact across the industry.

TikTok Challenges: Trend or Danger? What Every Parent and Teen Should Know

Everyone seems to be doing TikTok challenges—but are they always harmless? From positive movements like the Ice Bucket Challenge to risky viral trends that have led to serious injuries, social media challenges can influence how teens think, behave, and seek attention online In this video, we'll explore: 0:00 Why teens are drawn to TikTok challenges & The hidden pressure of fitting in and going viral.

From Tee Time to Uptime: A True Cyber Resilience Story

In this 90-second customer case study, Mehdi Salehi from Golfbreaks shares the operational and security gains his team saw with N-central. Highlights include about 20% annual cost savings, around 20 minutes saved per end-user support session, a 90% increase in third-party patch coverage, and about 70% improvement in server OS update coverage. Watch the short video to see how automation and a central pane of glass helped reduce the burden on the team and deliver greater peace of mind.

Field Service Costs and Your P&L: How Search Time Quietly Drains Both

At least 30 minutes disappear before the average field technician can begin the actual repair. That time goes into searching for part numbers, procedures, and documentation across fragmented systems. Across 1,000 technicians and 250 working days, even this conservative estimate adds up to at least 125,000 hours of productive capacity lost to lookup activity. Yet this loss rarely appears as a separate line item on any field service P&L. This is a critical information architecture problem.

Enforce your team's database standards automatically with Custom Policy Checks in Redgate Flyway Enterprise

Every engineering team has a list of “things we don’t do”. No TRUNCATE TABLE in production. Every audit table must end in _audit. Foreign keys follow a naming convention. But until now, enforcing those standards has meant relying on pull request checklists, tribal knowledge, or a separate linting tool bolted onto the pipeline.

11 Incident Management Best Practices Every IT Team Should Follow

A well-defined incident management process can mean the difference between a minor disruption and a major business outage. When critical services fail, every minute of downtime matters. Yet many IT teams still face challenges such as unclear ownership, poor prioritization, communication gaps, alert fatigue, and manual processes that delay resolution. The result is longer outages, missed SLAs, and frustrated users.

[Webinar] Building Regulated Infrastructure: How Lucis Standardized Security for Global Care

In Healthtech, downtime is more than a loss of revenue, it is a disruption to patient care. Whether supporting digital health platforms or AI-driven healthcare applications, infrastructure must remain secure, compliant, and highly available. Join Lucis and Qovery for a technical breakdown of building compliant and secure infrastructure that scales AI and healthcare workloads, handles traffic peaks, and maintains SOC 2, HDS, and HIPAA standards.

Beyond tokens per watt - using Ubuntu 26.04 LTS for AI

Tokens per watt (TpW) – the measure of useful AI work produced per watt of energy consumed – is the metric at top of mind for CEOs, heads of AI, and infrastructure teams alike. With the tremendous cost of GPU clusters, extracting as much value as possible from the expense is critical. But in the pursuit of tokens, it’s important to remember that hardware efficiency isn’t the only factor influencing data center operating costs, or the output of useful, revenue-generating AI work.

Turning Disconnected Alerts into Actionable Insights

The previous post in this series focused on shared context and why hybrid operations depend on a connected view across cloud, network, and infrastructure. Once that context is in place, the operational benefits become easier to see—especially during incident response, where signal volume and fragmented tooling can slow teams down. Alert noise remains one of the most persistent challenges in hybrid environments. Every layer of the stack can generate its own warnings, anomalies, and service events.