Uptime Monitor
Live health checks for CleverCat services. Current upstream app coverage is derived from configured checks returned by our live status feed.
Current upstream checks: DupliCat API, PressKit API, TabCalendar API .
Configured app checks appear automatically in the table below (for example DupliCat, PressKit, and TabCalendar when configured).
Status feed: live /health.json response.
Live status data could not be fetched. This may be a temporary network issue.
All configured checks are passing.
- Page rendered at
- Jun 12, 2026, 2:24:19 AM
- Live health collected at
- Jun 12, 2026, 2:24:19 AM
- Last successful live refresh
- Jun 12, 2026, 2:24:19 AM
- Fallback snapshot
- No fallback snapshot in use.
- Total checks
- 4
- Passing checks
- 4/4
Service state
Service checks are passing in this snapshot.
Status pipeline
Status pipeline is healthy. This page is using a live /health.json response.
Status feed detail
No current status-pipeline failure.
Per-check snapshot
CleverCat Site
OK- HTTP
- 200
- Latency
- 0 ms
- Endpoint
- https://clevercat.app
- Details
- Healthy response
DupliCat API
OK- HTTP
- 200
- Latency
- 92 ms
- Endpoint
- https://duplicate.clevercat.app/health
- Details
- Healthy response
PressKit API
OK- HTTP
- 200
- Latency
- 81 ms
- Endpoint
- https://epk.clevercat.app/health
- Details
- Healthy response
TabCalendar API
OK- HTTP
- 200
- Latency
- 91 ms
- Endpoint
- https://calendar.clevercat.app/health
- Details
- Healthy response
Incident history (latest first)
- Date/time (UTC)
- Jun 12, 2026, 2:24:19 AM
- Date/time (Pacific)
- Jun 11, 2026, 7:24:19 PM
- Scope
- CleverCat site and configured upstream checks
- Summary
- No active service incidents in this snapshot. Automated checks are passing.
- Update approach
- Automated snapshot refresh runs on a timer. Manual notes are posted on state change.
This monitor auto-refreshes periodically and shows service state separately from status-feed failures. For incident notes and escalation details, see status.