Status

Every line below is measured while this page is being built for you. There is no scoreboard behind it and no separate service keeping track. If a check does not come back, the page says so instead of showing green.

Measured at 23:34 UTC

• This websiteWorking

  The pages you are reading. This one reads as working because it just served you, which makes it the weakest claim here rather than the strongest.

• DatabaseWorking

  16 ms

  One query, run while this page was being built, with the time it took shown next to it. Slower than two seconds reads as degraded and the measured number stays on screen. If the database cannot be reached at all, every row here that depends on a query reads as could not read, and none of them guesses.

• DiscoveryDegraded

  19 hours ago · 25 in the last 24 hours

  When the last new candidate was written to the ledger, and how many arrived in the past 24 hours. A pass runs every four hours and only records companies it has not seen before, so a quiet stretch means it found nothing new, not that it failed to run. This is a record of new rows, not a heartbeat. More than six hours since the last one reads as degraded.

• EnrichmentWorking

  32 hours ago · 7 waiting · 0 out of attempts

  When a company record was last filled in, how many qualified candidates are still waiting for one, and how many have used up their three attempts. The failure count is the number worth watching: a backlog clears, a stuck row does not.

• DraftingWorking

  54 hours ago · 0 in the review queue

  When a message was last drafted, and how many are sitting in the review queue. Every draft waits for a person to approve it, so a queue here is the system working as designed. A queue that never moves is not.

• Public demoWorking

  2 calls · 2 finished · median 49 seconds · Too few calls to report a rate.

  Calls to the free run on the home page over the past 24 hours: how many were made, how many finished, and the median time they took. Real traffic with real outcomes, which makes it the strongest signal on this page. The success rate is published only when there were at least five calls, because two out of two is not a rate. Fewer than half of those calls finishing reads as degraded.

• Rate limitsWorking

  Whether the limiter is keeping its counters in Redis or in this process memory. Memory is a genuine degradation and is marked as one: the ceilings still hold, but a restart or a deploy forgets who has run in the last hour and how much of the daily allowance is already spent.

Submissions in the last 30 days: 1

Could not read means the check itself did not come back in time. It is not a report that the component is down, and it is not a report that it is fine. Quiet is different again: the check answered and found no work in the window, which is a normal state for a system that runs six times a day. Nothing on this page ever falls back to the last value that happened to be green.

There is no uptime percentage here and no list of past incidents. Nothing in this system records availability over time, so a figure like 99.98 percent would have to be invented, and an invented number on a status page is worse than no number. This page starts from what it can measure right now, every time you open it.

This page is served by the same application it reports on, so it cannot tell you that application is down. If Knockwire is properly broken, this address does not load at all, and a page that will not open is the outage report.

What this page does not tell you

• The proxy network and the addresses reads go out from. That infrastructure is not run by this application and not observed by it. A green tick for something we do not measure would be worth less than the empty space.
• Outbound email. Testing it means opening a connection to the mail host on every page load, against the exact mailbox the sending caps exist to protect. Nothing here keeps a record of individual send outcomes either, so there is no honest number to publish.
• Delivery as a state. Submitting a contact form is off by default and the scheduled passes never send, so delivery is reported as a count of submissions over the last 30 days. A green light next to it would be a claim about work the system is not currently doing.
• Anything run by somebody else. Payment processing, hosting, and the public sources discovery reads from are other systems with their own reporting. This page reports what Knockwire can see from inside itself, and stops there.