What we got wrong, and what we changed
Every mistake we found that a visitor could have seen or been affected by, in plain words, newest first. It does not list every internal bug, and it leaves out security details. We add to it when we fix something.
The UK ETA article said "a parent" can apply for a child
What you could have seen
The UK ETA article said a parent can apply on a child's behalf, in the text and again in the questions at the end. GOV.UK says only that you can apply for someone else, such as a child; it does not say who that person must be.
What we changed
The sentence now says what GOV.UK says: someone else can apply for a child. Each traveller still needs their own ETA.
Two travel articles said more than their official sources
What you could have seen
For two days, the new UK ETA article was vague about connecting flights (GOV.UK says people who stay airside do not currently need one) and stated what happens after a passport renewal, which GOV.UK does not state. The Thailand arrival-card article repeated a warning about fake websites that came from news reports, not from a Thai government page.
What we changed
Every sentence in both articles was checked against GOV.UK, the Home Office, the Tourism Authority of Thailand and Thai embassy pages. What they do not say was removed; the transit rule now matches GOV.UK word for word in meaning.
The site was unreachable for five days
What you could have seen
From 18 to 23 October 2026, wingoratravel.com did not open. The code was fine; the domain registrar had suspended the address because an ownership-verification email had not been confirmed. Daily price alerts also failed during those days.
What we changed
The verification is done. The daily alert job now calls the site on its own server address, so it keeps working even if the public address has a problem.
Arabic dates after the 28th were moved
What you could have seen
Typing a date like "30 نوفمبر" in the Arabic search box searched for 28 November instead.
What we changed
The day is now checked against the real length of the month. A day that does not exist is dropped, never quietly changed to another one.
Arrows between Arabic city names pointed backwards
What you could have seen
On the Arabic site, "دبي → لندن" reads right to left, so the arrow pointed from London to Dubai.
What we changed
Arabic headings now use an arrow that points the way Arabic is read.
Choosing Heathrow sent you to all London airports
What you could have seen
Some fares came back labelled with a city code (LON) instead of the airport you picked (LHR). The card showed "LON", and the booking link opened a search across every London airport.
What we changed
The card, the time zone and the booking link now use the actual airport of each fare.
On phones, the cheapest fare’s button could not be tapped
What you could have seen
For part of a day, an invisible, closed filter panel sat over the results on mobile and caught taps meant for the first card’s Select button.
What we changed
Fixed the same day. Our tests now tap every Select button with the panel closed as well as open.
Dates in Arabic articles appeared reversed
What you could have seen
A date written 2026-09-13 displayed as 13-09-2026 on Arabic pages, because the browser reorders digits and dashes inside right-to-left text.
What we changed
Dates inside Arabic text are now isolated so they always read in the same order.
Arrival times used the wrong time zone
What you could have seen
A one-way flight to Istanbul showed its arrival time in Abu Dhabi’s time zone, one hour off, with a label that looked entirely normal.
What we changed
Every airport now has its real time zone, worked out for the moment of travel. If we cannot tell an airport’s time zone, we leave the label out rather than guess.
Sample prices were shown as if they were real
What you could have seen
For a period after launch, before the live fare connection was set up, search results showed generated sample prices that were not marked as samples.
What we changed
Sample data now exists only on a developer’s machine. If live fares are unavailable, the site says so instead of showing anything invented.
Round-trip searches came back empty
What you could have seen
Once real fares replaced sample data, a search for an exact departure and return date found nothing, because our fare source does not answer exact date pairs.
What we changed
We now ask for the whole month and show the fares nearest your dates. Each card shows its own date and says how far it is from the one you chose.