Status
Is it working?
This page is written by a person, not by a monitor, and it is the one place to look before writing to us. If you are mid-event and something is wrong, the second half of this page is the useful half: it says what each kind of problem means for photos that have already been taken.
Everything is working
No known problems. This line is set by hand, so it means a person last looked on the date below rather than that a monitor checked a second ago.
Last checked 18 October 2026
There is no automated check behind that, and saying so is the point. We have not built uptime monitoring, so this page cannot tell you about a problem nobody has noticed yet, and it carries no uptime percentage because there is nothing honest to calculate one from. What it can do is stop you being the fifteenth person to report the same thing.
Where the live signal is
Everything here runs on two providers, both of which do have real monitoring and publish it. If this page is reachable and claims everything is fine, and your own experience says otherwise, these are the next two places to look — and if this page is not reachable at all, they are the first.
Vercel status
The website, the join pages and the browser camera.
Supabase status
The database, the photo storage and everything the app talks to.
Worth being clear about the obvious weakness: this page is hosted on one of those two providers, so a bad enough day there takes this page with it. The links above are hosted elsewhere and stay up when we do not, which is why they are here rather than embedded.
What a problem actually means for your event
These four fail separately, and knowing which one you are looking at changes what you should do about it. The short version, if you read nothing else: a photo that has been taken is very hard to lose, and nothing on this list quietly discards one.
Joining an event
A code is rejected, or scanning a card opens a page that will not finish loading. Guests already in the event are unaffected — this is the door, not the room.
If some guests are in and others cannot get in, try the typed code rather than the card: they take different routes to the same place and it is common for one to be sick while the other is fine.
Taking photos
The camera still opens and the shutter still works. What you would notice is photos sitting with a progress indicator rather than finishing.
This is the one that matters least, because the app holds photos on the phone and keeps retrying until they land. A guest can carry on shooting through a bad patch and the photos arrive when it clears. The thing not to do is delete the app, which is the only way to lose them.
Developing and viewing the roll
The roll does not develop at the time it was meant to, or it develops and the photos are slow to appear, or some load and others do not.
Nothing is lost while this is happening — developing is a change of state, not a process that can half-finish and discard anything. A roll that is late still develops with every photo in it.
The live wall and the host console
The wall on the screen in the room stops advancing, or the host page will not sign in or shows stale numbers.
Both of these are windows onto the event rather than part of it. Guests can keep shooting with the wall frozen and nobody in the room needs to be told.
Before you assume it is us
Most “is it down” messages turn out to be one phone on one network, and the check takes under a minute. Ask a second guest on a different phone whether they are seeing it too. If they are not, it is local: the usual cause at a venue is a phone clinging to guest wifi that has stopped carrying data, and turning wifi off so the phone uses mobile data fixes it more often than anything we could do from here.
If two phones on two networks both see it, that is worth telling us about. The contact page has a line for a live event problem, which is the one that gets looked at first.
Past problems
Nothing has happened that was worth writing down since this page went up, and the empty space is the honest reporting of that rather than a log waiting to be switched on. It is also a short history: this is a young service, so read it as “nothing yet” rather than as a record stretching back years.
When something does happen, it gets an entry here with a date, how long it lasted and whether anything was lost — including the ones that make us look bad, because a log that only contains the flattering ones is not a log.
What we do not promise
No uptime guarantee, no service credits and no response-time commitment, and this page is not the place those would be created. What is actually promised about availability is in the terms, which governs if anything here reads like more than it is. The reason to be blunt about it is that a venue deciding whether to put a client’s wedding through this deserves to know what they are and are not buying before the evening, not during it.
What there is instead is a design that assumes bad nights: photos are held on the phone and retried rather than dropped, a roll that develops late still develops whole, and the live wall can freeze without touching a single photograph. Those are the properties that matter at a venue with two bars of signal, and they hold whether or not anybody is watching a dashboard.