Skip to main content

Degraded Service

Independent monitors probe our boot and health endpoints every minute from outside the application.

Last updated 09-01-2026 9:23 PM · Machine-readable feed: /api/public/status (add ?summary=1 for a compact response)

Components

Availability for each monitored component, with a day-by-day history for the last 45 days. Green means fully available, amber means partial, orange means a sustained outage, and grey means no monitoring data for that day.

Application Boot

Confirms the app server starts and can serve a request.

Operational
Uptime (24h)
97.15%
Uptime (7d)
65.81%
Uptime (30d)
51.85%
Uptime (90d)
51.85%
Response
4539 ms
Checks (24h)
1440
45 days ago17 days measuredToday

Last checked 09-01-2026 9:23 PM

Deep Health Check

Confirms the database, storage, and background jobs respond.

Operational
Uptime (24h)
96.04%
Uptime (7d)
65.31%
Uptime (30d)
51.62%
Uptime (90d)
51.62%
Response
4539 ms
Checks (24h)
1440
45 days ago17 days measuredToday

Last checked 09-01-2026 9:23 PM

Live Site

Loads the public homepage and flags server errors (500 responses).

Operational
Uptime (24h)
96.39%
Uptime (7d)
65.04%
Uptime (30d)
58.02%
Uptime (90d)
58.02%
Response
4539 ms
Checks (24h)
1440
45 days ago13 days measuredToday

Last checked 09-01-2026 9:23 PM

Latest Deployment

Latest Deployment Healthy

Release v0.1.0 passed every boot and deep health check and is confirmed as a known good build.

Healthy

Next Planned Step

Continuous

Routine monitoring only. Checks continue every minute, and any failure opens an incident here automatically.

Running Build
v0.1.0
Checks Passed
5136 passed · 33 failed
Last Known Good
v0.1.0+3fc1d28
Last Checked
08-29-2026 4:50 AM

Live Health Check

Run straight from your browser against the running application, so you can tell an application outage apart from a local network problem.

Contacting the health endpoint…

Subscribe To Status Updates

Get a message the moment we open or resolve an incident. Choose email for a person, or a webhook to pipe updates into your own tools. Unsubscribing is one click, any time.

We'll send one confirmation email first — updates start only after you confirm.

Put Our Status On Your Site

Show your own customers our current uptime and any active incident, without them leaving your site.

Appearance

Always light background

Accent Color

#1d2b62

Embed The Widget

Drops a live status panel onto your page. It refreshes itself every minute, so there's nothing to maintain.

<iframe
  src="https://checksmith.com/status/widget"
  title="CheckSmith.ai system status"
  width="340"
  height="260"
  loading="lazy"
  style="border:0;max-width:100%"
></iframe>

Use The JSON Feed

The same data as a small JSON payload, if you'd rather style it yourself.

curl https://checksmith.com/api/public/status?summary=1

Both options are public and cached briefly, so embedding them costs you nothing and never exposes account data.

What "Down" Means Here

All Systems Operational
Every monitor answered on its last run. If the app still misbehaves for you, run the live health check above; when it reports Healthy, the issue is local to your browser, network, or account rather than the service.
Degraded Service
Part of the platform is answering and part is not. Pages usually still load, but actions that save data, sign you in, or send email can fail or run slowly.
Failing or No Answer
The application is not responding. Our monitors alert the on-call team automatically, and a bad release rolls back to the last known good build without anyone stepping in. Nothing you saved before the outage is lost.
Reporting a Problem
Use "Copy for support" above and include that text with your message from the Contact page. It carries the build number and the exact failing check, which is usually all we need to diagnose the issue.

Active Incidents

No active incidents. Everything the monitors watch is responding normally.

Incident History

Every incident our monitors opened in the last 90 days, with the full timeline from detection through resolution.

