Skip to main content
Zenfolio logo

Is Zenfolio Down?

No — Zenfolio is up

Reachable from 7 of 8 checked regions — 1 region answered but refused our checks

Average response time: 3659ms

Last checked · checks run every 6 hours

Official status page: https://status.zenfolio.com

Zenfolio uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
3139ms
Avg response, 30 days

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

30-day history

10-day clean streak
Aug 23: no data
Aug 24: no data
Aug 25: no data
Aug 26: no data
Aug 27: no data
Aug 28: no data
Aug 29: no data
Aug 30: no data
Aug 31: no data
Sep 1: no data
Sep 2: no data
Sep 3: no data
Sep 4: no data
Sep 5: no data
Sep 6: no data
Sep 7: no data
Sep 8: no data
Sep 9: no data
Sep 10: no data
Sep 11: no data
Sep 12: 100.00% uptime, 16 checks
Sep 13: 100.00% uptime, 31 checks
Sep 14: 100.00% uptime, 31 checks
Sep 15: 100.00% uptime, 32 checks
Sep 16: 100.00% uptime, 46 checks
Sep 17: 100.00% uptime, 21 checks
Sep 18: 100.00% uptime, 32 checks
Sep 19: 100.00% uptime, 31 checks
Sep 20: 100.00% uptime, 32 checks
Sep 21: 100.00% uptime, 15 checks
Aug 23 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.

bom
5084ms
DNS 295ms TCP 1ms TLS 4ms TTFB 4179ms
cdg
3179ms
DNS 135ms TCP 1ms TLS 5ms TTFB 3117ms
dfw
2488ms
DNS 49ms TCP 1ms TLS 4ms TTFB 2475ms
ewr
4503ms
DNS 18ms TCP 1ms TLS 5ms TTFB 4487ms
fra
2464ms
DNS 49ms TCP 1ms TLS 7ms TTFB 2443ms
gru
3930ms
DNS 123ms TCP 1ms TLS 4ms TTFB 3864ms
iad
3965ms
DNS 32ms TCP 1ms TLS 4ms TTFB 3819ms
jnb
HTTP 429 · challenge

Answered in 449ms — the origin is serving traffic, it just refused our client.

What Zenfolio does

Zenfolio hosts websites and client galleries for professional photographers, handling image upload and delivery, client proofing, print ordering and booking. A photographer's public portfolio and the private galleries they deliver shoots through both run on it. Zenfolio runs two generations of the platform side by side, Zenfolio and Zenfolio Classic, and also operates Photobooker and BookMe.

What an outage looks like

Galleries fail to load or show broken thumbnails while the site's pages render, because image delivery is reported separately from websites. Uploads stall part-way through a shoot. Clients can browse a gallery but cannot complete a print order, or the order completes without a confirmation email. Sign-in fails for the photographer while public galleries stay visible to visitors.

What to do about it

Read status.zenfolio.com and find your generation first. Zenfolio and Zenfolio Classic are listed as separate component groups, each with its own Websites, Upload, Download, Content Rendering, Order Processing, Email Communication, Login and Search rows, and Photobooker is a third group. A colleague on the other generation proves nothing about yours. If Order Processing is the affected row, tell clients to return later rather than retry payment.

Is it down for everyone, or just you?

If this page says Zenfolio 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

S
SmugMug
F
Flickr
Webflow
Webflow
Acuity Scheduling
Acuity Scheduling

Zenfolio outage FAQ

My galleries work but a client cannot order prints. Is Zenfolio down?
Partly. Order Processing is a component separate from Websites and Content Rendering on Zenfolio's status page, so galleries can load and images render perfectly while checkout fails. This is the expensive failure mode for a photographer, because nothing looks broken to you and the client usually leaves rather than reporting it. Check the Order Processing row for your platform generation.
A colleague's Zenfolio site is fine and mine is not. Why?
Most likely you are on different generations of the platform. Zenfolio reports Zenfolio and Zenfolio Classic as two separate component groups with their own Websites, Upload, Login and Order Processing rows, so an incident can take one while the other is untouched. Photobooker is reported separately again. Match the group to the product you actually log into before concluding the problem is local to you.
Will an upload that failed part-way lose my images?
The originals are still on your own machine, so nothing is lost there, but Zenfolio publishes no guarantee about how a partially completed upload is handled. Treat a stalled upload as incomplete rather than as partially saved: check the gallery for the file count you expected once Upload is reported operational, and re-upload the missing files rather than assuming the batch resumed.
Can clients still see galleries I already delivered?
It depends which component failed. Content Rendering and Download are listed separately from Websites, so a gallery page can load while the images inside it do not appear or cannot be downloaded. If the Websites row is the affected one, the gallery link itself will not open. Either way the gallery and its contents are not deleted, and access returns when the component does.
Does a Zenfolio outage stop booking enquiries reaching me?
It can, and through two different rows. Email Communication is a separate component in each product group, so a booking made through the site can succeed while the notification to you never sends. Bookings and BookMe are reported separately again. If you rely on Zenfolio for enquiries, check for new bookings in the dashboard after an incident rather than trusting that the absence of email means no activity.

How we measure this

  • We request Zenfolio'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 Zenfolio 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 Zenfolio 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