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 1 hr ago. Last stored result reached it in 603 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 758 ms | 0 |
| Nov 7 | 0 | 0.0 | 821 ms | 0 |
| Nov 7 | 0 | 0.0 | 968 ms | 0 |
| Nov 7 | 0 | 0.0 | 605 ms | 0 |
| Nov 7 | 0 | 0.0 | 865 ms | 0 |
| Nov 8 | 0 | 0.0 | 899 ms | 0 |
| Nov 8 | 0 | 0.0 | 733 ms | 0 |
| Nov 8 | 0 | 0.0 | 967 ms | 0 |
| Nov 8 | 0 | 0.0 | 659 ms | 0 |
| Nov 9 | 0 | 0.0 | 633 ms | 0 |
| Nov 9 | 0 | 0.0 | 679 ms | 0 |
| Nov 9 | 0 | 0.0 | 895 ms | 0 |
| Nov 9 | 0 | 0.0 | 705 ms | 0 |
| Nov 10 | 0 | 0.0 | 887 ms | 0 |
| Nov 10 | 0 | 0.0 | 830 ms | 0 |
| Nov 10 | 0 | 0.0 | 679 ms | 0 |
| Nov 10 | 0 | 0.0 | 879 ms | 0 |
| Nov 11 | 0 | 0.0 | 717 ms | 0 |
| Nov 11 | 0 | 0.0 | 925 ms | 0 |
| Nov 11 | 0 | 0.0 | 910 ms | 0 |
| Nov 11 | 0 | 0.0 | 622 ms | 0 |
| Nov 12 | 0 | 0.0 | 749 ms | 0 |
| Nov 12 | 0 | 0.0 | 891 ms | 0 |
| Nov 12 | 0 | 0.0 | 715 ms | 0 |
| Nov 12 | 0 | 0.0 | 719 ms | 0 |
| Nov 13 | 0 | 0.0 | 1012 ms | 0 |
| Nov 13 | 0 | 0.0 | 938 ms | 0 |
| Nov 13 | 0 | 0.0 | 864 ms | 0 |
| Nov 13 | 0 | 0.0 | 775 ms | 0 |
| Nov 14 | 0 | 0.0 | 695 ms | 0 |
| Nov 14 | 0 | 0.0 | 1023 ms | 0 |
| Nov 14 | 0 | 0.0 | 603 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 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Airalo 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 Airalo goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Airalo alerts to Slack, Discord or a webhook — free.
Airalo, at airalo.com, is one of the Travel services we monitor. Find travel eSIMs for iPhone, iPad, and Android devices in over 200 destinations. Purchase data for countries, regions, or global connection.
Airalo publishes an official status page at status.airalo.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with travel services: booking and check-in failures, flight-status pages not loading, and app errors.
Measured uptime from our checks: 100% over 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 843 ms average, 547–1207 ms range across 17 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Airalo incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
843 ms on average over the last 24 hours (547–1207 ms).
Yes, at https://status.airalo.com.
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 Airalo here at once, the problem is on Airalo'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 Airalo. 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.