Is the Orrery API up right now?
This page checks the production surfaces of Orrery, the weather and energy data API, live from your own browser: service liveness at api.orr.sh, the full weather data path behind the flagship wind endpoint, and the docs and site hosts. The latency you see is your real network round trip, not a number we picked.
Running live checks from your browser
Checks run live against the production endpoints.
API core
GET /health on api.orr.sh: gateway routing and service liveness.
CheckingAtmosphere endpoint
GET /v1/atmosphere: International Standard Atmosphere state, computed in-process.
CheckingWeather data path
GET /v1/weather/wind: the flagship pipeline end to end, from the freshest GFS cycle to hub-height wind.
CheckingAPI reference
docs.orrery.sh, the reference generated from the OpenAPI spec.
CheckingDeveloper site
orrery.sh, the developer landing.
CheckingMarketing site
orreryhq.com, the company home and early-access signup.
Checking
How this page works
The API checks call the same public endpoints you would: they read the HTTP status and time the round trip from where you are. The weather data path check exercises the whole pipeline (resolve the freshest GFS cycle, fetch and decode the model fields, extrapolate to hub height), so a pass means the flagship endpoint is genuinely serving, not merely that a load balancer answered.
The site checks are opaque reachability probes against the static hosts. Because everything runs in your browser, a single failing row can also mean something local to you, like an ad blocker or a network filter; cross-check from another network before assuming the worst.
Want the data behind this page? Browse the API reference or start at orrery.sh. No key is needed during the early preview.