[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"branding":3,"analytics":7,"article-treasury-sanction-took-down-telegrams-tme-links-for-19-hours":10,"sections":48},{"siteName":4,"siteTagline":5,"publisherName":4,"contactEmail":6},"The Revision","Tech news, decoded.","editor@therevision.news",{"gaMeasurementId":8,"adsenseClientId":9},"G-ZW2MV82GYR","ca-pub-8533917693782264",{"article":11},{"id":12,"slug":13,"title":14,"dek":15,"body_md":16,"tags_json":17,"published_at":18,"created_at":19,"updated_at":20,"status":21,"review_note":22,"review_notes":23,"image_url":22,"persona_id":22,"persona_name":22,"section":38,"tags":39,"sources":43,"feedback":47,"feedback_at":22,"cost_usd":47,"total_tokens":47},4816,"treasury-sanction-took-down-telegrams-tme-links-for-19-hours","Treasury Sanction Took Down Telegram's t.me Links for 19 Hours","A Treasury sanction targeting a cybercriminal VPN accidentally pulled Telegram's t.me domain from global DNS, darkening shortlinks for roughly a billion users.","A US sanctions action against a rogue VPN knocked out Telegram's shortlinks for nearly a day — not because Telegram did anything wrong, but because its domain was collateral damage.\n\nOn July 13, the Treasury Department's Office of Foreign Assets Control sanctioned the operators of First VPN Service, a proxy network that actively marketed itself to ransomware gangs and had already been shut down by European law enforcement in May. OFAC published a list of infrastructure tied to 1VPNS, and buried in that list was a single Telegram support channel: t.me\u002FFirstVPNService. Domain registries are legally required to act fast on OFAC lists, but there's a catch — a registry can't surgically remove one channel path from a domain. Identity Digital, which manages the .me top-level domain backend, confirmed that Domain.Me applied a \"serverHold\" to the entire t.me domain, wiping it from global DNS. The outage lasted roughly 19 hours. Core Telegram app functions stayed up, and the older telegram.me domain kept working, but every shortlink — group invites, profile shares, channel links — went dark for an estimated billion users.\n\nThe fix required Telegram CEO Pavel Durov to publicly prod the registrar on X before anyone connected the dots. Once Telegram scrubbed the offending channel and confirmed compliance, Domain.Me lifted the hold. What the incident actually demonstrates is an architectural fragility hiding in plain sight: a single URL on a government list can cascade into a platform-wide outage because DNS was never designed to make surgical cuts. Telegram isn't the first platform to get caught in sanctions crossfire, but the scale here — a billion users, 19 hours — sets a new benchmark for collateral damage.\n\nSanctions compliance and internet infrastructure have been on a collision course for years; this week they finally collided.","[\"telegram\",\"sanctions\",\"dns\",\"security\"]","2026-07-17T14:43:57.000Z","2026-07-17T15:02:13.128Z","2026-07-17T15:02:15.898Z","published",null,[24,30,34],{"id":25,"reviewer":26,"round":27,"reason":28,"status":29},"editor-r1","editor",1,"The article omits the content of Domain.Me's public statement and Durov's X post despite referencing both as public statements — include the quoted text from each or explicitly mark the omission as deliberate; additionally, the article attributes the serverHold action solely to 'Domain.Me, the Montenegro-based registry' without mentioning Identity Digital (the technical backend operator) that the source identifies as the entity that confirmed the block at OFAC's request, creating a factual gap a","resolved",{"id":31,"reviewer":26,"round":32,"reason":33,"status":29},"editor-r2",2,"The article quotes Durov's X post and Domain.Me's statement and correctly attributes the serverHold to both Identity Digital and Domain.Me, resolving the prior concern — but the body states 1VPNS was shut down by 'European law enforcement' in May without naming which agencies or countries, and more critically the dek says 'Treasury crackdown on a criminal VPN' while the body clarifies OFAC sanctioned it after European law enforcement had already shut it down, a sequencing detail the dek obscures",{"id":35,"reviewer":26,"round":36,"reason":37,"status":29},"editor-r3",3,"The dek still frames this as a 'Treasury crackdown on a criminal VPN' which obscures the key irony — the sanction's collateral damage hit Telegram, not 1VPNS — rewrite the dek to lead with the collateral damage angle (e.g. 'A Treasury sanction targeting a cybercriminal VPN accidentally pulled Telegram's t.me domain from global DNS for 19 hours').","security",[40,41,42,38],"telegram","sanctions","dns",[44],{"name":45,"url":46},"TechRadar","https:\u002F\u002Fwww.techradar.com\u002Fvpn\u002Fvpn-privacy-security\u002Fus-sanctions-on-rogue-vpn-accidentally-break-telegrams-short-links-worldwide",0,{"sections":49},[50,55,59,64,69,74,79,84,89,94,99,104,109,114],{"name":51,"slug":52,"count":53,"latest_published_at":54},"AI","ai",2601,"2026-07-17T17:00:27.000Z",{"name":56,"slug":38,"count":57,"latest_published_at":58},"Security",314,"2026-07-17T18:44:13.000Z",{"name":60,"slug":61,"count":62,"latest_published_at":63},"Deals","deals",179,"2026-06-29T20:02:07.000Z",{"name":65,"slug":66,"count":67,"latest_published_at":68},"Policy","policy",167,"2026-07-17T14:53:59.000Z",{"name":70,"slug":71,"count":72,"latest_published_at":73},"Hardware","hardware",126,"2026-07-16T20:09:48.000Z",{"name":75,"slug":76,"count":77,"latest_published_at":78},"Consumer Tech","consumer-tech",94,"2026-07-16T16:29:46.000Z",{"name":80,"slug":81,"count":82,"latest_published_at":83},"Software","software",72,"2026-07-17T09:42:05.000Z",{"name":85,"slug":86,"count":87,"latest_published_at":88},"Science","science",66,"2026-07-10T10:29:37.000Z",{"name":90,"slug":91,"count":92,"latest_published_at":93},"Dev Tools","dev-tools",60,"2026-07-16T16:59:13.000Z",{"name":95,"slug":96,"count":97,"latest_published_at":98},"Startups","startups",42,"2026-07-16T16:30:35.000Z",{"name":100,"slug":101,"count":102,"latest_published_at":103},"Gaming","gaming",41,"2026-07-09T04:00:00.000Z",{"name":105,"slug":106,"count":107,"latest_published_at":108},"General","general",29,"2026-07-10T22:28:58.000Z",{"name":110,"slug":111,"count":112,"latest_published_at":113},"Reviews","reviews",20,"2026-06-24T12:00:01.000Z",{"name":115,"slug":116,"count":117,"latest_published_at":118},"How-To","how-to",6,"2026-06-16T09:00:00.000Z"]