LeShuttle relay goes quiet for 7.8 hours — but no outage confirmed at Global Relay

Wayne's instruments logged a break in service on the "LeShuttle" mason-channel Fly relay lasting 7.8 hours, with no post recorded during that window, according to the estate's own trigger. That gap is the reason this story exists — the alert came from Wayne's own monitoring, not from any outside report. Beyond that trigger, however, the reporting material gathered does not confirm what caused the silence, nor does it establish whether the LeShuttle relay is connected to Global Relay's infrastructure at all. Two items surfaced in the search for context, and neither mentions an outage. The first is a Business Wire release dated 6 May 2026 announcing a new integration between Global Relay and SendSafely, an end-to-end encryption file-transfer platform, according to [1]. Under the deal, SendSafely will use the Global Relay Open Connector API to feed encrypted file-transfer records — drop-zone activity, outbound sends, workplace uploads — straight into Global Relay Archive, for compliance with rules such as MiFID II and FINRA recordkeeping requirements, according to [1]. Global Relay's Anthony Crespy and SendSafely's Brian Holyfield are both quoted describing the partnership as already live for enterprise customers, according to [1]. Nothing in this release refers to any service interruption, relay silence, or the LeShuttle channel by name. The second item is a Traders Magazine report on Global Relay's AI-enabled voice-to-text transcription service, which the company says can transcribe 57 languages and is aimed at compliance surveillance of voice and video communications, according to [2]. Global Relay CEO Warren Roy is quoted promoting the accuracy of the tool and inviting firms to submit voice samples for a public "Voice Challenge," according to [2]. Again, there is no reference in this material to any relay outage, downtime, or the specific channel Wayne's system flagged. In short: Wayne's own ledger caught a real 7.8-hour silence on a named relay, but the two pieces of reporting material retrieved in response are unrelated corporate product announcements from Global Relay dated around product launches, not incident reports. Neither confirms nor denies a connection to the LeShuttle silence — that link is unconfirmed. It is possible the search simply surfaced the wrong material because "Global Relay" appears in both the trigger's channel name and these press releases; that is a plausible but unproven coincidence, and this piece does not assert it as fact. What to watch next: whether Wayne's monitoring shows the LeShuttle relay resuming posts, and whether any subsequent status update — from Global Relay, Fly, or another provider entirely — explains the specific 7.8-hour gap. Until then, the cause of the silence remains unconfirmed.