Performance for any scale of application
Designed for large location-based applications, the TravelTime models, IP infrastructure, and integrations, meet your organisation’s performance needs globally.
Why performance matters
Fast, accurate insights are essential for any location-based app—powering seamless search, matching, and heavy computations like route optimisation.
Performance that handles millions of locations without delay is crucial.
At TravelTime, our API is engineered for lightning-fast, scalable performance, so your applications always run smoothly.
Try our live demo tool
TravelTime can calculate 100,000 travel times to different locations in a single
request. Try the real-time demo tool.
Enter an address and choose a mode of transport.
Public transportLoading...
High-performance API across
multiple instances
This table shows benchmarking results for TravelTime API across different instance types and request sizes. These are for a single connection and do not account for concurrency.
| Machine type | Destinations | HTTP request duration | Receiving time | Sending time |
|---|---|---|---|---|
| t2.medium | 5,000 | 170.71 | 195.18 | 3.08 |
| t2.medium | 10,000 | 172.66 | 198.56 | 2.72 |
| t2.medium | 25,000 | 194.70 | 232.02 | 8.17 |
| t2.medium | 100,000 | 234.59 | 257.02 | 7.34 |
| m6i.large | 5,000 | 167.30 | 180.37 | 0.23 |
| m6i.large | 10,000 | 167.28 | 179.34 | 1.29 |
| m6i.large | 25,000 | 191.41 | 217.06 | 7.62 |
| m6i.large | 100,000 | 224.92 | 253.82 | 6.58 |
Calculated using our GitHub benchmarking repositoryTest the performance
for yourself
We've made testing as simple as possible, providing accessible tools that don’t require much developer time.
See what our customers say
TravelTime is trusted globally to deliver accurate results.
“We now see results returned 4X faster from the TravelTime API than when we were using the Google API.”
Jonathan Beckman
Head of Product
Reliable performance at scale
TravelTime API performance scales to meet the needs of your application, processing multiple requests and large amounts of destinations with ease.
Calculated using our GitHub benchmarking repositoryPerformance on
AWS m6i.xlarge
Scaling the number of destinations impacts request duration, receive time, and send time. This table highlights key trends in latency as the destinations increase from 5,000 to 100,000 destinations.
| Destinations | Request duration avg (ms) | Receiving time P90 (ms) | Sending time (ms) |
|---|---|---|---|
| 5,000 | 167.30 | 180.37 | 0.23 |
| 10,000 | 167.28 | 179.34 | 1.29 |
| 25,000 | 191.41 | 217.06 | 7.62 |
| 100,000 | 224.92 | 253.82 | 6.58 |
Calculated using our GitHub benchmarking repositoryHow TravelTime delivers unbeatable performance
TravelTime is the result of years of development work and obsessing over every possible optimisation and efficiency saving.
Proprietary technology
Dedicated infrastructure
Comprehensive system integration and monitoring
Proprietary technology
Why choose TravelTime
Performance
Our models are not only accurate, they are blazingly fast. TravelTime is capable of processing millions of results in milliseconds, integrating into the core of your application.
Scale
We meet the needs of startups and enterprise clients across 200+ countries and territories. With our fast, cost-effective API, you can harness accurate insights at any scale.
Accuracy
TravelTime models have been built from the ground-up and relentlessly tested to produce industry-leading results.
Licensing and integration
Seamlessly integrate TravelTime using our SDKs, database integrations, and platform partnerships. Our licensing gives you freedom to build without compromise.
Pricing model
We don’t charge for API usage per transaction. You can calculate as many journey times as you need for one fixed cost.
Support
Speak directly with the team that built and maintains TravelTime. We don’t monetise support and work to help you build the best application possible.
Accurate location insights in the core of your application
Build without compromise. Get started with the leading location API today.