Changes / Gusto / We are aware of potential error messages that customers may be experiencing when accessing Gusto.com. Our teams are working to resolve this as a top priority. Thank you for your patience at this time.
Gusto: Critical incident: We are aware of potential error messages that customers may be experiencing when accessing Gusto.com. Our teams are working to resolve this as a top priority. Thank you for your patience at this time.
Summary
Customers could encounter error messages when accessing Gusto.com; Gusto marked the incident critical and listed the API and Gusto.com website as affected. It started at 2024-01-17 17:37 UTC and was resolved at 2024-01-17 17:40 UTC, lasting 3 min; no cause or fix was stated.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: We are aware of potential error messages that customers may be experiencing when accessing Gusto.com. Our teams are working to resolve this as a top priority. Thank you for your patience at this time.
Before: not present
After: critical
Before: not present
After: resolved
Before: not present
After: 2024-01-17 17:37 UTC
Before: not present
After: 2024-01-17 17:40 UTC
Before: not present
After: API, Gusto.com website
Before: not present
After: We are currently investigating this issue.
Before: not present
After: This incident has been resolved.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Critical incident: We are aware of potential error messages that customers may be experiencing when accessing Gusto.com. Our teams are working to resolve this as a top priority. Thank you for your patience at this time. (this change) Customers could encounter error messages when accessing Gusto.com; Gusto marked the incident critical and listed the API and Gusto.com website as affected. It started at 2024-01-17 17:37 UTC and was resolved at 2024-01-17 17:40 UTC, lasting 3 min; no cause or fix was stated. | Major incident |