Service status
Nothing on this page was typed in advance.
Every line below is a live check against production, re-run at most once a minute. If a system ListPik depends on stops answering, this page turns before anyone writes a sentence about it.
Live checks
Five systems, each one asked directly.
Website and studio
Marketing pages, the photo studio, sign-in, and checkout screens.
The application server rendered this page, so the web tier answered.
OperationalEnhancement pipeline
The image model behind single-photo enhancement and virtual staging.
Accepting requests.
Operational643 msAccounts and credits
Postgres records for accounts, credit balances, and job history.
Answering normally.
Operational518 msPhoto storage
The private bucket holding uploaded originals and finished results.
Uploads and downloads are reachable.
Operational497 msBatch queue
The worker that drains multi-photo batches in the background.
Queued photos are being picked up on time.
Operational608 ms
Last 30 days
What actually happened to the photos.
Availability is only half of the question. These figures come from the job records themselves: every photo that reached a finished state in the window, whether it came out as a result or as a failure.
Fewer than 20 photos finished in the last 30 days. That is too small a sample to publish as a success rate, so no figure is shown until the window carries one.
Incident log
Written by hand, kept in full.
No incidents have been recorded since reporting began on August 27, 2026. Entries stay on this page once they are added, including the ones that are resolved.
How this is measured
The limits of the number.
Each check opens a real connection: a query against the account database, a listing against the private photo bucket, a request to the image model, and a look at whether queued photos are leaving the queue on time. Latency is the round trip measured from this server, so it includes the network between us.
There is no long-term probe archive behind this page yet, so ListPik does not publish a rolling uptime percentage. Saying “99.9% for ninety days” without ninety days of stored measurements would be exactly the kind of decorative claim the rest of the site argues against.
The reliability figures count only photos that reached a finished state, so a photo still waiting in the queue is neither a success nor a failure. Failed enhancements return the reserved credit automatically. Rates and durations are published; job volumes are not.
The same reading is available as JSON at /api/status if you would rather poll it than read it. It answers with a 503 while any system is in outage, so an external monitor can watch it directly.