Around 13:20 UTC on 15 April 2026, our monitors picked up what looks like an issue with Jet2 (jet2.com). One of our checks timed out after waiting 15 seconds for a response — which is usually a sign that something's not quite right on the server side, even if it's not always a full outage. As an independent monitoring service, all we can share is what our own checks detected, so we wanted to put together a quick summary of what we're seeing and what might be useful if you're trying to get things done on Jet2 right now.
What Our Monitors Are Showing
At 13:20 UTC, our monitor reported a timeout after 15,000ms when attempting to reach jet2.com. In plain terms, that means the site didn't respond within the 15-second window we allow before flagging a potential problem. This kind of result can point to a few different things — heavy traffic overwhelming the servers, an infrastructure hiccup, or something deeper going on in the backend. It doesn't necessarily mean the whole site was down for everyone, but it does suggest something wasn't behaving normally at that moment.
We took a look at Jet2's status page, but from what we can see, it doesn't appear to be a dedicated technical status page — it loads content related to flight information and travel updates rather than system health. So unfortunately we don't have a formal incident update from Jet2 to point you to, and we don't have a full picture yet of the scope or cause of what we detected.
What People Are Saying
We haven't come across specific social media reports or community threads directly referencing this particular Jet2 issue at the time of writing. It's worth checking platforms like X or community travel forums to see if others are experiencing the same thing — sometimes reports surface there before any official update does.
It is worth noting that around late October 2025, there were reports of a broader Microsoft outage affecting a wide range of services. We can't say whether anything similar is a factor here — that's purely context, not a confirmed connection.
What You Can Do in the Meantime
If you're trying to reach Jet2 and running into trouble, here are a few things worth trying:
- Try again in a few minutes. Timeouts are sometimes brief and resolve on their own, especially if the cause is a traffic spike.
- Use the Jet2 app if you have it installed — mobile apps sometimes stay accessible even when the main website is struggling.
- Call Jet2 directly if you have an urgent booking concern. Their contact details are available on their website when it's accessible.
- Check your booking confirmation email — it'll have your flight details and booking reference handy without needing to log in.
- Try a different browser or network — occasionally a local DNS or caching issue can make a site appear down when it isn't.
Keep an Eye on Jet2 with Uptrue
This is exactly the kind of thing Uptrue is built for — catching those moments when a service you rely on starts behaving oddly, so you're not left wondering if it's just you. If you'd like to set up your own monitors for Jet2 or any other site you care about, you can do that for free at uptrue.io.
It's worth saying clearly: everything here reflects Uptrue's own observation based on what our monitors detected around 13:20 UTC on 15 April 2026. The situation may well have already resolved by the time you're reading this. For the most accurate and up-to-date information, your best bet is to check Jet2's official site directly.