Keep these limits in mind when creating your Object Storage buckets. Limits apply per region, endpoint type, and account, unless otherwise specified.

Supported endpoint types by region

Review the table below to see which regions support each of the available endpoint types.

👍
Some regions support more than one endpoint. You should select the highest standard endpoint available when creating a new bucket. E3 endpoints offer the highest performance and capacity, followed by E2, then E1.
Legacy E0 endpoints include the four original Object Storage regions in Atlanta, Frankfurt, Newark, and Singapore. These endpoints have lower limits than all other endpoint types. There are no plans to increase limits for E0 endpoints.

Location	Country	Region	S3 hostname	E0	E1	E2	E3
North America
Atlanta, GA	United States	us-southeast	us-southeast-1.linodeobjects.com	✓
Chicago, IL	United States	us-ord	us-ord-1.linodeobjects.com		✓
Los Angeles, CA	United States	us-lax	us-lax-1.linodeobjects.com		✓
Miami, FL	United States	us-mia	us-mia-1.linodeobjects.com		✓
Newark, NJ	United States	us-east	us-east-1.linodeobjects.com	✓
Seattle, WA	United States	us-sea	us-sea-1.linodeobjects.com or		✓
Seattle, WA	United States	us-sea	us-sea-9.linodeobjects.com				LA*
Washington, DC	United States	us-iad	us-iad-1.linodeobjects.com, us-iad-10.linodeobjects.com		✓
Asia
Jakarta	Indonesia	id-cgk	id-cgk-1.linodeobjects.com		✓
Chennai	India	in-maa	in-maa-1.linodeobjects.com		✓
Mumbai 2	India	in-bom-2	in-bom-1.linodeobjects.com				LA*
Osaka	Japan	jp-osa	jp-osa-1.linodeobjects.com		✓
Singapore	Singapore	ap-south	ap-south-1.linodeobjects.com	✓
Singapore 2	Singapore	sg-sin-2	sg-sin-1.linodeobjects.com			✓
Europe
Frankfurt	Germany	eu-central	eu-central-1.linodeobjects.com	✓
Frankfurt 2	Germany	de-fra-2	de-fra-1.linodeobjects.com				LA*
Madrid	Spain	es-mad	es-mad-1.linodeobjects.com		✓
Paris	France	fr-par	fr-par-1.linodeobjects.com		✓
London 2	Great Britain	gb-lon	gb-lon-1.linodeobjects.com				✓
Milan	Italy	it-mil	it-mil-1.linodeobjects.com		✓
Amsterdam	Netherlands	nl-ams	nl-ams-1.linodeobjects.com		✓
Stockholm	Sweden	se-sto	se-sto-1.linodeobjects.com		✓
Oceania
Melbourne	Australia	au-mel	au-mel-1.linodeobjects.com			✓
South America
São Paulo	Brazil	br-gru	br-gru-1.linodeobjects.com		✓

*This endpoint is in Limited Availability status, if you would like to request access please open a support ticket.

Supported features by endpoint type

Feature support is consistent across endpoints, with the exception of the following three items.

	E0 (Legacy)	E1	E2	E3
Object level Access Control Lists	Yes	Yes	No	No
Custom domain support	Yes	Yes	No	No
In product static website support *	Yes	Yes	No	No

*For static website support you should use the CDN vs. supporting out of Object Storage directly.

Product limits

Object Storage limits by endpoint type

Limit	E0 (Legacy)	E1	E2	E3
Performance limits
Default number of Requests Per Second (RPS), per bucket	750	750	2,000	2,000
Maximum number of Requests Per Second (RPS), per bucket	750	<=2,000	<=5,000	20,000
Maximum Lifecycle Policy Deletes Per Second, per bucket (see Note 1)	75	75	100	300
Quotas
Default capacity per account, per endpoint	5 TB	100 TB	100 TB	500 TB
Default number of objects per account, per endpoint	50 M	100 M	100 M	500 M
Maximum number of buckets per account, per endpoint	1,000	1,000	1,000	1,000
Connection limits
Connections per bucket	<per bucket rate limit	<per bucket rate limit	<per bucket rate limit	2,000
Connections per account	750	750	2,000	2,000
Bucket Limits
Maximum capacity per bucket	1 TB	1 PB	5 PB	5 PB
Maximum number of objects per bucket	50 million	100 million	100 million	10 billion

Note 1: Lifecycle Policy deletes execute over a 24 hour period. The Lifecycle delete rate per second, per bucket, is the maximum rate that can be expected over a 24 hour period.

Multi-part uploads

The maximum upload size of a single object is 5 GB. You can use multi-part uploads to upload an object that exceeds this limit. Both s3cmd and Cyberduck will do this for you automatically as part of the upload process.

Bucket rate limits

Bucket rate limits specify the maximum Requests Per Second (RPS) for an endpoint. The rate limits for E0 and E1 endpoints are calculated differently than the E2 and E3 endpoints.

For E0 and E1 endpoints all operations count towards one rate limit for the bucket.
For E2 and E3 endpoints there are separate rate limits for each operation.


Operation	E0/E1 Default Rate Limits	E2/E3 Default Rate Limits	E2 Maximum Rate Limits	E3 Maximum Rate Limits
GET	750 RPS Limit for all operations combined. You can request an override of up to 2,000 RPS.	2,000 RPS	5,000 RPS	20,000 RPS


PUT		500 RPS	1,000 RPS	2,000 RPS
LIST		100 RPS	200 RPS	400 RPS
DELETE		200 RPS	200 RPS	400 RPS
All other operations		400 RPS	800 RPS	1,000 RPS

*Contact support to request an increase to the default RPS, per bucket.

Optimize to avoid rate limiting

The rate limit for the number of RPS applies to a bucket and is evaluated against each bucket once per second. If the duration of any request is greater than one second, any open requests will count against the rate limit in the next one second window.

For example, assume there are 750 requests for a single bucket with a duration of two seconds each. All of the requests that do not complete within the first second will count against the rate limit in the next second. With a rate limit of 750 RPS for the bucket, no additional requests can be processed within the two second window until the first 750 requests complete. Any requests that are rate limited will receive a 503 response.

To help avoid rate limiting you can structure your data across multiple buckets, each of which will have its own rate limit.