dohosGet started
PLATE Nº 169

Status history

An empty history here means nothing has happened since — not that nothing gets written down. No incident has been recorded against Dohos since this page existed to record one. The moment something real is confirmed, it gets an entry, on this same page, in the same honest register described below.

PLATE Nº 169 · STATUS HISTORY
WHAT AN ENTRY ACTUALLY CONTAINS, ONCE ONE EXISTS

Not a status word — a structured, honest account.

What happened, what scope was affected, when it began, what's actually been done, what a reader should do if anything, when the next update lands — and, deliberately, what still isn't known.

THE SHAPE A REAL ENTRY FOLLOWS
We are investigating [confirmed service or security issue] affecting [scope] beginning [time]. We have [confirmed action]. Users should [safe action]. We will update by [time or condition]. We are not yet able to confirm [material unknown].
EVERY BRACKET STANDS FOR A FACT THAT WOULD BE VERIFIED BEFORE IT REPLACED THE BRACKET.

That shape isn't filled in with an example here, because there's nothing real to fill it with — inventing a sample incident to demonstrate the format would misrepresent something that hasn't happened as something that has. If an earlier entry turns out to have been wrong, the correction is its own new entry, not a quiet edit to the original.

HOW SEVERITY IS DESCRIBED, WITHOUT A NUMBER ATTACHED

When an entry exists, it carries a severity — the full classification lives at incident response, stated there once.

Severity tells you what kind of situation it is. It does not come with a promised response time attached — no such figure is published for any severity level, on this page or anywhere else. A number with nothing real behind it doesn't protect a reader from a slow response; it just makes a slow response feel like a broken promise on top of everything else.

THE RECORD, AS IT STANDS

Month by month, honestly short.

JUNE 2026NO INCIDENTS RECORDED
JULY 2026NO INCIDENTS RECORDED
AUGUST 2026NO INCIDENTS RECORDED

EMPTY BECAUSE NOTHING HAS BEEN CONFIRMED — NOT BECAUSE EARLIER MONTHS WERE LEFT OFF THE LEDGER.

WHAT THIS PAGE WILL NOT SAY, EVEN ABOUT A REAL INCIDENT

A few phrasings, avoided on purpose.

“FULLY CONTAINED”Not used unless every piece of available evidence actually supports that conclusion.
“NO IMPACT”Real, confirmed impact is never called “no impact” just because it turned out to be limited in scope.
“Only” AFFECTEDNever used to make a real number of affected restaurants or callers read as smaller than it was.
“SOPHISTICATED ATTACK”Not reached for as a way of explaining a failure away, in place of stating specifically what was done.
WHAT PEOPLE ACTUALLY ASK
What actually counts as an incident here?

Anything that meaningfully affects one of the systems named on the current status page. A brief, purely internal hiccup with no effect a restaurant or caller would notice isn’t treated as one.

Will I find out before I notice a problem myself?

Not necessarily — an entry depends on the issue being confirmed and written up first, by people, not an instant automated alert. Subscribing to updates gets a notification the moment an entry is published, which is the fastest this page itself can tell you.

Does an empty record mean nothing was ever close to a problem?

It means no incident met the bar above and got written up. It’s a record of what was confirmed and disclosed, not a guarantee of a flawless run nobody is claiming.

If an entry is corrected later, does the original get deleted?

No. The correction is its own new, dated entry that says plainly what the earlier one got wrong — the original stays visible.

THE NEXT STEP

Open the line.

Tell us about your restaurant. We load your menu, you place a call, and you hear it answered yourself.