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 21 min ago. Last stored result reached it in 179 ms.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 16 | 0 | 0.0 | 283 ms | 0 |
| Tue 19 | 0 | 0.0 | 112 ms | 0 |
| Tue 21 | 0 | 0.0 | 181 ms | 0 |
| Tue 23 | 0 | 0.0 | 99 ms | 0 |
| Wed 01 | 0 | 0.0 | 148 ms | 0 |
| Wed 04 | 0 | 0.0 | 81 ms | 0 |
| Wed 06 | 0 | 0.0 | 117 ms | 0 |
| Wed 08 | 0 | 0.0 | 218 ms | 0 |
| Wed 10 | 0 | 0.0 | 113 ms | 0 |
| Wed 13 | 0 | 0.0 | 211 ms | 0 |
| Wed 15 | 0 | 0.0 | 127 ms | 0 |
| Wed 17 | 0 | 0.0 | 123 ms | 0 |
| Wed 19 | 0 | 0.0 | 161 ms | 0 |
| Wed 21 | 0 | 0.0 | 225 ms | 0 |
| Wed 23 | 0 | 0.0 | 130 ms | 0 |
| Thu 01 | 0 | 0.0 | 144 ms | 0 |
| Thu 03 | 0 | 0.0 | 117 ms | 0 |
| Thu 06 | 0 | 0.0 | 261 ms | 0 |
| Thu 08 | 0 | 0.0 | 101 ms | 0 |
| Thu 10 | 0 | 0.0 | 121 ms | 0 |
| Thu 12 | 0 | 0.0 | 151 ms | 0 |
| Thu 14 | 0 | 0.0 | 121 ms | 0 |
| Thu 16 | 0 | 0.0 | 131 ms | 0 |
| Thu 18 | 0 | 0.0 | 150 ms | 0 |
| Thu 20 | 0 | 0.0 | 76 ms | 0 |
| Thu 22 | 0 | 0.0 | 183 ms | 0 |
| Fri 00 | 0 | 0.0 | 112 ms | 0 |
| Fri 02 | 0 | 0.0 | 111 ms | 0 |
| Fri 04 | 0 | 0.0 | 78 ms | 0 |
| Fri 06 | 0 | 0.0 | 273 ms | 0 |
| Fri 08 | 0 | 0.0 | 289 ms | 0 |
| Fri 10 | 0 | 0.0 | 124 ms | 0 |
| Fri 11 | 0 | 0.0 | 127 ms | 0 |
| Fri 13 | 0 | 0.0 | 168 ms | 0 |
| Fri 15 | 0 | 0.0 | 102 ms | 0 |
| Fri 17 | 0 | 0.0 | 229 ms | 0 |
| Fri 19 | 0 | 0.0 | 110 ms | 0 |
| Fri 21 | 0 | 0.0 | 130 ms | 0 |
| Fri 23 | 0 | 0.0 | 170 ms | 0 |
| Sat 01 | 0 | 0.0 | 137 ms | 0 |
| Sat 03 | 0 | 0.0 | 142 ms | 0 |
| Sat 05 | 0 | 0.0 | 157 ms | 0 |
| Sat 08 | 0 | 0.0 | 82 ms | 0 |
| Sat 10 | 0 | 0.0 | 201 ms | 0 |
| Sat 12 | 0 | 0.0 | 109 ms | 0 |
| Sat 14 | 0 | 0.0 | 82 ms | 0 |
| Sat 17 | 0 | 0.0 | 87 ms | 0 |
| Sat 19 | 0 | 0.0 | 179 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 FriendliAI 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 FriendliAI goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send confirmed down and recovery alerts to Slack, Discord or a webhook — free. Early warnings are part of Owner Alerts.
FriendliAI, at friendli.ai, is one of the Entertainment services we monitor. FriendliAI is the fastest inference cloud for agents, built to run frontier open-weight models in production at scale. It delivers up to 7x faster output token speed, up to 90% lower inference costs, and 99.99% uptime across the most demanding agent workloads — long-context inference, real-time streaming, and accurate tool calling.
FriendliAI publishes an official status page at status.friendli.ai; 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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 128 ms average, 74–201 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 FriendliAI incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
128 ms on average over the last 24 hours (74–201 ms).
Yes, at https://status.friendli.ai.
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 FriendliAI here at once, the problem is on FriendliAI'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 FriendliAI. 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.