Thanx Outage History

Started Oct 23, 2026, 11:59 PM UTC· resolved Oct 24, 2026, 12:04 AM UTC

1. monitoring Oct 23, 2026, 11:59 PM UTC

   We noticed some latent ordering experiences in the app and on web ordering. Our engineering team took action to restore these services, and ordering is loading normally again. We're continuing to monitor to make sure there are no further issues.

2. resolved Oct 24, 2026, 12:04 AM UTC

   Our engineering team has confirmed the issue as resolved.

Read the full incident report →

Started Aug 21, 2026, 06:39 PM UTC· resolved Aug 27, 2026, 12:04 AM UTC

1. identified Aug 21, 2026, 06:39 PM UTC

   We're aware of a delay affecting the availability of the latest reporting data in the dashboard, currently running a few hours behind. No data has been lost. This may also cause campaign audience targeting to reflect slightly delayed customer activity on automated campaigns. However, scheduled one-time campaigns are still sending on time. Our engineering team has identified the cause and is actively working to close the gap.

2. monitoring Aug 22, 2026, 11:43 AM UTC

   The delay affecting availability of latest reporting data has been resolved. We are actively monitoring to see if this holds over a longer period of time before marking this as resolved.

3. resolved Aug 27, 2026, 12:04 AM UTC

   The delay was kept at an acceptable level and has since subsided; the issue is resolved.

Read the full incident report →

Started Jul 21, 2026, 11:36 AM UTC· resolved Jul 21, 2026, 01:07 PM UTC

1. identified Jul 21, 2026, 11:36 AM UTC

   We are currently investigating a platform-wide issue affecting ordering and have identified the root cause. Our team is actively working on resolution.

2. identified Jul 21, 2026, 11:41 AM UTC

   A fix is being deployed right now.

3. resolved Jul 21, 2026, 01:07 PM UTC

   The incident has been resolved.

Read the full incident report →

Started May 08, 2026, 03:03 AM UTC· resolved May 09, 2026, 08:09 AM UTC

1. investigating May 08, 2026, 03:03 AM UTC

   A subset of orders may be experiencing slow or failed checkout due to an upstream AWS networking issue affecting one availability zone in us-east-1. Most orders are unaffected. AWS health status: https://health.aws.amazon.com/health/status. We're monitoring and will update as the upstream issue resolves.

2. monitoring May 08, 2026, 03:52 PM UTC

   The AWS team is continuing to work toward full restoration of the use1-az4 data center. We are not seeing a large volume of platform issues, but will keep this incident open until AWS confirms full restoration.

3. resolved May 09, 2026, 08:09 AM UTC

   The AWS team has confirmed that the incident has been resolved. See https://health.aws.amazon.com/health/status for details

Read the full incident report →

Started Mar 25, 2026, 08:32 PM UTC· resolved Mar 31, 2026, 01:01 AM UTC

1. investigating Mar 25, 2026, 08:32 PM UTC

   We are aware of delays affecting transactional emails (login links, signup confirmations) to Yahoo, AOL, and AT&T email addresses, and have escalated to Yahoo teams to investigate and resolve.

2. investigating Mar 25, 2026, 09:01 PM UTC

   We've identified an issue causing delays in transactional emails (receipts, rewards, and account notifications) for customers with Yahoo email addresses. Our engineering team has identified the root cause and has taken steps to mitigate it. We are actively working with Yahoo to restore normal email delivery as quickly as possible. We'll continue to post updates here as we make progress.

3. monitoring Mar 26, 2026, 10:03 PM UTC

   We've seen a significant drop in latency for Yahoo users receiving emails. Less than 5% of users are still seeing more than a minute delay in receiving emails. We are continuing to monitor the progress and will provide an update once this is fully resolved.

4. resolved Mar 31, 2026, 01:01 AM UTC

   Transactional email delivery to Yahoo and AOL addresses has been fully restored and is operating normally. Guests should no longer experience any delays with these emails.

