User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Travel
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 40 min ago. Last stored result reached it in 1103 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 719 ms | 0 |
| Nov 7 | 0 | 0.0 | 612 ms | 0 |
| Nov 7 | 0 | 0.0 | 584 ms | 0 |
| Nov 7 | 0 | 0.0 | 499 ms | 0 |
| Nov 8 | 0 | 0.0 | 482 ms | 0 |
| Nov 8 | 0 | 0.0 | 806 ms | 0 |
| Nov 8 | 0 | 0.0 | 509 ms | 0 |
| Nov 8 | 0 | 0.0 | 515 ms | 0 |
| Nov 9 | 0 | 0.0 | 573 ms | 0 |
| Nov 9 | 0 | 0.0 | 613 ms | 0 |
| Nov 9 | 0 | 0.0 | 585 ms | 0 |
| Nov 9 | 0 | 0.0 | 929 ms | 0 |
| Nov 10 | 0 | 0.0 | 380 ms | 0 |
| Nov 10 | 0 | 0.0 | 358 ms | 0 |
| Nov 10 | 0 | 0.0 | 512 ms | 0 |
| Nov 10 | 0 | 0.0 | 859 ms | 0 |
| Nov 11 | 0 | 0.0 | 719 ms | 0 |
| Nov 11 | 0 | 0.0 | 1279 ms | 0 |
| Nov 11 | 0 | 0.0 | 511 ms | 0 |
| Nov 11 | 0 | 0.0 | 542 ms | 0 |
| Nov 12 | 0 | 0.0 | 850 ms | 0 |
| Nov 12 | 0 | 0.0 | 556 ms | 0 |
| Nov 12 | 0 | 0.0 | 1814 ms | 0 |
| Nov 12 | 0 | 0.0 | 388 ms | 0 |
| Nov 13 | 0 | 0.0 | 386 ms | 0 |
| Nov 13 | 0 | 0.0 | 438 ms | 0 |
| Nov 13 | 0 | 0.0 | 792 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Wingly yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Wingly goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Wingly alerts to Slack, Discord or a webhook — free.
We track Wingly (wingly.io) as part of the Travel group. Wingly is a flight sharing platform. Find pilots or passengers for your trip.
Wingly publishes an official status page at status.wingly.io; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with travel services: booking and check-in failures, flight-status pages not loading, and app errors.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 683 ms average, 336–2879 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Wingly incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
683 ms on average over the last 24 hours (336–2879 ms).
Yes, at https://status.wingly.io.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For travel services, watch for booking and check-in failures, flight-status pages not loading, and app errors. If many people report Wingly here at once, the problem is on Wingly's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Wingly. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.