Revolut Outage History
56 incidents recorded over the last 365 days, 55 of them resolved, 1 still open. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Revolut Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Aug 23, 2026 | Transfers — incident | — | Investigating |
| Aug 19, 2026 | Transfers — incident | 3h 34m | Resolved |
| Aug 18, 2026 | Sign Up — incident | 2h 8m | Resolved |
| Aug 14, 2026 | Card order — incident | 1h 54m | Resolved |
| Aug 14, 2026 | Transfers — incident | 3h 52m | Resolved |
| Aug 14, 2026 | Internal transfers — incident | 2h 54m | Resolved |
| Aug 4, 2026 | Transfers — incident | 62h 54m | Resolved |
| Aug 1, 2026 | Transfers — incident | 47h 37m | Resolved |
| Aug 1, 2026 | Premium — incident | 50h 20m | Resolved |
| Jul 30, 2026 | Card order — incident | 97h 34m | Resolved |
| Jul 30, 2026 | Premium — incident | 104h 18m | Resolved |
| Jul 28, 2026 | Topping up via bank card — incident | 149h 33m | Resolved |
| Jul 28, 2026 | Transfers — incident | 149h 51m | Resolved |
| Jul 27, 2026 | Premium — incident | 173h 32m | Resolved |
| Jul 27, 2026 | Transfers — incident | 177h 10m | Resolved |
| Jul 23, 2026 | Transfers — incident | 277h 38m | Resolved |
| Jul 20, 2026 | Credit — incident | 354h 0m | Resolved |
| Jul 15, 2026 | Transfers — incident | 469h 14m | Resolved |
| Jul 14, 2026 | Vault access — incident | 485h 41m | Resolved |
| Jul 6, 2026 | Stock trading — incident | 673h 34m | Resolved |
| Jul 6, 2026 | Transfers — incident | 677h 34m | Resolved |
| Jul 4, 2026 | Sign-up for Business — incident | 726h 48m | Resolved |
| Jul 2, 2026 | Stock trading — incident | 771h 35m | Resolved |
| Jul 2, 2026 | Transfers — incident | 774h 25m | Resolved |
| Jun 30, 2026 | Transfers — incident | 817h 40m | Resolved |
| Jun 30, 2026 | Transfers — incident | 819h 8m | Resolved |
| Jun 27, 2026 | Transfers — incident | 885h 28m | Resolved |
| Jun 25, 2026 | Sign Up — incident | 941h 4m | Resolved |
| Jun 25, 2026 | Credit — incident | 941h 4m | Resolved |
| Jun 25, 2026 | Transfers — incident | 941h 4m | Resolved |
| Jun 25, 2026 | Revolut Website — incident | 941h 4m | Resolved |
| Jun 25, 2026 | Identity Verification — incident | 941h 4m | Resolved |
| Jun 25, 2026 | Live support chat — incident | 941h 4m | Resolved |
| Jun 24, 2026 | RevPoints — incident | 970h 47m | Resolved |
| Jun 23, 2026 | Transfers — incident | 998h 38m | Resolved |
| Jun 19, 2026 | Topping up via bank card — incident | 1088h 44m | Resolved |
| Jun 17, 2026 | Card Payments — incident | 1138h 28m | Resolved |
| Jun 15, 2026 | Transfers — incident | 1177h 39m | Resolved |
| Jun 1, 2026 | Stock trading — incident | 1517h 19m | Resolved |
| Jun 1, 2026 | Transfers — incident | 1520h 50m | Resolved |
| May 28, 2026 | Stock trading — incident | 1610h 53m | Resolved |
| May 28, 2026 | Identity Verification — incident | 1618h 35m | Resolved |
| May 27, 2026 | Cryptocurrency access — incident | 1631h 16m | Resolved |
| May 27, 2026 | Transfers — incident | 1633h 34m | Resolved |
| May 27, 2026 | Transfers — incident | 1640h 52m | Resolved |
| May 26, 2026 | Transfers — incident | 1670h 34m | Resolved |
| May 25, 2026 | Cryptocurrency access — incident | 1681h 15m | Resolved |
| May 23, 2026 | Transfers — incident | 1743h 52m | Resolved |
| May 19, 2026 | Transfers — incident | 1839h 24m | Resolved |
| Apr 30, 2026 | Transfers — incident | 2288h 5m | Resolved |
| Apr 24, 2026 | Topping up via bank card — incident | 2435h 20m | Resolved |
| Apr 22, 2026 | Transfers — incident | 2486h 5m | Resolved |
| Apr 22, 2026 | Live support chat — incident | 2486h 5m | Resolved |
| Apr 22, 2026 | Internal transfers — incident | 2486h 24m | Resolved |
| Apr 19, 2026 | Transfers — incident | 2544h 49m | Resolved |
| Apr 8, 2026 | Stock trading — incident | 2820h 25m | Resolved |
How to Read This Revolut Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Revolut acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Revolut outage in this window ran 117d 12h, against a mean recovery of 41d 23h. If you depend on Revolut in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.