Read the full incident report →

Started Feb 25, 2026, 04:58 PM UTC· resolved Feb 25, 2026, 05:28 PM UTC

1. investigating Feb 25, 2026, 04:58 PM UTC

   We're aware of an issue affecting the synchronization of menu availability and location status from ordering partner systems to the Thanx ordering experience. Some items marked as unavailable may still appear available, and some enabled locations may not display correctly. Our engineering team is actively investigating and working to resolve the issue. We'll continue to post updates here until full sync functionality is restored. We apologize for the inconvenience.

2. investigating Feb 25, 2026, 04:59 PM UTC

   We've made a fix that resolves the issue with unavailable items still displaying. We are continuing to investigate the root cause, as well as identifying a fix for location statuses.

3. resolved Feb 25, 2026, 05:28 PM UTC

   We have confirmed that the issues regarding item availability and location state displays have been resolved. We've added new logs and will continue to monitor to ensure no future disruption around availability syncing.

Read the full incident report →

Started Feb 15, 2026, 01:22 AM UTC· resolved Feb 16, 2026, 07:09 PM UTC

1. investigating Feb 15, 2026, 01:22 AM UTC

   We are currently investigating an issue affecting the newest versions of our mobile app (v47.13.0 on iOS and v47.13.1 on Android) where certain content blocks may not be clickable. This issue does not impact ordering or checkout functionality. Our team is actively working on a fix and expects an updated app version to be available before the end of next week. Guests using older versions of the app are not affected. We appreciate your patience and will continue to share updates as they become available.

2. resolved Feb 16, 2026, 07:09 PM UTC

   We have pushed out new releases for both Android (v47.14.1) and iOS (v47.14.0), which have fixed the issues with the content blocks. Guests will be directed to the correct ordering menu category when they click a content block in the app.

Read the full incident report →

Started Feb 04, 2026, 05:03 PM UTC· resolved Feb 04, 2026, 05:22 PM UTC

1. investigating Feb 04, 2026, 05:03 PM UTC

   We’re aware that https://www.thanx.com is currently down and are investigating the issue. Ordering websites are not impacted.

2. identified Feb 04, 2026, 05:20 PM UTC

   Our upstream network provider, Cloudflare, is currently experiencing an issue. See their status page for updates: https://www.cloudflarestatus.com

3. resolved Feb 04, 2026, 05:22 PM UTC

   Cloudflare has rolled out a fix, and the site is back up.

Read the full incident report →

Started Jan 19, 2026, 05:35 PM UTC· resolved Jan 19, 2026, 05:36 PM UTC

1. investigating Jan 19, 2026, 05:35 PM UTC

   We are currently investigating an issue causing the Merchant Dashboard to load as a blank page for some merchants. Our team is actively working to identify the root cause and restore full functionality as quickly as possible.

2. resolved Jan 19, 2026, 05:36 PM UTC

   The issue has been identified and resolved. The dashboard is now loading normally for all users.

Read the full incident report →

Started Jan 09, 2026, 08:29 PM UTC· resolved Jan 10, 2026, 04:43 AM UTC

1. investigating Jan 09, 2026, 08:29 PM UTC

   We are currently experiencing an issue with scheduled Toast Online Ordering delivery orders (orders scheduled as ASAP are not experiencing issues). Guests may not be able to place an order for locations using UberDirect or DoorDash for their delivery provider. Our team is actively investigating the issue.

2. monitoring Jan 09, 2026, 08:33 PM UTC

   We've pushed out a fix to this issue and are actively monitoring to ensure there are no more delivery order errors.

3. resolved Jan 10, 2026, 04:43 AM UTC

   The issue impacting scheduled Toast Online Ordering delivery orders has been resolved. A fix has been deployed, and we are no longer seeing delivery order errors for locations using Uber Direct or DoorDash. Our team will continue to monitor to ensure continued stability.

Read the full incident report →

