Praxy status
Is Praxy working right now?
Every check here is a real request to the same public address you use. Readings are cached briefly on the way to you, so one can be up to a few minutes old. Nothing on this page is a claim written in advance — the timestamp below says exactly how old the reading you are looking at is.
All systems operational
Checked 2026-11-07 23:34 UTC
Talking to Praxy
The channels you reach Praxy through.
WhatsApp assistant
Messaging Praxy on WhatsApp, and the replies that come back.
Operational
- Database connections in use:
- 0 of 30
What this check sees
Checks the API and product database behind WhatsApp. It cannot see WhatsApp's own delivery — if Meta is having an outage, this row stays green while messages do not arrive. Answered in 158 ms.
Voice calls
Live calls with Praxy, including mock interviews.
Operational
What this check sees
Checks the call gateway's own readiness. It cannot see the telephony carrier, so a carrier fault will not appear here. Answered in 63 ms.
Jobs
Search over the job index, and how current that index is.
Job search
Searching and filtering the job index.
Operational
- Open jobs:
- 4,036,416
- Companies:
- 93,833
What this check sees
Checks the jobs API and the database it serves from. Answered in 283 ms.
Job index freshness
How current the listings are, as opposed to whether search responds.
Operational
- Last sweep:
- 16 hours ago
- Median listing age:
- 5.6 days
What this check sees
Reads the freshness figures the jobs API publishes about itself. Shares a process with Job search, so these two rows are not independent confirmations. Answered in 283 ms.
Your workspace
The web app and everything behind your signed-in session.
Praxy web app
app.praxy.me — chat, resumes, saved jobs and settings.
Operational
What this check sees
Loads the sign-in page, which is the first thing a signed-out visitor sees. It does not sign in, so it cannot detect an authentication fault. Answered in 601 ms.
Praxy API
The service behind the web app: resumes, tailoring, mock interviews, saved jobs and auto-apply.
Operational
- Database connections in use:
- 0 of 30
What this check sees
Checks the API process and its database. Shares that process with the WhatsApp assistant, so those two rows move together. Auto-apply's own gateway has no public address, so it is covered only as far as this API reaches it. Answered in 158 ms.
Public pages and integrations
Pages that work without an account, and the MCP endpoint.
praxy.me
The public site, including /jobs and the apply links.
Operational
What this check sees
The marketing site and the apply links. This status page is served by the same deployment, so this row cannot tell you the site is down — if it were, this page would not have loaded. Treat it as a check on the deployment answering, not as independent evidence. Answered in 232 ms.
Praxy MCP
The read-only MCP endpoint you connect an AI client to.
Operational
What this check sees
Checks MCP's OAuth discovery document. MCP runs inside the Praxy API process, so it shares that row's fate. Answered in 394 ms.
Incident history
The last 90 days.
No incidents have been published in the last 90 days.
What this page cannot see
- Someone else’s outage. If WhatsApp itself is down, or a phone carrier is dropping calls, Praxy’s own services answer normally and these rows stay green while you still cannot get through.
- Quality, as opposed to uptime. A check confirms a service answered. It cannot tell you the answer was any good.
- Your account specifically. Everything here is measured signed-out. A fault that only affects your account will not appear.
- The host underneath this page. This page runs on the same platform as the services it reports on, so a platform-wide outage takes down both at once and this page would simply stop loading. A status page should not share a failure domain with what it watches; this one currently does, and you should read an all-clear here with that in mind.
Seeing something this page is not? Tell us at admin@praxy.me. The raw readings are at /api/status.
