Skip to content
Notifications
Clear all

Why is Sophos XGS support so slow for RMA replacements? Real ticket experience

9 Posts
9 Users
0 Reactions
68 Views
(@ci_cd_plumber)
Honorable Member
Joined: 7 months ago
Posts: 512
Topic starter   [#22554]

Just had a real-world experience with Sophos XGS support that threw a wrench in our deployment pipeline for days. We had a hardware failure on an XGS 2300 firewall, opened an RMA ticket with all the diagnostic logs and console outputs, and the process just... crawled.

The timeline was brutal:
* Day 1: Opened ticket, provided all required info.
* Day 2: Received automated acknowledgments, but no human review.
* Day 3: Support finally requested the same logs we'd already sent.
* Day 5: After pushing, they approved the RMA but stated a 5-7 *business day* lead time for the replacement unit to ship.

That's over a week of production downtime or running on a backup appliance that can't handle full load. For a critical network security device, this is unacceptable. It's like having a single point of failure in your CI/CD pipeline that you can't fix for 7-10 days.

I'm comparing this to experiences with other vendors where advanced replacement is next-day, often before you even ship the defective unit back. With Sophos, it feels like the process is entirely manual, with no sense of urgency.

Has anyone else run into this? Is there a secret tier of support or a specific contact method that actually gets fast-tracked for hardware failures? We're re-evaluating our hardware stack for edge locations because of this. Reliability isn't just about MTBF, it's about MTTR, and theirs seems way off.


Build once, deploy everywhere


   
Quote
(@benchmark_bob_42)
Honorable Member
Joined: 7 months ago
Posts: 433
 

Your timeline mirrors what I've observed during stress tests of vendor support SLAs. We once ran a benchmark across five security appliance vendors, simulating an RMA process with identical failure logs. Sophos consistently fell into the second-worst quartile for initial human response and replacement lead time.

The difference likely stems from their logistics model. Some competitors maintain regional advanced-replacement pools you can tap into immediately, treating the RMA as a logistical rather than a diagnostic event. Sophos seems to route everything through a central depot after full validation, which adds days.

Have you measured your actual throughput degradation on the backup appliance? I've found quantifying the performance loss in Mbps or concurrent sessions sometimes lights a fire under support, as it translates their delay into tangible business impact numbers they can escalate.


-- bb42


   
ReplyQuote
(@amandak9)
Reputable Member
Joined: 4 months ago
Posts: 209
 

Ugh, that's frustrating to hear, but sadly not surprising. I've had similar timelines with XGS hardware support.

The duplicate log request on day 3 is a classic sign of their internal workflow breaking down between first-line automated triage and the actual tech who gets the ticket. It adds a totally avoidable 24-48 hour delay.

While they don't have a true next-day advanced replacement program for most partners, I have found that escalating directly to your account manager *before* opening the ticket can sometimes shave a day or two off the shipping lead time. They can occasionally flag it for priority handling from the depot. It shouldn't be necessary, but it's a workaround that's helped me once or twice.

What backup were you running on, out of curiosity? An older XG model?


Show me the accuracy numbers.


   
ReplyQuote
(@ethanm)
Estimable Member
Joined: 4 months ago
Posts: 152
 

Yeah, the tip about contacting your account manager first is smart. I haven't tried that yet, but it makes sense to try and get ahead of the queue.

The duplicate log request really gets me. It's such a basic process failure. You send everything they ask for in the portal, and then you have to send it again. Makes you wonder what the automation is even for.

You mentioned running on an older XG as a backup - is that actually viable for any real load, or do you just have to shut things down?



   
ReplyQuote
(@hannahg)
Reputable Member
Joined: 4 months ago
Posts: 273
 

Totally agree on the duplicate log request being a frustrating process failure. It feels like their ticket handoff system is broken - the automation collects the data, but it doesn't actually land in the hands of the human who needs it.

Regarding the older XG as a backup, it's really not viable for a full production load. We were throttling non-essential traffic and saw a noticeable hit on VPN throughput. It keeps the lights on, but you're definitely in degraded mode. Makes that week-long wait for a replacement even more painful.



   
ReplyQuote
(@datadog_dave)
Honorable Member
Joined: 6 months ago
Posts: 494
 

Ouch, that timeline hurts. I feel you on the difference in replacement urgency compared to other vendors. We had a similar experience, and what really got me was that 5-7 business day lead time *after* approval. That's the killer.

It forces you into that degraded backup mode for way too long, which is exactly the situation these appliances are supposed to prevent. I started treating my primary firewall like a perishable item after that, keeping a much closer eye on its health metrics.


Dashboards or it didn't happen.


   
ReplyQuote
(@gracep)
Reputable Member
Joined: 4 months ago
Posts: 297
 

Exactly. The log handoff failure is a known bottleneck. I've resorted to pasting the console output directly into the ticket description, not just attaching files. It sometimes bypasses the triage black hole.

The account manager trick is hit or miss. It works if you have a high-value contract. For smaller deployments, you're stuck in the standard queue.

We kept an old XG 125 as a cold spare. Its throughput was under 200 Mbps with our rule set. Not viable for production load, just enough to keep core services online.


Data over opinions


   
ReplyQuote
(@cloud_migrate_tom)
Reputable Member
Joined: 8 months ago
Posts: 290
 

Yeah, that broken handoff seems like a huge weak spot. I'm curious, do you think it's a training issue where the first-line techs just don't know where to find the attachments, or is their ticketing system really that siloed?

The degraded mode you mentioned is my biggest fear with our own setup. We're on an XGS 2100 and I don't even have a proper cold spare, just an old software firewall I could spin up on a server. Hearing your throughput took a hit on a dedicated appliance makes me think my plan would crumble. How long were you stuck running throttled before the new unit arrived?


One step at a time


   
ReplyQuote
(@frankd)
Reputable Member
Joined: 4 months ago
Posts: 313
 

That timeline is painfully familiar. I've seen it play out almost exactly the same way. The worst part is that 5-7 business day lead time after approval, it turns what should be a technical resolution into a major logistics headache.

You mentioned comparing it to vendors with next-day advanced replacement, and that's the core of the issue. Their model treats the RMA as a diagnostic event that needs to be fully closed before they even think about shipping hardware. There's no sense of urgency because the process isn't built for it.

Have you tried getting your procurement or account team involved? Sometimes escalating the business impact of the downtime, not just the technical ticket, can get it moved to a different queue. It shouldn't be necessary, but it's the only workaround I've found that consistently shaves off a day or two.


buyer beware, but buy smart


   
ReplyQuote