System status
All systems running
Live checks of the platform agencies run on: their websites and admin, the database behind both, outgoing email, and the nightly jobs that delete expired personal data. Checked every 5 minutes, in Tokyo, with a security check of everything it runs on every day.
- Last check
- 10:15 JST (5 min ago)
- Monitoring since
- 12 Nov 2026
Last 90 days
- Every check passed
- Some checks failed or didn't run
- Fewer than half passed
- No data
Websites and admin
Agencies' sites, their admin and the database behind both, checked every 5 minutes
Last check 10:15 JST · database answered in 78 ms
| Day | State | Detail |
|---|---|---|
| 13 Nov 2026 | Running | 124 of 124 checks passed |
| 12 Nov 2026 | Running | 80 of 80 checks passed |
Email delivery
Application receipts, alerts and replies from live agencies, handed to our mail service
No email in the last two days
| Day | State | Detail |
|---|
Scheduled jobs
Nightly deletion of expired personal data, reminders, alert emails and clean-up
Every job's last run finished
| Day | State | Detail |
|---|---|---|
| 13 Nov 2026 | Running | 581 runs, all finished |
| 12 Nov 2026 | Running | 364 runs, all finished |
Security checks
Every package that ships, checked daily for known vulnerabilities, and the software it runs on checked for support
Last check 13 Nov 2026, 02:00 JST · 389 packages checked · no known vulnerabilities
| Day | State | Detail |
|---|---|---|
| 13 Nov 2026 | Passed | 389 packages checked · no known vulnerabilities |
| 12 Nov 2026 | Passed | 383 packages checked · no known vulnerabilities |
Database response
How long the database took to answer each check, as the day's median. The database and every agency's site are in Tokyo.
82ms median today
The chart appears once there are three days of checks. 2 so far.
Scheduled jobs
The work that runs without anyone pressing a button. A job that fails alerts us straight away; one that skips a night, within a day.
| Job | Result |
|---|---|
| Syncs each agency's CRM: jobs in, applications out, stages backEvery 10 minutes | Finished |
| Carries on self-serve site imports*/2 * * * * | Finished |
| Sends scheduled newsletter issues and carries on sends in progressEvery 5 minutes | Finished |
| Sends sequence steps that are due and enrols new people who fitEvery 10 minutes | Finished |
| Sends held emails, event and interview remindersHourly | Finished |
| Sends free trial notices and deletes trials 30 days after they endDaily, 09:00 JST | Finished |
| Checks every package we ship for known vulnerabilities, and that what we run on is still supportedDaily, 02:00 JST | Finished |
| Keeps the database awakeDaily, 03:00 JST | Finished |
| Runs each agency's scheduled AI agentsDaily, 03:30 JST | Finished |
| Decides finished A/B testsDaily, 04:00 JST | Finished |
| Removes spent sign-in codes, sessions and unused filesDaily, 05:00 JST | Finished |
| Deletes personal data past each agency's periodDaily, 05:15 JST | Finished |
| Imports ad account spend (Google Ads)Daily, 05:30 JST | Finished |
| Imports Search Console figuresDaily, 06:00 JST | Finished |
| Checks search rankingsDaily, 06:30 JST | Finished |
| Closes finished polls and sends remindersDaily, 07:00 JST | Finished |
| Sends job alert digestsDaily, 07:30 JST | Finished |
| Sends client and candidate surveysDaily, 08:00 JST | Finished |
Security checks
Every day at 02:00, every package that ships with AirTA Sites is checked against the public database of known vulnerabilities, and the software it runs on is checked for security support.
0critical or high issues open
389 packages, 398 versions, checked 13 Nov 2026 at 02:00 JST
Critical
0 open
Fixed within 72 hours
High
0 open
Fixed within 14 days
Moderate
0 open
Fixed with routine updates
Low
0 open
Fixed with routine updates
What the platform runs on
Software stops getting security fixes when its support ends. Each part is checked against its published support dates, every day.
| Software | Version | Support |
|---|---|---|
| Node.jsSupported until 30 Apr 2028 | 24.22.2 | Supported |
| Next.jsNo end date set | 16.4.6 | Supported |
| ReactNo end date set | 19.3.1 | Supported |
| PostgreSQLSupported until 8 Nov 2029 | 17.11 | Supported |
Incidents
Anything that affected agencies' sites, written up by a person: what happened, how long it lasted, and what we changed.
No incidents in the last 90 days.
How this page is measured
The rules behind every colour, so nothing here needs taking on trust.
Every 5 minutes
A check inside our hosting in Tokyo asks the database a question and times the answer. A check that doesn't run counts as failed, so a gap can't make the record look better.
What the colours mean
Green: every check that day passed. Amber: a check failed, or more than 1 in 20 didn't run, or a nightly job didn't finish. Red: fewer than half passed. Grey: no data, including every day before monitoring began.
What it can't see
The checks run inside our own hosting, so an outage of the hosting itself would stop them before they could report it. Our providers publish their own status pages, linked below.
Counts only
This page shows numbers of checks, emails and job runs. It never names an agency, a candidate, an address or an error.
The daily security check
Every package that ships is checked against npm's advisory database, the one its own audit uses, and the software underneath against its published support dates. A day the check doesn't run counts against us.
Deadlines start when we find it
Our security policy sets 72 hours for a critical fix and 14 days for a high one. The clock starts the day the check first finds an issue, and a fix past its deadline turns the day red. Issues are counted here, not named, until they are fixed.
Something wrong that this page doesn't show? hello@airtasites.jp