put.io Outage History

put.io is up right now

put.io had 3 outages in the last 2 years totaling 104h 34m of downtime — averaging 0.1 incidents per month.

There were 3 put.io outages since December 21, 2024 totaling 104h 34m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.put.io

Major August 5, 2026

%2 of files might be unavailable

Detected by Pingoru
Aug 05, 2026, 04:36 AM UTC
Resolved
Aug 05, 2026, 09:54 AM UTC
Duration
5h 17m
Affected: FilesTransfersStreaming
Timeline · 5 updates
  1. investigating Aug 05, 2026, 04:36 AM UTC

    %2 of files might be unavailable. We are currently investigating the issue.

  2. monitoring Aug 05, 2026, 05:29 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. identified Aug 05, 2026, 05:50 AM UTC

    The issue has been identified and a fix is being implemented.

  4. monitoring Aug 05, 2026, 09:38 AM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Aug 05, 2026, 09:54 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical March 18, 2026

Major outage in our datacenter

Detected by Pingoru
Mar 18, 2026, 11:04 PM UTC
Resolved
Mar 18, 2026, 11:48 PM UTC
Duration
43m
Affected: FilesTransfersStreaming
Timeline · 3 updates
  1. investigating Mar 18, 2026, 11:04 PM UTC

    We are currently investigating this issue.

  2. monitoring Mar 18, 2026, 11:12 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Mar 18, 2026, 11:48 PM UTC

    This incident has been resolved.

Read the full incident report →

Major December 21, 2024

Error in YouTube downloads.

Detected by Pingoru
Dec 21, 2024, 11:00 AM UTC
Resolved
Dec 25, 2024, 01:33 PM UTC
Duration
4d 2h
Affected: Transfers
Timeline · 2 updates
  1. investigating Dec 24, 2024, 02:35 PM UTC

    Most YouTube downloads currently error as `Could not download`. This is due to a recent change on their side. We're working on a solution.

  2. resolved Dec 25, 2024, 01:33 PM UTC

    The issue remains unresolved as there are currently no solutions available. We are awaiting a fix or solution to emerge.

Read the full incident report →