Toast API Outage History

Toast API is up right now

Toast API had 12 outages in the last 2 years totaling 80h 37m of downtime — averaging 0.5 incidents per month.

There were 12 Toast API outages since August 6, 2025 totaling 80h 37m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status-dev.toasttab.com

Major April 28, 2026

Possible 500 Error Responses

Detected by Pingoru
Apr 28, 2026, 11:56 PM UTC
Resolved
Apr 29, 2026, 01:22 AM UTC
Duration
1h 25m
Affected: Config APIOrder APIRestaurants API
Timeline · 3 updates
  1. investigating Apr 28, 2026, 11:56 PM UTC

    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.

  2. identified Apr 29, 2026, 12:34 AM UTC

    We have implemented a fix that has resolved the 500 errors on order requests. We are continuing to investigate issues with delayed publishing.

  3. resolved Apr 29, 2026, 01:22 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice December 8, 2025

Rounding error in some ordersBulk responses

Detected by Pingoru
Dec 08, 2025, 07:47 PM UTC
Resolved
Dec 08, 2025, 07:47 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Dec 08, 2025, 07:47 PM UTC

    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.

Read the full incident report →

Notice December 5, 2025

Toast API Downtime

Detected by Pingoru
Dec 05, 2025, 01:18 PM UTC
Resolved
Dec 05, 2025, 01:18 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Dec 05, 2025, 01:18 PM UTC

    Between approximately 3:30AM and 4:30AM EST, Toast APIs were unavailable due to an issue at a service provider. Functionality has been restored.

Read the full incident report →

Notice November 30, 2025

Third Party Ordering - DoorDash Outage

Detected by Pingoru
Nov 30, 2025, 12:04 AM UTC
Resolved
Nov 30, 2025, 01:33 AM UTC
Duration
1h 29m
Affected: Order API
Timeline · 2 updates
  1. investigating Nov 30, 2025, 12:04 AM UTC

    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.

  2. resolved Nov 30, 2025, 01:33 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical October 20, 2025

Orders API is failing

Detected by Pingoru
Oct 20, 2025, 07:34 PM UTC
Resolved
Oct 21, 2025, 12:07 PM UTC
Duration
16h 32m
Affected: Cash Management APIConfig APICredit Card APICRM APIGift Cards APILabor APILoyalty APIMenu APIOrder APIPartners API and WebhookRestaurants APIStock API and Webhook
Timeline · 6 updates
  1. investigating Oct 20, 2025, 07:34 PM UTC

    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.

  2. investigating Oct 20, 2025, 08:55 PM UTC

    We are continuing to investigate this issue and will post updates here.

  3. identified Oct 20, 2025, 09:43 PM UTC

    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.

  4. identified Oct 20, 2025, 11:33 PM UTC

    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.

  5. monitoring Oct 21, 2025, 12:08 AM UTC

    Our APIs have recovered and are fully available. We'll continue to monitor our systems.

  6. resolved Oct 21, 2025, 12:07 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical October 20, 2025

Config API returning 500/error

Detected by Pingoru
Oct 20, 2025, 12:30 PM UTC
Resolved
Oct 20, 2025, 09:42 PM UTC
Duration
9h 11m
Affected: Config APILabor API
Timeline · 3 updates
  1. investigating Oct 20, 2025, 12:30 PM UTC

    The Config API is currently returning 500/error for most requests. We're investigating and will make updates here.

  2. investigating Oct 20, 2025, 02:21 PM UTC

    We are continuing to investigate this issue. We've noted as well that the /timeEntries endpoint is returning 500 failures.

  3. resolved Oct 20, 2025, 09:42 PM UTC

    We are consolidating our reported incidents and providing updates in the other, Orders incident. Subscribers will continue to get updates.

Read the full incident report →

Minor October 3, 2025

Possible 500 error responses to API requests

Detected by Pingoru
Oct 03, 2025, 08:51 PM UTC
Resolved
Oct 03, 2025, 11:10 PM UTC
Duration
2h 19m
Affected: Config APIOrder API
Timeline · 2 updates
  1. investigating Oct 03, 2025, 08:51 PM UTC

    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.

  2. resolved Oct 03, 2025, 11:10 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice September 22, 2025

Brief API Downtime

Detected by Pingoru
Sep 22, 2025, 08:29 PM UTC
Resolved
Sep 22, 2025, 08:29 PM UTC
Duration
—
Affected: Partners API and Webhook
Timeline · 1 update
  1. resolved Sep 22, 2025, 08:29 PM UTC

    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.

Read the full incident report →

Notice September 11, 2025

Very brief API downtime

Detected by Pingoru
Sep 11, 2025, 06:51 PM UTC
Resolved
Sep 11, 2025, 06:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Sep 11, 2025, 06:51 PM UTC

    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.

Read the full incident report →

Notice August 21, 2025

Sporadic errors on Toast APIs

Detected by Pingoru
Aug 21, 2025, 07:04 PM UTC
Resolved
Aug 21, 2025, 09:19 PM UTC
Duration
2h 15m
Affected: Authentication APICash Management APIConfig APICredit Card APICRM APIGift Cards APILabor APILoyalty APIMenu APIOrder APIPartners API and WebhookRestaurants APIStock API and WebhookSandbox (All APIs)
Timeline · 2 updates
  1. investigating Aug 21, 2025, 07:04 PM UTC

    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.

  2. resolved Aug 21, 2025, 09:19 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 6, 2025

Possible 502 error responses to API requests

Detected by Pingoru
Aug 06, 2025, 08:43 PM UTC
Resolved
Aug 08, 2025, 08:06 PM UTC
Duration
1d 23h
Affected: Authentication APICash Management APIConfig APICredit Card APICRM APILabor APIMenu APIOrder APIPartners API and WebhookRestaurants APIStock API and Webhook
Timeline · 4 updates
  1. investigating Aug 05, 2025, 05:42 PM UTC

    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.

  2. identified Aug 05, 2025, 07:32 PM UTC

    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.

  3. investigating Aug 06, 2025, 08:43 PM UTC

    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.

  4. resolved Aug 08, 2025, 08:06 PM UTC

    The issue causing 502 error responses for some API requests has been fully resolved. All systems are now operating normally.

Read the full incident report →