Is there an imgix outage?
imgix status: Systems Active
Last checked: 9 minutes ago
Get notified about any outages, downtime or incidents for imgix and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 9 minutes ago
Get notified about any outages, downtime or incidents for imgix and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for imgix.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
| Component | Status |
|---|---|
| API Service | Active |
| Docs | Active |
| Purging | Active |
| Rendering Infrastructure | Active |
| Sandbox | Active |
| Stripe API | Active |
| Web Administration Tools | Active |
| Content Delivery Network | Active |
| Amsterdam (AMS) | Active |
| Ashburn (BWI) | Active |
| Ashburn (DCA) | Active |
| Ashburn (IAD) | Active |
| Atlanta (ATL) | Active |
| Atlanta (FTY) | Active |
| Atlanta (PDK) | Active |
| Auckland (AKL) | Active |
| Boston (BOS) | Active |
| Brisbane (BNE) | Active |
| Buenos Aires (EZE) | Active |
| Cape Town (CPT) | Active |
| Chennai (MAA) | Active |
| Chicago (CHI) | Active |
| Chicago (MDW) | Active |
| Chicago (ORD) | Active |
| Columbus (CMH) | Active |
| Content Delivery Network | Active |
| Copenhagen (CPH) | Active |
| Curitiba (CWB) | Active |
| Dallas (DAL) | Active |
| Dallas (DFW) | Active |
| Denver (DEN) | Active |
| Dubai (FJR) | Active |
| Frankfurt (FRA) | Active |
| Frankfurt (HHN) | Active |
| Helsinki (HEL) | Active |
| Hong Kong (HKG) | Active |
| Houston (IAH) | Active |
| Johannesburg (JNB) | Active |
| London (LCY) | Active |
| London (LHR) | Active |
| Los Angeles (BUR) | Active |
| Los Angeles (LAX) | Active |
| Madrid (MAD) | Active |
| Melbourne (MEL) | Active |
| Miami (MIA) | Active |
| Milan (MXP) | Active |
| Minneapolis (MSP) | Active |
| Montreal (YUL) | Active |
| Mumbai (BOM) | Active |
| Newark (EWR) | Active |
| New York (JFK) | Active |
| New York (LGA) | Active |
| Osaka (ITM) | Active |
| Palo Alto (PAO) | Active |
| Paris (CDG) | Active |
| Perth (PER) | Active |
| Rio de Janeiro (GIG) | Active |
| San Jose (SJC) | Active |
| Santiago (SCL) | Active |
| Sāo Paulo (GRU) | Active |
| Seattle (SEA) | Active |
| Singapore (SIN) | Active |
| Stockholm (BMA) | Active |
| Sydney (SYD) | Active |
| Tokyo (HND) | Active |
| Tokyo (NRT) | Active |
| Tokyo (TYO) | Active |
| Toronto (YYZ) | Active |
| Vancouver (YVR) | Active |
| Wellington (WLG) | Active |
| DNS | Active |
| imgix DNS Network | Active |
| NS1 Global DNS Network | Active |
| Docs | Active |
| Netlify Content Distribution Network | Active |
| Netlify Origin Servers | Active |
| Storage Backends | Active |
| Google Cloud Storage | Active |
| s3-ap-northeast-1 | Active |
| s3-ap-northeast-2 | Active |
| s3-ap-southeast-1 | Active |
| s3-ap-southeast-2 | Active |
| s3-ca-central-1 | Active |
| s3-eu-central-1 | Active |
| s3-eu-west-1 | Active |
| s3-eu-west-2 | Active |
| s3-eu-west-3 | Active |
| s3-sa-east-1 | Active |
| s3-us-east-2 | Active |
| s3-us-standard | Active |
| s3-us-west-1 | Active |
| s3-us-west-2 | Active |
View the latest incidents for imgix and check for official updates:
Description: # What happened? On June 10, 2022, 07:16 UTC, the imgix service experienced an increase in elevated rendering errors. A fix was implemented at 08:35 UTC, which restored the service back to normal error levels. # How were customers impacted? Between 07:16 UTC and 08:32 UTC, some customers received errors when making requests through the Rendering API. Previously cached assets continued to serve a successful response, but some files that were not cached returned a 502 or 503 error. At its peak, error rates reached 6% for requests to the Rendering API. # What went wrong during the incident? Erratic network behavior from our upstream network provider caused an increase in error rates to our backend services. As errors began to grow, one of our systems we designed to automatically remediate backend failures failed to trigger, allowing errors to surface through the Rendering API. Remediations were being identified, though we were delayed in posting a public status update. Eventually, a fix was pushed, immediately restoring service. # What will imgix do to prevent this in the future? We are investigating the network behavior detected at our upstream provider in order to update our configurations. We are expecting these changes to prevent a similar incident from occurring. We will also be fixing our automated tooling so that error rates get resolved before they impact the rendering service. Lastly, we will be revisiting our policies for status updates to ensure that incidents are communicated in a timely manner.
Status: Postmortem
Impact: Critical | Started At: June 10, 2022, 8:29 a.m.
Description: We observed a short increase in rendering errors between the hours of 06:14 UTC to 06:23 UTC that was immediately resolved. While the incident is resolved, we are continuing to monitor the service and will continue to investigate the proximate cause.
Status: Resolved
Impact: None | Started At: May 5, 2022, 6:14 a.m.
Description: We observed a short increase in rendering errors between the hours of 06:14 UTC to 06:23 UTC that was immediately resolved. While the incident is resolved, we are continuing to monitor the service and will continue to investigate the proximate cause.
Status: Resolved
Impact: None | Started At: May 5, 2022, 6:14 a.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: April 7, 2022, 1:31 a.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: April 7, 2022, 1:31 a.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.
