We have issued an official response to this issue here: Pyrogram network issue - #38 by ShaneAtReplit.