JT’s Meta Apps Outage Stretches Past a Week With No End in Sight

JT customers in Jersey and Guernsey have spent more than a week unable to load images and videos inside Meta apps, and a fix still doesn’t have a published timeline. The Channel Islands mobile operator is on its fifth consecutive service update saying it is “working directly with Meta” to resolve the problem. Customers complained first on Facebook and Instagram on Friday, and the issue was still active as of yesterday.

JT’s most recent update, posted on the company’s Service Announcements page at 8 July at 16:15, said Meta “remains fully engaged” in restoring service but offered no completion date. The outage now stretches past eight days from the first acknowledged report. The Jersey Evening Post has published an account; JT has declined to respond to the JEP’s questions.

What the Issue Actually Looks Like on a Phone

JT customers report the failure inside Meta’s mobile apps on their phones, where the same content loads normally on a home Wi-Fi connection or on another carrier’s data network. The break sits between JT’s mobile network and Meta’s image servers. JT has described the problem as an “intermittent issue affecting Meta apps,” a wording that covers images, videos, reels and GIFs inside the wider Meta family. For affected users the result is a feed full of empty boxes and stalled videos that never finish loading.

The list of affected content types is broader than the initial complaints suggested. Customers first flagged the problem on Facebook and Instagram, and WhatsApp, also owned by Meta, sits on the same image-server path inside Meta’s infrastructure. The wider “Meta apps” wording in JT’s update extends the scope to Threads and Messenger, the other apps inside the company’s family. Four content types have been named in JT’s rolling announcements:

• Images and photos failing to load or display
• GIFs not displaying
• Videos stalling or refusing to play
• Reels failing to load

JT is the dominant mobile operator across Jersey and Guernsey, so the blast radius covers a large share of the Channel Islands’ mobile users. The complaints first surfaced publicly on Friday 3 July.

A Week of Friday-by-Friday Updates

JT has issued a rolling series of named Service Announcements on the same Meta apps problem, with the same closing line each time: “We’ll share further updates as soon as more information becomes available.” The sequence so far:

1. Friday 3 July, 08:35. JT posts its first Service Announcement on the Meta apps issue.
2. Monday 6 July. JT confirms the problem is ongoing and says its teams are “working directly with Meta to resolve the issue.”
3. Wednesday 8 July. JT’s engineers are “continuing to work closely with Meta to investigate the intermittent issue.”
4. Wednesday 8 July, 16:15. JT publishes its most recent update, saying Meta “remains fully engaged and are working to restore normal service as quickly as possible.”
5. Yesterday, 9 July. Customers were still experiencing the issue, and JT declined to respond to questions from the Jersey Evening Post.

We understand how frustrating this is. We’ll share further updates as soon as more information becomes available.

The block quote is the closing paragraph of JT’s 8 July 16:15 update, by the JT Help Team, on JT’s current service announcements page. JT has repeated the same closing line in every update. As of yesterday, customers were still experiencing the issue, and JT has declined to respond to questions from the Jersey Evening Post.

Meta’s Side of the Conversation

Meta has not publicly acknowledged the Channel Islands’ specific problem. The complaint thread sits on JT’s side; the working sessions sit in private JT-Meta channels. None of JT’s updates cite a public Meta statement on this issue.

For JT customers, that absence has a shape. The local operator keeps fielding questions that Meta, the party with the actual content, has yet to take publicly. JT’s wording is careful: every announcement asks customers to bear with the company while it works with a partner that has not stood in front of a microphone or issued a press line on the topic. Customers complaining on social media have been addressing JT, not Meta, in part because Meta has no local presence to complain to. The asymmetry is built into the relationship: JT owns the connectivity, Meta owns the content, and the fault line sits between them.

JT has not said what the underlying technical fault is, only that it is “intermittent.” Customer posts on local Facebook groups have speculated that the problem sits with Meta’s content delivery network rather than JT’s own routing. JT has neither confirmed nor denied that diagnosis in any of its public updates. The fix requires both sides to act, which is why JT keeps returning to “working with Meta.”

