← Dashboard

System health

Per-endpoint health over the last 24 hours: did the call succeed (HTTP 2xx, parseable JSON) and did the response contain the fields our parsers depend on? Schema drift catches an upstream API quietly dropping a field; success rate catches it failing entirely.

Outbound calls (24h)
287,399
665 failed
Success rate
99.77%
weighted across all endpoints
Schema drift
0
all clear
Most recent drift

Endpoint health

EndpointCallsSuccessAvg / MaxSchemaNotes
ea/list2,616100.00%1474 / 5280msok
ea/snapshot1100.00%251 / 251msok
ea/detail95,78299.90%145 / 29154msok
cp/station_list28,80499.99%406 / 8839msok
cp/station_info1,78599.66%370 / 4612msok
blink/detail67,814100.00%144 / 16873msok
blink/afdc1100.00%597 / 597msok
evgo/auth2,618100.00%125 / 2332msok
evgo/sites10,48094.77%1242 / 6017msok
evgo/chargers76,73599.99%690 / 30092msok
evgo/pricing48199.79%890 / 30028msok
google/places-text-search282100.00%583 / 1008msok
google/places-detailsok
google/places-autocompleteok
google/routes-matrixok
google/routes-computeok

User-triggered routes (Google Places autocomplete/details, Routes API) appear here only when their containers happen to flush via a co-located write — most of their calls log first-occurrence to Vercel function logs instead.