Vendor reports: degradedResolved · vendor status “resolved”Official status API
CEM - EB360 Mobile Application - *everbridge.net
Reported by Everbridge · Communication & Messaging · source last read 3 min ago
- Vendor start
- Jan 14, 2026, 18:35 UTC
- Vendor's clock
- Resolved
- Jan 15, 2026, 13:18 UTC
- Vendor's clock
- First seen by Statuswall
- Nov 11, 2026, 02:11 UTC
- Statuswall's clock
- Duration
- 18 h 43 min
- From vendor start and resolution
Summary
Built from the facts below, no AI
Potential impact, not a confirmed outage of your systems.
What the vendor confirmed
Affected products and regions
- Components: Everbridge (EMA & EB360 Mobile).[E6]
What is unknown
- Which regions are affected: the vendor did not say.[E5]
- Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.
Last update in these facts: 2026-11-11 02:11 UTC · summary s1, evidence b9585970a03c1d8b
Evidence (8)
- E1Everbridge reports degraded. (vendor) source (opens in a new tab)
- E2Vendor title: "CEM - EB360 Mobile Application - *everbridge.net". (vendor) source (opens in a new tab)
- E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
- E4Vendor-reported start: 2026-01-14 18:35 UTC. (vendor) source (opens in a new tab)
- E5The vendor did not state which regions are affected. (Statuswall)
- E6Components the vendor attached: Everbridge (EMA & EB360 Mobile). (vendor) source (opens in a new tab)
- E7Vendor-reported resolution: 2026-01-15 13:18 UTC. (vendor) source (opens in a new tab)
- E8First seen by Statuswall: 2026-11-11 02:11 UTC. (Statuswall)
Affected scope
Not stated by the vendor
Components: Everbridge (EMA & EB360 Mobile)
No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.
Potential relevance
Everbridge is not in your stack. Follow it to see whether reports like this fall inside the regions you use.
Timeline
Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.
- Jan 14, 2026, 18:35 UTCVendor-reported startVendor time
- Jan 15, 2026, 13:18 UTCVendor-reported resolutionVendor time
- Nov 11, 2026, 02:11 UTCFirst seen by Statuswall (vendor status: resolved)Seen by Statuswall