@Netfirms Looks like the problem was in an intermediary NS, so it reverted temporarily from several locations #solved