Vendor Status Watch

← all vendors

Castle status history

Current state: operational — “All Systems Operational” per https://status.castle.io (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

1incidents, last 30 days
2incidents, last 90 days
5incidents on record
Incidents per week, last 12 weeks:
Get Castle alerts in your Slack — free templateRSS for Castle

How long do Castle incidents last?

9 minmedian incident duration5 measured
12.2 h90th percentile1 in 10 ran longer
10 minmedian, major/critical only2 incidents

From 5 incidents with a vendor-posted start and resolve time. Longest on record: Degraded performance and latency due to upstream provider issues — 12.2 h (2026-05-08 04:31 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (5)

StartedIncidentStatusImpactDuration
2026-09-07 13:11 UTCRisk & Filter API Outageresolvedcritical12 min
2026-07-31 16:55 UTCElevated number of errorsresolvedmajor9 min
2026-05-08 04:31 UTCDegraded performance and latency due to upstream provider issuesresolvedminor12 h 09 min
2026-03-17 09:56 UTCRisk and Filter API Outageresolvednone0 min
2026-01-22 23:01 UTCAPI Outageresolvednone0 min

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch Castle with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "castle"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}