Quiq System Status

All systems operational

Messaging Channels

SMS Operational
Quiq Web Chat Operational
Facebook Messenger Integration Operational
Twitter Direct Messaging Integration Operational
Apple Messaging Operational
Google RBM Operational
Google Verified SMS Operational
WhatsApp Integration Operational
Instagram Integration Operational
WeChat Integration Operational
Kik Integration Operational

Systems

AWS - U.S. West - Production Cluster (AOR1) Operational
AWS - U.S. West - Production Cluster (AOR3) Operational
AWS - U.S. East - Production Cluster (AVA1) Operational
AWS - Germany - Production Cluster Operational
Azure - U.S. - Production Cluster Operational
AWS - U.S. West - Demo Cluster Operational
AWS - U.S. West - Staging Cluster Operational

Subscribe to Updates

If you would like to be notified of future updates, please add your contact information using the form below. We will only notify you of issues and your information will not be used for offers or promotional purposes.

Report an Outage

Please only use this form to report significant, business-impacting outages of Quiq services (Severity 1 or Severity 2). Please email support@quiq.com with less critical errors or questions.
For a faster response, please provide your Quiq Tenant ID. This is the text that appears in your Quiq site URL, before '.goquiq.com'

Past Incidents

Azure Cluster Outage Outage
First reported Sep. 13, 2021 2:17 AM MT. Resolved Sep. 13, 2021 3:57 AM MT.
A scheduled update to the Azure cluster caused several nodes in the cluster to fail and not properly restart. The errant nodes had to reconfigured and redeployed to the cluster.
During this time, most Quiq services were unavailable to customers hosted on this cluster.
Quiq Virginia Cluster Partial Outage Partial Outage
First reported Jun. 7, 2021 12:36 PM MT. Resolved Jun. 7, 2021 1:02 PM MT.
A Quiq-external integration failed to process Quiq webhook notifications causing Quiq to buffer many webhook messages. Due to a long-standing coding error, these messages were buffered in memory rather than saved to an external queue, as designed. To preserve system integrity, the Quiq system automatically detected the error and stopped processing messages, queuing all data to prevent any data loss.
The issue was resolved by allocating more resources to the Virginia cluster and manually processing the problematic messages. No data was lost during this time, including customer messages.
Quiq is immediately publishing fixes to avoid unnecessarily loading webhook messages into memory, and making the system more resilient to webhook recipient errors.
Twilio SMS Outage Partial outage - SMS
First reported Feb. 28, 2021 6:06 AM MT. Resolved Feb. 28, 2021 8:55 AM MT.
Twilio experienced a full SMS outage during this time. All Quiq SMS traffic on Twilio was impacted during this outage window. Quiq utilizes multiple SMS carriers and many Quiq sites were not impacted.
Facebook Messenger Inbound Attachments Lost Partial outage
First reported November 20th, 2020 12:00 PM MDT. Resolved November 23rd, 2020 11:20 AM MDT.
Facebook Messenger has an issue with inbound images/attachments. Facebook is not passing the images/attachments on to its partner providers. Facebook has still not solved the root issue, but Quiq was able to work around their issue with a code update. For details see the bug report.
Assets (images) delayed upload Degraded Performance
First reported November 3, 2020 11:47 AM MDT. Resolved November 3, 2020 11:57 AM MDT.
Asset (pictures) retrieval from an external data source was experiencing high latency. The underlying latency issues were resolved and systems are fully operational again. This only affected users on one of Quiq's clusters in Oregon. No data was lost but image uploads were delayed.
Facebook Messenger Outage Partial outage
First reported August 6th, 2020 4:00 PM MDT. Resolved August 6th, 2020 7 PM MDT.
Facebook Messenger experienced an outage which therefore impacted Quiq's integration with Facebook Messenger. For details see the bug report.
Content Delivery Network (CDN) Failure Partial outage
First reported July 17, 2020 3:19 PM MDT. Resolved July 17, 2020 3:39 PM MDT.
Quiq's primary CDN provider, Cloudflare, experienced a widespread outage today. See Cloudflare Status. Quiq enacted our disaster recovery program, preparing to move all traffic to our alternative CDN. Cloudflare resolved their issues before this cutover was completed. During this time, users could not load Quiq. Existing sessions were not affected.
Facebook Integration Failure Partial outage
First reported March 4, 2020 10:29 AM MT. Resolved March 4, 2020 11:01 AM MT.
Facebook recently changed their Messaging APIs and broke Quiq's Facebook integration. Agents could not send or receive Facebook messages during this time. Quiq updated the relevant code to uptake this new API.
Quiq was aware of the API change and had made proactive modifications to the product. The actual Facebook API change was different than Quiq's expectations from Facebook.
Content Delivery Network (CDN) Failure Partial outage
First reported July 2, 2019 7:50 AM MDT. Resolved July 2, 2019 8:09 AM MDT.
Quiq's primary CDN provider, Cloudflare, experienced a widespread outage today. See Cloudflare Status. Quiq enacted our disaster recovery program, preparing to move all traffic to our alternative CDN. Cloudflare resolved their issues before this cutover was required. During this time, users could not log in to Quiq. Existing sessions were not affected.
Quiq Services Unavailable Service Outage for Oregon Cluster
First reported May 18, 2018 12:08 PM MDT. Resolved May 18, 2018 12:20 PM MDT.
Incorrect resource reservations for nodes in Oregon AWS ECS cluster causing cascading node failures. Resource reservations have been corrected.
Graphs Unavailable on Manager View Partial Outage
First reported Aug 21, 2017 10:40 PM MDT. Resolved Aug 22, 2017 9:00 AM MDT.
One of our vendors experienced an outage during this time. The underlying issue has been resolved.
Web chat - cannot open new chats Degraded Performance
First reported Aug 10, 2017 13:48 MDT. Resolved Aug 10, 2017 16:24 MDT.
This incident has been resolved.
Amazon Web Services - Twilio Outage Degraded Performance
First reported Feb 28, 2017 11:15 MDT. Resolved Feb 28, 2017 15:03 MDT.
Amazon Web Services is having failures in the US-EAST-1 region with S3. This is causing failures for Twilio. MMS will be delayed during this time. Twilio status page