Thirty years in AV teaches you one reflex. When a signal drops in the middle of a show, you don't panic. You ask one question first: is it my gear, or is it upstream?
Until you answer that, you can't fix anything. You're just guessing in the dark, swapping cables that were never the problem.
Software is the same. When your dashboard won't load, or your episode won't publish, the first thing you want isn't an apology. It's an answer. Is it me, or is it them?
For PodGlue, the honest answer to that question now lives in one place.
What we shipped
There's a new status page at status.podglue.com.
It tells you, in plain language, whether PodGlue is healthy right now. The web app. The API behind it. Audio and RSS delivery, the part that actually gets your show to listeners. And publishing, the part that pushes your content out into the world.
Each one has its own line. Green when it's fine. Not green when it isn't.
It isn't a marketing page that always says everything is wonderful. A robot checks every one of those systems every five minutes, around the clock, and writes down what it finds. The page shows you the real result, not the version we wish were true.
A Tuesday example
Say it's a Tuesday and you go to publish an episode, and the button just spins.
The old way: you refresh. You clear your cache. You wonder if your wifi is bad. You email support and wait. You lose an hour to a problem that was never yours to begin with.
The new way: you open status.podglue.com. If "Publishing" is showing a problem, you have your answer in five seconds. It's us. We already know, and you can watch the incident log update as we work through it.
If everything on the page is green, that's an answer too. It points you somewhere more useful than refreshing for the tenth time.
Either way, you stop guessing.
Why this one matters to me
I've published over 700 episodes. I know the specific dread of hitting publish before a deadline and watching nothing happen. You feel powerless, and worse, you feel alone with it.
A status page doesn't make outages fun. Nothing does. But it changes the relationship. It says: we're not going to hide. When something breaks, you'll know before you have to ask, and you'll watch us fix it in the open.
That's the only kind of trust worth having with the tool your show runs on.
What's next
Right now the page tracks the four systems that matter most to your show. Over time it grows a longer memory: months of uptime, every incident we've worked through, the whole record sitting there in public.
It already keeps that history grouped by month, with a green check on every month nothing went wrong. My quiet goal is to keep that column boring.
If you host with PodGlue, status.podglue.com is yours to bookmark. Next time something feels off, you'll have one honest page that tells you whether it's you or us. Usually that's the only thing you needed to know.
Ready to make every episode compound?
PodGlue is the operating system for relationship-driven podcasters.
Get Started FreeRelated reading
Our Homepage Was Too Clever. So We Rewrote All of It.
We described PodGlue like a pitch deck instead of a tool. A busy podcaster does not want a philosophy. They want their Saturday back. So we rewrote the whole homepage to say what it actually does.
I Built a Team of AI Agents. The Best One Said Stop.
I wired up four AI agents to ship a feature while I slept. The first real job they ran, the most valuable thing any of them did was refuse to write code.
I Watched My Product Break on a Sales Call
Four demos in one day. The product sold itself, and then the studio wouldn't connect, and a login button did nothing. Here's what the rough edges taught me that the polished parts couldn't.