Service Disruption
The issue affecting order creation on Square Point of Sale has been 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.
The latest update from Square.
State
Resolved
Started
41 d ago
2026-09-21 19:40 UTC
Lasted
2 days
until 2026-09-24 00:25 UTC
Worst impact
Degraded
Timeline
3 updatesIdentified
2 days 94%
Monitoring
3 h 7 min 6%
Updates
Times in UTCAs posted by Square
The issue affecting order creation on Square Point of Sale has been 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.
We have released a fix for Square Point of Sale and are beginning to see impacted services return to full functionality. Your business's ability to operate smoothly is our top priority, and our Engineering team is taking proactive steps to prevent similar incidents. Thank you for your understanding as we worked through this issue.
We are continuing to work on a fix for Square Point of Sale. Some Sellers will experience a disruption with saving open orders on iOS. We understand how important it is for all of our services to be running for your business, we'll be back with further updates as they come to hand. Thank you for your patience with us as we work 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