It was a stress test for the industry that afternoon. From around 5:40 pm and building to 7 pm, commuters in major cities were left without a way to book a ride with any of the three. Rapido later put out word that a short-lived technical matter had been resolved and service was back up.
Peak-hour stumbles spotlight reliability race
There is no better currency in ride-hailing than uptime during the peak, and Thursday evening’s glitches made a point of it. The kind of disruption that erodes commuter confidence comes at the worst possible time for platforms vying for demand.
Then there is the matter of Rapido. In publicly owning up to the issue and confirming it was fixed, the company steered the narrative in its favour while its rivals offered nothing in the way of comment.
What users reported across cities
In Bengaluru, Delhi, Chennai, Hyderabad and Kolkata, people said they could not get a ride. Some on Rapido ran into errors with the server or location data. None of the usual fixes like relogging or reinstalling the app would do during the outage.
The trouble was not confined to mobility apps. Food-delivery and quick-commerce users put in complaints too. There are indications Blinkit had trouble with orders, but one cannot say for sure if a single source was behind it all.
Company responses and restoration status
Rapido has confirmed a technical difficulty on its end earlier in the day. Riders may have seen a ‘brief technical issue’ trying to make a booking, the company said, before internal teams sorted it out. An apology was issued and services are restored.
Uber’s public page for August 27 tells a different story, showing no incident despite the noise from users. One will not find a similar admission from Ola in the reports either. Of the three, only Rapido has put a public face on the technical side of things.
To be clear on the position each platform is in:
– Rapido: has put services back after a ‘brief technical issue’.
– Ola: disruptions are being reported by users but there is no confirmation from the company.
– Uber: user reports exist but the status page does not reflect an incident.
What triggered the disruption?
That is still an open question. While some have pointed to Amazon Web Services as a culprit given its role as a cloud backbone for so many consumer apps, neither Ola, Uber nor Rapido has confirmed a common AWS failure was to blame.
One might see the timing across unrelated apps as evidence of shared infrastructure under strain. But without a verified root cause, it is hard to draw a line between them.
What commuters should expect next
Rapido says the books are balanced and riders can expect to go about their business as normal. The whole affair has put a finer point on the need for swift response and open status updates in the rush hour.
As for the platforms, there is a strategic lesson here. Being reliable between 5:40 and 7 pm is more than a technical box to tick; it is what builds brand trust and keeps customers.
