Correct block duration wording to match what was observed

Author: pushkarsingh32

README.md

@@ -34,7 +34,7 @@ Covered so far: every error class in [youtube-transcript-api](https://github.com
 
 The most common failures (`IpBlocked`, `RequestBlocked`) say something about the network the request came from, not about the video. In rough order of effort:
 
-1. Wait and retry later with a back-off instead of a tight loop. Blocks on one IP often lift after some hours.
+1. Wait and retry later with a back-off instead of a tight loop. How long a block lasts varies: on one home IP we saw a block lift after roughly 25 minutes and return soon after requests resumed at about ten a minute, so slow down well below that.
 2. Run from a different network. A home or office connection is treated differently from a cloud server.
 3. Send requests through a proxy provider. [youtube-transcript-api supports proxy configuration](https://github.com/jdepoix/youtube-transcript-api#working-around-ip-bans-requestblocked-or-ipblocked-exception).
 4. Cache what you fetch and fetch each video once.

data/errors.yaml

@@ -18,7 +18,7 @@ errors:
       kind: environment
       text: "No fixed video reproduces it. It depends on the network the request comes from: send enough requests from one IP, or run from a datacenter IP."
     actions:
-      - "Stop and wait. Blocks on a single IP often lift after some hours, so back off instead of retrying in a loop."
+      - "Stop and wait. How long a block lasts varies. On one home IP (2026-10-17) it lifted after roughly 25 minutes and came back soon after requests resumed at about ten a minute, so back off and slow down instead of retrying in a loop."
       - "Run the code from a different network, for example a home or office connection instead of a cloud server."
       - "Send the requests through a proxy provider. The library supports proxy configuration."
       - "Cache what you already fetched and fetch each video once."

errors/ipblocked.md

@@ -22,7 +22,7 @@ No fixed video reproduces it. It depends on the network the request comes from:
 
 ## What to do
 
-- Stop and wait. Blocks on a single IP often lift after some hours, so back off instead of retrying in a loop.
+- Stop and wait. How long a block lasts varies. On one home IP (2026-10-17) it lifted after roughly 25 minutes and came back soon after requests resumed at about ten a minute, so back off and slow down instead of retrying in a loop.
 - Run the code from a different network, for example a home or office connection instead of a cloud server.
 - Send the requests through a proxy provider. The library supports proxy configuration.
 - Cache what you already fetched and fetch each video once.