Russia announces ceasefire in Syria's Idlib from Saturday

Syria's war has killed more than 370,000 people and displaced millions since it started in 2011


Afp August 31, 2019
Smoke billows into the sky following a reported regime air strike on the eastern outskirts of Maaret al-Numan in Syria's northwestern province of Idlib on August 24, 2019. PHOTO: AFP

MOSCOW: Russia on Friday announced that Syrian government forces would cease-fire from Saturday morning in Idlib, one of the last holdouts of opposition to President Bashar al-Assad.

An agreement was reached on "a unilateral ceasefire by Syrian government forces in the Idlib de-escalation zone, from 6:00 am on August 31," the Russian Reconciliation Centre for Syria said in a statement.

Syria flare-up kills 35 fighters, including 26 pro-regime forces: monitor

The announcement came after Russian-backed regime forces advanced in the militant-held bastion, with monitors reporting airstrikes that killed civilians including children.

In Washington, Secretary of State Mike Pompeo voiced concern over the "horrific effects" on civilians from the airstrikes by Assad and his allies.

"He underscored the need for an immediate return to a ceasefire," the State Department said in a statement after Pompeo met the UN special envoy on Syria, Geir Pedersen.

The Russian statement said the ceasefire aimed "to stabilise the situation" in Idlib and urged anti-government fighters to "abandon armed provocations and join the peace process".

Eight years on, Syria's neighbours weary of war refugees

After months of intense bombardment, regime forces launched a ground offensive against Idlib earlier this month.

Syria's war has killed more than 370,000 people and displaced millions since it started in 2011.

Russia launched a military intervention in support of Assad in 2015, helping his forces to reclaim large parts of the country from opposition fighters and jihadists.

COMMENTS

Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