Refresh the Page and Wait For It To Finish Loading
Update your Browser if you're not using the latest version.
Be sure your browser is not blocking dialog boxes for this Site, otherwise requests requiring comfirmation may not execute.
Still no luck? Delete the cookies and cached files for this Site.
If you still can't get it working, submit below with your browser version and we'll take a look.
Try these patterns:
- From [address] To [address] (for trip plan)
- [line/route name] (for schedules, etc.)
- [address] (for nearby stops)
- Agency name (for lines and contact info)
Use complete addresses with State or Region abbreviation.
Schedule times are based on official data published by the transit agency. It is up to the agency to follow best practices so dates and timetables match print publications (it's a learning curve so be patient).
If times for a given day are fragmented across schedules (sloppy data publication), usually each time in each schedule is correct.
Updates are typically displayed within one hour of publication, but if load is high and backup servers are in use processing may be delayed.
Route maps are based on the trip with the most stops. Stops not on that trip appear last (maybe out of sequence) on timetables.
For some transit providers, Holiday schedules may actually be some other regular schedule, such as Weekend or Sunday, but appear listed by Holiday name.
Only schedules in recent publications are listed.
Some lines, such as seasonal or temporary lines, may be discontinued or renamed.
When a line is removed from recent publications, it is deactivated. If it's included in a later publication, it's reactivated and appears with new schedules.
If a line you know has current service and is not listed, notify the transit agency and request the schedule be included in their data publication.
For information about upcoming schedules, you must contact the transit agency.
Note: Support for data outside North America and Oceania is pending completion of locale neutral features. Please be patient. We apologize for the delay.
We've upgraded our intermediate certificates to new standard encryption levels.
Restart your device for Site certificates to reload.
If that doesn't work, you are using a very old browser.
Update your browser.
This is a frustrating issue to encounter and we apologize for the inconvenience.
We don't expect future upgrades will be needed for many years to come.
The schedule is probably the same but an internal identifier has changed.
When an identifier changes and the route cannot be resolved in previous data, a new record is created and the number changes.
Times are still correct and usually for the same route. However, the name may have changed slightly.
The transit provider may not yet provide the service or we haven't implemented it yet.
Please be patient.
If you cannot locate real-time or alert information anywhere, convey your support for the service to your transit provider.
Holiday schedules may or may not be a Weekend, Sunday or other regular schedule.
Current formats do not assign familiar names to schedules. We do so for your convenience when it's obvious.
To see if a Holiday schedule is another regular schedule, you'll have to check the times.
The Server thinks it's being abused.
This can happen for legitimate requests, though very rarely.
Most of the time, waiting a few moments before trying again will solve the problem.
If you are prevented from using the service, tell us.
We apologize for the inconvenience.
Updates are underway.
Please be patient. It won't be long until it starts working again.
You may see new features.
Our top priority is keeping your experience consistent and delightful.
We apologize for the inconvenience.
See the developers page for best practice requirements.
Feedback from transit providers is always welcome and goes straight to the developer! We value your opinions and suggestions.
Note: If you publish for use outside North America or Oceania, support is expected following completion of locale neutral services. Once your locale is supported, full feature support is planned.
If you are planning real-time services, see the developers page to speed support for your service.
submit 0 4c3f7bqput1tfkru9g814soi97 5d0533fb926722ff2909a822d51155ef en-us hlp_
Please remember to include your email address if a reply is needed.