A fire at the COP30 United Nations climate summit in Bel\u00e9m, Brazil, forced the temporary closure of the conference\u2019s main venue, according to officials. More than 20 people were treated for smoke inhalation and other related injuries.<\/p>\n\n\n\n
The incident occurred in the Blue Zone, the area where international delegations, negotiators, and ministers meet to conduct formal climate talks. Officials said<\/a> the fire broke out shortly after 2 p.m. on Thursday and was brought under control within about six minutes. All attendees were safely evacuated.<\/p>\n\n\n\n According to conference organizers, 13 people were initially treated on site for smoke inhalation. Local outlet g1 later reported that 21 people received medical attention, including 19 for smoke inhalation and two for anxiety episodes.<\/p>\n\n\n\n As a precaution, the Brazilian government and the UNFCCC temporarily closed the Blue Zone while fire authorities conduct a full safety assessment. The Green Zone, which hosts public exhibits and civil society events, remains open.<\/p>\n\n\n\n In a follow-up update, officials said they are working on a plan to resume activities \u201cfocused on negotiations\u201d once the venue is cleared by fire and health authorities. Any meetings held Thursday night will be limited to consultations with groups whose sessions were interrupted.<\/p>\n\n\n\n Local authorities are investigating the cause of the fire. Par\u00e1 Governor Helder Barbalho told g1<\/a> that teams are examining two initial hypotheses: a generator malfunction or a short circuit in an exhibition stand inside the Countries Pavilion, where the fire was reported.<\/p>\n\n\n\n Bel\u00e9m, the capital of Par\u00e1 state in northern Brazil, is hosting COP30, the 30th annual United Nations Climate Change Conference. The summit brings together nearly 200 countries to negotiate global climate commitments.<\/p>\n\n\n\n BREAKING \ud83d\udd34
Fire breaks out in pavilion at COP30 climate talks in Belem, Brazil. pic.twitter.com\/8sNslDzdHt<\/a><\/p>— Open Source Intel (@Osint613) November 20, 2025<\/a><\/blockquote>