Vendor reports: degradedResolved · vendor status “resolved”Official status API
Delayed processing of some thread events
Reported by Plain · Customer Support · source last read 5 min ago
- Vendor start
- Oct 14, 2026, 08:46 UTC
- Vendor's clock
- Resolved
- Oct 14, 2026, 10:19 UTC
- Vendor's clock
- First seen by Statuswall
- Before tracking began
- Statuswall's clock
- Duration
- 1 h 33 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
What is unknown
Last update in these facts: 2026-10-14 10:19 UTC · summary s1, evidence ff3d230e81050e6a
Evidence (7)
- E1Plain reports degraded. (vendor) source (opens in a new tab)
- E2Vendor title: "Delayed processing of some thread events". (vendor) source (opens in a new tab)
- E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
- E4Vendor-reported start: 2026-10-14 08:46 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-10-14 10:19 UTC. (vendor)
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
Plain 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.
- Oct 14, 2026, 08:46 UTCVendor-reported startVendor time
- Oct 14, 2026, 10:19 UTCVendor-reported resolutionVendor time
No changes observed yet. Statuswall began recording changes on incidents in November 2026.