Keysight Technologies expanded the company's KeysightCare program to provide a growing customer base with fast, reliable access to priority technical support.
KeysightCare is a scalable and comprehensive support model offering test and measurement expertise through a dedicated, proactive single point of contact for instruments, software, application measurements and test. This integrated support model is now available with five tiers to meet the specific hardware, software and technical support needs of customers.
The newest offering in the KeysightCare portfolio is KeysightCare Technical Support, tailored to cover all Keysight instruments at a customer site, regardless of performance level, use model, warranty period or discontinuance status. Since November 2018, classic KeysightCare Assured is included with the majority of newly delivered Keysight instruments and software. However, customers still operate previously acquired equipment in R&D and manufacturing test setups, which require fast predictable access to technical support experts.
KeysightCare Technical Support provides for committed response time from a live technical support expert, as well as access to technical expertise through the KeysightCare portal and a knowledge center 24x7, which contains decades of R&D expertise in thousands of technical articles and programming examples on leading edge technologies.
"Our customers demand faster access to technical support when challenges arise in operating test and measurement instruments and software," said Ted Burns, Global Director of KeysightCare. "Since Keysight implemented KeysightCare in 2018, we've been able to improve committed response times by 50 percent, while continuing to invest in our global support infrastructure, empowering our customers to mitigate project risk and get products to market faster. KeysightCare helps customers remove barriers to success through a committed, accessible, and proactive engagement with our measurement experts."
KeysightCare is offered in five service levels:
- NEW KeysightCare Technical Support – This entry level technical support offering, removes technical barriers with less than two business days committed response time by technical support and application engineers.
This level is tailored to cover all Keysight instruments at a customer site, regardless of performance level, use model, warranty period, or discontinuance status.
- KeysightCare Assured Delivers Fast Support – This level offers committed four-business-hour technical response, repair coverage with ten-business-day repair turnaround time, and proactive firmware notifications.
- KeysightCare Enhanced Delivers Priority Support – This level offers committed two-business hour technical response, repair coverage with seven-business-day repair turnaround time, calibration coverage with five-business-day turnaround time, and proactive firmware notifications.
- KeysightCare Performance Delivers Enterprise Support – This level offers committed two-clock hour technical response, repair coverage with five-business-day turnaround time, calibration coverage with three-business-day turnaround time, proactive firmware notifications, and 24x7 emergency response
- KeysightCare Software – This level delivers subscription support and protects software investment with flexible licensing options to maintain budget control and balance project's requirements. Software remains always current with the latest enhancements and measurement standards
The Latest
Pilots are everywhere, stakeholders are seeking results, businesses are pushing for new tools, and IT teams are being asked to make AI secure, reliable, and useful at scale. But as organizations move from testing AI to operationalizing it, many are discovering that the biggest barrier is not the model, the use case, or even the budget. It is the file data foundation within ...
Fast or cheap? For most of my career in engineering, speed and quality sat on opposite ends of a seesaw. The "OR" in "fast or cheap" was non-negotiable. It was expected that pushing for faster releases meant that something in quality would give way. Tightening quality controls meant the schedule slipped. Every engineering leader I know has lived some version of that tradeoff ... The seesaw is starting to level out ...
I have been building enterprise software for more than 20 years ... One thing stays true across all of it: You do not find out your foundation is wrong during the crisis. You find out when the debt comes due. For a lot of organizations, that bill is arriving now. New research ... puts hard numbers on something practitioners have been sensing for a while. The telemetry problem isn't coming. It's already here ...
The rapid growth of AI workloads is pushing traditional log management approaches to their limits, according to The State of Log Management 2026 report from Dynatrace. Modern logs have become critical to understanding, validating, and securing AI-driven decisions, helping organizations ensure reliability, compliance, and performance at scale. However, the volume and complexity of AI telemetry are overwhelming legacy tools ...
For years, secure connectivity has relied on a familiar pattern: route traffic back to centralized gateways, inspect it, and then allow access. This model worked when applications lived in a handful of data centers and users were largely confined to offices. That model is now under strain. Applications are distributed across clouds, users connect from everywhere, and real-time workloads demand performance that centralized inspection points struggle to deliver. As traffic volumes grow and latency expectations shrink, routing everything through a small number of control points has become both a performance bottleneck and a resilience risk. The future of secure connectivity requires a different approach ...
The AI experimentation phase is over, and the private cloud is where enterprise AI workloads are being deployed for security and scale, according to Private Cloud Outlook 2026, a new report from Broadcom ... 2026 marks an acceleration into a full AI tipping point. The shift is being shaped by three forces — costs, complexity, and control — that public cloud environments are increasingly failing to address for production AI at scale. Key findings from the report include ...
44% of organizations have reported an outage in the past year tied to suppressed or ignored alerts, and 78% had at least one incident where no alert was fired at all ... Engineers learned about failures from customers. That gap between what our tools report and what our customers experience is the problem DevOps teams have been quietly solving with GenAI tooling, even as most enterprises continue to run their NOCs on manual alert triage ...
Cloud outages are usually described as technical failures. When a service goes down, a dependency breaks, or a region has issues, the focus immediately shifts to infrastructure. But if you look closely at how these incidents actually unfold, the root cause is rarely the technology itself. It is almost always tied to decisions made earlier, during design, implementation, or day-to-day operations. The system behaves the way it was built. The real question is how it was built ...
77% of leaders say their teams need AI skills urgently. 64% say their organization plans to train current employees rather than hire new ones. So far, so reasonable. The part that surprised me is who's been put in charge: 34% of those leaders say IT and engineering own the AI skills mandate. Learning and Development or HR own it at 7% of organizations. That's roughly five-to-one in favor of the people who understand the tools, over the people whose actual job is teaching adults how to learn new ones ...
In the ever-evolving digital landscape, enterprises are increasingly focused on enhancing their observability stacks to gain deeper insights into their IT environments. Observability has become a cornerstone of modern IT operations, enabling organizations to monitor, diagnose, and optimize their systems with unprecedented precision. However, a critical piece of the puzzle often goes unnoticed in this transformation: IBM i ...