Vendor reports: operationalResolved · vendor status “resolved”Official status API
Small amount of errors during a planned test operation
Reported by Factorial · HR, Finance & Ops · source last read 2 min ago
- Vendor start
- May 16, 2025, 05:30 UTC
- Vendor's clock
- Resolved
- May 16, 2025, 04:30 UTC
- Vendor's clock
- First seen by Statuswall
- Before tracking began
- Statuswall's clock
- Duration
- Not available
- Needs both vendor times
Affected scope
Not stated by the vendor
The vendor's feed gives no region for this incident. It is not assumed to be global.
Potential relevance
Factorial 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.
- May 16, 2025, 04:30 UTCVendor-reported resolutionVendor time
- May 16, 2025, 05:30 UTCVendor-reported startVendor time
No changes observed yet. Statuswall began recording changes on incidents in November 2026.