Status
Service status
What our two websites and the API answered the last time we read them back after a release, and whether this website is answering right now. Measurements only: this page makes no promise about the future.
Right now
The last release readback
Read on . Each row counts checks we ran from outside, over the internet, against the live sites and the live API at their own hosting addresses; each row says which address it read.
- The embark.day website. 93 of 93 pages answered. Read at the website's own hosting address, not at the embark.day name. 198 checks answered as expected, 1 did not, 0 were not run. Why it did not: No cause was recorded.
- The agileintegrations.net website. 36 of 36 pages answered. Read at the website's own hosting address, not at the agileintegrations.net name. 84 checks answered as expected, 0 did not, 0 were not run.
- The API's health check. Read at the API's own hosting address. 1 check answered as expected, 0 did not, 0 were not run.
- The weather map's data doors. model fields from the run of 22 September 2026 (558.1 h old), radar frame of 28 September 2026 (397.3 h old); oldest layer 606.1 h; 231/333 reference-view tiles drawing; measured 15 October 2026. Read at the API's own hosting address. 6 checks answered as expected, 0 did not, 0 were not run.
- The API's doors: open ones answer, keyed ones refuse a call with no key, closed ones stay closed. Read at the API's own hosting address. 117 checks answered as expected, 0 did not, 0 were not run.
- Billing: a paid call draws the balance once. Read at the API's own hosting address. 2 checks answered as expected, 2 did not, 1 was not run. Why not run: the readback had no empty test account to try it with. Why they did not: The readback's own test account was out of credit (402).
- Accounts kept apart: one account cannot read another's data. Read at the API's own hosting address. 2 checks answered as expected, 0 did not, 0 were not run.
- Video: tracking, overlap removal and detection. Read at the API's own hosting address. 3 checks answered as expected, 0 did not, 3 were not run. Why not run: the readback's own test account reached its spending limit before it ran.
- Everything else the readback checked. Read at the API's and the two websites' own hosting addresses and at a test setup of ours; its security checks also try the embark.day and agileintegrations.net names. 89 checks answered as expected, 5 did not, 1 was not run. Why not run: no reason was recorded. Why they did not: The readback's own test account was out of credit (402). The embark.day name does not serve these pages yet: it redirects. Its security checks are read again when it does.
In all, 502 checks answered as expected, 8 did not, and 5 were not run.
The last overnight test run
Every night we run our whole set of automated tests. The most recent run on record, on 15 October 2026, did not pass. Our rule is that a night like that holds the next release until each failed check has been fixed or is named as an open item.
If something is not answering
Tell us. The support page says where to write and what to include.