Intel pulls out of Mobile World Congress because of coronavirus

HP Envy 32 Intel logo
HP Envy 32 Intel logo (Image credit: Windows Central)

What you need to know

  • Intel pulled out of Mobile World Congress due to the coronavirus.
  • Intel is expected to make announcements at the event, but will not have anyone attend it in person.
  • Amazon, LG Electronics, Ericsson, and NVIDIA have also pulled out of the conference.

Intel will not attend Mobile World Congress this year due to safety concerns caused by the coronavirus. Several large tech companies have also pulled out of the event, including Amazon, LG Electronics, Ericsson, and NVIDIA. While Intel won't have anyone attend the event in person, VentureBeat states that the company is still expected to make announcements at the conference.

VentureBeat also shared the following statement from Intel:

The safety and wellbeing of all our employees and partners is our top priority, and we have withdrawn from this year's Mobile World Congress out of an abundance of caution. We are grateful to the GSMA for their understanding and look forward to attending and supporting future Mobile World Congress events.

Mobile World Congress runs from February 24 through February 27 in Barcelona. Mobile World Congress is a massive conference with tens of thousands of people attending from around the world, so security concerns regarding the coronavirus are heightened.

More than 42,000 cases of the coronavirus have been reported so far, and the death toll for it recently surpassed 1,000.

Sean Endicott
News Writer and apps editor

Sean Endicott is a tech journalist at Windows Central, specializing in Windows, Microsoft software, AI, and PCs. He's covered major launches, from Windows 10 and 11 to the rise of AI tools like ChatGPT. Sean's journey began with the Lumia 740, leading to strong ties with app developers. Outside writing, he coaches American football, utilizing Microsoft services to manage his team. He studied broadcast journalism at Nottingham Trent University and is active on X @SeanEndicott_ and Threads @sean_endicott_.