Started Jan 07, 2026, 09:39 PM UTC· resolved Jan 08, 2026, 12:27 AM UTC

1. investigating Jan 07, 2026, 09:39 PM UTC

   We are observing delays to our analytics and targeting for ordering-related data. The root cause appears to be due to an internal AWS infrastructure bug. The AWS database team is currently investigating the issue.

2. resolved Jan 08, 2026, 12:27 AM UTC

   The AWS team was able to resolve the underlying issue, and we are no longer observing any latency in order reporting or targeting. Please refresh the dashboard to view updated reports.

Read the full incident report →

Started Oct 22, 2025, 07:32 PM UTC· resolved Oct 22, 2025, 08:38 PM UTC

1. resolved Oct 22, 2025, 07:32 PM UTC

   The issue affecting reward redemptions at some Toast-integrated locations has been resolved. Guests can now redeem rewards normally, and all systems are operating as expected. We’ll continue monitoring to ensure everything remains stable.

2. investigating Oct 22, 2025, 07:32 PM UTC

   We’re currently investigating an issue affecting reward redemptions at a subset of Toast-integrated locations. Guests at these locations may be unable to redeem rewards at the point of sale. Our team has identified a potential fix and is working to implement it as quickly as possible. We’ll continue to monitor closely and will provide another update once the fix has been deployed and validated.

3. resolved Oct 22, 2025, 08:38 PM UTC

   This issue has been resolved

Read the full incident report →

Started Oct 20, 2025, 02:04 PM UTC· resolved Oct 21, 2025, 03:19 AM UTC

1. identified Oct 20, 2025, 02:04 PM UTC

   Due to the AWS outage, Thanx is experiencing a full platform outage. See https://health.aws.amazon.com/health/status for more details. We’ll update this page as we learn more

2. monitoring Oct 20, 2025, 04:13 PM UTC

   The AWS team has identified the root cause and is in the process of mitigating the service outage. We're continuing to monitor the situation and will post an update when we have more information.

3. monitoring Oct 20, 2025, 05:26 PM UTC

   The AWS team is actively working on mitigation for the AWS platform outage. You can review specific actions the AWS team is taking at https://health.aws.amazon.com/health/status. We will continue to monitor the situation and provide an update as soon as we learn more.

4. monitoring Oct 20, 2025, 08:36 PM UTC

   The AWS team has reported improved service stability. We are seeing the Thanx platform begin to recover and are still monitoring the situation. See https://health.aws.amazon.com/health/status for additional details

5. resolved Oct 21, 2025, 03:19 AM UTC

   The AWS service disruption has been fully resolved. All Thanx systems have recovered, and functionality across our platform is operating normally.

Read the full incident report →

Started Oct 10, 2025, 05:05 PM UTC· resolved Oct 10, 2025, 05:32 PM UTC

1. investigating Oct 10, 2025, 05:05 PM UTC

   Web ordering authentication is degraded, so guests may be unable to log in to their accounts. Our team is working on a fix to resolve the issue as quickly as possible.

2. resolved Oct 10, 2025, 05:32 PM UTC

   This has been resolved, so guests will not encounter issues logging into the web experience.

Read the full incident report →

Started Sep 10, 2025, 07:35 PM UTC· resolved Sep 10, 2025, 08:40 PM UTC

1. investigating Sep 10, 2025, 07:35 PM UTC

   We're currently experiencing a reporting delay in our data platform and are investigating.

2. resolved Sep 10, 2025, 08:40 PM UTC

   Our reporting systems have caught up and is now operating within normal parameters.

Read the full incident report →

Started Aug 25, 2025, 08:57 PM UTC· resolved Sep 06, 2025, 01:24 AM UTC

1. investigating Aug 25, 2025, 08:57 PM UTC

   We are investigating reports of loyalty timeout errors impacting Olo customers. Thanx has escalated this and is coordinating with Olo ti diagnose the issue.

