Usually feels like
An evening
You put the machine down and come back to it the same day.
Announced work with an end in view fits an evening. Work that arrives without notice and keeps going has left this band, whatever the notice said.
The wait, in plain words
Deliberate downtime tends to look like one of a small number of screens, and the thread running through all of them is that something is answering.
| What you see | What it suggests |
|---|---|
| A plain page that loads quickly and says the site is being worked on | Somebody wrote that page and put it there. Machines that fall over do not leave notes behind them. |
| Most of the market working, one part refusing | Work on a single component. Deposits, withdrawals and messages are the usual candidates for being taken down alone. |
| Nothing at all, no page, no error text, no response | Indistinguishable from every other silence. That is an address coming back, and it is a different card. |
| A page that half arrives, over and over, on every path you try | More likely load than intent, although the two overlap heavily during planned work. |
The tell is that maintenance leaves evidence and a failure does not explain itself. If you are being told anything at all, in words, on a page that loaded, then somebody is present at the other end and the wait has an owner.
It is still an evening wait rather than a minutes wait. The work finishes when it finishes, nobody involved knows you are sitting there, and your session is not a factor in anybody's planning.
Underneath, while nothing moves
Markets of this shape run more than one front end and more than one service behind them, which is why maintenance is so often partial. Taking a component down while leaving the rest running is ordinary engineering, and from outside it produces the strange experience of a site that works perfectly until you try to do the specific thing you came to do.
Announcements are where this wait gets dangerous, and the danger is not technical. A notice served from an address the market itself controls is worth something, because it was placed where only somebody with control of the service could place it. The same words repeated somewhere else are worth close to nothing, because anybody can type them.
That gap is the whole reason a maintenance notice from an unrelated place is a poor thing to act on. It costs nothing to write that a market is doing planned work, and it costs nothing to add a helpful new address that will be ready when it comes back. A notice with an address attached should be read as an offer rather than as news.
A stated end is the strangest part of this wait. It is one of the few waits on this site where the people doing the work attach a time to it themselves, and it is still not a promise. Planned work runs over everywhere in the world, and the estimate was made before the work started, by someone who did not yet know what they would find. Read it as intent.
Behaving, and not behaving
Deliberate work and a failure that happens to look tidy are separated by whether the explanation could only have come from the service.
Work that is going as planned
A page served from the market's own addresses says the work is happening. Parts of the site behave normally. The behaviour is consistent across every string you hold, which is what a central decision looks like from outside.
The notice changes at some point, or things start working shortly after the stated end. Somebody is present and keeping the page honest.
Something that is not maintenance
The only source telling you about maintenance is not the market. No address you hold serves any such page, and the explanation reached you sideways from somewhere with an interest in what you do next.
Or the notice is genuine and the stated end has gone past more than once without the page changing. The wait has quietly stopped having an end in view, which means it has quietly left this band.
The second case is worth sitting with. A wait with a stated end that has passed is no longer a wait with a stated end, and treating it as one anyway is how people lose a whole evening on the strength of a sentence written before the work began.
There is also no reason to turn this into a support ticket. Planned work is the one situation where the people who could answer you are demonstrably busy doing the exact thing you would be asking about.
Safe to do meanwhile
Maintenance is one of the few waits where the sensible list is genuinely short.
- Try the other published string onceConsistent behaviour across both is information in itself, and it costs a single attempt to collect.
- Trust a notice only where it was servedA notice on a page the market served carries weight. The same sentence anywhere else carries none of it.
- Do not collect a new address tonightAddress changes are announced on the market's schedule, and downtime is exactly when bad strings travel best.
- Come back after the stated end, not at itWork that finishes on the minute is rare, and the first stretch afterwards is the busiest part of the day.
What makes it longer
Planned work is planned by people, and people are the reason it runs over.
- Work that turns out to be larger than it looked, which is most work everywhere.
- A migration that has to be finished or rolled back, and neither of those can be rushed safely.
- Everybody returning at once the moment it ends, which makes the stretch afterwards feel like the outage carried on.
- Partial availability, which tempts you to keep poking the one broken component all evening instead of leaving.
- Acting on a notice from somewhere that could not have known, which does not lengthen the maintenance but can cost you far more than an evening.
What this card is not. This card does not know whether any maintenance is happening, keeps no notice board, and reports nothing about the state of anything.