Current service signal
Operational
All configured health checks are passing.
- Page rendered at
- Jun 12, 2026, 2:23:43 AM
- Live health collected at
- Jun 12, 2026, 2:23:43 AM
- Last successful live refresh
- Jun 12, 2026, 2:23:43 AM
- Fallback snapshot
- No fallback snapshot in use.
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: live /health.json response.
Status feed detail
No current status-pipeline failure.
Live status data could not be fetched. Use the pipeline detail above to see whether the failure was a feed timeout, invalid response, or missing snapshot.
or email support@clevercat.app
Per-check snapshot
CleverCat Site
OK- HTTP
- 200
- Latency
- 0 ms
- Endpoint
- https://clevercat.app
- Details
- Healthy response
DupliCat API
OK- HTTP
- 200
- Latency
- 424 ms
- Endpoint
- https://duplicate.clevercat.app/health
- Details
- Healthy response
PressKit API
OK- HTTP
- 200
- Latency
- 361 ms
- Endpoint
- https://epk.clevercat.app/health
- Details
- Healthy response
TabCalendar API
OK- HTTP
- 200
- Latency
- 420 ms
- Endpoint
- https://calendar.clevercat.app/health
- Details
- Healthy response
Incident history (latest first)
- Date/time (UTC)
- Jun 12, 2026, 2:23:43 AM
- Date/time (Pacific)
- Jun 11, 2026, 7:23:43 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.
Automated status check
- Uptime monitor: https://clevercat.app/uptime
Reliability snapshot disclosure
- This page includes a server-rendered snapshot and auto-refreshes periodically.
- Detailed per-check endpoint and latency context is published on /uptime.
- Service degradation and status-pipeline degradation are shown separately so a stale feed does not read like a live healthy state.
Status levels
- Operational: all configured checks are passing.
- Degraded: one or more checks are failing or slow.
- Stale: the status feed is degraded and the latest available snapshot is displayed.
- Error: status signal could not be loaded.
Incident updates
- Automated signal refresh runs on a timer.
- During active incidents, status notes include scope and current state, with follow-ups as needed.
- If there is no major change, notes may still be posted to confirm investigation is in progress.
Need help right now?
Email support@clevercat.app and include:
- HubSpot portal ID
- Steps to reproduce
- Timestamp and timezone
- Any relevant screenshots or error text