- Service Status
- /
- ImageKit

Is ImageKit Down?
- ImageKit's status page
- Operational · no open incidents
- FlareWarden checks
- Website reachable · 8 of 8 regions · 304 ms
Right now
The verdict is the worse of these two. How we decide
ImageKit's status page
imagekitio.statuspage.io · read · checked every 3 minutes
| Component | Status |
|---|---|
| Image Transformation - SGP Region | Operational |
| Image Transformation - MUM Region | Operational |
| Image Transformation - US East Region | Operational |
| Image Transformation - US West Region | Operational |
| Image Transformation - AUS Region | Operational |
| Imagekit Website & Dashboard | Operational |
| Fast Upload API | Operational |
| REST API | Operational |
| AWS cloudfront | Operational |
| Video Delivery and Processing | Operational |
FlareWarden checks
imagekit.io from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours
- Regions up
- 8 of 8
- Response
- 304 ms
- Checked
By region
- Amsterdam reachable, 67 ms
- Dallas reachable, 173 ms
- Paris reachable, 235 ms
- San Jose reachable, 109 ms
- Singapore reachable, 261 ms
- Stockholm reachable, 194 ms
- Sydney reachable, 1137 ms
- Toronto reachable, 259 ms
Timing by region
| Region | DNS | TCP | TLS | TTFB |
|---|---|---|---|---|
| Amsterdam | 40 ms | 4 ms | 7 ms | 58 ms |
| Dallas | 112 ms | 1 ms | 4 ms | 146 ms |
| Paris | 114 ms | 17 ms | 19 ms | 191 ms |
| San Jose | 88 ms | 2 ms | 7 ms | 102 ms |
| Singapore | 241 ms | 2 ms | 7 ms | 256 ms |
| Stockholm | 143 ms | 1 ms | 5 ms | 178 ms |
| Sydney | 319 ms | 1 ms | 3 ms | 1134 ms |
| Toronto | 205 ms | 8 ms | 13 ms | 237 ms |
History
Incidents ImageKit reported
Since Oct 22, 15 days · from imagekitio.statuspage.io
- Incidents
- 1
- Major or critical
- 0
- Median to resolve
- 28d 5h
- lasted 28d 5h
ImageKit website availability
Measured by FlareWarden · imagekit.io
- Last 7 days
- 100%
- Last 30 days
- 100%
- Last 90 days
- 100%
- Avg response, 30 days
- 205ms
Last 30 days
73-day clean streakMeasured by FlareWarden's own checks of imagekit.io from multiple regions every 6 hours. ImageKit's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 73 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
What ImageKit does
ImageKit optimizes and delivers images and video over a global CDN, converting to modern formats such as AVIF and WebP and applying more than 50 URL-based transformations on the fly. It attaches to storage you already have, including S3, Google Cloud Storage, Azure Blob and plain HTTP origins, rather than replacing it. Around 300,000 developers and 3,000 businesses use it.
What an outage looks like
Images and video fail to load across a site, leaving broken placeholders on pages that are otherwise fine, because the markup is yours and only the media URLs point at ImageKit. New transformations return errors while previously delivered variants may still be served. Uploads through the Fast Upload API fail, so newly added product photos never appear. The dashboard will not open.
What to do about it
Check imagekitio.statuspage.io. Image Transformation is reported per region, with separate rows for US East, US West, EU, Singapore, Mumbai and Australia, so confirm the region serving your traffic before concluding it is global. Video Delivery and Processing, the Fast Upload API, the REST API and the website and dashboard are listed individually. Your original files sit in your own origin storage and are not at risk.
Is it down for everyone, or just you?
If this page says ImageKit is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.
Related services
ImageKit outage FAQ
Are my original images lost?
Is the outage global or only my region?
Why do some images work and others do not?
Does an ImageKit outage stop my pages loading?
How we measure this
- We request ImageKit's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
- Response times average only the regions that actually served the page, so a timeout never inflates the number.
- Where ImageKit publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of ImageKit itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.
Get alerted when ImageKit goes down
We check ImageKit every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.
Start Free Monitoring

