When submarine cables fail, will telegram.org still work?

Will not work

Domestic direct connections (O)
0

Domestic cloud services (?)
0

Foreign connections (X)
1

When submarine cables fail, can telegram.org still load normally?

Based on the latest test, under a submarine-cable outage scenario telegram.org may “not work.” If international connectivity is cut or blocked, the site may fail to load.

Why might telegram.org “not work” when submarine cables fail?

During testing, when the homepage loaded we found that some content or resources had to be fetched from outside the country. Those resources usually load fine, but when cables are cut or traffic is severely congested those connections can fail—and the site may break along with them.

Does this mean telegram.org will definitely be unavailable during severe cable congestion?

Not necessarily. This result is inferred from resource dependencies observed while loading the homepage. It reflects higher risk—not a guarantee that every page or every feature would fail completely.

How is resilience for telegram.org under cable outages assessed?

When opening the homepage of telegram.org, we observed 31 requests across 1 domains.
If any involve connections abroad, the outcome is classified as “Will not work.” If there are no foreign connections but there is reliance on in-country nodes of multinational cloud services, the outcome is “Uncertain.” If connections are only domestic aside from that international-cloud pattern, the outcome is “May work.”
For detailed rules and the full workflow, see the research methodology and overall report.

Site location

  • Foreign / OtherAS62041 Telegram Messenger Inc149.154.167.99

Test parameters

Test environment

  • IP: 220.132.212.194
  • City: Banqiao
  • Region: Taipei
  • Country: TW
  • Organization: AS3462 Data Communication Business Group
  • DNS server: 168.95.1.1

View on GitHub

{
  "url": "https://telegram.org",
  "canonicalURL": "https://telegram.org",
  "httpStatus": 200,
  "timestamp": "2026-07-20T19:27:08.917Z",
  "testParameters": {
    "customDNS": "168.95.1.1",
    "useAdblock": true,
    "adblockUrls": [
      "https://filter.futa.gg/hosts_abp.txt",
      "https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_15_DnsFilter/filter.txt"
    ],
    "useCache": true,
    "hasIPinfoToken": true
  },
  "testingEnvironment": {
    "ip": "220.132.212.194",
    "hostname": "220-132-212-194.hinet-ip.hinet.net",
    "city": "Banqiao",
    "region": "Taipei",
    "country": "TW",
    "loc": "25.0143,121.4672",
    "org": "AS3462 Data Communication Business Group",
    "timezone": "Asia/Taipei",
    "source": "ipinfo json api (direct)",
    "dnsServer": "168.95.1.1"
  },
  "requestCount": 31,
  "uniqueDomains": 1,
  "test_results": {
    "domestic": {
      "cloud": 0,
      "direct": 0
    },
    "foreign": {
      "cloud": 0,
      "direct": 1
    }
  },
  "domainDetails": [
    {
      "originalUrl": "https://telegram.org/",
      "type": "document",
      "ipinfo": {
        "domain": "telegram.org",
        "ip": "149.154.167.99",
        "city": "Amsterdam",
        "region": "North Holland",
        "country": "NL",
        "loc": "52.3740,4.8897",
        "org": "AS62041 Telegram Messenger Inc",
        "timezone": "Europe/Amsterdam"
      },
      "category": "foreign/direct"
    }
  ]
}

Last tested: 7/21/2026, 3:27:08 AM (HTTP 200)

{{ t('search.noResults', { query: searchQuery }) }}

You can browse the dataset of tested sites and run a manual test with this tool.