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 11 min ago. Last stored result reached it in 565 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 17 | 0 | 0.0 | 612 ms | 0 |
| Mon 19 | 0 | 0.0 | 572 ms | 0 |
| Mon 21 | 0 | 0.0 | 632 ms | 0 |
| Mon 23 | 0 | 0.0 | 553 ms | 0 |
| Tue 01 | 0 | 0.0 | 625 ms | 0 |
| Tue 03 | 0 | 0.0 | 608 ms | 0 |
| Tue 05 | 0 | 0.0 | 558 ms | 0 |
| Tue 07 | 0 | 0.0 | 644 ms | 0 |
| Tue 10 | 0 | 0.0 | 651 ms | 0 |
| Tue 12 | 0 | 0.0 | 474 ms | 0 |
| Tue 14 | 0 | 0.0 | 630 ms | 0 |
| Tue 16 | 0 | 0.0 | 754 ms | 0 |
| Tue 18 | 0 | 0.0 | 642 ms | 0 |
| Tue 21 | 0 | 0.0 | 663 ms | 0 |
| Tue 23 | 0 | 0.0 | 344 ms | 0 |
| Wed 01 | 0 | 0.0 | 609 ms | 0 |
| Wed 03 | 0 | 0.0 | 601 ms | 0 |
| Wed 06 | 0 | 0.0 | 569 ms | 0 |
| Wed 08 | 0 | 0.0 | 467 ms | 0 |
| Wed 10 | 0 | 0.0 | 605 ms | 0 |
| Wed 12 | 0 | 0.0 | 581 ms | 0 |
| Wed 14 | 0 | 0.0 | 626 ms | 0 |
| Wed 16 | 0 | 0.0 | 646 ms | 0 |
| Wed 19 | 0 | 0.0 | 588 ms | 0 |
| Wed 21 | 0 | 0.0 | 758 ms | 0 |
| Wed 23 | 0 | 0.0 | 628 ms | 0 |
| Thu 01 | 0 | 0.0 | 587 ms | 0 |
| Thu 03 | 0 | 0.0 | 475 ms | 0 |
| Thu 05 | 0 | 0.0 | 539 ms | 0 |
| Thu 07 | 0 | 0.0 | 739 ms | 0 |
| Thu 09 | 0 | 0.0 | 587 ms | 0 |
| Thu 11 | 0 | 0.0 | 689 ms | 0 |
| Thu 14 | 0 | 0.0 | 622 ms | 0 |
| Thu 16 | 0 | 0.0 | 730 ms | 0 |
| Thu 18 | 0 | 0.0 | 635 ms | 0 |
| Thu 20 | 0 | 0.0 | 657 ms | 0 |
| Thu 22 | 0 | 0.0 | 589 ms | 0 |
| Thu 23 | 0 | 0.0 | 576 ms | 0 |
| Fri 01 | 0 | 0.0 | 610 ms | 0 |
| Fri 03 | 0 | 0.0 | 385 ms | 0 |
| Fri 05 | 0 | 0.0 | 675 ms | 0 |
| Fri 07 | 0 | 0.0 | 665 ms | 0 |
| Fri 09 | 0 | 0.0 | 742 ms | 0 |
| Fri 10 | 0 | 0.0 | 532 ms | 0 |
| Fri 11 | 0 | 0.0 | 538 ms | 0 |
| Fri 13 | 0 | 0.0 | 669 ms | 0 |
| Fri 15 | 0 | 0.0 | 539 ms | 0 |
| Fri 17 | 0 | 0.0 | 565 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 Linkfire 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 Linkfire goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Linkfire alerts to Slack, Discord or a webhook — free.
We track Linkfire (linkfire.com) as part of the Entertainment group. Smart links for music marketing and podcast promotion. From your first single to your first world tour, Linkfire simplifies music and podcast promotion every step of the way. Trusted by major labels and over 50k artists.
Linkfire publishes an official status page at status.linkfire.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with 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: 584 ms average, 190–742 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 Linkfire incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
584 ms on average over the last 24 hours (190–742 ms).
Yes, at https://status.linkfire.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 Linkfire here at once, the problem is on Linkfire'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 Linkfire. 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.