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 252 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 21 | 0 | 0.0 | 268 ms | 0 |
| Mon 23 | 0 | 0.0 | 446 ms | 0 |
| Tue 01 | 0 | 0.0 | 383 ms | 0 |
| Tue 03 | 0 | 0.0 | 400 ms | 0 |
| Tue 06 | 0 | 0.0 | 317 ms | 0 |
| Tue 08 | 0 | 0.0 | 1023 ms | 0 |
| Tue 10 | 0 | 0.0 | 331 ms | 0 |
| Tue 12 | 0 | 0.0 | 315 ms | 0 |
| Tue 14 | 0 | 0.0 | 400 ms | 0 |
| Tue 16 | 0 | 0.0 | 339 ms | 0 |
| Tue 19 | 0 | 0.0 | 422 ms | 0 |
| Tue 21 | 0 | 0.0 | 405 ms | 0 |
| Tue 23 | 0 | 0.0 | 341 ms | 0 |
| Wed 01 | 0 | 0.0 | 315 ms | 0 |
| Wed 04 | 0 | 0.0 | 438 ms | 0 |
| Wed 06 | 0 | 0.0 | 391 ms | 0 |
| Wed 08 | 0 | 0.0 | 354 ms | 0 |
| Wed 10 | 0 | 0.0 | 694 ms | 0 |
| Wed 12 | 0 | 0.0 | 305 ms | 0 |
| Wed 15 | 0 | 0.0 | 400 ms | 0 |
| Wed 17 | 0 | 0.0 | 352 ms | 0 |
| Wed 19 | 0 | 0.0 | 498 ms | 0 |
| Wed 21 | 0 | 0.0 | 668 ms | 0 |
| Wed 23 | 0 | 0.0 | 295 ms | 0 |
| Thu 01 | 0 | 0.0 | 452 ms | 0 |
| Thu 03 | 0 | 0.0 | 294 ms | 0 |
| Thu 05 | 0 | 0.0 | 272 ms | 0 |
| Thu 08 | 0 | 0.0 | 1126 ms | 0 |
| Thu 10 | 0 | 0.0 | 339 ms | 0 |
| Thu 12 | 0 | 0.0 | 768 ms | 0 |
| Thu 14 | 0 | 0.0 | 376 ms | 0 |
| Thu 16 | 0 | 0.0 | 2732 ms | 0 |
| Thu 18 | 0 | 0.0 | 719 ms | 0 |
| Thu 20 | 0 | 0.0 | 371 ms | 0 |
| Thu 22 | 0 | 0.0 | 393 ms | 0 |
| Fri 00 | 0 | 0.0 | 1478 ms | 0 |
| Fri 01 | 0 | 0.0 | 957 ms | 0 |
| Fri 03 | 0 | 0.0 | 287 ms | 0 |
| Fri 05 | 0 | 0.0 | 271 ms | 0 |
| Fri 07 | 0 | 0.0 | 269 ms | 0 |
| Fri 09 | 0 | 0.0 | 247 ms | 0 |
| Fri 10 | 0 | 0.0 | 302 ms | 0 |
| Fri 11 | 0 | 0.0 | 3088 ms | 0 |
| Fri 13 | 0 | 0.0 | 355 ms | 0 |
| Fri 15 | 0 | 0.0 | 4038 ms | 0 |
| Fri 17 | 0 | 0.0 | 446 ms | 0 |
| Fri 19 | 0 | 0.0 | 345 ms | 0 |
| Fri 21 | 0 | 0.0 | 257 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 Feature.fm 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 Feature.fm goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Feature.fm alerts to Slack, Discord or a webhook — free.
We track Feature.fm (feature.fm) as part of the Entertainment group. Deepen your relationship with your fans, promote your music and grow your career as an artist. Music smart links, Pre-Saves, merch, tours and more - all in one place.
Feature.fm publishes an official status page at status.feature.fm; when we can read it, its incident level is folded into the status shown here.
Typical issues with entertainment services: streams buffering or not starting, playback errors, and app sign-in problems.
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: 856 ms average, 184–4038 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Feature.fm incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
856 ms on average over the last 24 hours (184–4038 ms).
Yes, at https://status.feature.fm.
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 Feature.fm here at once, the problem is on Feature.fm'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 Feature.fm. 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.