2. investigating Aug 26, 2025, 05:48 PM UTC

   Our team is continuing to urgently investigate the issue. We are in close communication with the Olo team. We will post an update as soon as we have a material update on this situation.

3. resolved Aug 28, 2025, 05:19 AM UTC

   We are closing this incident as there is not evidence of anything wrong with the Thanx platform. That said, we are continuing to escalate this with Olo and gather more information as customers continue to report elevated instances of "loyalty response timeouts". Thanx engineering has completed a detailed review of the past 24 hours of network traffic during which Olo continues to report elevated loyalty response timeouts. Based on Cloudflare network logs (the lowest level of our infrastructure stack), Thanx systems have remained healthy, with only 0.002% of requests taking longer than 5 seconds (the definition of a "timeout"). Nearly 20% of the internet's traffic runs through Cloudflare so we consider this a reliable indicator of our platform stability.

4. investigating Aug 29, 2025, 08:18 PM UTC

   There is an intermittent issue impacting some loyalty orders through the Olo <> Thanx integration. A small subset of guests may experience order failures due to “loyalty response timeouts". Thanx and Olo are actively engaged at the highest levels to resolve this. We will provide updates as we learn more. You can continue to track this issue on the Olo Status page status.olo.com or continue to monitor here.

5. monitoring Sep 02, 2025, 09:13 PM UTC

   The intermittent errors through the Thanx <> Olo integration have subsided substantially over the last 72 hours. We're currently observing normal behavior between the systems and continue to monitor the situation.Olo and Thanx are still actively engaged at the highest levels to resolve this. We will continue provide updates as we learn more. You can continue to monitor here or via the Olo status page at status.olo.com.

6. monitoring Sep 04, 2025, 05:00 AM UTC

   We observed a minor spike of intermittent loyalty response timeouts between 17:00:00 UTC and 17:19:57 UTC on Sep 3. Thanx engineering has confirmed that our systems remain healthy, and we are actively engaged with the Cloudflare team to diagnose the situation. At this time, we are observing normal behavior between the systems. We remain in close communication with both Olo and Cloudflare and will continue to provide updates here as we learn more. You can continue to monitor here or via the Olo status page at status.olo.com.

7. resolved Sep 06, 2025, 01:24 AM UTC

   The intermittent errors through the Olo <> Thanx integration have subsided substantially over the last week, we're still observing improved behavior between the systems and continue to monitor the situation. Thanx and Olo are still actively engaged at the highest levels to resolve this. We will provide updates as we learn more. You can continue to track this issue on the Olo Status page status.olo.com or continue to monitor here.

Read the full incident report →

Started Aug 21, 2025, 06:59 PM UTC· resolved Aug 21, 2025, 09:06 PM UTC

1. investigating Aug 21, 2025, 06:59 PM UTC

   We are experiencing delays in Thanx ordering experiences. Our team is actively investigating this issue and will provide further updates when we have more details.

2. identified Aug 21, 2025, 07:10 PM UTC

   Ordering services have been improved, but we are continuing to monitor performance. The temporary performance issue has been caused by an operational issue with the AWS platform. More details on AWS performance can be found here: https://health.aws.amazon.com/health/status

3. resolved Aug 21, 2025, 09:06 PM UTC

   We are no longer seeing platform issues and AWS has reported that the underlying networking issues have been resolved. See https://health.aws.amazon.com/health/status for additional details under the incident entitled "Operational issue - AWS Internet Connectivity (N. Virginia)".

Read the full incident report →

Started Aug 19, 2025, 08:40 PM UTC· resolved Aug 19, 2025, 10:23 PM UTC

1. investigating Aug 19, 2025, 08:40 PM UTC

   Users who have already encountered this issue will need to reinstall the app in order to receive the latest fix. We are releasing a patch update that will automatically prompt affected users to update (which will reinstall the app and resolve the issue). Until that update is available in the app stores, impacted users may continue to experience the issue.

