SF Transit Pulse

Know what to take. Know why.

Live Muni reliability and explainable journey recommendations.

—live vehicles matched to a route
—directions with possible longer waits

Beyond a single ETA

See what an ETA alone can miss.

01

Direction health

Check each direction separately for uneven spacing and longer waits.

02

Can you catch the transfer?

See the expected connection buffer when two concrete trips are available.

03

Why this route?

Open the evidence only when you want to understand the recommendation.

Illustrative example · A useful tradeoff

Fastest isn't always the easiest trip.

FASTEST28 min

8 min walk · 1 transfer · Watch

+3 min

Less walking. No transfer. Steadier service.

Muni right now

Check your route before you go.

Show on map
All vehicles with current locations

Routes needing attention

Each direction can run differently, so we check them separately.

What may affect your ride

See service and street updates together.

A street event near a route may affect service, but it does not prove what caused a delay.

Open updates +

Muni service updates

Nearby street work

Plan your trip

Where do you want to go?

Search for a Muni stop, San Francisco address, or landmark. We'll connect places to a nearby stop and compare the routes you can take now.

Latest predictions + on-device planning · Public Beta

Start from where you are

Find Muni stops near you

Choose a distance, then allow location access. We'll show every Muni stop inside that range and the routes you can take there.

Your location is used only on this page to calculate distance. It is not uploaded or saved.

Select “Find nearby stops” when you're ready to share your location with this page.

For an address or landmark, we use its nearest Muni stop. The walk to that stop is shown before you compare routes and is not included in the transit ETA.

More travel info

Other things that may affect your trip.

01

Old data doesn't stay “live.”

Checking…

Every source publishes freshness and failure state instead of silently substituting stale data.

02

Historical incident context

Loading…

Read what this can—and cannot—tell you

Historical records only compare past conditions across areas. They do not predict crime or label a place safe or unsafe.

03

Recent parking activity

Loading…

Recent paid-session activity is compared with the feed's own timestamp.

How we build each result

What we check before recommending a trip.

SF Transit Pulse answers one practical question: What should I take right now, and why?

We only say what the available data supports.

  1. 1
    Collect current updates

    Check vehicle locations, arrival estimates, service notices, route paths, and when each source was updated.

  2. 2
    Check each route direction

    Look for steady vehicle spacing, vehicles too close together, long waits, and limited live data in each direction.

  3. 3
    Build trips you may be able to make

    Compare direct and one-transfer trips. When complete live predictions are available, check whether two specific trips connect; otherwise label the time as an estimate.

  4. 4
    Compare what matters to you

    Fastest favors transit time. Balanced weighs time, steady service, walking, transfers, and only large historical differences. Historical context gives those past differences more weight.

  5. 5
    Explain the recommendation

    Show why one route ranks first, what the other options offer, and where the data is limited.

Important limits

  • Historical incident data cannot tell whether you will be safe.
  • A nearby street event does not prove what caused a transit delay.
  • No live update does not mean a route has stopped running.
  • A comparison score is not an arrival time.
  • Live predictions can change, so a possible transfer is not guaranteed.