When a tab fails, people invent a story. The story is usually worse than the outage. "They shut down." "My account is gone." "It's just me, I'm bad at computers." A public status page is how you replace the story with a sentence.
Oernoe's homepage word for this is Tracker. https://tracker.oernoe.com
Open it once while nothing is wrong. The healthy view should look familiar, so a red day doesn't feel like a blank product.
Late August 2026. I'm not going to paste fake uptime percentages. I don't publish a 99.something number in this journal.
## What a status page is for
Known problems. Planned maintenance, when we actually plan it. A short history so you can see whether last Tuesday was a blip or a week.
It cannot prevent an outage. It cannot see your cafe Wi-Fi. It cannot tell you that your extension ate the page. It can tell you we already know Search is sad, or that we don't.
That last part matters. If Tracker is quiet and your tab is broken, the next step is a specific report: URL, browser, signed in or not, screenshot. If Tracker is loud and your tab is broken, you can wait or work around without writing a manifesto.
## Why we owe you this
We're asking people to put files in Drive, health-shaped notes in Health, conversations in Chat. Those are not anonymous weather widgets. When those hosts fail, silence reads like contempt.
A status page is a low form of respect. It says: we will not make you poll five group chats. We will not hide behind a homepage that still shows a smiling tile.
It also protects us from our own rumor mill. One person on a bad mobile network can convince a room that "Oernoe is down." Sometimes it is. Sometimes it's one host. Sometimes it's one asset on a CDN. The page should be specific enough that those cases don't look identical.
## How to read it without getting played
Look at the service name, not the brand mood. Search being slow is not Chat being offline.
Look at the update time. A two-day-old incident with no sentence is worse than a fresh "we're looking." I would rather post an ugly "we don't know yet" than leave a green box that someone painted by accident.
Look at what it tells you to do. "Wait" is a real instruction. "Use the mobile browser instead of an app we never shipped" is a real instruction. "Everything is fine" while your POST is 500 is a bug in the status page, and you should tell Support that.
Don't treat a status page as a privacy dashboard. It is operational. Different document. Privacy: https://www.oernoe.com/legal/privacy
## Tracker and the rest of the suite
The live set this month is Search, Health, Chat, AI, Docs, Drive, Tracker. If a host in that set fails, Tracker should have a row that matches the name people use.
If Mail is not a live peer yet, don't show Mail as "operational" just to look complete. Green lies are worse than missing rows. Same for an Android app that is not in the store. A status row for a product you cannot open is theater.
Older posts talked about "Oernoe Status" as a name. You may still see that wording. The homepage tile you can defend today is Tracker. If both hosts exist, they still have to answer the same question. I'm not going to invent a diagram. If you're lost, start at tracker.oernoe.com.
## What we will not put on a status page
User counts. Revenue. Cheerful adjectives.
Personal account states. If you're banned, that's not an incident. If your file is missing and nobody else is missing files, that's Support, not a red banner.
Medical advice. If Health the product is down, the page can say Health is down. It cannot tell you what to do about a symptom. Emergency services are still the emergency path.
## How this ties to Support
Status first, ticket second. I said this in the Support post and I'll say it again because people skip.
https://support.oernoe.com
Contact on www.oernoe.com
support@oernoe.com when the form isn't enough
A useful ticket after a quiet Tracker: "Drive upload fails in Firefox, signed in, this URL, this time, here's the error text." A useful ticket after a loud Tracker: "Your incident says Search, I'm also seeing AI fail," if that's true.
Please don't @ random social accounts and assume that's a pager. Official company presence is thin. LinkedIn exists. Don't trust a clone help account that only looks like us. We have a whole separate problem with pages that steal the login aesthetic.
## Maintenance, when it's real
Planned work should have a window and a service name. If we miss the window, the same page should say we missed it. That is the standard I want. We have not always met it. Journal posts about launches missed months too. Operational honesty and editorial honesty are the same muscle.
If we take Search down on purpose for a short time, I'd rather you see it on Tracker than hear it as a rumor that "privacy search died."
## What still needs to improve
More specific sentences. Less green-by-default.
A habit of updating while an incident is boring, not only when it starts and ends.
Matching names to the homepage so a new user can find the row.
No fake graphs. If we don't have a public historical metric we trust, we shouldn't draw one that looks official.
I opened this piece because the first version was three polite paragraphs. Those paragraphs were correct and empty. A status page is one of the few places a small company can look like an adult. We should use it.
Bookmark Tracker. Open it on a calm day. When a bad day happens, you'll know whether to wait, switch hosts, or write us. That's the whole benefit. Not transparency as a brand. Less guessing.
## A calm-day drill
Open Tracker. Note which services appear. Note whether the names match the homepage. Note the last update time, even if it just says operational. Close the tab.
Do this once a month if you actually keep files here. It takes a minute. The point is not anxiety. The point is a baseline. People who only open status pages during a scare read every yellow box as a fire.
If you run a classroom or a small team on Docs, assign someone to check Tracker before you announce the platform died to twenty people. You'll look less foolish.
## What I'll put in an incident note if I'm the one writing it
Service name. Start time. What users see: timeouts, 500s, empty results. What we tried. What we want you to do: retry, wait, use a second host. Next update window, even if the next update is still looking.
I will not put jokes in the first note. I will not blame a generic third party without a name we're allowed to use. I will not mark it resolved because one engineer loaded the homepage from the office.
If we were wrong — we thought it was DNS, it was a bad deploy — the history should say that. Status history is for later readers, including us.
## Rumors, clones, and fake status pages
If someone sends you a status URL that is not tracker.oernoe.com or a host we have actually linked from the site, treat it as a prop. Phishing likes urgent outages. A page that says sign in to see incident details is a bad sign. Incident details should not need your password.
We also should not train you to trust a screenshot of a green box posted on an unofficial account. Open the host yourself.
## The small-company excuse, used carefully
We are small. That is why a status page matters more, not less. A giant company can be down and you'll hear it everywhere. A small one can be down and you'll think you typed the URL wrong.
Small is not an excuse for a decorative page. If we can't update Tracker, we should say that on Support. If Tracker itself is the thing that's down, Support and the contact form are the backup. Yes, that's awkward. It's still better than silence.
Use the page. Hold us to the sentences on it. If the sentences are empty, this journal post failed too.
Oernoe's homepage word for this is Tracker. https://tracker.oernoe.com
Open it once while nothing is wrong. The healthy view should look familiar, so a red day doesn't feel like a blank product.
Late August 2026. I'm not going to paste fake uptime percentages. I don't publish a 99.something number in this journal.
## What a status page is for
Known problems. Planned maintenance, when we actually plan it. A short history so you can see whether last Tuesday was a blip or a week.
It cannot prevent an outage. It cannot see your cafe Wi-Fi. It cannot tell you that your extension ate the page. It can tell you we already know Search is sad, or that we don't.
That last part matters. If Tracker is quiet and your tab is broken, the next step is a specific report: URL, browser, signed in or not, screenshot. If Tracker is loud and your tab is broken, you can wait or work around without writing a manifesto.
## Why we owe you this
We're asking people to put files in Drive, health-shaped notes in Health, conversations in Chat. Those are not anonymous weather widgets. When those hosts fail, silence reads like contempt.
A status page is a low form of respect. It says: we will not make you poll five group chats. We will not hide behind a homepage that still shows a smiling tile.
It also protects us from our own rumor mill. One person on a bad mobile network can convince a room that "Oernoe is down." Sometimes it is. Sometimes it's one host. Sometimes it's one asset on a CDN. The page should be specific enough that those cases don't look identical.
## How to read it without getting played
Look at the service name, not the brand mood. Search being slow is not Chat being offline.
Look at the update time. A two-day-old incident with no sentence is worse than a fresh "we're looking." I would rather post an ugly "we don't know yet" than leave a green box that someone painted by accident.
Look at what it tells you to do. "Wait" is a real instruction. "Use the mobile browser instead of an app we never shipped" is a real instruction. "Everything is fine" while your POST is 500 is a bug in the status page, and you should tell Support that.
Don't treat a status page as a privacy dashboard. It is operational. Different document. Privacy: https://www.oernoe.com/legal/privacy
## Tracker and the rest of the suite
The live set this month is Search, Health, Chat, AI, Docs, Drive, Tracker. If a host in that set fails, Tracker should have a row that matches the name people use.
If Mail is not a live peer yet, don't show Mail as "operational" just to look complete. Green lies are worse than missing rows. Same for an Android app that is not in the store. A status row for a product you cannot open is theater.
Older posts talked about "Oernoe Status" as a name. You may still see that wording. The homepage tile you can defend today is Tracker. If both hosts exist, they still have to answer the same question. I'm not going to invent a diagram. If you're lost, start at tracker.oernoe.com.
## What we will not put on a status page
User counts. Revenue. Cheerful adjectives.
Personal account states. If you're banned, that's not an incident. If your file is missing and nobody else is missing files, that's Support, not a red banner.
Medical advice. If Health the product is down, the page can say Health is down. It cannot tell you what to do about a symptom. Emergency services are still the emergency path.
## How this ties to Support
Status first, ticket second. I said this in the Support post and I'll say it again because people skip.
https://support.oernoe.com
Contact on www.oernoe.com
support@oernoe.com when the form isn't enough
A useful ticket after a quiet Tracker: "Drive upload fails in Firefox, signed in, this URL, this time, here's the error text." A useful ticket after a loud Tracker: "Your incident says Search, I'm also seeing AI fail," if that's true.
Please don't @ random social accounts and assume that's a pager. Official company presence is thin. LinkedIn exists. Don't trust a clone help account that only looks like us. We have a whole separate problem with pages that steal the login aesthetic.
## Maintenance, when it's real
Planned work should have a window and a service name. If we miss the window, the same page should say we missed it. That is the standard I want. We have not always met it. Journal posts about launches missed months too. Operational honesty and editorial honesty are the same muscle.
If we take Search down on purpose for a short time, I'd rather you see it on Tracker than hear it as a rumor that "privacy search died."
## What still needs to improve
More specific sentences. Less green-by-default.
A habit of updating while an incident is boring, not only when it starts and ends.
Matching names to the homepage so a new user can find the row.
No fake graphs. If we don't have a public historical metric we trust, we shouldn't draw one that looks official.
I opened this piece because the first version was three polite paragraphs. Those paragraphs were correct and empty. A status page is one of the few places a small company can look like an adult. We should use it.
Bookmark Tracker. Open it on a calm day. When a bad day happens, you'll know whether to wait, switch hosts, or write us. That's the whole benefit. Not transparency as a brand. Less guessing.
## A calm-day drill
Open Tracker. Note which services appear. Note whether the names match the homepage. Note the last update time, even if it just says operational. Close the tab.
Do this once a month if you actually keep files here. It takes a minute. The point is not anxiety. The point is a baseline. People who only open status pages during a scare read every yellow box as a fire.
If you run a classroom or a small team on Docs, assign someone to check Tracker before you announce the platform died to twenty people. You'll look less foolish.
## What I'll put in an incident note if I'm the one writing it
Service name. Start time. What users see: timeouts, 500s, empty results. What we tried. What we want you to do: retry, wait, use a second host. Next update window, even if the next update is still looking.
I will not put jokes in the first note. I will not blame a generic third party without a name we're allowed to use. I will not mark it resolved because one engineer loaded the homepage from the office.
If we were wrong — we thought it was DNS, it was a bad deploy — the history should say that. Status history is for later readers, including us.
## Rumors, clones, and fake status pages
If someone sends you a status URL that is not tracker.oernoe.com or a host we have actually linked from the site, treat it as a prop. Phishing likes urgent outages. A page that says sign in to see incident details is a bad sign. Incident details should not need your password.
We also should not train you to trust a screenshot of a green box posted on an unofficial account. Open the host yourself.
## The small-company excuse, used carefully
We are small. That is why a status page matters more, not less. A giant company can be down and you'll hear it everywhere. A small one can be down and you'll think you typed the URL wrong.
Small is not an excuse for a decorative page. If we can't update Tracker, we should say that on Support. If Tracker itself is the thing that's down, Support and the contact form are the backup. Yes, that's awkward. It's still better than silence.
Use the page. Hold us to the sentences on it. If the sentences are empty, this journal post failed too.
O
Oernoe Editorial Team
Technology experts committed to building privacy-first solutions and helping users understand how digital services work. Passionate about creating transparent, ethical platforms.
Get in touchRelated Articles
Want to Learn More?
Explore our complete guides and knowledge base for more insights on privacy, technology, and best practices.
Browse Our Guides