Lotame status history
Current state: operational — “All Systems Operational” per https://status.lotame.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Lotame incidents last?
From 4 incidents with a vendor-posted start and resolve time. Longest on record: Regional Edge Services Degradation — 9.4 h (2025-10-20 12:32 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)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-08-25 14:15 UTC | Platform UI/API Degradation | resolved | none | 0 min |
| 2026-06-29 12:15 UTC | Dropbox Outage | resolved | none | 0 min |
| 2026-04-22 15:29 UTC | Edge Services Degredation | resolved | major | 2 h 02 min |
| 2025-10-20 12:32 UTC | Regional Edge Services Degradation | resolved | major | 9 h 25 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 Lotame with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"lotame"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}
