System Status
Live status for all 9 Farun API endpoints. Uptime measured over a rolling 90-day window. Incident history below.
All Operational
Last checked just now
9
Endpoints monitored
99.98%
Avg uptime (90d)
0
Open incidents
14 days ago
Last incident
Routing
/v1/routing/directions Latency
124ms
Uptime 90d
99.98%
Status
operational
/v1/routing/optimized Latency
418ms
Uptime 90d
99.96%
Status
operational
Maps
/v1/tiles/vector/{z}/{x}/{y} Latency
38ms
Uptime 90d
99.99%
Status
operational
Spatial
/v1/elevation Latency
89ms
Uptime 90d
99.98%
Status
operational
/v1/isochrone Latency
540ms
Uptime 90d
99.95%
Status
operational
/v1/geocoding/search Latency
76ms
Uptime 90d
99.99%
Status
operational
/v1/geocoding/reverse Latency
95ms
Uptime 90d
99.97%
Status
operational
/v1/geocoding/details Latency
95ms
Uptime 90d
99.97%
Status
operational
/v1/routing/matrix Latency
95ms
Uptime 90d
99.97%
Status
operational
Infrastructure
API Gateway
Global edge
Map tile CDN
Multi-region
Routing engine cluster
Primary + failover
Spatial compute
Dedicated workers
RapidAPI gateway
External dependency
Map data pipeline
Batch / scheduled
Incident history
Past 90 daysP95 latency on /v1/isochrone exceeded 2s for 41 minutes due to a backend queue saturation event. Resolved by scaling the worker pool. No requests were dropped.
A map data update caused a partial CDN cache invalidation that resulted in stale tile responses in 3 edge regions for 12 minutes. Affected regions: EU-West, AP-South, AP-Southeast.
A scheduled infrastructure rotation caused a brief cold-start period for routing workers. Median latency rose to 890ms for approximately 8 minutes. Fully recovered on next request cycle.
No open incidents. All APIs are operating normally.
Stay informed
Subscribe to receive email alerts when any Farun API endpoint experiences degraded performance or an outage. You'll be notified at the start and end of every incident.