Philo Outage History

Started Oct 27, 2026, 02:04 PM UTC· resolved Oct 28, 2026, 01:34 AM UTC

1. investigating Oct 27, 2026, 02:04 PM UTC

   We are currently investigating this incident where customers are losing access to viewing paid content for Roku billed customers.

2. identified Oct 27, 2026, 03:08 PM UTC

   Issue has been identified! We are starting to fix impacted users and restore access. Immediate fix can be done by closing the Philo app and then relaunching it.

3. monitoring Oct 27, 2026, 08:09 PM UTC

   We implemented a fix and are currently monitoring the results!

4. resolved Oct 27, 2026, 08:14 PM UTC

   This incident has been resolved!

5. identified Oct 27, 2026, 10:22 PM UTC

   Identified that some users were missed by our initial fix. Working on getting those addressed!

6. identified Oct 27, 2026, 10:24 PM UTC

   We implemented a fix and are currently monitoring the result.

7. identified Oct 27, 2026, 10:25 PM UTC

   Roku-billed customers may experience issues accessing content during their active billing period.

8. resolved Oct 28, 2026, 01:34 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 09, 2026, 10:42 PM UTC· resolved Oct 09, 2026, 11:00 PM UTC

1. investigating Oct 09, 2026, 10:42 PM UTC

   We’re currently experiencing issues with our Phone Support service. Chat and Email Support remain available, but may experience some delays while we work to resolve the issue. Our team is actively investigating and working to restore normal service as quickly as possible. We appreciate your patience and apologize for any inconvenience..

2. investigating Oct 09, 2026, 10:42 PM UTC

   We’re currently experiencing issues with our Phone Support service. Chat and Email Support remain available, but may experience some delays while we work to resolve the issue. Our team is actively investigating and working to restore normal service as quickly as possible. We appreciate your patience and apologize for any inconvenience.

3. monitoring Oct 09, 2026, 10:57 PM UTC

   We implemented a fix and are currently monitoring the result..

4. monitoring Oct 09, 2026, 10:57 PM UTC

   We implemented a fix and are currently monitoring the result.

5. resolved Oct 09, 2026, 11:00 PM UTC

   This incident has been resolved..

6. resolved Oct 09, 2026, 11:00 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 15, 2026, 04:00 PM UTC· resolved Sep 22, 2026, 06:33 PM UTC

1. investigating Sep 15, 2026, 04:00 PM UTC

   We are currently investigating this incident.

2. investigating Sep 15, 2026, 04:00 PM UTC

   We are currently investigating this incident..

3. identified Sep 15, 2026, 05:05 PM UTC

   Roku has identified the error causing the spike in playback issues for the affected devices.

4. identified Sep 15, 2026, 05:05 PM UTC

   Roku has identified the error causing the spike in playback issues for the affected devices..

5. resolved Sep 22, 2026, 06:26 PM UTC

   Roku has confirmed that the recent OS rollout has been reverted and that the issue should be resolved..

Read the full incident report →

Started Jul 27, 2026, 12:40 AM UTC· resolved Jul 27, 2026, 01:24 AM UTC

1. identified Jul 27, 2026, 12:40 AM UTC

   Customers who are trying to sign up or reactivate their Philo accounts using Apple billing are currently impacted by an outage on Apple's end: .

2. identified Jul 27, 2026, 12:40 AM UTC

   Customers who are trying to sign up or reactivate their Philo accounts using Apple billing are currently impacted by an outage on Apple's end:

3. resolved Jul 27, 2026, 01:24 AM UTC

   This incident has been resolved! If any possible purchases were made during this downtime, please restart your Philo app to get things corrected. Contact our support team should any issues continue..

4. resolved Jul 27, 2026, 01:24 AM UTC

   This incident has been resolved! If any possible purchases were made during this downtime, please restart your Philo app to get things corrected. Contact our support team should any issues continue.

Read the full incident report →

Started Jun 23, 2026, 02:42 AM UTC· resolved Jun 24, 2026, 06:23 PM UTC

1. investigating Jun 23, 2026, 02:42 AM UTC

   We are currently investigating this incident..

2. investigating Jun 23, 2026, 02:42 AM UTC

   We are currently investigating this incident.

3. identified Jun 23, 2026, 07:42 AM UTC

   Amazon confirmed they identified the issue and are working on a fix. Our engineers are also working on restoring access for impacted customers. .

4. identified Jun 23, 2026, 07:42 AM UTC

   Amazon confirmed they identified the issue and are working on a fix. Our engineers are also working on restoring access for impacted customers.

5. identified Jun 23, 2026, 03:00 PM UTC

   We are aware that there are some Amazon billed customers that are still affected by the Amazon Outage. Our engineers our continuing to work on restoring access to customers who were impacted..

6. identified Jun 23, 2026, 03:00 PM UTC

   We are aware that there are some Amazon billed customers that are still affected by the Amazon Outage. Our engineers our continuing to work on restoring access to customers who were impacted.

7. monitoring Jun 23, 2026, 03:56 PM UTC

   We received the all clear from Amazon and have pushed changes we had implemented to mitigate the issue and are currently monitoring the result..

