Buenos Aires (EZE)

22 September 2025, 15:47 UTC
Platform South America Buenos Aires (EZE)
 
22 September 2025, 15:47 UTC

Traffic in Buenos Aires (EZE) has been temporarily rerouted.

All other locations and services are unaffected.

Platform North America South America Buenos Aires (EZE) Ashburn (IAD) Boston (BOS) Santiago (SCL) Chicago (CHI) Columbus (CMH) Miami (MIA)
 
03 April 2025, 00:25 UTC

We are investigating elevated errors to our Ashburn (IAD), Boston (BOS), Buenos Aires (EZE), Chicago (CHI), Columbus (CMH), Miami (MIA), Santiago (SCL) Point of Presence (POP).

All other products and services are unaffected by this incident.


 
03 April 2025, 01:04 UTC

Our engineers have identified the contributing factor and are applying a fix for our Ashburn (IAD), Boston (BOS), Buenos Aires (EZE), Chicago (CHI), Columbus (CMH), Miami (MIA), and Santiago (SCL) POP.

 
03 April 2025, 01:45 UTC

Our engineers have identified an additional contributing factor and are applying an adjusted mitigation strategy to Buenos Aires (EZE), Santiago (SCL), Ashburn (IAD), Boston (BOS), Chicago (CHI), Columbus (CMH), Miami (MIA) POPs.

All other locations and services are unaffected.

 
03 April 2025, 02:45 UTC

Engineering has confirmed the impact to Buenos Aires (EZE), Santiago (SCL), Ashburn (IAD), Boston (BOS), Chicago (CHI), Columbus (CMH), Miami (MIA) POPs has been mitigated.

 
03 April 2025, 02:56 UTC

Engineering has confirmed that Buenos Aires (EZE), Santiago (SCL), Ashburn (IAD), Boston (BOS), Chicago (CHI), Columbus (CMH), Miami (MIA) POPs has been fully restored. Customers may have experienced elevated errors and increased latency from 00:25 to 01:45 UTC.

This incident is resolved.

Affected customers may have experienced impact to varying degrees and to a shorter duration than as set forth above.

To offer feedback on our status page, click "Give Feedback

Status Post, Created Date/Time: 2025-04-03 00:51:46 UTC 



Note: Our Customer Escalation Management team will update the start date and time of the initial "investigating" status post upon the resolution of this incident. This update is meant to provide our customers and their end users with a potential impact window. The date and time mentioned in the message above indicates when the status post was requested by our Acute Incident Response team.


05 September 2024, 19:48 UTC
Platform North America Europe Asia South America Oceania Africa Amsterdam (AMS) Adelaide (ADL) Bogota (BOG) Cape Town (CPT) Auckland (AKL) Buenos Aires (EZE) Ghana (ACC) Ashburn (IAD) Brussels (BRU) Brisbane (BNE) Bangkok (BKK) Curitiba (CWB) Johannesburg (JNB) Copenhagen (CPH) Christchurch (CHC) Fortaleza (FOR) Dublin (DUB) Melbourne (MEL) Lima (LIM) Frankfurt (FRA) Perth (PER) Atlanta (PDK) Frankfurt (HHN) Rio de Janeiro (GIG) Boston (BOS) Chennai (MAA) Helsinki (HEL) Sydney (SYD) Santiago (SCL) Calgary (YYC) London (LCY) Wellington (WLG) Sāo Paulo (CGH) Chicago (CHI) London (LON) Sao Paulo (GRU) Dubai (FJR) London (LHR) Dubai (DXB) Lisbon (LIS) Fujairah (FJR) Hong Kong (HKG) Madrid (MAD) Hyderabad (HYD) Manchester (MAN) Marseille (MRS) Columbus (CMH) Milan (LIN) Columbus (LCK) Milan (MXP) Kolkata (CCU) Oslo (OSL) Dallas (DFW) Munich (MUC) Denver (DEN) Kuala Lumpur (KUL) Detroit (DTW) Gainesville (GNV) Paris (CDG) Manila (MNL) Honolulu (HNL) Paris (PAR) Rome (FCO) Houston (IAH) Mumbai (BOM) Sofia (SOF) Stockholm (BMA) Kansas City (MCI) New Delhi (DEL) Vienna (VIE) Osaka (ITM) Los Angeles (BUR) Los Angeles (LAX) Miami (MIA) Minneapolis (MSP) Seoul (ICN) Minneapolis (STP) Singapore (QPG) Montreal (YUL) Newark (EWR) New York (LGA) New York (NYC) Palo Alto (PAO) Tokyo (HND) Phoenix (PHX) Tokyo (NRT) Portland (PDX) Tokyo (TYO) San Jose (SJC) Seattle (BFI) St. Louis (STL) Toronto (YYZ) Vancouver (YVR)
 
05 September 2024, 19:48 UTC

We are investigating elevated errors to our Platform delivery services.

 
05 September 2024, 21:44 UTC

Our engineers are continuing to investigate the impact to our Platform delivery services.

 
05 September 2024, 22:01 UTC

Our engineers have identified the contributing factor and are applying a fix to our Platform delivery services.

 
05 September 2024, 23:00 UTC

Our engineers have identified the contributing factor and are continuing to apply the mitigation strategy to our Platform delivery services.

 
05 September 2024, 23:34 UTC

Engineering has deployed a fix and have confirmed a gradual recovery to our Platform delivery service. We will continue to monitor until we’ve confirmed that customer experience has been fully restored.

 
06 September 2024, 00:48 UTC

Engineering has confirmed that our Platform delivery services have been fully restored. Customers may have experienced elevated errors and latency. In addition, Compute customers may have also experienced delayed configuration deployments from the 5th of September at 19:48 to the 6th of September at 00:48 UTC.

