Is ImageKit Down?

No — ImageKit is up

Reachable from all 8 checked regions

Average response time: 222ms

Last checked 5 hours ago · checks run every 6 hours

Official status page: https://imagekitio.statuspage.io

ImageKit uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

297ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 27 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

27-day clean streak

Aug 22 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams

32ms

DNS 12ms TCP 2ms TLS 7ms TTFB 25ms

arn

112ms

DNS 70ms TCP 1ms TLS 5ms TTFB 106ms

bom

93ms

DNS 64ms TCP 2ms TLS 6ms TTFB 81ms

ord

128ms

DNS 17ms TCP 1ms TLS 3ms TTFB 85ms

sin

104ms

DNS 80ms TCP 2ms TLS 8ms TTFB 97ms

sjc

198ms

DNS 158ms TCP 1ms TLS 6ms TTFB 191ms

syd

965ms

DNS 114ms TCP 1ms TLS 4ms TTFB 960ms

yyz

149ms

DNS 71ms TCP 8ms TLS 12ms TTFB 119ms

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 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

Bunny.net

Cloudflare

AWS

Vimeo

ImageKit outage FAQ

Are my original images lost?

No. ImageKit integrates with storage you already control, such as S3, Google Cloud Storage, Azure Blob or an HTTP origin, rather than requiring you to migrate files into it. An incident affects delivery and transformation, not the originals sitting in your bucket. If you upload through ImageKit's own media library instead, those files are stored on their side but an outage is still a delivery problem.

Is the outage global or only my region?

Often regional. Image Transformation is broken out into six separate rows on the status page: US East, US West, EU, Singapore, Mumbai and Australia. Visitors routed to a healthy region see working images while visitors elsewhere see breakage, which is why reports from your own team can disagree about whether anything is wrong at all.

Why do some images work and others do not?

Because delivery and transformation are separate concerns, and video is separate again. A variant that has already been generated and cached at the edge can keep serving while a request for a new size or format fails. That is why older pages look fine and a newly published page, which needs fresh transformations, is the one that breaks.

Does an ImageKit outage stop my pages loading?

The page itself loads, since the HTML comes from your own server or host. What fails is every element whose URL points at ImageKit, which on an image-heavy site is most of what a visitor notices. Pages that lazy-load media below the fold can look normal at first and break as the reader scrolls down.

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.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the 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. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when ImageKit goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required