Basalts3 api

Product

Three sites, one namespace

A region is three facilities within 40 km. Objects are split into sixteen fragments and spread across them, so losing a building is a metric, not an incident.

S3 API gatewaystateless, anycastPlacement12+4 erasureStorage nodes3 facilitiesScrubbercontinuous verify

Durability

Coding
12 data + 4 parity fragments
Placement
3 facilities, max 6 fragments each
Scrub interval
every object every 14 days
Annual durability
99.999999999%

Availability

Read SLA
99.99% monthly
Write SLA
99.9% monthly
Site loss
reads continue, writes degrade to 2 sites
Planned maintenance
no availability impact

Performance

TTFB, cached
8 ms p50
TTFB, cold
18 ms p50 / 61 ms p99
Per-account throughput
40 Gbit/s default
Max object
5 TiB, 10,000 parts

Limits

Buckets per account
1,000 soft
Objects per bucket
unlimited
Request rate
8,000/s per prefix
Multipart parts
5 MiB – 5 GiB each

Storage classes

Class€/TB/monthRetrievalMin. durationUse for
Standard4.90immediatenoneactive data, CDN origins
Infrequent2.10immediate30 daysbackups, secondary copies
Archive0.90under 4 hours90 dayscompliance retention
Deep archive0.35under 12 hours180 daysregulatory, tape replacement
No retrieval fees on any class. Archive and deep archive have a minimum storage duration, which is a real cost we pass on. Getting the data back is always free — that is the whole point.