A live broadcast on YouTube and an offline label in Gyre can coexist because the two displays are separate status signals. The mismatch alone does not show which one is wrong or identify its cause; first verify the intended broadcast and its health in YouTube Live Control Room.
Then establish whether your Gyre setup uses YouTube channel authorisation or manual setup, compare the channel and broadcast shown in Gyre, and collect evidence from both services. If YouTube shows the intended stream as live and healthy while Gyre still says offline, send Gyre support the stream identifier and the evidence rather than guessing at a fix.
What an offline/live mismatch can mean
A status label is meaningful only in the context of the system displaying it. YouTube’s Live Control Room reports the state of the event and the incoming stream as YouTube sees it, including stream health and error messages. Gyre describes its own broadcast-status view and, for its channel-authorisation workflow, says status is synchronised in real time. Those descriptions do not establish that both products measure the same thing or that their displays must always agree.
That distinction matters when a viewer says the stream is live but Gyre says offline. “Live” may refer to the YouTube event being visible to viewers; “offline” may be a status shown in Gyre’s interface. Neither phrase, without the relevant channel, event and health details, is enough to diagnose what happened. The account, broadcast ID, setup path, timestamps and error text are not known from the question alone.
Do not begin by recreating the broadcast, replacing a stream key or changing equipment. Those actions can disrupt a working stream and may remove useful evidence. First establish which event is actually live, which channel it belongs to and what YouTube reports about the incoming stream. If the stream is serving viewers, avoid making a change solely to make two labels match.
Think of the two views as answering different operational questions. YouTube helps you verify what it has received for a particular event. Gyre helps you check the broadcast and channel as represented in Gyre’s workflow. A difference between them is a reason to compare details, not proof that either product is generally more reliable.
Confirm the intended broadcast in Live Control Room
Open YouTube Studio and go to Live Control Room. Locate the event you expect to be live, then check its channel, title and broadcast identifier. Make sure you are looking at the intended event rather than a scheduled stream, an older broadcast or a different live event on the same channel. YouTube’s Live Control Room guidance describes where to view live stream status.
Record the event’s video or stream identifier and the time you checked it. If you have several channels or more than one event in progress, compare the channel name and event details against the destination configured in Gyre. A public video page can help confirm what viewers see, but it is not a substitute for inspecting the event in Studio: the control room is where YouTube provides its stream-status and health information.
Check whether the event is actually live, scheduled, ended or waiting for an incoming stream. Do not infer that Gyre is connected to a broadcast just because a video page is available, or that a Gyre offline label means no one can watch the YouTube event. The key is to match the same event across both products.
If you need to confirm how prerecorded material can be sent as a YouTube live event, the guide to streaming a prerecorded video explains that broader workflow. It is useful background, but it cannot confirm whether a particular event is receiving a signal now. Keep this troubleshooting check focused on the current event and its identifier.
Read YouTube’s stream health and error text
Once you have the correct event open, inspect the health indicator and any error text in Live Control Room. YouTube’s stream troubleshooting guide explains that its interface can show stream status and specific errors. Record the wording as shown, including whether YouTube describes a critical or moderate issue. Do not paraphrase an error so loosely that support cannot distinguish it from another message.
YouTube’s help guidance distinguishes severity: critical errors can prevent an event from starting or cause viewer problems, while moderate issues can affect quality. Treat that guidance as information about YouTube’s assessment, not as an explanation of why Gyre displays offline. A healthy YouTube stream and a Gyre offline status are still separate observations; neither tells you the mechanism behind the difference.
If YouTube reports a problem, follow the relevant steps in its error guidance and note what you changed. For example, YouTube recommends checking the encoder and stream condition when troubleshooting encoder-based broadcasts. A third-party encoder may need an updated stream key, and YouTube also advises checking the outbound connection. These checks apply when your setup actually uses an encoder; they are not a universal remedy for a status discrepancy.
Do not rotate a key or restart the broadcast just because the two status views differ. First check whether YouTube is receiving the intended stream and whether its error text points to an ingestion problem. If the stream is healthy, changing a working encoder configuration can introduce a new failure without explaining the original mismatch.
For a local encoder workflow, the pre-recorded streaming setup guide can help you understand where the outgoing broadcast originates. If the issue is that a stream stops after a machine restart, a separate Compute Engine restart troubleshooting guide covers that different failure mode. Neither article establishes that a key, encoder or virtual machine caused this particular Gyre status difference.
Identify Gyre authorisation or manual setup
Next, determine how this broadcast was created in Gyre. Gyre’s article about its YouTube API workflow describes a channel-authorisation route in which Gyre creates broadcasts through the YouTube API and reports status as synchronised in real time. The same vendor article says manual stream creation remains available for advanced YouTube Studio configurations. These are descriptions of Gyre’s product workflow, not a diagnosis of an individual account.
If you authorised a YouTube channel in Gyre, note which channel was authorised and whether it is the channel owning the event shown in Live Control Room. Confirm that you are inspecting the same destination in both places. The vendor’s description of real-time status synchronisation does not tell us how a particular mismatch arises, nor does it establish a universal delay interval or guarantee that every status change will appear identically in both interfaces.
If you created the event manually in YouTube Studio, establish how Gyre was connected to that event. Check whether the setup uses a third-party encoder and stream key, and whether the relevant event and key are the ones configured for the current broadcast. Do not assume that a key issue is the answer: YouTube’s key and encoder checks matter only if that is the path your setup uses and the evidence points towards an ingestion problem.
If you are unsure which path was used, look at the original setup steps or Gyre’s current account view, and ask the person who configured the channel. Write down what you find. Knowing whether Gyre created the event through authorisation or was connected to a manually created event gives support a concrete starting point and prevents a generic encoder checklist from being applied to the wrong workflow.
The distinction is also relevant when you are planning a continuous prerecorded channel. The overview of a 24/7 YouTube stream on a cloud server discusses a different operating arrangement; it does not mean a server or a purchase will resolve an inconsistency between Gyre and YouTube. Choose troubleshooting steps according to the actual connection method, not according to assumptions about how a nonstop stream must be built.
Compare the channel and broadcast in Gyre
With the YouTube event details in hand, open Gyre and check the channel and broadcast it lists. Compare the channel identity, event title or identifier, and current status with the Live Control Room record. If Gyre shows more than one broadcast, verify that you are comparing the active one. A mismatch can be as simple to describe as “YouTube event X on channel Y is live; Gyre broadcast Z for channel W is offline”, but only make that statement after checking the values.
The comparison below keeps the two displays in their proper roles:
| Check | YouTube Live Control Room | Gyre |
|---|---|---|
| Main question | What does YouTube show for this event and incoming stream? | Which channel and broadcast does Gyre show, and what status does it display? |
| Useful evidence | Event identifier, health indicator, error text and time checked | Channel, broadcast identifier or title, setup path and time checked |
| What it cannot establish alone | Why Gyre displays a different status | Whether YouTube is receiving a healthy stream |
If the channel or event differs, correct the comparison before taking any action. For instance, a live event on one YouTube channel does not show that a Gyre entry associated with another channel is live. If they match and Gyre remains offline, preserve the state and record when you observed it rather than repeatedly changing settings to see whether the display catches up.
Keep a short timeline: when the broadcast began, when you checked YouTube, when you checked Gyre and whether anything changed between those checks. Use exact times and time zone, especially if someone else is monitoring the channel. This helps distinguish observations made at different moments without claiming that there is a standard delay between the services.
A useful status note is factual: “At 21:10 UTC, the Live Control Room event with identifier [ID] on [channel] showed live and healthy; at the same time, Gyre showed [status] for [broadcast].” Replace the bracketed items with what you actually see. Do not add an explanation such as “the API is broken” unless support has confirmed it.
Escalate with matching evidence
If YouTube shows the intended broadcast as live and healthy but Gyre continues to show it offline, contact Gyre support with a concise evidence bundle. Include the YouTube channel name, the event or video identifier, the matching Gyre broadcast details and whether the setup used channel authorisation or manual creation. Add the times and time zone for each observation, plus screenshots of both status views and any YouTube health message.
Make screenshots useful rather than merely numerous. Capture enough of each interface to show which channel and event you mean, the visible status and the time if it is displayed. If the error message is separate from the status panel, include it as well. Do not expose passwords, private stream keys or other credentials in screenshots or messages; a stream identifier is useful for support, but a secret key is not.
State what you have already checked: that you opened the intended event in Live Control Room, read its health and error text, confirmed Gyre’s channel and broadcast, and identified the setup route. If you made a change in response to a YouTube error, name the change and its time. This allows support to work from observed facts rather than asking you to repeat checks or infer a cause from the word “offline”.
If YouTube reports an ingestion error, contact YouTube support or use its official troubleshooting steps for that error as appropriate, while keeping Gyre’s status evidence separate. If YouTube remains healthy and Gyre’s display remains inconsistent, Gyre support is the relevant place to ask about Gyre’s account view. The available platform guidance does not establish which service is at fault in an individual case, so avoid treating an escalation to either service as a guaranteed fix.
While waiting for a response, avoid unnecessary changes to a broadcast that viewers can watch. Save the event ID, health message and timestamps somewhere accessible to the person on duty. If you need to keep a stream running overnight, a repeatable handover note is more useful than an undocumented restart: it records what is live, which dashboard shows what, and what evidence has already been sent.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Does Gyre showing offline mean my YouTube stream is not live?
Not by itself. Check the intended event in YouTube Live Control Room and confirm its status and stream health there. The two services expose separate status views, so a mismatch needs comparison rather than an assumption.
Should I restart the stream or change the stream key?
Not solely because Gyre says offline. First check YouTube’s health indicator and error text, and establish whether your setup uses a manual encoder and key. Follow YouTube’s relevant troubleshooting only if its evidence points to that path; a change can interrupt a working broadcast.
What should I send Gyre support?
Send the channel, event or video identifier, Gyre broadcast details, setup path, timestamps with time zone and screenshots of both status views. Include YouTube’s exact health message if present, but never include a private stream key or password.
Does YouTube’s healthy status prove Gyre is wrong?
No. It shows YouTube’s view of the intended incoming stream at the time you checked; it does not establish why Gyre displays another status. Share the matching evidence with Gyre support if the discrepancy remains.