Contents x
Rate Limits
    • Print
    • Dark
      Light
    Contents

    Rate Limits

      • Print
      • Dark
        Light
      Article summary

      Backblaze implements rate limiting safeguards to ensure that all customers have consistent access to high-performance storage, protecting against potential disruptions caused by misuse or abuse of the APIs by other users.

      Rate Limit Error Codes

      The following error codes can be returned when rate limits are reached.

      Backblaze B2 Native API and Partner API Error

      HTTP STATUS CODEOVERVIEW
      429 - Too Many RequestsThe client has reached the limit of requests within a specific time period. This error response may include a Retry-After header where the value is the number of seconds a developer should wait before re-requesting the resource.

      Backblaze S3-Compatible API Error

      HTTP STATUS CODEOVERVIEW
      503 - SlowDownThe client has reached the limit of requests within a specific time period. This error response may include a Retry-After header where the value is the number of seconds a developer should wait before re-requesting the resource.

      Error Mitigation

      You can take the following steps to help avoid rate limit errors: 

      • Refactoring code to eliminate unnecessary requests.
      • Caching data when appropriate.
      • Handling 429 or 503 errors with a retry mechanism that implements exponential backoff.
      Retry Mechanisms
      The Backblaze B2 SDKs follow the guidelines that are provided in the Backblaze B2 Integration Checklist. If you work with a library that does not have a retry mechanism or you call the API endpoints directly from your code, refer to the integration checklist for guidance.

      You can find information about retry behavior for the AWS SDKs here.

      Contact the Support Team if you have any questions or if you see a 429 or 503 status code.

      Was this article helpful?
      What's Next