--- title: A Routine Scan Took A Live News Broadcast Off Air description: A subnet scan took a production control room offline mid-broadcast. The CMDB said it was empty. Here's how that happened and what stopped it recurring. image: https://www.apexconfiguration.com/hubfs/AI-Generated%20Media/Images/Broadcast%20Control%20Room%20Technician.png --- [![APEX CONFIGURATION GROUP](https://www.apexconfiguration.com/hs-fs/hubfs/Act3%20child/images/ACG-logo.png?width=135&height=93&name=ACG-logo.png "APEX CONFIGURATION GROUP")](https://www.apexconfiguration.com/) [![APEX CONFIGURATION GROUP](https://www.apexconfiguration.com/hs-fs/hubfs/Act3%20child/images/ACG-logo.png?width=135&height=93&name=ACG-logo.png "APEX CONFIGURATION GROUP")](https://www.apexconfiguration.com/) - [Home](https://www.apexconfiguration.com) - ServiceNow - [ServiceNow CMDB](https://www.apexconfiguration.com/servicenow-cmdb) - [CMDB Health Check](https://www.apexconfiguration.com/cmdb-health-check) - [CMDB Design & Implementation](https://www.apexconfiguration.com/cmdb-design-implementation) - [Managed Service](https://www.apexconfiguration.com/managed-cmdb-services) - [Automation & Optimisation](https://www.apexconfiguration.com/cmdb-automation-tools) - Maximising ServiceNow - [CMDB Health Dashboard](https://www.apexconfiguration.com/cmdb-health-dashboard-servicenow) - [CMDB Dependency Mapping](https://www.apexconfiguration.com/cmdb-relationship-table) - [CMDB Configuration Items](https://www.apexconfiguration.com/cmdb-configuration-items) - [CMDB Workspace](https://www.apexconfiguration.com/cmdb-workspace-servicenow) - [CMDB Best Practice](https://www.apexconfiguration.com/cmdb-best-practices) - [ServiceNow Discovery](https://www.apexconfiguration.com/servicenow-discovery-setup) - [Service Mapping](https://www.apexconfiguration.com/servicenow-service-mapping) - About - [How We Help](https://www.apexconfiguration.com/about-apex) - [What is a CMDB?](https://www.apexconfiguration.com/what-is-cmdb) - [Benefits](https://www.apexconfiguration.com/benefits-of-cmdb) - Resources - [Blog](https://www.apexconfiguration.com/blog) - [Contact Us](https://www.apexconfiguration.com/contact-us) [Contact Us](https://www.apexconfiguration.com/contact-us) [Contact Us](https://www.apexconfiguration.com/contact-us) - [Home](https://www.apexconfiguration.com) - ServiceNow - [ServiceNow CMDB](https://www.apexconfiguration.com/servicenow-cmdb) - [CMDB Health Check](https://www.apexconfiguration.com/cmdb-health-check) - [CMDB Design & Implementation](https://www.apexconfiguration.com/cmdb-design-implementation) - [Managed Service](https://www.apexconfiguration.com/managed-cmdb-services) - [Automation & Optimisation](https://www.apexconfiguration.com/cmdb-automation-tools) - Maximising ServiceNow - [CMDB Health Dashboard](https://www.apexconfiguration.com/cmdb-health-dashboard-servicenow) - [CMDB Dependency Mapping](https://www.apexconfiguration.com/cmdb-relationship-table) - [CMDB Configuration Items](https://www.apexconfiguration.com/cmdb-configuration-items) - [CMDB Workspace](https://www.apexconfiguration.com/cmdb-workspace-servicenow) - [CMDB Best Practice](https://www.apexconfiguration.com/cmdb-best-practices) - [ServiceNow Discovery](https://www.apexconfiguration.com/servicenow-discovery-setup) - [Service Mapping](https://www.apexconfiguration.com/servicenow-service-mapping) - About - [How We Help](https://www.apexconfiguration.com/about-apex) - [What is a CMDB?](https://www.apexconfiguration.com/what-is-cmdb) - [Benefits](https://www.apexconfiguration.com/benefits-of-cmdb) - Resources - [Blog](https://www.apexconfiguration.com/blog) - [Contact Us](https://www.apexconfiguration.com/contact-us) [Contact Us](https://www.apexconfiguration.com/contact-us) [tel:+442080588135](tel:+442080588135)[mailto:contact@apexconfiguration.com](mailto:contact@apexconfiguration.com) [Case Studies](https://www.apexconfiguration.com/blog/tag/case-studies)[Service Mapping](https://www.apexconfiguration.com/blog/tag/service-mapping) [ServiceNow](https://www.apexconfiguration.com/blog/tag/servicenow)[ServiceNow Discovery](https://www.apexconfiguration.com/blog/tag/servicenow-discovery)[Broadcast & Media](https://www.apexconfiguration.com/blog/tag/broadcast-media) # A Routine Scan Took A Live News Broadcast Off Air [![Krzysztof Chrzanowski](https://www.apexconfiguration.com/hs-fs/hubfs/krzysztof-chrzanowski.webp?width=40&height=40&name=krzysztof-chrzanowski.webp)](https://www.apexconfiguration.com/blog/author/krzysztof-chrzanowski) by [Krzysztof Chrzanowski](https://www.apexconfiguration.com/blog/author/krzysztof-chrzanowski) 7 min read Oct 9, 2026, 9:00:02 AM Last updated on 9 Oct 2026, 09:00:02 A configuration management team scanned a subnet they believed was offline. The CMDB showed no dependency relationships against it, no live services, nothing running. The scan took the room offline anyway. It was a production control room, live, mid-broadcast, on a global news channel. ## Key Takeaways - A subnet scan, run because the records showed no dependencies and nothing running, took a production control room offline during a live global news broadcast. - The equipment in the room had been left marked "in stock" and "non-operational" in ServiceNow, so nothing showed it underpinning a live service. - The cause was a process gap before it was a data gap. Nobody owned the step where equipment moves from "in stock" to "live and operational" once it is installed. - The scanning team had followed its own rules and checked the records first. The records were wrong, which moved the review upstream to how equipment status is set. - The fix ran in order. Apex identified the real hardware in each control room by hand, ran light-touch horizontal discovery with custom pattern extensions, then rebuilt the service maps top down. - The client added a second confirmation from someone physically responsible for the room before any change to operational status inside a control room. Nobody scanning that subnet intended to interrupt a broadcast. The tooling did exactly what it was told. It had been told the room was empty, and that's the part worth tracing back through [how a configuration management database is meant to reflect the estate](https://www.apexconfiguration.com/what-is-cmdb) to understand how a live room ends up looking that way. ## How a live production room disappeared from the CMDB The breakdown started upstream of configuration management, in the handoff between procurement, asset management and configuration management. Equipment that was live and actively in production had been left marked "in stock" and "non-operational" in ServiceNow. Master control rooms and production control rooms depend on that status field more than most infrastructure does. If a room's equipment is recorded as non-operational, nothing shows it as underpinning a live service. The production control room in question had no equipment linked to it as running anything at all, so it read as an empty room rather than a live one. That's the part that makes this different from an ordinary data quality gap. It wasn't that the room was missing from the CMDB. The room was there. The equipment inside it was there. What was missing was the operational status and the service dependency that would have told anyone looking that switching it off would take a news channel off air. It's also worth being clear about what the status field was doing for other, correctly-marked infrastructure in the same estate. Elsewhere, non-operational genuinely meant non-operational, and the field was trusted precisely because it was usually accurate. That's what made this particular room dangerous rather than merely wrong. The field lied convincingly, in an environment where the same field was reliable everywhere else. ## What happened when the scan ran The internal configuration management team scanned the subnet as part of routine discovery, working from what the CMDB told them: no dependency relationships, so no live production risk. The scan took the production control room offline during a live global news broadcast. Viewers noticed before the internal team did. Some switched to a rival news channel for the duration of the outage, which is a direct hit to a broadcaster's two scarcest assets: audience attention and advertiser confidence in the schedule actually running. ## Why status fields matter more than most CMDB attributes Most configuration item attributes are useful without being safety-critical. Operational status, on infrastructure that underpins a live broadcast, is different. It's the field that tells a scanning tool, a change requester or an engineer whether what they're about to touch is live. The procurement-to-configuration-management handoff broke because nobody owned the step where equipment moves from "in stock" to "live and operational" in ServiceNow. Once equipment physically went live in a control room, updating its CMDB status wasn't anyone's defined task. It stayed marked as it was when it arrived. That's a process gap before it's a data gap. Fixing the CMDB record after the fact doesn't stop it recurring on the next piece of equipment that goes live without someone updating its status. The internal review that followed the outage focused first on the scanning team's own process, on the reasonable assumption that a scan shouldn't have been able to take live infrastructure down. That review found the scanning process had followed its own rules correctly. It checked the CMDB before scanning, exactly as it was supposed to. The CMDB was wrong. That finding shifted the review upstream, into how equipment status gets set once it's installed, which is a less comfortable place to look than the scanning tooling, because the fix isn't a configuration change to a scanning job. It's a process that had never been assigned to anyone at all. ## How Apex approached the fix Three things had to happen, in order, and doing them in the wrong order would have caused the same problem again on the next scan. - **Establish what was actually in each room first.** Before touching discovery configuration, Apex identified the real hardware in every master control room and production control room by hand, working from what was physically there rather than what the CMDB claimed. - **Scan with custom pattern extensions, light touch, once the room was known.** With the real equipment confirmed, Apex performed carefully scoped [horizontal discovery](https://www.apexconfiguration.com/servicenow-discovery-setup) using custom pattern extensions written for this estate, rather than a generic discovery sweep against infrastructure this sensitive. This is the same discipline covered in [why scanning on its own isn't a CMDB](https://www.apexconfiguration.com/blog/servicenow-discovery-isnt-a-cmdb). - **Rebuild the service maps top down, from the business service to the infrastructure.** Once the equipment and its operational status were correct, pattern-based service mapping connected each control room's hardware to the broadcast service it underpinned, so status and dependency told the same story. The sequencing is the part that's easy to skip under pressure. Scanning first, against infrastructure whose status can't be trusted, is how the original incident happened. Establishing ground truth before scanning is what stopped it happening again. A generic discovery pattern was part of how the original status field went unnoticed for as long as it did, which is why the custom pattern extensions mattered rather than being a technical footnote. Standard discovery patterns are built to identify common infrastructure types and their common states. Broadcast equipment, control room routing hardware and the specific vendor systems used in a live production environment don't always match those patterns cleanly, which means a generic scan can either miss them or misclassify them. Writing extensions specific to this estate meant discovery could recognise the actual equipment in use and report its state accurately, rather than defaulting to whatever the closest generic match happened to suggest. It's also worth naming why this pattern is specific to broadcast rather than incidental to it. Most estates have some infrastructure with a genuinely low blast radius if it goes offline unexpectedly. A broadcast production environment doesn't have much of that. Whether equipment is "just a server" or "the thing keeping a channel on air" depends entirely on whether the CMDB has the right room, the right status and the right service dependency recorded against it, which is exactly the combination that failed here. Since the fix, the client has added one further check. Any change to a configuration item's operational status inside a designated control room now requires a secondary confirmation from someone physically responsible for that room, rather than a single ServiceNow field update from anyone with edit access. A status field is only as trustworthy as the process that changes it, and a single-person edit was part of how "in stock" survived long after the equipment went live in the first place. ## What this means if your CMDB has status fields nobody owns A configuration item marked non-operational is a green light to scan it, change it, or take it offline without a second thought. If your estate includes any infrastructure where "non-operational" might not be true, that's not a minor data quality issue. It's the difference between a routine scan and a live incident. ## How Apex helps We run a discovery and integration coverage review that establishes what's actually missing from your estate view, including status fields that don't match reality, and what that gap would cost you during an incident. For environments with sensitive live infrastructure, that review is the step before any discovery configuration change, not after. Talk it through on a [CMDB diagnostic call](https://www.apexconfiguration.com/cmdb-diagnostic-call), or [book a meeting](https://www.apexconfiguration.com/book-a-meeting) directly with the team. ## Frequently asked questions ### Why did the CMDB show the room as empty if the equipment was physically there? The equipment was recorded in ServiceNow, but its status field read "in stock" and "non-operational" rather than live and in production. Discovery and change tooling both rely on that status to judge risk, so equipment marked non-operational reads as safe to scan or touch, regardless of what's physically happening in the room. ### Whose responsibility is it to update equipment status when it goes live? In this case, nobody's, which was the root cause. The handoff between procurement, asset management and configuration management had no defined step for moving equipment from "in stock" to "live and operational" once it was installed and switched on. That ownership gap needs a named process step, not just a one-off data correction. ### Is horizontal discovery safe to run against sensitive broadcast infrastructure? It can be, but not as a generic sweep. Apex used light-touch scanning with custom pattern extensions written specifically for this estate, and only after confirming what was actually in each room by hand. Generic discovery against infrastructure this sensitive, without that groundwork, carries real risk. ### How do we check whether we have the same gap? Pull a list of configuration items marked non-operational or in stock, and cross-check a sample against what's actually deployed and running. Pay particular attention to any location where "non-operational" hasn't been reviewed since equipment was physically installed. *Written by Krzysztof Chrzanowski, Apex Configuration Group.* Book a free call to discuss how Apex can help you on your journey to a better CMDB   [![\CMDB Diagnostic Call\](https://hubspot-no-cache-eu1-prod.s3.amazonaws.com/cta/default/147949153/interactive-378363509978.png)](https://www.apexconfiguration.com/hs/cta/wi/redirect?encryptedPayload=AVxigLL%2BuZaA4OGhWplcJUZPSygxHRoLwW3Kh0kBVdp4c6QS9MaW0pDwkD%2FPvV7krtKIF0HLZe15bYrxFVFs0Bhiz3MIgw6Op0xvG%2Fwu48R7WxiywqeLddk8DGqj09xIfEcBBK7DuSWtcxOQc1kw%2B5fWzyh%2FsW3W7AQMQdc8FD38YgapibWvpivhNxMVUss3La37EdmfcvUaQmxFqcMUEaT2KyNwuGWkLj%2BIBF%2FmfgrjvcY%3D&webInteractiveContentId=378363509978&portalId=147949153) - Recent - Topics - Archive Recent ### Recent Topics ### Topics - [ServiceNow (35)](https://www.apexconfiguration.com/blog/tag/servicenow) - [CMDB (27)](https://www.apexconfiguration.com/blog/tag/cmdb) - [CMDB Data Quality (11)](https://www.apexconfiguration.com/blog/tag/cmdb-data-quality) - [Case Studies (5)](https://www.apexconfiguration.com/blog/tag/case-studies) - [Change Management (5)](https://www.apexconfiguration.com/blog/tag/change-management) - [Duplicate CIs (5)](https://www.apexconfiguration.com/blog/tag/duplicate-cis) - [CI Ownership (4)](https://www.apexconfiguration.com/blog/tag/ci-ownership) - [Compliance & Audit (4)](https://www.apexconfiguration.com/blog/tag/compliance-audit) - [IT Governance (4)](https://www.apexconfiguration.com/blog/tag/it-governance) - [Service Mapping (4)](https://www.apexconfiguration.com/blog/tag/service-mapping) - [Vulnerability Management (4)](https://www.apexconfiguration.com/blog/tag/vulnerability-management) - [Agentic AI (3)](https://www.apexconfiguration.com/blog/tag/agentic-ai) - [Data Model Design (3)](https://www.apexconfiguration.com/blog/tag/data-model-design) - [Enterprise Risk Management (3)](https://www.apexconfiguration.com/blog/tag/enterprise-risk-management) - [IRE (3)](https://www.apexconfiguration.com/blog/tag/ire) - [Incident Management (3)](https://www.apexconfiguration.com/blog/tag/incident-management) - [Service Graph Connectors (3)](https://www.apexconfiguration.com/blog/tag/service-graph-connectors) - [ServiceNow Discovery (3)](https://www.apexconfiguration.com/blog/tag/servicenow-discovery) - [Configuration Management (2)](https://www.apexconfiguration.com/blog/tag/configuration-management) - [Cyber Security (2)](https://www.apexconfiguration.com/blog/tag/cyber-security) - [Dependency Views (2)](https://www.apexconfiguration.com/blog/tag/dependency-views) - [IT Cost Optimisation (2)](https://www.apexconfiguration.com/blog/tag/it-cost-optimisation) - [Manufacturing (2)](https://www.apexconfiguration.com/blog/tag/manufacturing) - [Problem Management (2)](https://www.apexconfiguration.com/blog/tag/problem-management) - [CI Reconciliation (1)](https://www.apexconfiguration.com/blog/tag/ci-reconciliation) - [CMDB Remediation (1)](https://www.apexconfiguration.com/blog/tag/cmdb-remediation) - [CSDM (1)](https://www.apexconfiguration.com/blog/tag/csdm) - [IT Asset Management (1)](https://www.apexconfiguration.com/blog/tag/it-asset-management) - [ITOM (1)](https://www.apexconfiguration.com/blog/tag/itom) - [Managed Services (1)](https://www.apexconfiguration.com/blog/tag/managed-services) - [Operational Efficiency (1)](https://www.apexconfiguration.com/blog/tag/operational-efficiency) - [ServiceNow Advisory (1)](https://www.apexconfiguration.com/blog/tag/servicenow-advisory) See all Archive ### Archive - [October 2026 (8)](https://www.apexconfiguration.com/blog/archive/2026/10) - [September 2026 (16)](https://www.apexconfiguration.com/blog/archive/2026/09) - [August 2026 (2)](https://www.apexconfiguration.com/blog/archive/2026/08) - [July 2026 (4)](https://www.apexconfiguration.com/blog/archive/2026/07) - [June 2026 (3)](https://www.apexconfiguration.com/blog/archive/2026/06) - [May 2026 (2)](https://www.apexconfiguration.com/blog/archive/2026/05) See all ### Subscribe by email Share this [Share on X](https://x.com/intent/post?url=https://www.apexconfiguration.com/blog/routine-scan-took-live-broadcast-off-air&text=A+Routine+Scan+Took+A+Live+News+Broadcast+Off+Air) [Share on Facebook](https://www.facebook.com/sharer/sharer.php?u=https://www.apexconfiguration.com/blog/routine-scan-took-live-broadcast-off-air&t=A+Routine+Scan+Took+A+Live+News+Broadcast+Off+Air) [Share on LinkedIn](https://www.linkedin.com/shareArticle?mini=true&url=https://www.apexconfiguration.com/blog/routine-scan-took-live-broadcast-off-air&t=A+Routine+Scan+Took+A+Live+News+Broadcast+Off+Air) Previous story [← Managing A CMDB: Staffing Realities vs Managed Service](https://www.apexconfiguration.com/blog/managing-a-cmdb-staffing-realities-vs-managed-service) ![Krzysztof Chrzanowski](https://www.apexconfiguration.com/hs-fs/hubfs/krzysztof-chrzanowski.webp?width=64&height=64&name=krzysztof-chrzanowski.webp) By [Krzysztof Chrzanowski](https://www.apexconfiguration.com/blog/author/krzysztof-chrzanowski) Co-owner and Operations Director at Apex Configuration Group, based in Wrocław, Poland. Before co-founding Apex, Krzysztof worked as a Senior Configuration Manager (CMDB) at Warner Bros. Discovery,… [Full profile & credentials →](https://www.apexconfiguration.com/blog/author/krzysztof-chrzanowski) ### Get Email Notifications [![APEX CONFIGURATION GROUP](https://www.apexconfiguration.com/hs-fs/hubfs/Act3%20child/images/ACG-logo.png?width=135&height=93&name=ACG-logo.png)](https://www.apexconfiguration.com/) ServiceNow CMDB specialists delivering enterprise-grade implementation, remediation, and managed services. Address: 20 Wenlock Road, London, England, N1 7GU VAT Number: 505 0347 31 Company Number: 15871442 Email: [contact@apexconfiguration.com](mailto:contact@apexconfiguration.com) [Follow Apex Configuration Group on LinkedIn](https://www.linkedin.com/company/apex-configuration-group) Services - [CMDB Health Check](https://www.apexconfiguration.com/cmdb-health-check) - [Design & Implementation](https://www.apexconfiguration.com/cmdb-design-implementation) - [Managed Service](https://www.apexconfiguration.com/managed-cmdb-services) - [Automation & Optimisation](https://www.apexconfiguration.com/cmdb-automation-tools) - [Health Dashboard & Reporting](https://www.apexconfiguration.com/cmdb-health-dashboard-servicenow) Company - [What is a CMDB?](https://www.apexconfiguration.com/what-is-cmdb) - [Benefits](https://www.apexconfiguration.com/benefits-of-cmdb) - [About](https://www.apexconfiguration.com/about-apex) - [Blog](https://www.apexconfiguration.com/blog) Resources - [Contact Us](https://www.apexconfiguration.com/contact-us) - [CMDB Diagnostic Call](https://www.apexconfiguration.com/cmdb-diagnostic-call) - [Book A Meeting](https://www.apexconfiguration.com/book-a-meeting) © 2026 Apex Configuration Group. All rights reserved. ServiceNow is a trademark of ServiceNow, Inc. We are not affiliated with or endorsed by ServiceNow. - [Terms](https://www.apexconfiguration.com/terms) - [Cookies](https://www.apexconfiguration.com/cookie-policy) - [Privacy](https://www.apexconfiguration.com/privacy-policy) ```json { "@context" : "https://schema.org", "@id" : "https://www.apexconfiguration.com/#organization", "@type" : [ "Organization", "ProfessionalService" ], "address" : { "@type" : "PostalAddress", "addressCountry" : "GB", "addressLocality" : "London", "addressRegion" : "England", "postalCode" : "N1 7GU", "streetAddress" : "20 Wenlock Road" }, "alternateName" : "Apex Configuration Group", "areaServed" : "GB", "contactPoint" : { "@type" : "ContactPoint", "areaServed" : "GB", "availableLanguage" : "en", "contactType" : "customer service", "telephone" : "+44 20 8058 8135" }, "identifier" : { "@type" : "PropertyValue", "propertyID" : "UK Companies House company number", "value" : "15871442" }, "image" : "https://www.apexconfiguration.com/hs-fs/hubfs/Act3%20child/images/Configuration-data.webp", "legalName" : "Apex Configuration Group Ltd", "logo" : "https://www.apexconfiguration.com/hs-fs/hubfs/Act3%20child/images/ACG-logo.png", "name" : "Apex Configuration Group Ltd", "sameAs" : [ "https://www.linkedin.com/company/apex-configuration-group", "https://find-and-update.company-information.service.gov.uk/company/15871442", "https://www.crunchbase.com/organization/apex-configuration-group-ltd" ], "telephone" : "+44 20 8058 8135", "url" : "https://www.apexconfiguration.com/" } ``` ```json { "@context" : "https://schema.org", "@id" : "https://www.apexconfiguration.com/#website", "@type" : "WebSite", "inLanguage" : "en-GB", "name" : "Apex Configuration Group", "publisher" : { "@id" : "https://www.apexconfiguration.com/#organization" }, "url" : "https://www.apexconfiguration.com/" } ``` ```json { "@context" : "https://schema.org", "@type" : "WebPage", "description" : "A subnet scan took a production control room offline mid-broadcast. The CMDB said it was empty. Here's how that happened and what stopped it recurring.", "inLanguage" : "en-GB", "name" : "A Routine Scan Took A Live News Broadcast Off Air", "publisher" : { "@type" : "Organization", "logo" : { "@type" : "ImageObject", "url" : "https://www.apexconfiguration.com/hs-fs/hubfs/Act3%20child/images/ACG-logo.png" }, "name" : "Apex Configuration Group Ltd", "url" : "https://www.apexconfiguration.com/" }, "url" : "https://www.apexconfiguration.com/blog/routine-scan-took-live-broadcast-off-air" } ``` ```json { "@context" : "https://schema.org", "@type" : "BreadcrumbList", "itemListElement" : [ { "@type" : "ListItem", "item" : "https://www.apexconfiguration.com/", "name" : "Home", "position" : 1 }, { "@type" : "ListItem", "item" : "https://www.apexconfiguration.com/blog/routine-scan-took-live-broadcast-off-air", "name" : "A Routine Scan Took A Live News Broadcast Off Air", "position" : 2 } ] } ``` ```json { "@context" : "https://schema.org", "@type" : "BlogPosting", "author" : { "@type" : "Person", "name" : "Krzysztof Chrzanowski", "sameAs" : [ "https://www.linkedin.com/in/krzysztof-chrzanowski-cmdb/" ], "url" : "https://www.apexconfiguration.com/blog/author/krzysztof-chrzanowski" }, "dateModified" : "2026-10-09T08:00:02+0000", "datePublished" : "2026-10-09T08:00:02+0000", "headline" : "A Routine Scan Took A Live News Broadcast Off Air", "image" : [ "https://147949153.fs1.hubspotusercontent-eu1.net/hubfs/147949153/AI-Generated%20Media/Images/Broadcast%20Control%20Room%20Technician.png" ], "mainEntityOfPage" : { "@id" : "https://www.apexconfiguration.com/blog/routine-scan-took-live-broadcast-off-air", "@type" : "WebPage" }, "publisher" : { "@type" : "Organization", "logo" : { "@type" : "ImageObject", "url" : "https://www.apexconfiguration.com/hs-fs/hubfs/Act3%20child/images/ACG-logo.png" }, "name" : "Apex Configuration Group Ltd", "url" : "https://www.apexconfiguration.com/" } } ```