This incident is resolved.

Affected customers may have experienced impact to varying degrees and to a shorter duration than as set forth above.

To offer feedback on our status page, click "Give Feedback

04 June 2024, 04:22 UTC
Platform South America Bogota (BOG) Buenos Aires (EZE) Rio de Janeiro (GIG) Santiago (SCL) Sao Paulo (GRU)
 
04 June 2024, 04:22 UTC

We are currently investigating performance impacts to our Rio de Janeiro (GIG), Bogota (BOG), Buenos Aires (EZE), Santiago (SCL), and Sao Paulo (GRU) Point of Presence (POP).

All other locations and services are unaffected.

 
04 June 2024, 05:06 UTC

Our engineers have identified the contributing factor and are applying a fix to our Bogota (BOG), Buenos Aires (EZE), Rio de Janeiro (GIG), Santiago (SCL), Sao Paulo (GRU) Point of Presence (POP).

All other locations and services are unaffected.

 
04 June 2024, 05:26 UTC

Engineering has confirmed the impact to Bogota (BOG), Buenos Aires (EZE), Rio de Janeiro (GIG), Santiago (SCL), Sao Paulo (GRU) Point of Presence (POP) has been mitigated.

 
04 June 2024, 05:46 UTC

Engineering has confirmed that Bogota (BOG), Buenos Aires (EZE), Rio de Janeiro (GIG), Santiago (SCL), Sao Paulo (GRU) Point of Presence (POP) has been fully restored. Customers may have experienced increased latency and 5xxx errors from 04:22 to 05:46 UTC.

This incident is resolved.

To offer feedback on our status page, click "Give Feedback

Platform South America Buenos Aires (EZE)
 
09 May 2024, 01:00 UTC

We're investigating possible performance impact affecting the Buenos Aires (EZE) data center.

All other locations and services are unaffected

 
09 May 2024, 01:22 UTC

Our engineers have identified the contributing factor and are applying a fix to our Buenos Aires (EZE) POP .

All other locations and services are unaffected.

 
09 May 2024, 02:11 UTC

Engineering has confirmed the impact to Buenos Aires (EZE) POP has been mitigated.

Platform South America Buenos Aires (EZE) Fortaleza (FOR) Lima (LIM) Rio de Janeiro (GIG)
 
17 April 2024, 19:15 UTC

We are investigating elevated errors to our Buenos Aires (EZE), Fortaleza (FOR), Lima (LIM), Rio de Janeiro (GIG) Point of Presence (POP)s.

 
17 April 2024, 21:00 UTC

Our engineers have identified the contributing factor and are applying a fix to our Buenos Aires (EZE), Fortaleza (FOR), Lima (LIM), Rio de Janeiro (GIG) Point of Presence (POP)s. 

All other locations and services are unaffected.

 
17 April 2024, 21:34 UTC

Engineering has confirmed the impact to our Buenos Aires (EZE), Fortaleza (FOR), Lima (LIM), Rio de Janeiro (GIG) Point of Presence (POP)s has been mitigated.

 
17 April 2024, 21:45 UTC

Engineering has confirmed that our Buenos Aires (EZE), Fortaleza (FOR), Lima (LIM), Rio de Janeiro (GIG) Point of Presence (POP)s has been fully restored. Customers may have experienced degraded performance from 19:15 to 21:45 UTC.

This incident is resolved.

Platform South America Buenos Aires (EZE)
 
14 March 2024, 00:20 UTC

We're investigating possible performance impact affecting the Buenos Aires (EZE) data center.

All other locations and services are unaffected

 
14 March 2024, 01:03 UTC

Engineering has deployed a fix and have confirmed a gradual recovery to Buenos Aires (EZE) . We will continue to monitor until we’ve confirmed that customer experience has been fully restored.




 
14 March 2024, 02:54 UTC

This event has been resolved.

09 March 2024, 01:08 UTC
Platform South America Bogota (BOG) Buenos Aires (EZE) Lima (LIM) Sao Paulo (GRU)
 
09 March 2024, 01:08 UTC

We're currently investigating performance impacts in Bogota (BOG), Buenos Aires (EZE), Lima (LIM), Sao Paulo (GRU).

All other locations and services are unaffected.

 
09 March 2024, 01:22 UTC

Our engineers have identified the contributing factor and are applying a fix to Bogota (BOG), Buenos Aires (EZE), Lima (LIM), Sao Paulo (GRU).

All other locations and services are unaffected.

 
09 March 2024, 02:04 UTC

Engineering has confirmed the impact to Bogota (BOG), Buenos Aires (EZE), Lima (LIM), Sao Paulo (GRU) has been mitigated.

 
09 March 2024, 02:14 UTC

Engineering has confirmed that Bogota (BOG), Buenos Aires (EZE), Lima (LIM), Sao Paulo (GRU) has been fully restored. Customers may have experienced increased latency and 5xx errors from 00:15 to 02:02 UTC.

This incident is resolved.

Platform South America Buenos Aires (EZE)
 
01 October 2023, 17:12 UTC

We're investigating possible performance impact affecting the Buenos Aires (EZE) data center.

All other locations and services are unaffected

 
01 October 2023, 17:24 UTC

This issue has been identified and a fix is being implemented. 

 
01 October 2023, 17:58 UTC

A fix has been implemented and we are monitoring the results.

 
01 October 2023, 18:51 UTC

This incident has been resolved.

Platform South America Buenos Aires (EZE) Lima (LIM)
 
26 July 2023, 01:02 UTC

We're investigating elevated errors in Buenos Aires (EZE), Lima (LIM).

All other locations and services are unaffected

 
26 July 2023, 01:35 UTC

A fix has been implemented and we are monitoring the results.

 
26 July 2023, 01:48 UTC

This incident has been resolved.