UPDATE: 7: 23 a.m. EDT — A Google Search Engine outage happened around 5:41 a.m. EDT in parts of Europe and is slowly spreading globally. The outage has spread to Washington, Boston and Detroit. While the Netherlands, Denmark and parts of Germany are still severely affected, the issue has stopped affecting India. There is still no word from the company on the problem.

UPDATE: 6:50 a.m. EDT — A Google search engine outage happened around 5:41 a.m. EDT in parts of Europe and is slowly spreading globally. While the outage remains most severe in the Netherlands and Denmark, it has spread to some cities in Israel and India. Although Google is still mum on the subject, a user going by the name Baba Jahedmanesh said that this was a protocol error caused by 'Experimental Quic' change in the settings. Inexplicably, he also said "So much for #NetNeutrality."

UPDATE: 6:34 a.m. EDT — A Google search engine outage affecting parts of Europe was first reported by users at around 5:41 a.m. EDT. While the company is yet to issue any statement on the problem, a user called Tommy said on Twitter that the issue could have caused by the company making changes to its Chrome browser.

The outage continues to spread and is now affecting parts of Italy and Hungary in Europe, and Phoenix, Arizona, in the U.S.

UPDATE: 6:24 a.m. EDT — An outage of Google's primary service, its search engine, that began in Europe on Monday morning, has spread to parts of the United States and the United Kingdom. Down Detector showed Fort Wayne, Chicago, St. Louis and New York as affected areas in the U.S., while London and Barcelona were added to the affected areas in Europe.

The outage is most severe in the Netherlands, Denmark and parts of Germany.

Original story:

Google is currently down in many parts of Europe. Outage detector website Down Detector showed at around 6 a.m. EDT, that almost whole of The Netherlands was affected by the outage, while German users faced outages in Cologne, Bonn, Munch, Berlin, Frankfurt and Hanover. Users were also facing issues in Antwerp and Brussels in Belgium and Odense and Copenhagen in Denmark.

While the company is yet to acknowledge the issue, customers have started complaining on Twitter.

The cause of the technical difficulties is not known as of 6:08 a.m. EDT.

This is a developing story.