Discussion in 'Complaints' started by Derec, Aug 11, 2018.
Never seen this in 8.5 months of driving. Acceptance 79% cancellation 11%
Happened to me yesterday. 45+ ride was 25 min.
They calculate the time based on congestion, not only on distance. So if the traffic jam was cleared before you got there you simply avoided losing time on congestion.
Or, it’s Uber being Uber...
Mine was at 1am so it was def Uber playing Ubergames
It's possible the pax changed the destination after the ping.
Personally I think it is a bug. I had a 45+ ping this week. Once I started the trip it was only 18 minutes. This was at night and no traffic.
For me it was likely a glitch or games.. it was a regular pax who goes home the same way nightly from her job. Not some airport pax, wise to the ways of bullpen potatoes.
Negative Reg, I t’s happened to me 5 times! Definitely an Uber glitch! First time pulled me out of a rare surge area! Never would’ve accepted the non surge ride without the 45+. Not too mention a tipped off my take on the way and paid way too much for fuel!
Yea its been happening since past weekend. 45+ really means 25+ now. Which is not terrible but I wish they would differentiate it and be accurate.
For those of you who have been getting this new twist on things, how long is it from ping to drop off? I'm wondering if Uber is giving you an estimate of the total amount of time that you will spend driving to the Pax and then taking them on their trip.
Happened to me twice Friday between 11-12
Nah definitely not. At most a combined time would have been 35 minutes.
3 times yesterday, twice today.. ranged from 15-25 minutes.. pick up locations were all fairly close... Anychance they’re testing a function like estimate ride time from Lyft platinum but making a mess outta it so far??
You got the "making a mess outta it" part right. But I seriously doubt they will ever give us any meaningful indication of ride time. Those short trips would never get picked up.
I got a 45+ ping tonight but it was probably a pax screw up. Came from the bar district right at bar close time with a 1.8X surge. I accepted but then got an error message. My guess is the error message was probably because they canceled right about the same time I accepted.
Bar close, surge and 45+ means they probably wanted to go to Denny's or something but put in the wrong city.
Mine was only a few minutes to pickup.
Two nights ago I literally got this three times in a row on stacked rides. Got the first 45+ ping... got there and it was a 14 minute ride. Before I dropped that one off I got another 45+ ping and that one was 16 minutes. Got a third 45+ ping as I was about to drop off the second rider and that one was 14 minutes.
Like the others, this was around midnight and there was no traffic or anything to speak of. They were all picked up and going to very different areas, so it wasn’t an accident or something that had gotten cleared up along the way.
Happened to me yesterday. 45 min ping only 18 mins
Sf has outside lands going on, they probably changes the algorithm to less with us during it.
Trip was 4 minutes
Happened to me yesterday twice as well.. It looks they changed the algorithm without changing the screen display
Separate names with a comma.