WeTravel Outage History

26 incidents recorded over the last 365 days, 26 of them resolved. 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 WeTravel Incident

WeTravel incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 29, 2026Currency conversion and payouts temporarily unavailableThe issue affecting currency conversion, wire payouts, and new wire transfer accounts with our payment partner has been resolved, and these services are now operating normally. You can resume using these features as…12h 2mResolved
Oct 16, 2026PIX (BRL) trip payments failing due to partner outagePIX payments in BRL have been fully restored and are working as usual.1h 34mResolved
Sep 22, 2026Failure to update participant information on the Manage Trip page. The issue affecting the ability to update participant information on bookings has been fixed, and the site is fully operational.7 minResolved
Sep 20, 2026Currency conversion and wire transfer issuesThe issue affecting currency conversion, wire payouts, and new wire transfer accounts with our payment partner has been resolved, and these services are now operating normally. You can resume using these features as…16h 6mResolved
Aug 25, 2026Some travelers unable to complete bookingBetween 13:11 and 22:19 UTC on 25 August, some travelers were unable to complete a booking when submitting the questions on an organizer's checkout form. The cause was a validation change that rejected certain valid…6 minResolved
Aug 11, 2026Wire Transfers & Wallet ConversionsWe experienced a brief, few-minute disruption affecting wire transfers and wallet conversions due to an issue with our payment provider. This has since been resolved, and all payment methods are now operating normally…-43 minResolved
Aug 10, 2026Wire Transfers & Wallet ConversionsWe experienced a brief, few-minute disruption affecting wire transfers and wallet conversions due to an issue with our payment provider. This has since been resolved, and all payment methods are now operating normally…-9 minResolved
Jul 30, 2026Investigating: Unsplash Image Uploads via FilestackThe issue affecting the Unsplash image search/upload feature has been resolved, and the service is now operating normally. The feature has been re-enabled, and no further issues have been observed.23h 5mResolved
Jun 21, 2026FX Convert feature issue partially downWe experienced a brief issue in which the FX Convert feature was partially unavailable due to our partner's outage. Some currencies could not be converted between 3:14 & 3:45 AM UTC. All services are functioning…5 minResolved
Jun 18, 2026Login and Payment processing issuesThe issue has been fully resolved. All functionalities are now working as normal.7 minResolved
May 19, 2026Trip Page Loading IssuesThe issue affecting trip pages has been fully resolved. Trip pages, booking flows, and payment links are now loading and functioning normally again. Thank you for your patience while our team worked on restoring the…29 minResolved
Apr 16, 2026WeTravel Access IssueThe earlier disruption affecting website access has now been resolved, and the site is fully operational; all services are functioning normally.11 minResolved
Apr 10, 2026Bookings not visible on participant accountsWe experienced a brief issue where bookings were not displayed on participant dashboards. This was resolved within 20 minutes, and no bookings or payments were impacted, as this was a display-only issue.-7 minResolved
Mar 31, 2026Elevated Bancontact Payment ErrorsBetween 09:48 and 11:02 UTC, Bancontact — a widely used Belgian online payment method — experienced elevated error rates, which impacted some transactions. The issue originated with the payment method provider (external…-1501 minResolved
Jan 29, 2026Connectivity issues with wetravel.com in certain locationsThis incident has been resolved.-791394 minResolved
Jan 29, 2026Issues with WeTravel Card ServiceThis incident has been resolved.-1117166 minResolved
Jan 29, 2026Connectivity issues with wetravel.com websiteWe encountered connectivity issues on our website, which lasted for approximately one hour. The issue has been fully resolved.-577736 minResolved
Jan 29, 2026Issues with file upload on WeTravelThe file upload issue has been resolved. Trip creation, bookings requiring document uploads, and itinerary file/image uploads are now working as expected.-427377 minResolved
Jan 29, 2026Service InterruptionThis incident has been fully resolved.-535364 minResolved
Jan 29, 2026WeTravel Card ServiceThis incident has been resolved.-626163 minResolved
Jan 29, 2026Issues with file upload on WeTravelThis incident has been resolved.-778580 minResolved
Jan 29, 2026Temporary Issues Affecting Platform AvailabilityThis incident has been resolved.-90494 minResolved
Jan 29, 2026Cloudflare Outage Impacting WeTravelThis incident has been resolved.-103093 minResolved
Jan 29, 2026Issues with Unsplash image uploadsThis incident has been resolved.-164671 minResolved
Jan 29, 2026Google Cloud Outage Impacting Client Verification ToolA widespread Google Cloud outage affected several services, including our client verification tool, leading to a disruption that lasted approximately 3 hours. The issue has been resolved, and all systems are operating…-331676 minResolved
Jan 29, 2026Issues affecting payments and transfers on WeTravelThe issue affecting some payments and wire transfers has been resolved, and all services are now operating normally. We apologize for the interruption and appreciate your patience.-386861 minResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next WeTravel incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This WeTravel 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 WeTravel 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 WeTravel outage in this window ran 23h 5m, against a mean recovery of 5h 23m. If you depend on WeTravel 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.