Snaps outages and incidents
Outage and incident data over the last 30 days for Snaps.
There have been 0 outages or incidents for Snaps in the last 30 days.
Severity Breakdown:
Tired of searching for status updates?
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowComponents and Services Monitored for Snaps
Outlogger tracks the status of these components for Xero:
| Component | Status |
|---|---|
| Snaps Platform | Active |
Latest Snaps outages and incidents.
View the latest incidents for Snaps and check for official updates:
Google Dialogflow Outage
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: Oct. 2, 2023, 9:03 p.m.
Updates:
-
Time: Oct. 3, 2023, 1:16 p.m.Status: ResolvedUpdate: This incident has been resolved.
-
Time: Oct. 2, 2023, 9:15 p.m.Status: MonitoringUpdate: The issue appears to be resolved. Functionality was degraded from 3:33pm to 4:49pm EST. We are waiting for confirmation from Google before we consider this incident closed.
-
Time: Oct. 2, 2023, 9:03 p.m.Status: InvestigatingUpdate: Google Dialogflow is experiencing failures which are affecting Quiq. Bots that use NLU are slow to respond and may fall back to default responses. We are taking steps to reduce the impact, and monitoring the situation. We will update when more information is availble.
AWS US-East Lambda Partial Outage
Description: This incident with AWS has been resolved and everything is operational.
Status: Resolved
Impact: None | Started At: June 13, 2023, 9:21 p.m.
Updates:
-
Time: June 13, 2023, 9:42 p.m.Status: ResolvedUpdate: This incident with AWS has been resolved and everything is operational.
-
Time: June 13, 2023, 9:21 p.m.Status: IdentifiedUpdate: Amazon Web Services Lambdas are not responding in Virginia regions. Bots are functional. Some Quiq features will not be available. Will impact customers with third-party CRM integrations. More updates soon.
Intermittent Bot Responses
Description: On October 3rd, 2022 from 10:06am through 11:02am Eastern time, we experienced intermittent increased latency to our Snaps' services. Snaps' bots were slow to respond and for some users became unresponsive. This was due to a background process requiring abnormally large resources. The issue was identified and has been resolved.
Status: Resolved
Impact: None | Started At: Oct. 3, 2022, 3:30 p.m.
Updates:
-
Time: Oct. 3, 2022, 3:30 p.m.Status: ResolvedUpdate: On October 3rd, 2022 from 10:06am through 11:02am Eastern time, we experienced intermittent increased latency to our Snaps' services. Snaps' bots were slow to respond and for some users became unresponsive. This was due to a background process requiring abnormally large resources. The issue was identified and has been resolved.
Proactive notifications disruption
Description: From 1:16PM until 3:33PM on June 21st 2022, we experienced a connectivity issue with a backend service that caused proactive notifications to fail to be picked up. All non proactive bot interactions continued to operate without disruption. Our alerting failed to recognize this scenario and we are investigating strategies to identify this issue more quickly in the future.
Status: Resolved
Impact: Minor | Started At: June 21, 2022, 8:06 p.m.
Updates:
-
Time: June 21, 2022, 8:06 p.m.Status: ResolvedUpdate: From 1:16PM until 3:33PM on June 21st 2022, we experienced a connectivity issue with a backend service that caused proactive notifications to fail to be picked up. All non proactive bot interactions continued to operate without disruption. Our alerting failed to recognize this scenario and we are investigating strategies to identify this issue more quickly in the future.
As of 11:52AM ET - bots are responding slowly.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: April 11, 2022, 4:49 p.m.
Updates:
-
Time: April 11, 2022, 6:03 p.m.Status: ResolvedUpdate: This incident has been resolved.
-
Time: April 11, 2022, 5:03 p.m.Status: MonitoringUpdate: An auto scaling configuration was changed for a new deployment we made and this caused our servers to have more than normal latency. Performance is back to normal, and we will continue to monitor the situation.
-
Time: April 11, 2022, 4:49 p.m.Status: IdentifiedUpdate: We are working to resolve the issue.
