Curb Mobile Proxies: NYC Taxi App Testing on a Carrier Line

Curb is the app that hails New York's yellow and green cabs, and it lives or dies on the phone network it runs over. A hail that stalls on a weak Verizon signal in Midtown is a lost ride. Fleet owners, taxi technology vendors, researchers comparing fare estimates and developers testing the app need a real New York carrier connection to test against. Our lines are real carrier connections in the city.

What Curb does with location and network

Curb uses the phone's location to place the pickup pin and the address to confirm the market. From a New York carrier address with the location set in the city, you get New York fares, the local fleet, and local promotions. The app also depends on a reliable connection for the hail, the driver match and the in-app payment; the behaviour of that flow on Verizon versus AT&T versus T-Mobile in the city is a real engineering question that lab Wi-Fi cannot answer.

Honest reasons to use a New York line

A fleet operator checking what passengers see when they request a cab near its garage. A vendor testing a Curb integration on real carrier networks before a release. A researcher comparing Curb's fare estimates with other options across neighbourhoods at set times. A developer reproducing a bug that only shows up on a congested carrier network at rush hour, which our lines in Manhattan experience daily. A passenger checking their own ride history and receipts from the city they ride in.

Sticky, and rotation rarely matters

A passenger account stays on a sticky line. Fare estimate checks do not vary by address, so rotation adds nothing; what matters is checking at consistent times. For carrier comparison, use the dashboard's free move to put the plan on a different carrier and rerun the same test.

Keep a simple log: carrier, hour, borough of the line, what you tapped and how long each step took. After a week of that you have a picture of the app on real New York networks that no lab can give you, and the pattern of where it struggles is usually obvious.

• Passenger account: sticky
• Fare checks: consistent times, no rotation needed
• Carrier comparison: move the plan, rerun the test

Taxi app QA on real New York carrier networks

Curb connects riders with yellow and partner taxis in New York and is used mostly from phones on the street, often in places where the signal is busy: outside stations, near arenas, in Midtown at rush hour. Teams building integrations with taxi booking, corporate travel tools that link to it, and QA staff testing ride flows care most about how the app behaves on an ordinary carrier connection in the city.

Route a test phone through a New York line with VLESS and run the flows you are responsible for: opening the app, setting a pickup, viewing the estimate, and payment set-up with a test card if your integration supports it, stopping short of a real request. Try both 4G and 5G and more than one carrier. A flow that is fine on office Wi-Fi and stalls on a busy carrier path is the bug you are looking for.

Real rides are booked by real riders. Do not request taxis you will not take; drivers lose time and money on every phantom request.

Log what you test with the carrier, the network type and the time. When a fix ships, rerun the same flow on the same line and compare. A bug report that says the estimate screen stalled on 4G at a given time and place is something an engineer can reproduce; a report that says it felt slow is not.

The rules

No fake hails, no automated requests, no promotion stacking across accounts. Curb's terms are clear and so is the law around taxi dispatch. Our lines are for testing and research on a real New York network and for your own account.

Setting up a Curb proxy on New York Proxies

1. Order a New York line on the carrier you want to test; 5G at $6 a day for latency work.
2. Run Curb on an Android phone plan or your own phone through the VLESS tunnel, region United States, Eastern time.
3. Open the app and confirm the pickup pin and fares resolve to New York.
4. Walk the estimate and hail flow up to the point of requesting a car; cancel before a driver is matched if you are only testing.
5. Log latency and failures by carrier and hour, especially on the Manhattan line at rush hour.
6. Move the plan to another carrier from the dashboard and repeat the same tests.

Curb proxy questions