Skip to main content
Zenfolio logo

Is Zenfolio Down?

No — Zenfolio is up
Zenfolio's status page
Operational · no open incidents
FlareWarden checks
Website reachable · 8 of 8 regions · 69 ms

Right now

The verdict is the worse of these two. How we decide

Zenfolio's status page

status.zenfolio.com · read · checked every 3 minutes

Operational
Zenfolio's components, as its status page reports them
ComponentStatus
WebsitesOperational
UploadOperational
DownloadOperational
Content RenderingOperational
Order ProcessingOperational
Email CommunicationOperational
LoginOperational
SearchOperational
APIOperational
WebsitesOperational
UploadOperational
DownloadOperational
17 more, all operational · show all 29
All of Zenfolio's components
ComponentStatus
Zenfolio Classic
WebsitesOperational
UploadOperational
DownloadOperational
Content RenderingOperational
Order ProcessingOperational
Email CommunicationOperational
LoginOperational
SearchOperational
APIOperational
Zenfolio
WebsitesOperational
UploadOperational
DownloadOperational
Content RenderingOperational
Order ProcessingOperational
Email CommunicationOperational
LoginOperational
SearchOperational
ZenfolioAIOperational
Photobooker
Photobooker Home PageOperational
BookingsOperational
SearchOperational
Content RenderingOperational
Email CommunicationOperational
LoginOperational
Image DeliveryOperational
ArchiveOperational
BookMeOperational
Zenfolio Home PageOperational
Support CenterOperational

FlareWarden checks

zenfolio.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable
Regions up
8 of 8
Response
69 ms
Checked

By region

  • Amsterdam reachable, 70 ms
  • Ashburn reachable, 162 ms
  • Dallas reachable, 50 ms
  • Frankfurt reachable, 65 ms
  • Newark reachable, 68 ms
  • Paris reachable, 47 ms
  • Stockholm reachable, 60 ms
  • São Paulo reachable, 30 ms
Timing by region
Connection timing for each region that loaded the page
RegionDNSTCPTLSTTFB
Amsterdam30 ms2 ms5 ms44 ms
Ashburn132 ms3 ms6 ms145 ms
Dallas30 ms1 ms4 ms39 ms
Frankfurt37 ms2 ms4 ms52 ms
Newark40 ms3 ms4 ms52 ms
Paris25 ms1 ms5 ms36 ms
Stockholm34 ms1 ms4 ms49 ms
São Paulo11 ms1 ms4 ms19 ms
We check that zenfolio.com loads, not every feature behind it. Test it yourself

History

Incidents Zenfolio reported

Since Oct 22, 15 days · from status.zenfolio.com

Incidents
0
Major or critical
0
Median to resolve
—

No incidents reported in this window.

Zenfolio website availability

Measured by FlareWarden · zenfolio.com

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

Last 30 days

55-day clean streak
Oct 7: 100.00% uptime, 31 checks
Oct 8: 100.00% uptime, 30 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 32 checks
Oct 14: 100.00% uptime, 30 checks
Oct 15: 100.00% uptime, 30 checks
Oct 16: 100.00% uptime, 31 checks
Oct 17: 100.00% uptime, 29 checks
Oct 18: 100.00% uptime, 25 checks
Oct 19: 100.00% uptime, 24 checks
Oct 20: 100.00% uptime, 16 checks
Oct 21: 100.00% uptime, 29 checks
Oct 22: 100.00% uptime, 22 checks
Oct 23: 100.00% uptime, 23 checks
Oct 24: 100.00% uptime, 29 checks
Oct 25: 100.00% uptime, 24 checks
Oct 26: 100.00% uptime, 24 checks
Oct 27: 100.00% uptime, 16 checks
Oct 28: 100.00% uptime, 32 checks
Oct 29: 100.00% uptime, 32 checks
Oct 30: 100.00% uptime, 32 checks
Oct 31: 100.00% uptime, 30 checks
Nov 1: 100.00% uptime, 32 checks
Nov 2: 100.00% uptime, 30 checks
Nov 3: 100.00% uptime, 32 checks
Nov 4: 100.00% uptime, 32 checks
Nov 5: 100.00% uptime, 32 checks
Oct 7 Today
No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of zenfolio.com from multiple regions every 6 hours. Zenfolio's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 55 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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

Test it yourself

Related services

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. 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 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. 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 Zenfolio 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 Zenfolio 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 Zenfolio goes down

We check Zenfolio 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
Free plan available No credit card required