Philo Outage History
3 incidents recorded over the last 365 days, 3 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Philo Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 27, 2026 | Roku billed customers are losing access during paid cycle | 11h 31m | Resolved |
| Oct 9, 2026 | Phone Support Service Disruption | 20 min | Resolved |
| Sep 15, 2026 | Video playback freezing on Roku G000x/H000x models | 170h 28m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Philo incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Philo Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Philo acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Philo outage in this window ran 7d 2h, against a mean recovery of 2d 12h. If you depend on Philo in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.