Service Disruption
Square reports a disruption with Kitchen Display System and Orders. Square is investigating and reports that the Engineering team is working to resolve the issue.
State
Investigating
Started
Ongoing for
31 min
Worst impact
Degraded
Timeline
1 updateInvestigating
31 min 100%
Updates
Times in UTCAs posted by Square
We are currently experiencing a disruption with Kitchen Display System and Orders. Your business operations are our top priority and our Engineering team is working rapidly to resolve this issue. We appreciate your patience during this disruption.
Square in the last 90 days
Full historyIncidents in 90 days
19
Days with an incident
22
Median duration
1 h 18 min
This incident
60% shorter than the median
Other Square incidents
All incidentsSquare·Service Disruption
A disruption affects some Square services. Square reports that the incident is resolved. The disruption lasted about 6 minutes.
Square·Service Disruption
Square reported a disruption that affected some e-money transactions, including e-money card payments in Japan. Square says the incident is resolved. It lasted about 71 minutes.
Square·Service Disruption
Square services had a disruption that affected Payment Acceptance and Orders. Square released a fix and monitored the services. The incident is resolved. It lasted about 1 hour and 26 minutes.
Square·Service Disruption
The issue causing delays in orders syncing across devices, including orders reaching kitchen displays, is now resolved. Your business operations are essential to us, and our Engineering team has implemented measures to strengthen our systems against similar incidents. We appreciate your patience throughout this resolution process.
Square·Service Disruption
We recently experienced a disruption that impacted some Square services. We understand how important it is for all of our services to be running for your business, and our Engineering team is actively discussing how to prevent future disruptions like this one. Thank you for your patience with us as we worked to resolve this issue.
Follow Square
Your coding agent knows when Square is down, and tells you when a failure is theirs, not yours. You can also get Square incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "square" and tell me if Square has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=square/feed subscribe https://outages.cc/feed.xml?providers=squareFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane