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 11 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 |
|---|---|---|---|---|
| Mon 12 | 0 | 0.0 | 609 ms | 0 |
| Mon 14 | 0 | 0.0 | 432 ms | 0 |
| Mon 16 | 0 | 0.0 | 585 ms | 0 |
| Mon 18 | 0 | 0.0 | 929 ms | 0 |
| Mon 20 | 0 | 0.0 | 970 ms | 0 |
| Mon 23 | 0 | 0.0 | 773 ms | 0 |
| Tue 01 | 0 | 0.0 | 434 ms | 0 |
| Tue 03 | 0 | 0.0 | 360 ms | 0 |
| Tue 05 | 0 | 0.0 | 380 ms | 0 |
| Tue 07 | 0 | 0.0 | 543 ms | 0 |
| Tue 09 | 0 | 0.0 | 358 ms | 0 |
| Tue 11 | 0 | 0.0 | 358 ms | 0 |
| Tue 14 | 0 | 0.0 | 552 ms | 0 |
| Tue 16 | 0 | 0.0 | 472 ms | 0 |
| Tue 18 | 0 | 0.0 | 1962 ms | 0 |
| Tue 20 | 0 | 0.0 | 394 ms | 0 |
| Tue 23 | 0 | 0.0 | 859 ms | 0 |
| Wed 01 | 0 | 0.0 | 413 ms | 0 |
| Wed 03 | 0 | 0.0 | 719 ms | 0 |
| Wed 05 | 0 | 0.0 | 978 ms | 0 |
| Wed 08 | 0 | 0.0 | 2184 ms | 0 |
| Wed 10 | 0 | 0.0 | 373 ms | 0 |
| Wed 12 | 0 | 0.0 | 356 ms | 0 |
| Wed 14 | 0 | 0.0 | 1289 ms | 0 |
| Wed 16 | 0 | 0.0 | 511 ms | 0 |
| Wed 18 | 0 | 0.0 | 864 ms | 0 |
| Wed 21 | 0 | 0.0 | 571 ms | 0 |
| Wed 23 | 0 | 0.0 | 378 ms | 0 |
| Thu 01 | 0 | 0.0 | 1118 ms | 0 |
| Thu 03 | 0 | 0.0 | 314 ms | 0 |
| Thu 05 | 0 | 0.0 | 850 ms | 0 |
| Thu 07 | 0 | 0.0 | 635 ms | 0 |
| Thu 09 | 0 | 0.0 | 425 ms | 0 |
| Thu 11 | 0 | 0.0 | 556 ms | 0 |
| Thu 13 | 0 | 0.0 | 919 ms | 0 |
| Thu 15 | 0 | 0.0 | 2709 ms | 0 |
| Thu 18 | 0 | 0.0 | 2879 ms | 0 |
| Thu 20 | 0 | 0.0 | 388 ms | 0 |
| Thu 22 | 0 | 0.0 | 377 ms | 0 |
| Fri 00 | 0 | 0.0 | 440 ms | 0 |
| Fri 02 | 0 | 0.0 | 336 ms | 0 |
| Fri 04 | 0 | 0.0 | 386 ms | 0 |
| Fri 06 | 0 | 0.0 | 438 ms | 0 |
| Fri 08 | 0 | 0.0 | 569 ms | 0 |
| Fri 10 | 0 | 0.0 | 376 ms | 0 |
| Fri 11 | 0 | 0.0 | 968 ms | 0 |
| Fri 13 | 0 | 0.0 | 481 ms | 0 |
| Fri 15 | 0 | 0.0 | 1103 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.