Showing 25 of 25 incidents from the last 90 days.

  • Resolved
    Application Boot
    Critical
    Lasted 1 min

    HTTP 502

    1. Issue Detected

      09-01-2026 7:24 PM

      HTTP 502

    2. Resolved

      09-01-2026 7:25 PM

      Monitors returned to normal and the incident closed automatically.

  • Resolved
    Deep Health Check
    Critical
    Lasted 1 min

    HTTP 502

    1. Issue Detected

      09-01-2026 7:24 PM

      HTTP 502

    2. Resolved

      09-01-2026 7:25 PM

      Monitors returned to normal and the incident closed automatically.

  • Resolved
    Live Site
    Critical
    Lasted 1 min

    HTTP 502

    1. Issue Detected

      09-01-2026 7:24 PM

      HTTP 502

    2. Resolved

      09-01-2026 7:25 PM

      Monitors returned to normal and the incident closed automatically.

  • Resolved
    Application Boot
    Critical
    Lasted 1 min

    Timeout of 8000 ms reached. Total time: 8000.692000 ms (DNS time: 0.010000 ms, TCP/SSL handshake time: -0.010000 ms, HTTP Request/Response time: 8000.612000 ms)

    1. Issue Detected

      09-01-2026 6:20 PM

      Timeout of 8000 ms reached. Total time: 8000.692000 ms (DNS time: 0.010000 ms, TCP/SSL handshake time: -0.010000 ms, HTTP Request/Response time: 8000.612000 ms)

    2. Resolved

      09-01-2026 6:21 PM

      Monitors returned to normal and the incident closed automatically.

  • Resolved
    Deep Health Check
    Critical
    Lasted 1 min

    Timeout of 8000 ms reached. Total time: 8000.620000 ms (DNS time: 8000.620000 ms, TCP/SSL handshake time: 0.000000 ms, HTTP Request/Response time: 0.000000 ms)

    1. Issue Detected

      09-01-2026 6:20 PM

      Timeout of 8000 ms reached. Total time: 8000.620000 ms (DNS time: 8000.620000 ms, TCP/SSL handshake time: 0.000000 ms, HTTP Request/Response time: 0.000000 ms)

    2. Resolved

      09-01-2026 6:21 PM

      Monitors returned to normal and the incident closed automatically.

  • Resolved
    Live Site
    Critical
    Lasted 1 min

    Timeout of 8000 ms reached. Total time: 8000.566000 ms (DNS time: 8000.566000 ms, TCP/SSL handshake time: 0.000000 ms, HTTP Request/Response time: 0.000000 ms)

    1. Issue Detected

      09-01-2026 6:20 PM

      Timeout of 8000 ms reached. Total time: 8000.566000 ms (DNS time: 8000.566000 ms, TCP/SSL handshake time: 0.000000 ms, HTTP Request/Response time: 0.000000 ms)

    2. Resolved

      09-01-2026 6:21 PM

      Monitors returned to normal and the incident closed automatically.

  • Resolved
    Deep Health Check
    Critical
    Lasted 1 min

    Timeout of 8000 ms reached. Total time: 8000.189000 ms (DNS time: 8000.189000 ms, TCP/SSL handshake time: 0.000000 ms, HTTP Request/Response time: 0.000000 ms)

    1. Issue Detected

      09-01-2026 6:18 PM

      Timeout of 8000 ms reached. Total time: 8000.189000 ms (DNS time: 8000.189000 ms, TCP/SSL handshake time: 0.000000 ms, HTTP Request/Response time: 0.000000 ms)

    2. Resolved

      09-01-2026 6:19 PM

      Monitors returned to normal and the incident closed automatically.

  • Resolved
    Application Boot
    Critical
    Lasted 1 min

    Timeout of 8000 ms reached. Total time: 8001.652000 ms (DNS time: 0.012000 ms, TCP/SSL handshake time: -0.012000 ms, HTTP Request/Response time: 8001.569000 ms)

    1. Issue Detected

      09-01-2026 6:01 PM

      Timeout of 8000 ms reached. Total time: 8001.652000 ms (DNS time: 0.012000 ms, TCP/SSL handshake time: -0.012000 ms, HTTP Request/Response time: 8001.569000 ms)

    2. Resolved

      09-01-2026 6:02 PM

      Monitors returned to normal and the incident closed automatically.

  • Resolved
    Deep Health Check
    Critical
    Lasted 1 min

    Timeout of 8000 ms reached. Total time: 8000.858000 ms (DNS time: 8000.858000 ms, TCP/SSL handshake time: 0.000000 ms, HTTP Request/Response time: 0.000000 ms)

    1. Issue Detected

      09-01-2026 6:01 PM

      Timeout of 8000 ms reached. Total time: 8000.858000 ms (DNS time: 8000.858000 ms, TCP/SSL handshake time: 0.000000 ms, HTTP Request/Response time: 0.000000 ms)

    2. Resolved

      09-01-2026 6:02 PM

      Monitors returned to normal and the incident closed automatically.

  • Resolved
    Live Site
    Critical
    Lasted 1 min

    Timeout of 8000 ms reached. Total time: 8000.804000 ms (DNS time: 8000.804000 ms, TCP/SSL handshake time: 0.000000 ms, HTTP Request/Response time: 0.000000 ms)

    1. Issue Detected

      09-01-2026 6:01 PM

      Timeout of 8000 ms reached. Total time: 8000.804000 ms (DNS time: 8000.804000 ms, TCP/SSL handshake time: 0.000000 ms, HTTP Request/Response time: 0.000000 ms)

    2. Resolved

      09-01-2026 6:02 PM

      Monitors returned to normal and the incident closed automatically.

  • Resolved
    Live Site
    Critical
    Lasted 1 min

    Timeout of 8000 ms reached. Total time: 8000.171000 ms (DNS time: 8000.171000 ms, TCP/SSL handshake time: 0.000000 ms, HTTP Request/Response time: 0.000000 ms)

    1. Issue Detected

      09-01-2026 5:14 PM

      Timeout of 8000 ms reached. Total time: 8000.171000 ms (DNS time: 8000.171000 ms, TCP/SSL handshake time: 0.000000 ms, HTTP Request/Response time: 0.000000 ms)

    2. Resolved

      09-01-2026 5:15 PM

      Monitors returned to normal and the incident closed automatically.

  • Resolved
    Deep Health Check
    Critical
    Lasted 1 min

    HTTP 502

    1. Issue Detected

      09-01-2026 3:41 PM

      HTTP 502

    2. Resolved

      09-01-2026 3:42 PM

      Monitors returned to normal and the incident closed automatically.

  • Resolved
    Application Boot
    Critical
    Lasted 1 min

    Timeout of 8000 ms reached. Total time: 8000.560000 ms (DNS time: 0.032000 ms, TCP/SSL handshake time: -0.032000 ms, HTTP Request/Response time: 8000.334000 ms)

    1. Issue Detected

      09-01-2026 3:28 PM

      Timeout of 8000 ms reached. Total time: 8000.560000 ms (DNS time: 0.032000 ms, TCP/SSL handshake time: -0.032000 ms, HTTP Request/Response time: 8000.334000 ms)

    2. Resolved

      09-01-2026 3:29 PM

      Monitors returned to normal and the incident closed automatically.

  • Resolved
    Deep Health Check
    Critical
    Lasted 1 min

    HTTP 502

    1. Issue Detected

      09-01-2026 2:31 PM

      HTTP 502

    2. Resolved

      09-01-2026 2:32 PM

      Monitors returned to normal and the incident closed automatically.

  • Resolved
    Application Boot
    Critical
    Lasted 1 min

    Timeout of 8000 ms reached. Total time: 8001.049000 ms (DNS time: 0.045000 ms, TCP/SSL handshake time: -0.045000 ms, HTTP Request/Response time: 8000.760000 ms)

    1. Issue Detected

      09-01-2026 1:27 PM

      Timeout of 8000 ms reached. Total time: 8001.049000 ms (DNS time: 0.045000 ms, TCP/SSL handshake time: -0.045000 ms, HTTP Request/Response time: 8000.760000 ms)

    2. Resolved

      09-01-2026 1:28 PM

      Monitors returned to normal and the incident closed automatically.

  • Resolved
    Deep Health Check
    Critical
    Lasted 1 min

    Timeout of 8000 ms reached. Total time: 8000.623000 ms (DNS time: 8000.623000 ms, TCP/SSL handshake time: 0.000000 ms, HTTP Request/Response time: 0.000000 ms)

    1. Issue Detected

      09-01-2026 1:27 PM

      Timeout of 8000 ms reached. Total time: 8000.623000 ms (DNS time: 8000.623000 ms, TCP/SSL handshake time: 0.000000 ms, HTTP Request/Response time: 0.000000 ms)

    2. Resolved

      09-01-2026 1:28 PM

      Monitors returned to normal and the incident closed automatically.

  • Resolved
    Live Site
    Critical
    Lasted 1 min

    Timeout of 8000 ms reached. Total time: 8000.541000 ms (DNS time: 8000.541000 ms, TCP/SSL handshake time: 0.000000 ms, HTTP Request/Response time: 0.000000 ms)

    1. Issue Detected

      09-01-2026 1:27 PM

      Timeout of 8000 ms reached. Total time: 8000.541000 ms (DNS time: 8000.541000 ms, TCP/SSL handshake time: 0.000000 ms, HTTP Request/Response time: 0.000000 ms)

    2. Resolved

      09-01-2026 1:28 PM

      Monitors returned to normal and the incident closed automatically.

  • Resolved
    Application Boot
    Critical
    Lasted 1 min

    HTTP 502

    1. Issue Detected

      09-01-2026 1:02 PM

      HTTP 502

    2. Resolved

      09-01-2026 1:03 PM

      Monitors returned to normal and the incident closed automatically.

  • Resolved
    Deep Health Check
    Critical
    Lasted 1 min

    HTTP 502

    1. Issue Detected

      09-01-2026 1:02 PM

      HTTP 502

    2. Resolved

      09-01-2026 1:03 PM

      Monitors returned to normal and the incident closed automatically.

  • Resolved
    Live Site
    Critical
    Lasted 1 min

    HTTP 502

    1. Issue Detected

      09-01-2026 1:02 PM

      HTTP 502

    2. Resolved

      09-01-2026 1:03 PM

      Monitors returned to normal and the incident closed automatically.

  • Resolved
    Deep Health Check
    Critical
    Lasted 1 min

    Timeout of 8000 ms reached. Total time: 8001.598000 ms (DNS time: 8001.598000 ms, TCP/SSL handshake time: 0.000000 ms, HTTP Request/Response time: 0.000000 ms)

    1. Issue Detected

      09-01-2026 6:06 AM

      Timeout of 8000 ms reached. Total time: 8001.598000 ms (DNS time: 8001.598000 ms, TCP/SSL handshake time: 0.000000 ms, HTTP Request/Response time: 0.000000 ms)

    2. Resolved

      09-01-2026 6:07 AM

      Monitors returned to normal and the incident closed automatically.

  • Resolved
    Deep Health Check
    Critical
    Lasted 2 min

    Timeout of 8000 ms reached. Total time: 8000.881000 ms (DNS time: 8000.881000 ms, TCP/SSL handshake time: 0.000000 ms, HTTP Request/Response time: 0.000000 ms)

    1. Issue Detected

      09-01-2026 5:34 AM

      Timeout of 8000 ms reached. Total time: 8000.881000 ms (DNS time: 8000.881000 ms, TCP/SSL handshake time: 0.000000 ms, HTTP Request/Response time: 0.000000 ms)

    2. On-Call Notified

      09-01-2026 5:35 AM

      1 alert sent to the on-call team by email, Slack, and paging.

    3. Resolved

      09-01-2026 5:36 AM

      Monitors returned to normal and the incident closed automatically.

  • Resolved
    Live Site
    Critical
    Lasted 2 min

    Timeout of 8000 ms reached. Total time: 8000.834000 ms (DNS time: 8000.834000 ms, TCP/SSL handshake time: 0.000000 ms, HTTP Request/Response time: 0.000000 ms)

    1. Issue Detected

      09-01-2026 5:34 AM

      Timeout of 8000 ms reached. Total time: 8000.834000 ms (DNS time: 8000.834000 ms, TCP/SSL handshake time: 0.000000 ms, HTTP Request/Response time: 0.000000 ms)

    2. On-Call Notified

      09-01-2026 5:35 AM

      1 alert sent to the on-call team by email, Slack, and paging.

    3. Resolved

      09-01-2026 5:36 AM

      Monitors returned to normal and the incident closed automatically.

  • Resolved
    Application Boot
    Critical
    Lasted 1 min

    Timeout of 8000 ms reached. Total time: 8001.624000 ms (DNS time: 0.034000 ms, TCP/SSL handshake time: -0.034000 ms, HTTP Request/Response time: 8001.479000 ms)

    1. Issue Detected

      09-01-2026 5:25 AM

      Timeout of 8000 ms reached. Total time: 8001.624000 ms (DNS time: 0.034000 ms, TCP/SSL handshake time: -0.034000 ms, HTTP Request/Response time: 8001.479000 ms)

    2. Resolved

      09-01-2026 5:26 AM

      Monitors returned to normal and the incident closed automatically.

  • Resolved
    Deep Health Check
    Critical
    Lasted 1 min

    Timeout of 8000 ms reached. Total time: 8001.481000 ms (DNS time: 8001.481000 ms, TCP/SSL handshake time: 0.000000 ms, HTTP Request/Response time: 0.000000 ms)

    1. Issue Detected

      09-01-2026 5:25 AM

      Timeout of 8000 ms reached. Total time: 8001.481000 ms (DNS time: 8001.481000 ms, TCP/SSL handshake time: 0.000000 ms, HTTP Request/Response time: 0.000000 ms)

    2. Resolved

      09-01-2026 5:26 AM

      Monitors returned to normal and the incident closed automatically.

This page reflects automated monitoring only and refreshes every minute. For help with your own workspace, reach us from the Contact page.