Live

Scheduled maintenance for TWINT

MaintenanceOfficial update

TWINT has an upcoming scheduled maintenance. Note: Stripe retrieves payment method planned maintenance information from payment method partners and the information may not be complete, accurate, or up to date.

The latest update from Stripe.

State

Scheduled

Starts

in 3 d

2026-11-05 03:00 UTC

Ongoing for

Not started

Worst impact

Maintenance

Updates

Times in UTC

As posted by Stripe

Scheduled2026-11-01 17:39 UTC

TWINT has an upcoming scheduled maintenance. Note: Stripe retrieves payment method planned maintenance information from payment method partners and the information may not be complete, accurate, or up to date.

Affected components

1
Acquirers and payment methods

Follow Stripe

Your coding agent knows when Stripe is down, and tells you when a failure is theirs, not yours. You can also get Stripe incidents in a feed reader or in Slack.

Prompt
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 "stripe" and tell me if Stripe 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.

RSS
https://outages.cc/feed.xml?providers=stripe
Slack
/feed subscribe https://outages.cc/feed.xml?providers=stripe

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane