File Storage · Brazil

Data inside the country, and the privacy certificate that comes with it

All three Brazilian datasheets declare ISO 27701, the privacy management extension on top of ISO 27001: the certification usually requested when a volume holds personal data. Fortaleza adds SOC 1, SOC 2 and SOC 3, ISO 37301, ISO 50001 and the Carbon Neutral and Zero Landfill marks; São Paulo declares Tier III Design and Tier III Constructed Facility. The volume mounts from the same PoP where the compute runs, so it does not leave the country to do it.

3

PoPs

57

Listed carriers

3

Exchange points

Why here

  • ISO 27701 declared at all three Brazilian sites: not a repeated badge, it is on all three datasheets.
  • Fortaleza: SOC 1, SOC 2, SOC 3, TR3, ISO 37001, ISO 37301, ISO 50001, Carbon Neutral and Zero Landfill.
  • São Paulo: Tier III Design Documents and Tier III Constructed Facility, plus ISO 22301 for continuity.

This country's PoPs, one by one

Nominal provisioning window for the site, computed by the catalog over the fastest available configuration. It is a reference lead time, not a contractual commitment: stock moves, and the firm date is confirmed by Engineering.

São Paulo

GRU

99.98%Published SLA

Activation window
Immediate
Address
Rua Eid. Manssur N° 666, Parque São George, Rodoviária Raposo Tavares, Km 25 – Cotia, São Paulo
Reference airport
Guarulhos International Airport

Rio de Janeiro

GIG

99.98%Published SLA

Activation window
Immediate
Address
Av. Dom Pedro II N° 329, Quinta Da Boa Vista – Rio de Janeiro
Reference airport
Galeão International Airport · 12 km

Fortaleza

FOR

99.98%Published SLA

Activation window
Immediate
Address
Tv. Dep. Francisco Marrocos Portela 1161, Alto Alegre II, Fortaleza - CE, 61933-120
Reference airport
Pinto Martins International Airport

Interconnection and peering

São Paulo

IX.br [PTT São Paulo]

Rio de Janeiro

IX.br [PTT Rio]

Fortaleza

IX.br [PTT Fortaleza]

Estimated latency from cities in this country

Geodesic estimates (great-circle distance × a fibre route factor), not measurements. Use them to compare which PoP sits closer to each origin; they are not an RTT promise.

OriginSão PauloGRURio de JaneiroGIGFortalezaFOR
São Paulo~5msclosest~11ms~43ms
Rio de Janeiro~11ms~5msclosest~40ms
Brasília~19msclosest~20ms~32ms
Belo Horizonte~13ms~10msclosest~35ms
Curitiba~10msclosest~16ms~48ms
Porto Alegre~19msclosest~23ms~56ms
Recife~39ms~35ms~15msclosest
Fortaleza~43ms~40ms~5msclosest
Manaus~48ms~51ms~43msclosest