Robocall Mitigation Progress Under STIR/SHAKEN Shows Mixed Results

STIR/SHAKEN was introduced to curb caller ID spoofing by enabling carriers to verify the identity of the calling party across IP-based networks. The framework adds a cryptographic signature to calls, signaling whether the origin can be validated. Early data points to meaningful reductions in certain types of spoofing, especially on domestic IP-to-IP traffic. Yet robocalls have adapted. International ingress, non-IP segments, and inconsistent analytics mean many people still see suspicious calls, while some legitimate calls face mislabeling or blocking. The result is measurable progress, tempered by operational gaps and uneven adoption.

STIR/SHAKEN tech solutions: what works?

The core tech solutions hinge on authenticated caller identity in SIP headers, supported by certificate authorities and attestation levels (A, B, C) to convey trust in the caller’s number. When both originating and terminating networks are IP-enabled and fully integrated with SHAKEN, spoofing becomes harder and traceback improves. This has helped limit some impersonation scams and improved accountability for originating providers. However, coverage gaps appear when calls traverse TDM interconnects or originate from non-compliant networks, where identity information may be stripped or never applied, reducing the effectiveness end-to-end.

Role of digital devices in call authentication

Digital devices display the outcome of network-level decisions. Phones surface labels like “Verified,” “Spam Likely,” or branded caller details when supported by carriers and analytics partners. Device experience varies: some handsets and apps show rich call data, while others provide minimal indicators. This inconsistency can confuse users, and false positives—where legitimate businesses are labeled as spam—undermine answer rates. Improving handset UX, aligning labeling conventions, and enabling secure enterprise verification can help devices convey clearer, more actionable signals to end users.

Online connectivity and call routing impacts

Online connectivity underpins STIR/SHAKEN’s reach. As voice traffic continues moving from legacy TDM to all-IP routing, authenticated identity persists across more hops. The toughest challenges occur at international gateways and mixed environments, where identity headers can be lost or untrusted. Smaller or non-domestic providers may not sign calls consistently, creating openings for abuse. Strengthening gateway vetting, expanding IP interconnects, and accelerating non-IP call authentication solutions are central to closing these loopholes and preserving verified identity across complex routes.

How the electronics industry supports standards

Across the electronics industry, handset makers, network equipment vendors, and enterprise telephony platforms play a role in end-to-end trust. Modern SBCs and softswitches can preserve identity headers, while PBX and contact center systems are increasingly able to originate signed calls via vetted carriers. Rich Call Data—when supported—lets enterprises present verified names or logos, reducing consumer doubt. Hardware and firmware must reliably pass authentication data without stripping headers, and enterprise systems need governance controls to ensure only authorized numbers and brands are used, maintaining a trustworthy ecosystem.

What internet services are doing next

Providers of internet services and analytics are layering risk models on top of STIR/SHAKEN to reduce robocalls that still bypass authentication. These models look at call volumes, velocity, answer patterns, and reputation signals to flag suspicious traffic. Enterprise-focused solutions aim to secure outbound campaigns with verification, consistent caller display, and feedback loops that correct mislabeling. Expect continued work on delegate certificates, enterprise attestation programs, and standardized branded calling so that legitimate organizations can be recognized more reliably, while malicious actors face more friction.

Key players and services currently shaping the landscape include major carriers and analytics vendors that operationalize authentication, labeling, and branded calling.

Mixed results, measurable lessons

The evidence to date suggests STIR/SHAKEN is necessary but not sufficient. It sharply reduces some domestic spoofing when networks are IP and compliant, yet determined robocallers exploit non-IP gaps and weakly vetted pathways. Analytics, branded calling, and enterprise verification help filter malicious traffic and protect answer rates, but they must be consistent across carriers, devices, and vendors. Continued expansion of IP interconnects, stronger gateway oversight, and standardized enterprise attestation are likely to deliver steadier gains. Progress is real, but closing ecosystem gaps remains the decisive next step.