When a Login Bounce Is Not an Outage

A lot of "Oernoe is down" tickets are a login bounce.

Saturday, August 29, 2026. I clicked drive.oernoe.com and landed on account.oernoe.com with a next= parameter. That is SSO trying to figure out who you are. It is annoying. It is not the same thing as Search being dead.

www.oernoe.com can show ads. This page is the journal. Status is at status.oernoe.com. Tracker is at tracker.oernoe.com and may ask you to sign in. Look at those before you write that the company exploded.

## What a bounce looks like

You type drive.oernoe.com. The bar changes to account.oernoe.com. There is a next= or a client_id= in the query. You sign in or you already had a session. The bar changes back. You are in Drive.

You type music.oernoe.com. You get a login page, maybe with sso_error=session_check_failed. That is the music host saying it does not know you yet. It is not a music outage by itself. Try account, then music again. Then Status. Then a three-line ticket if it still loops.

You type tracker.oernoe.com and get /login. Tracker has a door. Status might not. Use the one that loads.

I am not going to invent a spinner animation. If the bar changed hosts, read the new host. If the new host is account.oernoe.com, you are in login. Finish it or stop. Do not mash reload forty times and call that evidence. A bounce that succeeds in under a minute is not a story. A bounce that loops is a story. Three loops is enough to stop.

## Drive and Music through account.oernoe.com

Drive bounced me through account when I clicked it. Music asked for login. That is the account host doing a job. SSO is a boring word for "this service wants to know who you are before it shows files or a player."

I did not open music review. I do not review tracks. I will not tell you a song failed to play because I refused to log into an admin desk. If you cannot get into music.oernoe.com after a clean sign-in on a machine you own, that is a ticket with both hosts. If you cannot get in because you are on a library PC and you should not type a password, that is not an outage. That is you being careful. Good.

Docs, Chat, AI, Health, Studio, Maps can bounce too. I am not going to list every next= I have seen. The pattern is the same. Service host, then account host, then service host again. If the third step never happens, write both hosts down.

Do not bookmark the bounce URL. I wrote a bookmarks post for that. The bounce URL expires. Next week it is a dead SSO attempt with a state= you do not understand.

## Status is not Tracker

status.oernoe.com has loaded for me as a public page. I opened it today. I am not going to paste yesterday's uptime as if it were a law. Those numbers change. Read the page at the time you care about.

tracker.oernoe.com has sent me to a login. Tracker has a door. If you cannot sign in, you still have Status. Use Status. Do not sit in a Tracker login loop and decide the company is gone.

I already wrote about Tracker as a habit. This is not that post. This is the narrow claim: a login bounce is not an outage, and Status is the public check. Tracker is a signed-in check if you can get in.

If Status says the thing is working and your tab still loops on account.oernoe.com, say both in the ticket. "Status looked fine at 10:12 MT. drive.oernoe.com sent me to account.oernoe.com three times. Dummy retry on a file named dummy-829 failed because I never arrived in Drive." That is a ticket. "Oernoe is down" is a mood.

If Status will not load either, try a second network if you have one. Phone off Wi-Fi. A hotel that blocks unknown hosts is not our funeral. A school filter that hates new search engines is not our funeral. Say the network if you know it.

## What an outage looks like

Status says something is not operational. Tracker agrees, or Tracker will not load at all. Your tab spins on search.oernoe.com after you already have a session. Two machines fail the same way.

A unit covering a paragraph on www is a publisher layout bug. Host: www.oernoe.com. Not Search. Not Drive. Not an outage of the company. Ticket the unit and the host if it actually covers the text. Do not file "Search is tracking me" because you saw a unit on a journal page.

Search returning results while Drive bounces forever is two facts. Keep them two facts. Do not smash them into "the app." There is no Android app I will send you to. app.oernoe.com does not resolve.

mail.oernoe.com does not resolve. That is not an outage that started this morning. That host was not there when I clicked it. Do not file Mail down. If you still have a bookmark to it, deleting the bookmark is the fix.

## A dummy order I actually use

