Toast API had 22 outages in the last 2 years totaling 84h 7m of downtime — averaging 0.9 incidents per month.
There were 22 Toast API outages since August 2, 2024 totaling 84h 7m of downtime. Each is summarised below — incident details, duration, and resolution information.
From about 12:18PM EDT to 4:02PM EDT, a subset of Orders Webhooks were not delivered. The issue has been resolved and webhooks are functioning correctly now.
We have identified an issue that may result in 500 error responses for requests made to our Orders API. Our team is actively investigating and will provide updates here as we learn more.
We have implemented a fix that has resolved the 500 errors on order requests. We are continuing to investigate issues with delayed publishing.
This incident has been resolved.
The bulk orders endpoint was unavailable for a small subset of partners today, March 10, from about 1:31-1:41PM ET. Service has been restored.
Between October 7 and November 4 of this year, the AppliedTaxRate.taxAmount and Selection.tax of ordersBulk responses were rounded incorrectly and could have been off by a cent at the check selection level of the API response. If your integration consumes this information at the selection level, your customers may have been impacted. To identify impacted customers, examine the Order.pricingFeatures array in the orders response. If this array is empty for a customer, the customer was likely impacted. The issue has been fixed and the correct data can now be queried. If your integration consumes tax information only at the order and check level, you were not impacted by this issue.
Between approximately 3:30AM and 4:30AM EST, Toast APIs were unavailable due to an issue at a service provider. Functionality has been restored.
We are currently investigating an issue with third-party orders that flow through DoorDash. These orders will not be processed or sent to your POS devices. We will provide updates as we learn more.
This incident has been resolved.
The Orders API is currently down. All requests to the Orders API will return 503 errors. We're investigating the situation and will update here.
We are continuing to investigate this issue and will post updates here.
Our APIs will be returning 429s as capacity is scaled and systems are variously brought back online. We're leaving the incident as open and APIs an experiencing major outages.
All APIs are back online now, except for the Orders API. Endpoints in the Orders API will return 503 error responses for a while longer.
Our APIs have recovered and are fully available. We'll continue to monitor our systems.
This incident has been resolved.
The Config API is currently returning 500/error for most requests. We're investigating and will make updates here.
We are continuing to investigate this issue. We've noted as well that the /timeEntries endpoint is returning 500 failures.
We are consolidating our reported incidents and providing updates in the other, Orders incident. Subscribers will continue to get updates.
We have identified an issue that may result in 500 error responses for requests made to our Orders and Config APIs. Our team is actively investigating and will provide updates here as we learn more.
This incident has been resolved.
For a very short period of time between about 4:05AM and 4:20AM EST on Sept 22, several Toast APIs were down, resulting in 500 errors to requests. The problem has been identified and resolved.
For a very short period of time between about 1:55PM and 2:03PM EST on Sept 11, several Toast APIs were down, resulting in 500 errors to requests. The problem has been identified and resolved.
We're aware of an ongoing issue that is impacting all Toast APIs. Some requests to our APIs are failing. We're investigating and will provide updates as we have them.
This incident has been resolved.
We have identified an issue that could result in 502 error responses to requests to our APIs. We are investigating and will post updates here.
We have identified an issue that caused 502 error responses to a fraction of requests to our APIs. We will deploy a fix tomorrow, Wednesday, August 6th, aiming to resolve the issue by the end of that day.
We deployed the planned fix earlier today as scheduled. However, we are still observing 502 error responses affecting a portion of API requests. Our team is continuing to investigate the root cause and will provide further updates as we learn more.
The issue causing 502 error responses for some API requests has been fully resolved. All systems are now operating normally.
We are aware of an issue affecting the Stock API and are actively investigating the source. We are working to resolve this asap.
We are continuing to investigate this issue.
We have identified the problem, implemented a fix and are monitoring the results currently.
This incident has now been resolved.
A small number of Toast restaurants were intermittently unreachable via API for a short period between 11:27AM and 11:51AM EST. API service was restored and has been functioning normally since then.
We were notified of a disruption in Apple Pay payments. You may experience prolonged processing times, error messages, or denials on Apple Pay transactions. We are actively working to resolve the issue with our partners and will update this page as we receive more information. Please advise all servers and guests to attempt a different card or alternative payment method. https://central.toasttab.com/s/article/Taking-Payments
We have implemented a fix to resolve the issues surrounding Apple Pay transactions.
Between roughly 10:00PM EST and 10:10PM EST, a small number of Toast restaurants were unreachable via the Toast API. The situation is remedied and all operations are back to normal.
We have been alerted to system issues with the Toast API platform. Our engineers are investigating the cause and are working to resolve the issue as soon as possible. We will keep you updated as new information is available.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
From approximately 4:30AM EST to 9:30AM, a very small number of Orders Update webhooks events may not have been sent to ordering partners. The issue has been resolved.
An internal issue cause the Config and Orders APIs to return 500/errors for around 15 minutes starting at approximately 12:00PM EDT. The issue was resolved and no further errors should occur.
An internal issue cause the Config and Orders APIs to return 500/errors for around 5 minutes starting at approximately 3:46PM EDT. The issue was resolved and no further errors should occur.
Since approximately 11:00AM EST, the Orders API has been experiencing intermittent outages. Retrying a failed Order API request may prove successful. We'll keep this page updated with the incident status.
We are still investigating the issue.
This incident has been resolved.