Why the Fix Sits Beyond JT’s Switchboard

JT has used nearly identical language for a week: it is investigating, it is working directly with Meta, Meta is “fully engaged,” and customers will hear more when there is more to say. The repetition is itself a tell. When a mobile operator is routing calls, sending texts, and running a working 5G Standalone network in Guernsey, and one specific category of internet traffic still won’t load for its users, the fault has to be somewhere the operator cannot push a button and reset. JT engineers can rebuild their side of the link, but if Meta’s image servers are the failing hop, the JT side ends at a peering point and the rest is Meta’s to repair.

That is why JT has not published a workaround for affected customers, and why it has not published a fix-by date either. The intermittent issue description matters in the same way: a fault that comes and goes is harder to catch on a traceroute than a hard outage.

JT has also chosen not to put a custom status note in front of its mobile customers via SMS, the channel it would normally use for an outage it owned end to end. The chosen format, a public Service Announcements page updated at 16:15, is the format JT would use for an issue where its role is limited. Meta has not opened a status page entry that names the Channel Islands either. The two silence-shaped responses have left JT’s customers with no working estimate of when the images in their feeds will return.

A Loud Year on a Quiet Network

The Meta apps outage is the latest in a noisier-than-usual year for JT. The company switched on Guernsey’s first 5G sites in St Peter Port under its Ericsson-built 5G Standalone plan, with island-wide coverage due over four months, a rollout that How JT switched on Guernsey’s first 5G sites tracks in detail. It has separately been at the centre of a Coop Mobile complaint to the island’s competition regulator over the speed of customer transfers between networks. The Public Accounts Committee is set to investigate how JT is overseen as a telecoms provider in the Channel Islands.

Two service moments from late June and early July, before the Meta apps problem began, sit close enough to colour the read. JT carried out planned mobile maintenance across Jersey and Guernsey from 10:30pm on Tuesday 30 June to 5am on Wednesday 1 July, with brief call issues possible during the window. A separate ringtone fault appeared on top of that maintenance: some customers reported hearing an international ringtone when making local and UK calls.

JT handled the ringtone fault with a familiar shape: a public notice, an engineer-line investigation, a reassurance on charging, and a promise to update. The ringtone statement added an extra line, that customers would not be charged international rates for the affected calls, because the company had to plug a billing-shaped gap as well as a service gap. JT has separately dropped a plan to add two admin charges for elderly Islanders who do not pay by direct debit.

Across all of it, JT’s published language has stayed procedural: investigation, working with partner, please bear with us. The same template is now in its second week on the Meta apps problem. The public will read the next update when JT posts one.

Frequently Asked Questions

Which Meta apps are affected for JT customers?

Facebook, Instagram and WhatsApp sit inside the affected set, and JT’s update covers images, GIFs, videos and reels across “Meta apps” generally, a wording that pulls in Threads and Messenger too. Customers first complained about Facebook and Instagram image loading; JT’s later updates broadened the scope to the wider Meta family. WhatsApp, the third app named by JT, shares the same image-server path inside Meta’s infrastructure.

How long has the JT Meta outage been going?

It opened on Friday 3 July 2026, which puts it past a week as of today. JT’s first Service Announcement that day went up at 08:35. By yesterday, 9 July, customers were still experiencing the issue.

Has Meta publicly responded about the JT-side issue?

Meta has not publicly acknowledged the JT-specific problem. The closest adjacent event was a brief global Meta outage on 12 June 2026, which is a separate incident and not the issue JT customers have been living with. JT’s own updates have stayed the only public record of the Channel Islands problem.

When did JT last update customers about the Meta apps problem?

16:15 on 8 July 2026. JT’s Help Team wrote on the Service Announcements page that its engineers were “continuing to work closely with Meta to investigate the intermittent issue” and that Meta “remains fully engaged.” No further update has appeared on the page since.