8. monitoring Jun 23, 2026, 03:56 PM UTC

   We received the all clear from Amazon and have pushed changes we had implemented to mitigate the issue and are currently monitoring the result.

9. resolved Jun 24, 2026, 06:23 PM UTC

   This incident has been resolved. If you are actively billed by Amazon and still having symptoms of not being able to access paid content or asked to pay again, please reach out to our support team so we can assist you further..

10. resolved Jun 24, 2026, 06:23 PM UTC

    This incident has been resolved. If you are actively billed by Amazon and still having symptoms of not being able to access paid content or asked to pay again, please reach out to our support team so we can assist you further.

Read the full incident report →

Started Mar 03, 2026, 10:42 PM UTC· resolved Mar 04, 2026, 12:03 AM UTC

1. investigating Mar 03, 2026, 10:42 PM UTC

   We are currently investigating an issue that appears to be causing some users to encounter a black screen or loading dots when trying to view a show page. .

2. identified Mar 03, 2026, 11:24 PM UTC

   Our engineers believe they have identified the issue and are working on a possible solution. .

3. resolved Mar 04, 2026, 12:03 AM UTC

   The issue is now resolved. Thank you for your patience!.

Read the full incident report →

Started Oct 24, 2025, 05:22 PM UTC· resolved Oct 24, 2025, 05:43 PM UTC

1. investigating Oct 24, 2025, 05:22 PM UTC

   When opening the app, you may encounter a “shruggie” error message similar to what appears on the web..

2. identified Oct 24, 2025, 05:23 PM UTC

   We are continuing to work on a fix for this incident..

3. monitoring Oct 24, 2025, 05:28 PM UTC

   We implemented a fix and are currently monitoring the result..

4. resolved Oct 24, 2025, 05:43 PM UTC

   This incident has been resolved..

Read the full incident report →

Started Oct 22, 2025, 07:33 PM UTC· resolved Oct 22, 2025, 10:01 PM UTC

1. investigating Oct 22, 2025, 07:33 PM UTC

   We’re currently experiencing a service outage affecting Fire TV. Our engineering team is actively working to resolve the issue and restore service as quickly as possible..

2. identified Oct 22, 2025, 08:29 PM UTC

   .

3. resolved Oct 22, 2025, 10:01 PM UTC

   This incident has been resolved..

Read the full incident report →

Started May 20, 2025, 09:41 PM UTC· resolved May 20, 2025, 09:41 PM UTC

1. resolved May 20, 2025, 09:41 PM UTC

   Our engineers are investigating an issue causing problems for some customers with the video player..

2. resolved May 20, 2025, 11:11 PM UTC

   This incident has been resolved..

Read the full incident report →

Started Apr 23, 2025, 09:51 PM UTC· resolved Apr 24, 2025, 01:47 AM UTC

1. identified Apr 23, 2025, 09:51 PM UTC

   An external service used to deliver **email** codes for our **sign-up** and **sign-in** flows are currently impacted. This service is actively investigating the issue. Temporary workaround for existing customers is to use an already linked mobile number to your account as your sign-in method..

2. monitoring Apr 23, 2025, 10:14 PM UTC

   Our email delivery service looks to be improving and getting sign-up and sign-in issues resolved! There may be some codes that are have timed out, so signing back in to get a new code might be required. We'll continue to monitor the status until we have confirmed the issue to be fully resolved..

3. resolved Apr 24, 2025, 01:47 AM UTC

   This incident has been resolved..

Read the full incident report →

Started Jan 29, 2025, 03:07 PM UTC· resolved Jan 29, 2025, 03:31 PM UTC

1. investigating Jan 29, 2025, 03:07 PM UTC

   We are currently investigating this incident..

2. monitoring Jan 29, 2025, 03:26 PM UTC

   We have implemented a fix and are currently monitoring the result..

3. resolved Jan 29, 2025, 03:31 PM UTC

   This incident has been resolved..

Read the full incident report →

Started Jan 15, 2025, 09:05 PM UTC· resolved Jan 15, 2025, 09:30 PM UTC

1. identified Jan 15, 2025, 09:05 PM UTC

   We've received reports that videos are not playable and/or there is a black screen. We've identified the issue and are working on a fix..

2. monitoring Jan 15, 2025, 09:27 PM UTC

   A fix has been deployed and we are monitoring. .

3. resolved Jan 15, 2025, 09:30 PM UTC

   This incident has been resolved..

Read the full incident report →

Started Nov 14, 2024, 12:17 AM UTC· resolved Nov 14, 2024, 12:38 AM UTC

1. investigating Nov 14, 2024, 12:17 AM UTC

   We are actively investigating errors with video playback for live content. Our engineering team is working as quickly as possible to restore things, and we will post updates as they become available..

2. monitoring Nov 14, 2024, 12:32 AM UTC

   We believe we have identified and resolved the main issue, and are continuing to monitor for any remaining user impact. .

3. resolved Nov 14, 2024, 12:38 AM UTC

   The issue is now resolved. We appreciate everyone's patience and understanding!.

Read the full incident report →