SmugMug status history
Current state: operational — “All Systems Operational” per https://status.smugmug.com (Atlassian Statuspage), checked 2026-09-24 12:28 UTC.
How long do SmugMug incidents last?
From 9 incidents with a vendor-posted start and resolve time. Longest on record: Site unavailable - AWS cloud outage — 9.3 h (2025-10-20 07:17 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 (9)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-06-30 16:29 UTC | Blip in how some pages are loading | resolved | minor | 22 min |
| 2026-06-03 08:50 UTC | Blip in how some pages are loading | resolved | none | 3 h 07 min |
| 2026-04-11 03:21 UTC | Pages loading slowly | resolved | none | 29 min |
| 2026-02-07 18:58 UTC | Uploads processing slowly | resolved | minor | 8 h 10 min |
| 2026-02-07 04:01 UTC | Uploads processing slowly | resolved | none | 3 h 12 min |
| 2026-01-27 15:20 UTC | Uploads processing slowly | resolved | minor | 1 h 04 min |
| 2025-12-21 22:08 UTC | Pages loading slowly | resolved | none | 1 h 25 min |
| 2025-10-29 08:39 UTC | Errors in Lightroom Publishing Manager settings | resolved | none | 7 h 25 min |
| 2025-10-20 07:17 UTC | Site unavailable - AWS cloud outage | resolved | critical | 9 h 21 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 SmugMug with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"smugmug"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}
