About This Service

Avail Technologies delivers real-time transit data for agencies across the country. Live agency data is continuously processed and published as GTFS-Realtime Protocol Buffer messages via HTTP, ready for consumption by any standards-compliant client.

This is built on a cloud-native streaming pipeline architecture that leverages gRPC for high-throughput internal data streaming, Protocol Buffers for compact binary serialization, container-based services for elastic scalability, and OpenTelemetry for end-to-end observability.

The Avail architecture delivers near-real-time data freshness and simultaneous multi-agency processing at scale, with feeds that conform to the GTFS-Realtime spec. Every feed is timestamped and served with standard HTTP caching headers, giving downstream systems explicit control over freshness and re-fetch behavior.

GTFS-RealtimeCloud ArchitectureGoogle Protocol BuffersgRPCOpenTelemetry

Consumer Integration Guide

Each agency below publishes up to three types of GTFS-Realtime feed messages. Expand an agency card to see the ready-to-use endpoint URLs for each feed type. No authentication is required for public feeds.

How to request a feed: Send an HTTP GET to the URL shown in each agency card:

GET /GtfsProtoBuf?FeedLabel={Agency}&FeedType={Type}

The response is a binary GTFS-Realtime Protocol Buffer message (Content-Type: application/x-protobuf). Each feed type serves a distinct purpose:

  • VehiclePositions — Live GPS coordinates and occupancy for active vehicles. Used to animate bus icons on maps in real time.
  • TripUpdates — Arrival and departure time predictions per stop, powering “Next Bus in X minutes” displays and journey planners.
  • ServiceAlerts — Disruption notices, route detours, and rider advisories surfaced as alert banners within consumer apps.

Polling cadence: Feeds are updated as new data arrives from the agency — update frequency is data-driven, not on a fixed-interval. Typical update windows by feed type:

  • Vehicle Positions — sub-second up to every 15 seconds. Based on typical vehicle activity and GPS update rates.
  • Trip Updates — every 5–15 seconds. Based on typical trip patterns and schedule adherence.
  • Service Alerts — every 10–20 seconds. Based on typical service disruption patterns and alert propagation times.

If a feed type has no data or has not received an update within the last 28 seconds, it is automatically republished with a updated header timestamp, so consumers can be confident they are always receiving the most current snapshot — even when that snapshot is empty.

Efficient caching: Each response includes ETag and Last-Modified headers. Send If-None-Match or If-Modified-Since on subsequent requests — the service returns 304 Not Modified when the feed has not changed, saving bandwidth and parse time. On a 304, continue using your previously parsed payload.

Data integrity: Each response is an authoritative, atomic snapshot of all entities for that feed type at the given timestamp. Replace your full local state on every successful fetch — partial updates are never issued.

For complete technical details including HTTP status codes, Protocol Buffer specification, and feed encoding, see the Feed Publishing & Practices page.

Available Agency Feed Sources

IndyGoIndianapolis, IN - INDYGO
Alerts · TripUpdates · VehiclePositions
Feed Type URLs
Alerts:http://gtfs-rt-test.myavail.cloud/GtfsProtoBuf?FeedLabel=IndyGo&FeedType=Alerts
TripUpdates:http://gtfs-rt-test.myavail.cloud/GtfsProtoBuf?FeedLabel=IndyGo&FeedType=TripUpdates
VehiclePositions:http://gtfs-rt-test.myavail.cloud/GtfsProtoBuf?FeedLabel=IndyGo&FeedType=VehiclePositions
Static GTFS:https://realtime.indygo.net/InfoPoint/gtfs-zip.ashx
IndyGo_ModTestIndianapolis, IN - INDYGO w/TripModifications
Alerts · TripUpdates · VehiclePositions
Feed Type URLs
Alerts:http://gtfs-rt-test.myavail.cloud/GtfsProtoBuf?FeedLabel=IndyGo_ModTest&FeedType=Alerts
TripUpdates:http://gtfs-rt-test.myavail.cloud/GtfsProtoBuf?FeedLabel=IndyGo_ModTest&FeedType=TripUpdates
VehiclePositions:http://gtfs-rt-test.myavail.cloud/GtfsProtoBuf?FeedLabel=IndyGo_ModTest&FeedType=VehiclePositions
Static GTFS:https://realtime.indygo.net/InfoPoint/gtfs-zip.ashx
LexTranLexington, KY- LexTran
Alerts · TripUpdates · VehiclePositions
Feed Type URLs
Alerts:http://gtfs-rt-test.myavail.cloud/GtfsProtoBuf?FeedLabel=LexTran&FeedType=Alerts
TripUpdates:http://gtfs-rt-test.myavail.cloud/GtfsProtoBuf?FeedLabel=LexTran&FeedType=TripUpdates
VehiclePositions:http://gtfs-rt-test.myavail.cloud/GtfsProtoBuf?FeedLabel=LexTran&FeedType=VehiclePositions
Static GTFS:https://mystop.lextran.com/InfoPoint/gtfs-zip.ashx
LexTran_ModTestLexington, KY- LexTran w/TripModifications
Alerts · Shapes · Stops · TripModifications · TripUpdates · VehiclePositions
Feed Type URLs
Alerts:http://gtfs-rt-test.myavail.cloud/GtfsProtoBuf?FeedLabel=LexTran_ModTest&FeedType=Alerts
Shapes:http://gtfs-rt-test.myavail.cloud/GtfsProtoBuf?FeedLabel=LexTran_ModTest&FeedType=Shapes
Stops:http://gtfs-rt-test.myavail.cloud/GtfsProtoBuf?FeedLabel=LexTran_ModTest&FeedType=Stops
TripModifications:http://gtfs-rt-test.myavail.cloud/GtfsProtoBuf?FeedLabel=LexTran_ModTest&FeedType=TripModifications
TripUpdates:http://gtfs-rt-test.myavail.cloud/GtfsProtoBuf?FeedLabel=LexTran_ModTest&FeedType=TripUpdates
VehiclePositions:http://gtfs-rt-test.myavail.cloud/GtfsProtoBuf?FeedLabel=LexTran_ModTest&FeedType=VehiclePositions
Static GTFS:https://mystop.lextran.com/InfoPoint/gtfs-zip.ashx