Driver Had Account Deactivated on Uber on the Paulista Coast After 4,421 Refusals and 769 Cancellations in a Month, with Direct Impact on Service Predictability
4,421 refusals in a month became the breaking point within the app’s operation. A driver had their account deactivated on Uber after a pattern of rejection and cancellation considered abnormal.
In the final period before the block, in addition to the refusals, they canceled 769 accepted rides. In app logistics, this kind of behavior weighs on response time and service stability.
Refusal Pattern Reached 4,421 in the Last Month
The sequence of rejections alters the distribution of calls and forces the platform to recalculate availability. This increases friction for those requesting rides and pressures the network when demand rises.
-
A large part of the Netherlands lies below sea level and remains dry only because an invisible machine of dikes, pumps, and giant gates works nonstop, a system born from the tragedy of 1953, when the North Sea invaded the country and killed 1,836 people.
-
The largest bridge in Finland has just been inaugurated and cars simply cannot pass on it; only trams, bicycles, and pedestrians are allowed to cross the 1.2 km giant with a 135-meter pillar over the Baltic Sea.
-
Larger than Belgium and nestled at the mouth of the Amazon, Marajó Island is a giant that Brazil has forgotten, surrounded by water and energy on all sides, yet still isolated, poor, and dependent on diesel brought by barge.
-
Weighing as much as nine nuclear aircraft carriers, the Pioneering Spirit is the largest ship ever built and was made for a single task that no other machine in the world can accomplish: removing entire oil platforms from the seabed of the North Sea in one go.
With 4,421 rejected rides, the volume becomes an operational factor, as it reduces the predictability of service in areas with lower supply.
Cancellations After Accepting Totaled 769 and Affected Wait Time
Cancellation after acceptance usually generates a greater impact because the passenger has already entered the service flow. The immediate result is prolonged wait and the need for new allocation.
In this case, there were 769 cancellations in the same timeframe, reinforcing a pattern that tends to be interpreted as improper use of the acceptance tool.
Driver Claimed Lack of Notice and Cited R$ 28 thousand
The driver reported that the account was blocked without prior notice and said that the justification received was “excessive cancellation rate,” without further detail.
They sought to return to the app and requested payment of R$ 28 thousand, but the account remained deactivated.
Platform Stated Three Warnings Before the Block
Uber informed that the deactivation occurred due to violation of policies and internal rules. It also stated that, over the course of a month, it sent three communications regarding the conduct via email, in-app message, and push notification.
According to ConJur, a Brazilian site for legal news and analysis, it was recorded that there was no evidence of failure in sending, as the platform’s operation automates this type of notification.
“Security” Justification Appeared and Did Not Change the Outcome
The driver acknowledged canceling rides “for security reasons.” Still, the app’s rules provide consequences when cancellations are repeated excessively.
For the operational logic, the priority is to protect the flow of service and reduce efficiency loss in the system.
The case reinforces that extreme numbers of refusals and cancellations can lead to permanent account blocking. For those relying on the app, the practical effect is clear: the platform tends to act when service predictability begins to decline.
At the user end, this tightens control over operational behavior and increases pressure for stability in app-based transport, altering the strategic outlook of the sector.

Be the first to react!