cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

EE Blocked Siteground Websites

Babakbyatt
Investigator
Investigator

I have 298 websites hosted on SiteGround. Any client using EE Mobile cannot access their website. SiteGround support said because the SiteGround support team is in Bulgaria, they cannot identify the issue with EE because they do not have access to EE mobile phone. This is ridiculous, I will take legal action for damaging my business.

195 REPLIES 195
Chyriwsky
Valued Contributor
Valued Contributor

I've managed to speak with a complaints executive who are now opening dialogue with Siteground.

Great, thanks! This is quite ridiculous though, how could they suddenly not work?! How can we be sure that the same thing won't happen again in the future?

Chyriwsky
Valued Contributor
Valued Contributor

Well, nothing is ever foolproof. I imagine at a guess they have blacklisted a dodgy website and that's accidentally blocked all siteground sites.

@Babakbyatt : So it would appear. I'm sure that you had more posts before

If you think I helped please feel free to hit the "Thumbs Up" button below.

To phone EE CS: Dial Freephone +44 800 079 8586 - Option 1 for Mobile Phone & Mobile Broadband or Option 2 for Home Broadband & Home Phone

ISPs: 1999: Freeserve 48K Dial-Up > 2005: Wanadoo 1 Meg BB > 2007: Orange 2 Meg BB > 2008: Orange 8 Meg LLU > 2010: Orange 16 Meg LLU > 2011: Orange 20 Meg WBC > 2014: EE 20 Meg WBC > 2020: EE 40 Meg FTTC > 2022:EE 80 Meg FTTC SoGEA > 2025 EE 150 Meg FTTP

@Chyriwsky : So it was due to Contact Lock as I proposed?

If you think I helped please feel free to hit the "Thumbs Up" button below.

To phone EE CS: Dial Freephone +44 800 079 8586 - Option 1 for Mobile Phone & Mobile Broadband or Option 2 for Home Broadband & Home Phone

ISPs: 1999: Freeserve 48K Dial-Up > 2005: Wanadoo 1 Meg BB > 2007: Orange 2 Meg BB > 2008: Orange 8 Meg LLU > 2010: Orange 16 Meg LLU > 2011: Orange 20 Meg WBC > 2014: EE 20 Meg WBC > 2020: EE 40 Meg FTTC > 2022:EE 80 Meg FTTC SoGEA > 2025 EE 150 Meg FTTP
JohnMaz
Established Contributor
Established Contributor

We dont know yet as they haven't fixed the problem.  It's not working for my SIM card yet.  It's more likely to be a routing fault or a firewall issue I expect, but if posts were deleted perhaps I haven't seen what you saw.  It is certainly not the normal content block that tech support have access to, or that we do in our SIM card management, and we are seeking a solutoin htat sorts out the issue at source.  when it's properly fixed we should not need to change anything at our end.

XRaySpeX
EE Community Star
EE Community Star

Yes, I meant a wrongly applied Content Lock rule.

If you think I helped please feel free to hit the "Thumbs Up" button below.

To phone EE CS: Dial Freephone +44 800 079 8586 - Option 1 for Mobile Phone & Mobile Broadband or Option 2 for Home Broadband & Home Phone

ISPs: 1999: Freeserve 48K Dial-Up > 2005: Wanadoo 1 Meg BB > 2007: Orange 2 Meg BB > 2008: Orange 8 Meg LLU > 2010: Orange 16 Meg LLU > 2011: Orange 20 Meg WBC > 2014: EE 20 Meg WBC > 2020: EE 40 Meg FTTC > 2022:EE 80 Meg FTTC SoGEA > 2025 EE 150 Meg FTTP
morthanveld
Contributor
Contributor

Pleased to hear that there is some movement on this behind the scenes now. I have just replied to my ongoing Siteground support ticket pointing out the potential loss of business if I have to move all of my sites, as well as those of the customers I don't directly manage but who I know are also on SG. I also put a formal complaint in to EE yesterday after getting the runaround from a tech support call who clearly didn't understand the issue, and sounded like he didn't want to. 

Like many others affected, I can't afford to let this go and potentially wave goodbye a significant chunk of UK mobile traffic (to say nothing of the inconvenience to me of having to change DNS servers just so I can access my site dashboards), so hopefully some action is happening now. 

JohnMaz
Established Contributor
Established Contributor

I've had a High Level Complaints person called Bev contact me by email this evening.   Couid have been my email to the CEO, but perhaps more likely it was that I spent an hour on the on the phone and eventually managed to speak to a supervisor, who was technical enough to finally understood the issue.  I also asked to raise it as a high level complaint.  So hoping this will move along tomorrow.  One of the others is doing the same, so hopefully it's being coordinated behind the scenes.  Fingers crossed.

Instead of moving everything, temporarily use cloudflare. Save time and money. It's not Sitegrounds fault.