Is there an imgix outage?
imgix status: Systems Active
Last checked: 5 minutes ago
Get notified about any outages, downtime or incidents for imgix and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 5 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: There was an issue with requests to the Management API not completing. This incident started at 11:52 AM UTC and was resolved at 12:33 PM UTC. The rendering service was not impacted by this incident.
Status: Resolved
Impact: Minor | Started At: April 4, 2022, 11:52 a.m.
Description: There was an issue with requests to the Management API not completing. This incident started at 11:52 AM UTC and was resolved at 12:33 PM UTC. The rendering service was not impacted by this incident.
Status: Resolved
Impact: Minor | Started At: April 4, 2022, 11:52 a.m.
Description: # What happened? On December 17, 2021, 05:06 UTC, some uncached requests to the imgix service began to return a `503` response. By 05:36 UTC the issue had been completely resolved. # How were customers impacted? Between the hours of 05:01 UTC and 05:36 UTC, some requests to non-cached derivative images began to return a `503` error, with a 10% peak error rate being reached for parts of the incident. At 5:07 UTC, error rates began to decrease slowly, though a 5% error rate persisted until a fix was pushed at 5:36, which completely restored the service. # What went wrong during the incident? Large unexpected traffic patterns triggered a problematic interaction with a newly built internal automation, causing the initial incident. Our team pushed mitigations early on in the incident, though the mitigations had further unexpected interactions with the newly built automation. While the service _did_ begin to recover, the rate of recovery was slower than expected due to these interactions. Once the interaction was identified, another manual change was made which completely restored the service. # What will imgix do to prevent this in the future? We will be adding additional tooling which will enable us to more quickly identify proximate causes during incidents. We will also internally document the interactions and behaviors of our existing automation and mitigation runbooks to ensure smoother recovery times in the future. We also identified some improvement opportunities for some of our existing automation, which have completed fine-tuning.
Status: Postmortem
Impact: Major | Started At: Dec. 17, 2021, 5:33 a.m.
Description: # What happened? On December 12, 2021, 15:23 UTC, some imgix customers may have experienced issues with logging into their Dashboard and deploying Sources. Login issues were resolved by 16:23 UTC. Source deployment issues were resolved by 17:43 UTC. This incident only affected Web Administration tools - the rendering service was not affected. # How were customers impacted? Customers attempting to log into the dashboard may have encountered a login error. Once the login issue was resolved, it was discovered that Source deploys were delayed. By 17:43 UTC, all Source deployment issues had been fully resolved. # What went wrong during the incident? Our team quickly discovered that a major cloud provider was experiencing a regional outage. This affected several web administration components, such as imgix Dashboard logins and delayed Source deployments. Dashboard logins recovered on their own once the cloud provider recovered, though Source deployments remained delayed. It was assumed that Source deployments would eventually also resolve without intervention, though further investigation indicated that Source deployments required a manual fix, which took effect by 17:38 UTC. # What will imgix do to prevent this in the future? We will be auditing multi-region contingency plans for all web administration components along with implementing more monitoring to ensure that impacted components can be identified sooner.
Status: Postmortem
Impact: Minor | Started At: Dec. 15, 2021, 5:06 p.m.
Description: # What happened? On December 12, 2021, 15:23 UTC, some imgix customers may have experienced issues with logging into their Dashboard and deploying Sources. Login issues were resolved by 16:23 UTC. Source deployment issues were resolved by 17:43 UTC. This incident only affected Web Administration tools - the rendering service was not affected. # How were customers impacted? Customers attempting to log into the dashboard may have encountered a login error. Once the login issue was resolved, it was discovered that Source deploys were delayed. By 17:43 UTC, all Source deployment issues had been fully resolved. # What went wrong during the incident? Our team quickly discovered that a major cloud provider was experiencing a regional outage. This affected several web administration components, such as imgix Dashboard logins and delayed Source deployments. Dashboard logins recovered on their own once the cloud provider recovered, though Source deployments remained delayed. It was assumed that Source deployments would eventually also resolve without intervention, though further investigation indicated that Source deployments required a manual fix, which took effect by 17:38 UTC. # What will imgix do to prevent this in the future? We will be auditing multi-region contingency plans for all web administration components along with implementing more monitoring to ensure that impacted components can be identified sooner.
Status: Postmortem
Impact: Minor | Started At: Dec. 15, 2021, 5:06 p.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.
