User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
gigalixir.com · Cloud & developer
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 2 hr ago. Last stored result reached it in 262 ms.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 14 | 0 | 0.0 | 123 ms | 0 |
| Mon 16 | 0 | 0.0 | 268 ms | 0 |
| Mon 19 | 0 | 0.0 | 130 ms | 0 |
| Mon 21 | 0 | 0.0 | 100 ms | 0 |
| Mon 23 | 0 | 0.0 | 89 ms | 0 |
| Tue 01 | 0 | 0.0 | 283 ms | 0 |
| Tue 03 | 0 | 0.0 | 110 ms | 0 |
| Tue 05 | 0 | 0.0 | 175 ms | 0 |
| Tue 07 | 0 | 0.0 | 108 ms | 0 |
| Tue 09 | 0 | 0.0 | 282 ms | 0 |
| Tue 11 | 0 | 0.0 | 232 ms | 0 |
| Tue 14 | 0 | 0.0 | 240 ms | 0 |
| Tue 16 | 0 | 0.0 | 232 ms | 0 |
| Tue 18 | 0 | 0.0 | 112 ms | 0 |
| Tue 20 | 0 | 0.0 | 227 ms | 0 |
| Tue 23 | 0 | 0.0 | 291 ms | 0 |
| Wed 01 | 0 | 0.0 | 241 ms | 0 |
| Wed 03 | 0 | 0.0 | 147 ms | 0 |
| Wed 05 | 0 | 0.0 | 76 ms | 0 |
| Wed 08 | 0 | 0.0 | 231 ms | 0 |
| Wed 10 | 0 | 0.0 | 66 ms | 0 |
| Wed 12 | 0 | 0.0 | 125 ms | 0 |
| Wed 14 | 0 | 0.0 | 69 ms | 0 |
| Wed 16 | 0 | 0.0 | 55 ms | 0 |
| Wed 18 | 0 | 0.0 | 155 ms | 0 |
| Wed 21 | 0 | 0.0 | 284 ms | 0 |
| Wed 23 | 0 | 0.0 | 292 ms | 0 |
| Thu 01 | 0 | 0.0 | 138 ms | 0 |
| Thu 03 | 0 | 0.0 | 168 ms | 0 |
| Thu 05 | 0 | 0.0 | 214 ms | 0 |
| Thu 07 | 0 | 0.0 | 131 ms | 0 |
| Thu 09 | 0 | 0.0 | 249 ms | 0 |
| Thu 11 | 0 | 0.0 | 241 ms | 0 |
| Thu 13 | 0 | 0.0 | 133 ms | 0 |
| Thu 15 | 0 | 0.0 | 83 ms | 0 |
| Thu 17 | 0 | 0.0 | 83 ms | 0 |
| Thu 19 | 0 | 0.0 | 368 ms | 0 |
| Thu 22 | 0 | 0.0 | 187 ms | 0 |
| Fri 00 | 0 | 0.0 | 311 ms | 0 |
| Fri 02 | 0 | 0.0 | 92 ms | 0 |
| Fri 04 | 0 | 0.0 | 54 ms | 0 |
| Fri 06 | 0 | 0.0 | 94 ms | 0 |
| Fri 08 | 0 | 0.0 | 128 ms | 0 |
| Fri 10 | 0 | 0.0 | 151 ms | 0 |
| Fri 12 | 0 | 0.0 | 47 ms | 0 |
| Fri 14 | 0 | 0.0 | 253 ms | 0 |
| Fri 16 | 0 | 0.0 | 150 ms | 0 |
| Fri 17 | 0 | 0.0 | 262 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 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Gigalixir 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 Gigalixir goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Gigalixir alerts to Slack, Discord or a webhook — free.
Gigalixir, at gigalixir.com, is one of the Cloud & developer services we monitor. The only platform built to unlock the full power of Elixir and Phoenix, while providing a high-performance, buildpack-driven home for all your production applications.
Gigalixir publishes an official status page at status.gigalixir.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 175 ms average, 47–368 ms range across 12 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Gigalixir incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
175 ms on average over the last 24 hours (47–368 ms).
Yes, at https://status.gigalixir.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Gigalixir here at once, the problem is on Gigalixir'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 Gigalixir. 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.