Ecostruxure IT status history
Current state: operational — “All Systems Operational” per https://status.ecostruxureit.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Ecostruxure IT incidents last?
From 7 incidents with a vendor-posted start and resolve time. Longest on record: Unable to receive data — 6.2 h (2026-06-16 11:21 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 (7)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-06-29 18:14 UTC | SMS 2FA codes are not sent when signing in on ITE | resolved | minor | 54 min |
| 2026-06-17 10:12 UTC | Unable to receive data | resolved | minor | 2 h 42 min |
| 2026-06-16 11:21 UTC | Unable to receive data | resolved | none | 6 h 14 min |
| 2026-05-18 13:36 UTC | SMS 2FA Login Issue – EcoStruxure IT Expert | resolved | none | 2 h 57 min |
| 2026-04-08 07:55 UTC | Unable to receive data | resolved | major | 2 h 19 min |
| 2025-11-18 14:24 UTC | EcoStruxure IT service disruption | resolved | minor | 1 h 23 min |
| 2025-10-20 08:00 UTC | EcoStruxure IT mobile app push notifications unavailable | resolved | none | 0 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 Ecostruxure IT with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"ecostruxure-it"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}