Vendor reports: operationalResolved · vendor status “resolved”Official status API
Issue with upstream provider
Reported by Lattice · HR, Finance & Ops · source last read 2 min ago
- Vendor start
- Feb 26, 2026, 14:58 UTC
- Vendor's clock
- Resolved
- Feb 26, 2026, 03:30 UTC
- Vendor's clock
- First seen by Statuswall
- Before tracking began
- Statuswall's clock
- Duration
- Not available
- Needs both vendor times
Summary
Built from the facts below, no AI
Potential impact, not a confirmed outage of your systems.
What the vendor confirmed
What is unknown
Last update in these facts: 2026-02-26 14:58 UTC · summary s1, evidence b72a2a72824505ce
Evidence (7)
- E1Lattice reports operational. (vendor) source (opens in a new tab)
- E2Vendor title: "Issue with upstream provider". (vendor) source (opens in a new tab)
- E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
- E4Vendor-reported start: 2026-02-26 14:58 UTC. (vendor) source (opens in a new tab)
- E5The vendor did not state which regions are affected. (Statuswall)
- E6The vendor attached no components. (Statuswall)
- E7Vendor-reported resolution: 2026-02-26 03:30 UTC. (vendor) source (opens in a new tab)
Affected scope
Not stated by the vendor
Components: not stated by the vendor
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
Lattice 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.
- Feb 26, 2026, 03:30 UTCVendor-reported resolutionVendor time
- Feb 26, 2026, 14:58 UTCVendor-reported startVendor time
No changes observed yet. Statuswall began recording changes on incidents in November 2026.