Skip to content

Outage tracker / Vueling

Is Vueling down?

Short linkrlup.io/down/vueling

I'm having a problem

Awaiting datachecked 23 minutes ago

Vueling refused or filtered our probes from every region we have a reading for. A refused probe is evidence about our reception, not a failed check, so we publish no verdict rather than guessing in either direction.

As of Nov 5, 2026, 3:02 PM UTC, RealUptime could not obtain a reading for Vueling from any of the 4 regions it checks (US-East, US-West, Europe and Asia-Pacific). That is a fact about our own checks there and is not evidence about Vueling.

Front-door checks

Our checks of Vueling did not fail from two or more distant regions in the 3 days we have checked it (since Nov 2, 2026). This does not show Vueling works for users.

Email me when our checks of Vueling fail from two or more distant regions

One email when our checks of Vueling fail from two or more distant regions, and one when they pass, after you confirm the address. No account, no card.

This is our own reading from outside. It is not Vueling's official status.

our check readinglive · checked Nov 5, 2026, 3:02 PM UTC
US-East956 msAwaiting data
US-West1097 msAwaiting data
Europe506 msAwaiting data
Asia-Pacific2699 msAwaiting data
their status pagetheir claim, not our reading

Vueling publishes no status feed we can read, so the only reading here is our check reading on the left.

Vueling response time, by region

US-East

No response-time data yet for US-East.

US-West

No response-time data yet for US-West.

Europe

No response-time data yet for Europe.

Asia-Pacific

No response-time data yet for Asia-Pacific.

Why some readings show as awaiting data. 4 of 4 readings for Vueling came back as a filtered response to our automated checks (a response code that refuses automated clients, such as 403, 405, 406, 429 or 451, a redirect loop, or a timeout that a second endpoint answered) rather than a normal pass or failure. That tells us about our own probe's reception, not about Vueling's health, so we publish no verdict for those readings rather than guessing in either direction. 4 of those readings received an actual response: the connection, the TLS handshake, and the edge all answered, with a measured latency. Our check passed there, just not through the specific path automated checks are filtered on. Read how we tell the difference.

Check your own site while you wait on Vueling

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Vueling. It cannot diagnose Vueling's own systems.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    Awaiting dataUS-East, US-West, US-Central, Canada
    • US-East
      Awaiting datalatency: 956msstatus code: 403check reading: filtered as automatedchecked: Nov 5, 2026, 3:02 PM UTC
      0 people in the last 5 minutesNot enough reports to sayVueling refused our US-East probe, so we have no reading from there, and a refused probe is not a confirmed outage. We also do not have enough reports from US-East to say anything on their own.
    • US-West
      Awaiting datalatency: 1097msstatus code: 403check reading: filtered as automatedchecked: Nov 5, 2026, 3:01 PM UTC
      0 people in the last 5 minutesNot enough reports to sayVueling refused our US-West probe, so we have no reading from there, and a refused probe is not a confirmed outage. We also do not have enough reports from US-West to say anything on their own.
    • US-Central
      Not monitored from this regionVueling is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Canada
      Not monitored from this regionVueling is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • South America
    Not monitored from this regionVueling is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Europe
    Awaiting dataEurope, UK
    • Europe
      Awaiting datalatency: 506msstatus code: 403check reading: filtered as automatedchecked: Nov 5, 2026, 2:47 PM UTC
      0 people in the last 5 minutesNot enough reports to sayVueling refused our Europe probe, so we have no reading from there, and a refused probe is not a confirmed outage. We also do not have enough reports from Europe to say anything on their own.
    • UK
      Not monitored from this regionVueling is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • Asia Pacific
    Awaiting dataAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Awaiting datalatency: 2699msstatus code: 403check reading: filtered as automatedchecked: Nov 5, 2026, 2:38 PM UTC
      0 people in the last 5 minutesNot enough reports to sayVueling refused our Asia-Pacific probe, so we have no reading from there, and a refused probe is not a confirmed outage. We also do not have enough reports from Asia-Pacific to say anything on their own.
    • Southeast Asia
      Not monitored from this regionVueling is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Australia
      Not monitored from this regionVueling is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Vueling, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Vueling yet, which is not evidence that nothing is wrong.

Recent probe events

No probe events on record yet for Vueling.

check entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Vueling since November 2, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Vueling covering any window you pick, with our check readings and Vueling's own claim at the time, side by side.

Full check history for Vueling: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Put this badge in your README

Vueling uptime by RealUptime's checksLive, from this page's own readings.
[![Vueling uptime by RealUptime's checks](https://realuptime.io/outages/vueling/badge.svg?days=30)](https://realuptime.io/outages/vueling)
<a href="https://realuptime.io/outages/vueling"><img src="https://realuptime.io/outages/vueling/badge.svg?days=30" alt="Vueling uptime by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is Vueling down?", https://realuptime.io/outages/vueling. The readings change with every check, so give the date you read them.

How our checks compare with Vueling's stated SLA

At or above your target

Our checks of Vueling failed for none over the last 30 days, which is 100% uptime by our checks. A 99.9% target allows 43 minutes over that period.

Our checks show no gap in this period. That does not rule out one you saw.

These figures come from our own checks of one public endpoint per service. They are not the service's real uptime. This is computed from our own checks, not from Vueling's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primary
https://www.vueling.com/

What our check can and cannot see

A pass means the service's public web page loaded and answered normally. It does not show that the product, the API or sign-in behind it works; a page can load from a cache while the product is down.

Host checked: www.vueling.com

RealUptime is not affiliated with Vueling; the name identifies what we checked, and nothing here speaks for Vueling's own team. We send a single web request to Vueling from 4 regions on our own schedule and time the response. We do not see inside Vueling's systems, do not use an account or real transaction, and are not the same signal Vueling's own team has access to. Treat this as one external data point, not a verdict. What we check for Vueling is its front door only: a passing check means the endpoints above answered, not that the underlying product or account features work. Vueling operates in a limited set of regions, so we only check it from where it is actually available; we do not probe from a region we know it does not serve. We started monitoring this service on November 2, 2026 (3 of 14 days so far, 425 of 500 checks). We show a full track record once we have enough continuous history. Check back soon, or monitor your own site continuously with RealUptime. Read the full methodology.

Related services

ANA (All Nippon Airways)AOL MailAT&TAccorAeroméxico