Vendor Status Watch

← all vendors

Webdam status history

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

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

How long do Webdam incidents last?

3.3 hmedian incident duration4 measured
20.4 h90th percentile1 in 10 ran longer
3.2 hmedian, major/critical only2 incidents

From 4 incidents with a vendor-posted start and resolve time. Longest on record: Degraded performance with uploads and downloads — 20.4 h (2025-10-20 21:33 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 (4)

StartedIncidentStatusImpactDuration
2026-09-14 16:20 UTC502 Bad Gateway Errorsresolvedmajor5 h 35 min
2026-01-16 23:07 UTCDegraded performance with downloadsresolvedminor1 h 05 min
2025-10-20 21:33 UTCDegraded performance with uploads and downloadsresolvedminor20 h 24 min
2025-08-13 17:40 UTCUnable to load Webdamresolvedcritical45 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 Webdam with the template

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

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