Elevated Errors for Ashburn (IAD), Boston (BOS), Buenos Aires (EZE), Chicago (CHI), Columbus (CMH), Miami (MIA), Santiago (SCL)

Incident

03 April 2025, 02:56 UTC

Elevated Errors for Ashburn (IAD), Boston (BOS), Buenos Aires (EZE), Chicago (CHI), Columbus (CMH), Miami (MIA), Santiago (SCL)

Status: closed

Start: 03 April 2025, 00:25 UTC

End: 03 April 2025, 02:56 UTC

Duration: 2 hours 31 minutes

Affected Components:

Platform North America South America Buenos Aires (EZE) Ashburn (IAD) Boston (BOS) Santiago (SCL) Chicago (CHI) Columbus (CMH) Miami (MIA)

Affected Groups:

All Public Users

Investigating

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.

Identified

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.

Identified

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.

Monitoring

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.

Resolved

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.