User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Entertainment
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 315 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 19 | 0 | 0.0 | 181 ms | 0 |
| Mon 21 | 0 | 0.0 | 142 ms | 0 |
| Mon 23 | 0 | 0.0 | 169 ms | 0 |
| Tue 01 | 0 | 0.0 | 70 ms | 0 |
| Tue 03 | 0 | 0.0 | 118 ms | 0 |
| Tue 06 | 0 | 0.0 | 167 ms | 0 |
| Tue 08 | 0 | 0.0 | 197 ms | 0 |
| Tue 10 | 0 | 0.0 | 85 ms | 0 |
| Tue 12 | 0 | 0.0 | 156 ms | 0 |
| Tue 14 | 0 | 0.0 | 178 ms | 0 |
| Tue 16 | 0 | 0.0 | 136 ms | 0 |
| Tue 19 | 0 | 0.0 | 299 ms | 0 |
| Tue 21 | 0 | 0.0 | 307 ms | 0 |
| Tue 23 | 0 | 0.0 | 176 ms | 0 |
| Wed 01 | 0 | 0.0 | 188 ms | 0 |
| Wed 04 | 0 | 0.0 | 125 ms | 0 |
| Wed 06 | 0 | 0.0 | 165 ms | 0 |
| Wed 08 | 0 | 0.0 | 107 ms | 0 |
| Wed 10 | 0 | 0.0 | 153 ms | 0 |
| Wed 13 | 0 | 0.0 | 100 ms | 0 |
| Wed 15 | 0 | 0.0 | 157 ms | 0 |
| Wed 17 | 0 | 0.0 | 158 ms | 0 |
| Wed 19 | 0 | 0.0 | 96 ms | 0 |
| Wed 21 | 0 | 0.0 | 225 ms | 0 |
| Wed 23 | 0 | 0.0 | 165 ms | 0 |
| Thu 01 | 0 | 0.0 | 205 ms | 0 |
| Thu 03 | 0 | 0.0 | 108 ms | 0 |
| Thu 06 | 0 | 0.0 | 177 ms | 0 |
| Thu 08 | 0 | 0.0 | 184 ms | 0 |
| Thu 10 | 0 | 0.0 | 163 ms | 0 |
| Thu 12 | 0 | 0.0 | 153 ms | 0 |
| Thu 14 | 0 | 0.0 | 185 ms | 0 |
| Thu 16 | 0 | 0.0 | 165 ms | 0 |
| Thu 18 | 0 | 0.0 | 195 ms | 0 |
| Thu 20 | 0 | 0.0 | 171 ms | 0 |
| Thu 22 | 0 | 0.0 | 197 ms | 0 |
| Fri 00 | 0 | 0.0 | 165 ms | 0 |
| Fri 02 | 0 | 0.0 | 186 ms | 0 |
| Fri 04 | 0 | 0.0 | 63 ms | 0 |
| Fri 06 | 0 | 0.0 | 105 ms | 0 |
| Fri 08 | 0 | 0.0 | 122 ms | 0 |
| Fri 11 | 0 | 0.0 | 218 ms | 0 |
| Fri 13 | 0 | 0.0 | 220 ms | 0 |
| Fri 15 | 0 | 0.0 | 172 ms | 0 |
| Fri 17 | 0 | 0.0 | 234 ms | 0 |
| Fri 19 | 0 | 0.0 | 228 ms | 0 |
| Fri 21 | 0 | 0.0 | 133 ms | 0 |
| Fri 23 | 0 | 0.0 | 315 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 Gumlet 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 Gumlet goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Gumlet alerts to Slack, Discord or a webhook — free.
Gumlet, at gumlet.com, is one of the Entertainment services we monitor. Transform your website's media delivery with Gumlet, an all-in-one video hosting platform. Optimize images and videos for lightning-fast performance.
Gumlet publishes an official status page at status.gumlet.com; when we can read it, its incident level is folded into the status shown here.
Common problems for entertainment services: streams buffering or not starting, playback errors, and app sign-in problems.
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: 174 ms average, 15–315 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 Gumlet incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
174 ms on average over the last 24 hours (15–315 ms).
Yes, at https://status.gumlet.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For entertainment services, watch for streams buffering or not starting, playback errors, and app sign-in problems. If many people report Gumlet here at once, the problem is on Gumlet'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 Gumlet. 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.