2. identified Aug 19, 2025, 08:40 PM UTC

   We have identified an issue impacting version 45.3.1 on both iOS and Android. Our team is actively working on a new release to resolve the problem as soon as possible.

3. resolved Aug 19, 2025, 10:23 PM UTC

   We've pushed out a new version (45.5.2) to the App Stores that will fully resolve the issue and is expected to be available in both app stores over the next 1 to 2 days. As mentioned before, if guests reinstall version 45.3.1 on their device, they will no longer experience the issue.

Read the full incident report →

Started Aug 12, 2025, 03:44 PM UTC· resolved Aug 12, 2025, 04:17 PM UTC

1. investigating Aug 12, 2025, 03:44 PM UTC

   We've discovered an issue with handoff modes in Toast ordering and are actively investigating the issue.

2. resolved Aug 12, 2025, 04:17 PM UTC

   We have identified the root cause and implemented a fix. Handoff modes in Toast ordering are now functioning as expected, and no further impact is anticipated.

Read the full incident report →

Started Aug 01, 2025, 07:56 PM UTC· resolved Aug 01, 2025, 09:56 PM UTC

1. investigating Aug 01, 2025, 07:56 PM UTC

   We’re currently experiencing elevated latency with certain campaign issuance workloads, which is causing delays in email deliveries. Our team is actively investigating and working to resolve this with urgency.

2. resolved Aug 01, 2025, 09:56 PM UTC

   The issue has been resolved - all delayed emails and push notifications have been sent out. Our team is doing a deeper investigation to ensure we don't experience this going forward.

Read the full incident report →

Started Jul 03, 2025, 05:17 PM UTC· resolved Jul 03, 2025, 05:17 PM UTC

1. resolved Jul 03, 2025, 05:17 PM UTC

   From 9:20 AM to 9:55 AM PT, our Smart Link service experienced a spike in minor DDoS activity, which caused temporary timeouts when users interacted with Smart Links via link.thanx.com. This did not impact any authentication emails, but users who received marketing emails during this period may have encountered brief request timeouts when clicking links. The issue was mitigated quickly, and the service is now fully operational.

Read the full incident report →

Started Jun 05, 2025, 08:11 PM UTC· resolved Jun 06, 2025, 01:26 AM UTC

1. identified Jun 05, 2025, 08:11 PM UTC

   We've identified a data delay in our dashboard reporting and campaign targeting. After investigation, we are seeing the delay catch up and expect currently for the data to be fully caught up by midnight PST. We'll closely monitor till our data is fully caught up

2. resolved Jun 06, 2025, 01:26 AM UTC

   Database replication has fully caught up and all reporting data is up to date.

Read the full incident report →

Started May 05, 2025, 10:46 PM UTC· resolved May 05, 2025, 10:46 PM UTC

1. resolved May 05, 2025, 10:46 PM UTC

   Between 12:05pm and 2:30pm PT, some orders were unable to be placed and returned errors related to card registration failures. This issue has now been resolved. Our team is continuing to monitor and will be investigating insulation to avoid card registration issues going forward.

Read the full incident report →

Started Apr 30, 2025, 05:53 PM UTC· resolved Apr 30, 2025, 10:37 PM UTC

1. investigating Apr 30, 2025, 05:53 PM UTC

   We are seeing an elevated number of errors from American Express APIs affecting card enrollments. We are investigating this issue with American Express.

2. resolved Apr 30, 2025, 10:37 PM UTC

   The issue has been resolved by the Amax team.

Read the full incident report →

Started Apr 21, 2025, 04:40 PM UTC· resolved Apr 21, 2025, 04:40 PM UTC

1. resolved Apr 21, 2025, 04:40 PM UTC

   Our application observed increased robot traffic and a temporary downtime at 11:32-11:44 and 12:09-12:20 UTC. Our platform has since autocorrected and we have tightened our existing non-human traffic protection as a response and actively monitoring traffic

Read the full incident report →