Open status.oernoe.com. Read it. Note the time and your timezone.

Open the host you wanted. Read the bar.

If the bar is account.oernoe.com, that is login. Finish it or stop. On a machine you do not own, stop.

If you return to the host and it works, you do not need a ticket.

If you loop three times, stop. Do not loop thirty times. Thirty reloads are not a dummy. They are a tantrum. Then a dummy if you arrive. Dummy file in Drive. Dummy page in Docs. Dummy "test" in Chat. If the dummy works, your real file is not the bug. If the dummy fails, ticket the dummy, not the thesis.

I am not going to invent a button named Retry SSO. If you see a way to try again, use it once. Then Status. Then the ticket.

## What belongs in the ticket

Host you wanted. Host you landed on. Time, with a timezone. "Tonight" is not a time. "Aug 29 around 10:40 AM MT" is a time.

What you clicked. Typed drive.oernoe.com. Signed in, or tried to. What the screen did. Bar changed to account.oernoe.com. Query had client_id=drive, or you can say "a client_id I am not pasting." Looped three times. Dummy never loaded.

What you already tried. Status check. Second tab. Phone versus laptop if both are yours. Tracker or Status, what they showed you, in a sentence. A dummy. "I never got a dummy into Drive because I never arrived." That is still a dummy report. You tried to put one in.

I already wrote a longer ticket post. I am repeating the one line people skip: host, time, dummy. Not the document. Not the Health note.

## What you do not paste

The full next= URL if it contains a token you do not understand. Tokens look like long garbage in the query. If you do not know what it is, do not paste it. You can say "Drive sent me to account with client_id=drive." That is enough.

A screenshot of the password field filled. A session cookie. A recovery code. A password, even "so you can log in as me." Those turn a bounce into a leak.

Your Drive files. Your Health note. A Docs body. A Chat transcript. Titles, not bodies. Do not paste the bounce URL into Chat. Do not paste it into AI "to explain this error." Do not paste it into a journal comment. support.oernoe.com, three lines, or nothing.

If someone from support asks for a password, they should not. Do not give it. Say no and ask for another path. I did not open support admin to confirm a tone. I am telling you from this desk: passwords do not go in tickets.

## Shared chairs make bounces expensive

A bounce on a library PC is a reason to stop, not a reason to type a password. Wait until you have a machine you own. Login bounces are how people type passwords into the wrong chair.

Hotel Wi-Fi plus a bounce is two problems. The hotel may be intercepting. I am not saying it is. I am saying you cannot audit the PC. Do not type a password you care about. Search, if you must, as a guest. Files can wait.

A friend's laptop that "already has me signed in" is not a bounce. That is a session you should not have left. Sign out is a different post. If you bounced and signed in on that laptop, change the password later from a machine you own. Not from the friend's laptop as a victory lap.

If you are a person who files a lot of tickets, count to one Status check. Then one bounce. Then one dummy retry. Then the ticket. Three tickets in four minutes about a bounce we can see on Status as operational just makes the useful dummy hard to find.

Login bounce first. Status second. Ticket third, small. That is the order that wastes less of everyone.


## Timezones and loops

If you retry a bounce twenty times, you have a loop, not new information. Three tries. Then stop. Note the time. Status. Ticket.

If you retry across midnight, say the timezone. Overnight deploys happen. I will not pretend they never do. A calm ticket at 12:40 beats a stack at 12:41.

If you switched from phone to laptop mid-loop, say both. Phones use in-app browsers that lie about hosts. Open the real browser before you decide Account is dead.

## What I do when I am in a hurry

I do not type a password into a bounce on a machine I do not own. I wait. Hurry is how library PCs collect passwords. Hurry is how next= URLs get pasted into group chats.

If I am at home and Drive bounces, I finish login once. If it returns, I work. If it does not, I stop and write the sentence with both hosts. I do not open seven other tiles to "see if the whole company is down." Search plus Status is enough of a pulse.

Bounce is a door. Outage is a floor. Doors and floors need different tickets. Keep them apart.