TWINT outages and problems
In the past 24 hours, 43 user reports came in for TWINT. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 100.00% uptime for the day.
The busiest 15-minute window had 3 reports, about 9 hours ago. That stays below our outage threshold, so it doesn't count as downtime.
What TWINT's status page says
Checking www.twint.ch…
What people can report about TWINT
What went wrong
What people said was wrong in recent problem reports for TWINT.
Share of 10 recent reports that said what was wrong.
TWINT problem spikes, last 30 days
Since 5 October, TWINT had 1 outage spike.
- Sat 3 Oct: no data
- Sun 4 Oct: no data
- Mon 5 Oct: 8 reports
- Tue 6 Oct: 13 reports
- Wed 7 Oct: 21 reports
- Thu 8 Oct: 43 reports
- Fri 9 Oct: 25 reports
- Sat 10 Oct: 43 reports
- Sun 11 Oct: 22 reports
- Mon 12 Oct: 21 reports
- Tue 13 Oct: 61 reports
- Wed 14 Oct: 39 reports
- Thu 15 Oct: 29 reports
- Fri 16 Oct: 46 reports
- Sat 17 Oct: 29 reports
- Sun 18 Oct: 22 reports
- Mon 19 Oct: 12 reports
- Tue 20 Oct: 27 reports
- Wed 21 Oct: no data
- Thu 22 Oct: 3 reports
- Fri 23 Oct: 38 reports
- Sat 24 Oct: 28 reports
- Sun 25 Oct: 26 reports
- Mon 26 Oct: 19 reports
- Tue 27 Oct: 13 reports
- Wed 28 Oct: 20 reports
- Thu 29 Oct: 220 reports (outage spike that day)
- Fri 30 Oct: 40 reports
- Sat 31 Oct: 42 reports
- Sun 1 Nov: no data
-
Outage
Thu 29 Oct, 06:37–08:09Lasted 1 h 32 min35peak reports
A spike is a sharp rise in problem reports from users, kept exactly as this page showed it at the time. This history starts on 5 October 2026. Monthly reports for all services
How to fix TWINT not working
TWINT is up on our end, so if it won't work for you, the problem is most likely on your side. Work through these in order:
Check your connection and restart the app
TWINT needs a working data connection, so switch between Wi-Fi and mobile data and try again. If the app still hangs on the loading screen, close it fully from the app switcher and reopen it.
Look at the official status page
The service itself can be down while your phone and settings are fine. Check the official status page at https://www.twint.ch/en/status/ before you spend more time on your own setup. On this site, the status at the top of the page shows whether problem reports are above their usual level, counted in 15-minute windows over the last 24 hours.
Confirm your bank link and balance
Open the app, go to your profile, and check that your bank account or prepaid credit is still linked and has funds available. If your bank shows as disconnected, reconnect it there, since bank-side reauthorisations are a common cause of failed payments. If you use prepaid, top up at a sales point that carries TWINT credit.
Update the app or reinstall it
An outdated app can break logins and payments after a server-side change, so install the latest version from the App Store or Google Play. If that changes nothing, back up your data where the app offers it, then delete the app and reinstall it, and register again with your mobile number and password. If the problem survives a reinstall, use the help centre at https://twint.ch/en/help/.
While TWINT is down: what to use instead
- Card at the terminal At a shop till, tap or insert your debit or credit card on the same terminal, because the card payment runs over the card network and does not depend on the app.
- Apple Pay or Google Pay If your bank card is already stored in your phone wallet, you can still pay by phone at contactless terminals and in many online shops.
- E-banking transfer To pay back a friend or settle an invoice, send the money from your bank's e-banking app with their IBAN; it arrives slower but has nothing to do with the service.
- Cash Cash still works at a market stall or a farm shop that only takes mobile payments when nothing is broken.
Fix TWINT on Windows, Mac, Android and iPhone
TWINT on Windows
- Fix
- Clear your browser cache and disable any active VPNs that might block secure Twint payment gateways. Try using a different browser to load the Twint QR checkout code.
- Check
- Check if Twint is down on Windows by loading a merchant's Twint payment gateway or visiting the official Twint status page. If the QR code fails to generate while other sites work, Twint may be offline.
ping twint.chTest whether Twint's servers replynslookup twint.chCheck that Twint's DNS resolvestracert twint.chTrace where the connection dropsipconfig /flushdnsClear the DNS cache, then reloadTWINT on Mac
- Fix
- Disable content blockers or VPNs in Safari or Chrome that might prevent Twint payment screens from loading. You can also try completing the Twint transaction in an incognito window.
- Check
- Verify if Twint is experiencing issues on Mac by checking if online shop checkout pages can successfully render the Twint payment QR code. Alternatively, visit the Twint status portal to check for active outages.
ping -c 4 twint.chTest whether Twint's servers replynslookup twint.chCheck that Twint's DNS resolvestraceroute twint.chTrace where the connection dropssudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderFlush the macOS DNS cache, then reloadTWINT on Android
- Fix
- Fix Twint on Android by clearing the app's cache in your system settings and updating the app via the Google Play Store. Switching from Wi-Fi to mobile data can also resolve connection issues.
- Check
- To tell if Twint is down on Android, open the app and check if it fails to load your account details or displays connection errors. You can also check for service status updates on the Google Play Store page.
TWINT on iPhone and iPad
- Fix
- Fix Twint on iOS by updating the app through the App Store and restarting your iPhone. If the app still fails, try toggling your internet connection or reinstalling the Twint app.
- Check
- Check if Twint is down on iOS by opening the app and looking for connection timeout errors. You can also check the App Store reviews or the official Twint support page for service status.
Problems at the same time as TWINT
Since 5 October, TWINT's only spike in problem reports overlapped a spike at another service.
When several services get problem reports at once, something they share, such as a cloud host or a network, can be the real cause. Matching times alone do not prove it.
During the latest spike
TWINT: Thu 29 Oct, 06:37 to 08:09
- ESPN Fantasy Football, outage,27 Oct 19:50 to 30 Oct 05:40
- IRCTC, outage,05:30 to 08:55
- Union Bank, outage,05:47 to 12:19
- Archive of Our Own, outage,05:52 to 07:02, 07:55 to 1 Nov 00:04
- Discord, outage,05:58 to 07:32, 07:50 to 08:16
- Globe, outage,3 spikes, 06:24 to 08:18
- Globe At Home, outage,06:30 to 06:52, 07:59 to 08:20
- WOW, outage,06:30 to 06:58
40 more services. Red dot: outage. Amber dot: elevated reports.
A spike is a sharp rise in problem reports from users, as the live pages showed it. Times are Central European time.
When people report TWINT problems
The busiest hour for reports about TWINT is 12:00 to 13:00 Central European time, and the busiest day is Thursday.
By hour of the day
- 00:00 to 01:00: 0.29 reports on an average day
- 01:00 to 02:00: 0.31 reports on an average day
- 02:00 to 03:00: 0.09 reports on an average day
- 03:00 to 04:00: 0.03 reports on an average day
- 04:00 to 05:00: 0.08 reports on an average day
- 05:00 to 06:00: 0.56 reports on an average day
- 06:00 to 07:00: 1.9 reports on an average day
- 07:00 to 08:00: 0.79 reports on an average day
- 08:00 to 09:00: 1.3 reports on an average day
- 09:00 to 10:00: 1.8 reports on an average day
- 10:00 to 11:00: 1.4 reports on an average day
- 11:00 to 12:00: 2.4 reports on an average day
- 12:00 to 13:00: 3.4 reports on an average day
- 13:00 to 14:00: 2.6 reports on an average day
- 14:00 to 15:00: 2.3 reports on an average day
- 15:00 to 16:00: 2.3 reports on an average day
- 16:00 to 17:00: 2.2 reports on an average day
- 17:00 to 18:00: 2.1 reports on an average day
- 18:00 to 19:00: 1.6 reports on an average day
- 19:00 to 20:00: 1.1 reports on an average day
- 20:00 to 21:00: 1.2 reports on an average day
- 21:00 to 22:00: 0.96 reports on an average day
- 22:00 to 23:00: 0.98 reports on an average day
- 23:00 to 00:00: 0.56 reports on an average day
By day of the week
- Monday: 18 reports on an average Monday
- Tuesday: 29 reports on an average Tuesday
- Wednesday: 27 reports on an average Wednesday
- Thursday: 58 reports on an average Thursday
- Friday: 37 reports on an average Friday
- Saturday: 36 reports on an average Saturday
- Sunday: 23 reports on an average Sunday
Each bar is the average number of user reports in that hour, or on that day of the week, from 24 days of reports since 5 October 2026. The busiest bar is highlighted. Spikes in reports are left out, so one outage does not set the pattern.
What happens when TWINT goes down
TWINT is the Swiss mobile payment app tied to your bank account, used for paying at checkout tills, settling up with friends, and buying online. When it goes down, you cannot send or receive money, and store payments fail at the till even though your card still works.
The first thing people notice is a failed QR code payment at a shop counter or a transfer that spins and then errors out. Loading the app itself usually still works, so the list of past transactions stays visible while anything requiring the network, like a peer-to-peer payment or an online checkout, refuses to complete. Larger problems tend to hit everyone at once because there is one shared backend, but smaller glitches are often partial: you might be able to send money while a friend's payment bounces, or one merchant's terminal fails while the next works fine. If it seems stuck, waiting a few minutes and retrying the same payment often settles it, and the official status page will show whether the service itself is having a bad day.
TWINT IP address, servers and network
- IPv4 addresses
- 104.20.29.33
Show all 2
- 172.66.158.215
- IPv6 addresses
- 2606:4700:10::6814:1d21
Show all 2
- 2606:4700:10::ac42:9ed7
- Network
- AS13335 · Cloudflare, Inc., registered in the United States
- Served through
- Cloudflare · our check was answered by its Amsterdam (AMS) data centre
- DNS hosted by
- Microsoft Azure DNS
- HTTPS certificate
- Issued by Let's Encrypt, valid until 14 Dec 2026 (43 days)
- HTTP/3
- Supported
- Our check
- Answered in 382 ms
Checked from our server in Frankfurt, Germany, 5 days ago, for www.twint.ch. A service behind a CDN answers from many data centres, usually the one nearest to you, so these addresses are where its traffic enters, not where its own servers stand. Visitors elsewhere may see different addresses.
Checked from 11 places around the world
All 11 locations got an answer from www.twint.ch. 7 of the answers turned the automated check away (HTTP 403), which many sites do with bots; the site itself was up. Fastest from São Paulo (33 ms), slowest from Milan (984 ms). Every location connected through Cloudflare, Inc. (AS13335), using 2 different addresses.
| Location | Result | Time | Address reached |
|---|---|---|---|
| FrankfurtGermany | Up | 984 ms | 172.66.158.215 |
| ViennaAustria | Up | 906 ms | 104.20.29.33 |
| MilanItaly | Up | 984 ms | 104.20.29.33 |
| ParisFrance | Up | 974 ms | 172.66.158.215 |
| AmsterdamNetherlands | Up · HTTP 403 | 59 ms | 104.20.29.33 |
| MadridSpain | Up · HTTP 403 | 56 ms | 104.20.29.33 |
| WarsawPoland | Up · HTTP 403 | 128 ms | 172.66.158.215 |
| Los AngelesUSA | Up · HTTP 403 | 124 ms | 104.20.29.33 |
| São PauloBrazil | Up · HTTP 403 | 33 ms | 104.20.29.33 |
| SingaporeSingapore | Up · HTTP 403 | 415 ms | 172.66.158.215 |
| TokyoJapan | Up · HTTP 403 | 60 ms | 172.66.158.215 |
Checked with check-host.net from its servers in these cities 5 days ago, for www.twint.ch. Time is how long each server took to load the page.
TWINT FAQ
Is TWINT down right now?
Why does my bank app or browser say TWINT was not detected when I try to pay?
My payment went through in the shop but the amount is stuck as pending in the TWINT app. Is that normal?
I get an error when registering my number in the TWINT app. What should I check first?
Can I use TWINT abroad, for example to pay in a foreign online shop?
Service updates from @TWINT_ch
No posts about problems from @TWINT_ch in the last 14 days. The latest is from .
How we track TWINT
The status on this page comes from user-submitted problem reports for TWINT, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for TWINT, so a few complaints on a quiet day don't trigger anything, but a sudden jump well above normal does.
When reports climb well above normal, the status here changes to partial outage or major outage and the chart moves with it. This is separate from TWINT's official status page: user reports tend to show a problem early, while the official page confirms the cause. If the two disagree, check both.