Download websites that use Splunk RUM

About Splunk RUM

Real user monitoring moved measurement out of the data centre and into the browser. Server side instrumentation reports how quickly a response left the origin, but it cannot see the third party script blocking the render, the layout shift on a mid range phone, or the error thrown after the page was already drawn. Splunk RUM is the browser half of that picture, a RUM agent written in JavaScript that reports timings, faults and interactions from the visitor's own device back to the vendor's platform.

The browser half is also the only half anyone outside the company can observe. Back end tracing leaves nothing on a page, so an organisation can be deep into a monitoring platform and remain completely invisible to a crawler. Because the agent ships as JavaScript loaded by the page, this is one of the few pieces of an observability stack a scan can confirm directly, and confirming it implies a good deal more, since front end monitoring is rarely bought from a platform vendor by a team that is not already sending back end telemetry to the same place.

The inference is what makes the signal commercially interesting. A site carrying the agent belongs to an organisation with an existing relationship with Cisco (Splunk), an engineering team large enough to argue about performance budgets, and an observability line in its spending. For anyone selling into that market, or tracking consolidation between monitoring vendors, presence of the agent qualifies an account better than headcount or job postings do.

As of October 2026 we record it on 2 sites, and a product first catalogued in 2021 sitting at that level needs context rather than a headline. Monitoring agents are frequently served from a customer's own domain, injected through a tag manager, or bundled into an application build where the vendor's hostname never appears in the page source, and each of those defeats hostname based fingerprinting. Our number counts confirmed matches and nothing else.

The file answers what a domain lookup cannot. Checking one site tells you whether one company instruments its front end. The matched set, exported with every other technology detected on each host, lets you ask which frameworks the agent is paired with, which delivery networks sit in front of it, and which competing tools appear on the same domains during a migration. Questions like those are about a population, and a population is a file rather than a search box.