[uberparamedic]

I was 2 blocks from home after a drop off, so I went offline to save myself from wasting 18 minutes driving for $2.68. Anyway, I saw surge came on at 1.5 so I went online and after 10 seconds got a hit. I accepted.

After the ride there was no surge attached to the fare. Any ideas why this may be?

Thanks!

 

[oscardelta]

Because Uber is -- as far has the drivers are concerned -- a scam. Go ahead and complain. They'll come up with all kinds of exotic reasons as to why your ride wasn't really a surge ride. You'll see.

 

[Deric]

Driver app lags, so while it may have shown surge, on PAX app it was non surge

 

[Tedgey]

I was 2 blocks from home after a drop off, so I went offline to save myself from wasting 18 minutes driving for $2.68. Anyway, I saw surge came on at 1.5 so I went online and after 10 seconds got a hit. I accepted.

After the ride there was no surge attached to the fare. Any ideas why this may be?

Thanks!

First of all, welcome to the forum. As some have pointed out, we always benefit from a fresh perspective.

When a passenger requests a ride during a surge they get a warning message and they're asked to acknowledge they're paying a higher price. They're also given the option of notify me when the surge ends.

Our partner app is delayed by between a few seconds and I'm guessing here but 45 seconds or so in updating the surge price. So if a passenger opts for the notify me when surge ends option it will often time appear to the driver as if they've been pinged from a surge zone but not gotten the surge price. It's because your app hasn't updated the surge information yet.

 

[uberparamedic]

I'd agree with that. But the pax said his app had no drivers in the area, then I popped online after 5 mins+ of waiting.

 

[Just Another Uber Drive]

Driver app lags, so while it may have shown surge, on PAX app it was non surge

Yup. And this can be a lag of several minutes at times.

 

[Tedgey]

I'd agree with that. But the pax said his app had no drivers in the area, then I popped online after 5 mins+ of waiting.

You may have got fubered too. Or possibly even screwbered

 

[Just Another Uber Drive]

I'd agree with that. But the pax said his app had no drivers in the area, then I popped online after 5 mins+ of waiting.

When it surged more drivers went online. A lot can happen in a few seconds.

 

[UberReallySucks]

I was 2 blocks from home after a drop off, so I went offline to save myself from wasting 18 minutes driving for $2.68. Anyway, I saw surge came on at 1.5 so I went online and after 10 seconds got a hit. I accepted.

After the ride there was no surge attached to the fare. Any ideas why this may be?

Thanks!

What's more important is did you see the surge symbol and multiplier on the request you accepted? Just because you happen to be in a surging area doesn't necessarily mean you got a surging request.

 

[Tedgey]

It's for that reason I always wear a condom or two when driving

 

[LA Dispatcher]

It's for that reason I always wear a condom or two when driving

Good idea considering the bullseye on the new decal.

 

[Los Angeles driver]

It's for that reason I always wear a condom or two when driving

How, exactly, does a duck wear a condom? Do you put it on your beak?

 

[DudeCity]

That's the time the duck becomes a

Buck.........

 

[Tedgey]

Maybe this will help explain a few things

 

[ubermonkey]

you can always check if the ride is a surge ride or not in the waybill section