Google Messages RCS Support Shift Leaves Millions in Limbo

Google Messages, the default texting app on millions of Android phones, is suddenly failing to deliver on the very feature that set it apart: Rich Communication Services (RCS). Across several regions, users are discovering that they can no longer send or receive RCS messages, leaving them stuck with basic SMS and MMS.

The issue traces back to a quiet but significant change – Google is offloading responsibility for RCS support from its own Jibe platform to individual wireless carriers.

RCS, often referred to as the successor to SMS, allows richer communication: higher-quality media, read receipts, typing indicators, group chat stability, and end-to-end encryption. Google’s Jibe servers had been ensuring this worked smoothly for users worldwide, but with the shift, RCS access now depends entirely on whether a local carrier has chosen to support the standard. Unsurprisingly, the rollout is inconsistent, and many carriers outside the US and Europe appear uninterested in maintaining RCS infrastructure.

Reports highlight that users in countries such as Pakistan, Bangladesh, and Kenya are particularly hard hit. Their local operators either never invested in RCS or have deprioritized it, effectively cutting customers off from features they had grown accustomed to. Complaints flooding online forums show people encountering the frustrating message: “carrier not supported.” The problem surfaced following a recent Google Messages update, suggesting that the company deliberately shifted responsibility without fully preparing users for the fallout.

The situation has sparked confusion because Google has long positioned itself as the main advocate for RCS, even pushing Apple to finally adopt the standard. Handing off the technology to telecom operators marks a sharp departure from that stance. Some carriers blame Google for abandoning its support, while Google representatives insist that the ball is now in the operators’ court. This blame-shifting leaves customers caught in the middle, with no clear resolution in sight.

Adding to user frustration, the limitations aren’t confined to emerging markets. Even in the United States, some subscribers have reported sporadic RCS outages. On top of that, modified or rooted phones have been losing RCS compatibility for nearly a year, showing Google is actively narrowing the pool of devices that can reliably access the service. For many, RCS was the single biggest reason to stick with Google Messages instead of third-party apps, and the sudden unreliability undermines that loyalty.

Industry observers note that while it may be logical for telecom carriers to manage their own messaging infrastructure, the reality is that many lack the motivation to do so. Without Google’s direct involvement through Jibe, there is a risk that RCS becomes another stalled technology, available only in select markets rather than a universal upgrade to SMS. Unless Google actively collaborates with carriers to ensure smooth support, millions of Android users may find themselves left behind, relying on outdated texting systems while competitors like Apple lock in their users with seamless alternatives such as iMessage.

Ultimately, the transition signals a critical test for the future of RCS. If carriers embrace it, RCS could still fulfill its promise as a global standard. But if indifference continues, Google’s retreat may have effectively kneecapped its own messaging revolution.