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 21 min ago. Last stored result reached it in 63 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 15 | 0 | 0.0 | 57 ms | 0 |
| Mon 17 | 0 | 0.0 | 75 ms | 0 |
| Mon 19 | 0 | 0.0 | 130 ms | 0 |
| Mon 21 | 0 | 0.0 | 151 ms | 0 |
| Mon 23 | 0 | 0.0 | 37 ms | 0 |
| Tue 01 | 0 | 0.0 | 127 ms | 0 |
| Tue 03 | 0 | 0.0 | 55 ms | 0 |
| Tue 05 | 0 | 0.0 | 152 ms | 0 |
| Tue 08 | 0 | 0.0 | 407 ms | 0 |
| Tue 10 | 0 | 0.0 | 388 ms | 0 |
| Tue 12 | 0 | 0.0 | 289 ms | 0 |
| Tue 14 | 0 | 0.0 | 108 ms | 0 |
| Tue 16 | 0 | 0.0 | 121 ms | 0 |
| Tue 18 | 0 | 0.0 | 122 ms | 0 |
| Tue 21 | 0 | 0.0 | 47 ms | 0 |
| Tue 23 | 0 | 0.0 | 118 ms | 0 |
| Wed 00 | 0 | 0.0 | 63 ms | 0 |
| Wed 02 | 0 | 0.0 | 122 ms | 0 |
| Wed 04 | 0 | 0.0 | 74 ms | 0 |
| Wed 06 | 0 | 0.0 | 56 ms | 0 |
| Wed 09 | 0 | 0.0 | 26 ms | 0 |
| Wed 11 | 0 | 0.0 | 232 ms | 0 |
| Wed 13 | 0 | 0.0 | 42 ms | 0 |
| Wed 15 | 0 | 0.0 | 261 ms | 0 |
| Wed 17 | 0 | 0.0 | 87 ms | 0 |
| Wed 20 | 0 | 0.0 | 165 ms | 0 |
| Wed 22 | 0 | 0.0 | 65 ms | 0 |
| Thu 00 | 0 | 0.0 | 129 ms | 0 |
| Thu 02 | 0 | 0.0 | 73 ms | 0 |
| Thu 04 | 0 | 0.0 | 87 ms | 0 |
| Thu 06 | 0 | 0.0 | 35 ms | 0 |
| Thu 08 | 0 | 0.0 | 42 ms | 0 |
| Thu 10 | 0 | 0.0 | 103 ms | 0 |
| Thu 12 | 0 | 0.0 | 269 ms | 0 |
| Thu 14 | 0 | 0.0 | 199 ms | 0 |
| Thu 16 | 0 | 0.0 | 92 ms | 0 |
| Thu 19 | 0 | 0.0 | 102 ms | 0 |
| Thu 21 | 0 | 0.0 | 371 ms | 0 |
| Thu 23 | 0 | 0.0 | 215 ms | 0 |
| Fri 01 | 0 | 0.0 | 101 ms | 0 |
| Fri 03 | 0 | 0.0 | 56 ms | 0 |
| Fri 05 | 0 | 0.0 | 59 ms | 0 |
| Fri 07 | 0 | 0.0 | 161 ms | 0 |
| Fri 09 | 0 | 0.0 | 40 ms | 0 |
| Fri 11 | 0 | 0.0 | 377 ms | 0 |
| Fri 12 | 0 | 0.0 | 47 ms | 0 |
| Fri 14 | 0 | 0.0 | 67 ms | 0 |
| Fri 16 | 0 | 0.0 | 63 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 Ember 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 Ember goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Ember alerts to Slack, Discord or a webhook — free.
Ember is listed in our Travel category and checked at ember.to. Travel by electric bus between Dundee, Glasgow, Edinburgh, Aberdeen, Stirling, Kinross, Fort William, Inverness, Edinburgh Airport and more. Brand-new buses, affordable fares and real-time tracking.
Ember publishes an official status page at status.ember.to; 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: 135 ms average, 40–377 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Ember incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
135 ms on average over the last 24 hours (40–377 ms).
Yes, at https://status.ember.to.
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 Ember here at once, the problem is on Ember'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 Ember. 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.