by HonkWatch

Is Linode down in Bhutan?

Linode has problems

Bhutan No reports in the last hour checked 2 min ago
Partial outage reported by Linode Open incident: Connectivity Issue between ID-CGK (Jakarta) and SG-SIN-2 (Singapore 2). Going on for 4 d 12 h. Updated 6 Nov, 21:35 UTC, 2 min ago · Official status page
Report a problemFollow community reports
Change country

Reports from people in Bhutan

Last 24 hours · Bhutan · times in UTC

0 reports

No community reports in the last 24 hours from Bhutan. Having trouble? Add your report.

024 00:0006:0012:0018:00

Bars: reports every 15 minutes. Reports alone do not confirm an outage; a flat chart does not prove everything works.

Report totals as of 6 Nov, 21:37 UTC

Report a problem with Linode

Having trouble? Tap what isn't working. No account needed.

What isn't working?

Anonymous · one report per service per hour. This adds your experience to the chart, without contacting the provider or subscribing you to alerts.

Compare worldwide reports · Other services in Bhutan

Monitor the provider status with HonkWatch

Get monitoring alerts for Linode

HonkWatch watches the Linode status page for you and alerts you by email, Slack, Discord or Telegram when it reports a problem.

Free account required. Linode is selected on the next page. Review the monitor and choose where alerts go. Community reports do not trigger these monitoring alerts.

Start free Log in

Where this status comes from

Provider updates and website checks — Worldwide

The evidence below covers the provider and our available checks. It is not a separate verdict for Bhutan. The report chart above is filtered to Bhutan.

Our own checks of linode.com

Every 5 minutes, from our probes

Our checks from 35 cities: all fine.

Dallas: loaded in 3800 ms Madrid: loaded in 5635 ms Osaka: loaded in 6644 ms Hamina: loaded in 4553 ms Delhi: loaded in 3940 ms Seoul: loaded in 5565 ms Frankfurt: loaded in 5373 ms Hong Kong: loaded in 3707 ms Singapore: loaded in 3614 ms Amsterdam: loaded in 4095 ms Seattle: loaded in 4855 ms Querétaro: loaded in 5701 ms Mumbai: loaded in 3130 ms Jakarta: loaded in 5646 ms Cape Town: loaded in 4613 ms Tokyo: loaded in 4807 ms Atlanta: loaded in 3774 ms Port Louis: loaded in 7043 ms London: loaded in 6101 ms Lauterbourg: loaded in 2703 ms Warsaw: loaded in 3314 ms Sydney: loaded in 2805 ms New Jersey: loaded in 3463 ms Bangalore: loaded in 3168 ms Tel Aviv: loaded in 4269 ms Melbourne: loaded in 2751 ms St. Louis: loaded in 5211 ms Los Angeles: loaded in 3882 ms São Paulo: loaded in 6340 ms Doha: loaded in 6561 ms Johannesburg: loaded in 6251 ms New York: loaded in 3377 ms Portsmouth: loaded in 2204 ms Santiago: loaded in 6546 ms Toronto: loaded in 3259 ms
  • DallasReachable3800 ms, just now
  • MadridReachable5635 ms, just now
  • OsakaReachable6644 ms, just now
  • HaminaReachable4553 ms, just now
  • DelhiReachable3940 ms, 1 min ago
  • SeoulReachable5565 ms, 1 min ago
  • FrankfurtReachable5373 ms, 1 min ago
  • Hong KongReachable3707 ms, 1 min ago
  • SingaporeReachable3614 ms, 1 min ago
  • AmsterdamReachable4095 ms, 1 min ago
  • SeattleReachable4855 ms, 1 min ago
  • QuerétaroReachable5701 ms, 1 min ago
  • MumbaiReachable3130 ms, 1 min ago
  • JakartaReachable5646 ms, 1 min ago
  • Cape TownReachable4613 ms, 1 min ago
  • TokyoReachable4807 ms, 2 min ago
  • AtlantaReachable3774 ms, 2 min ago
  • Port LouisReachable7043 ms, 2 min ago
  • LondonReachable6101 ms, 2 min ago
  • LauterbourgReachable2703 ms, 2 min ago
  • WarsawReachable3314 ms, 2 min ago
  • SydneyReachable2805 ms, 2 min ago
  • New JerseyReachable3463 ms, 2 min ago
  • BangaloreReachable3168 ms, 2 min ago
  • Tel AvivReachable4269 ms, 2 min ago
  • MelbourneReachable2751 ms, 2 min ago
  • St. LouisReachable5211 ms, 2 min ago
  • Los AngelesReachable3882 ms, 2 min ago
  • São PauloReachable6340 ms, 2 min ago
  • DohaReachable6561 ms, 2 min ago
  • JohannesburgReachable6251 ms, 2 min ago
  • New YorkReachable3377 ms, 3 min ago
  • PortsmouthReachable2204 ms, 3 min ago
  • SantiagoReachable6546 ms, 3 min ago
  • TorontoReachable3259 ms, 3 min ago

This is separate from the status page: we request linode.com and note whether it answers. These automated checks do not sign in or use the app's features.

Parts of Linode

Linode

All 242 listed parts are working.

Incidents and maintenance

Open incidents

  • Customer Security Advisory: CVE-2026-98432 (investigating) Since 30 Oct, 18:10 UTC · Details
  • Connectivity Issue between ID-CGK (Jakarta) and SG-SIN-2 (Singapore 2) (monitoring) Since 25 Oct, 13:54 UTC. Affects ID-CGK (Jakarta), SG-SIN-2 (Singapore 2) · Details
  • Service Issue - Block Storage (BR-GRU) (monitoring) Since 28 Oct, 20:17 UTC. Affects BR-GRU (São Paulo) Block Storage · Details
  • Customer Security Advisory: Critical F5/NGINX Out-of-Band Vulnerabilities (investigating) Since 22 Oct, 20:08 UTC · Details
Outage history

Last 9030 days

0.00% of the time without a reported outage, since 2 Nov

Of the last 90 days, 5 had a partial or major outage, 0 had maintenance only and 85 have no data. Recent problems are listed in a table further down.

90 days ago30 days agoToday

No problems Partial outage Major outage Maintenance No data yet

Last 24 hours

Every 15 minutes, hours in UTC

Bars: the share of our own checks of linode.com that failed (9,647 checks). Shaded: when Linode's status page reported a problem. Community reports appear separately above, alongside our checks and provider updates.

0%5%10% 00:0006:0012:0018:00 0% of 102 checks failed3% of 116 checks failed1% of 105 checks failed0% of 108 checks failed0% of 103 checks failed0% of 99 checks failed1% of 104 checks failed0% of 114 checks failed0% of 107 checks failed0% of 105 checks failed0% of 104 checks failed1% of 109 checks failed0% of 106 checks failed0% of 103 checks failed0% of 105 checks failed0% of 105 checks failed1% of 106 checks failed1% of 107 checks failed0% of 106 checks failed0% of 104 checks failed2% of 109 checks failed0% of 106 checks failed4% of 113 checks failed0% of 104 checks failed2% of 107 checks failed0% of 106 checks failed0% of 105 checks failed0% of 104 checks failed0% of 104 checks failed1% of 108 checks failed0% of 107 checks failed0% of 106 checks failed0% of 103 checks failed0% of 107 checks failed1% of 106 checks failed0% of 105 checks failed0% of 105 checks failed0% of 102 checks failed0% of 107 checks failed0% of 105 checks failed0% of 100 checks failed0% of 112 checks failed0% of 103 checks failed0% of 107 checks failed0% of 103 checks failed0% of 104 checks failed1% of 100 checks failed0% of 102 checks failed0% of 99 checks failed0% of 104 checks failed0% of 94 checks failed0% of 99 checks failed0% of 105 checks failed1% of 88 checks failed0% of 81 checks failed0% of 103 checks failed10% of 102 checks failed1% of 105 checks failed1% of 99 checks failed0% of 98 checks failed1% of 84 checks failed3% of 86 checks failed0% of 96 checks failed0% of 90 checks failed0% of 83 checks failed0% of 101 checks failed0% of 110 checks failed0% of 93 checks failed7% of 105 checks failed2% of 88 checks failed3% of 74 checks failed0% of 105 checks failed0% of 81 checks failed2% of 97 checks failed2% of 87 checks failed1% of 99 checks failed4% of 113 checks failed2% of 104 checks failed4% of 95 checks failed0% of 104 checks failed0% of 102 checks failed0% of 87 checks failed1% of 91 checks failed0% of 112 checks failed3% of 91 checks failed0% of 88 checks failed0% of 105 checks failed0% of 96 checks failed0% of 88 checks failed0% of 101 checks failed0% of 107 checks failed1% of 106 checks failed0% of 108 checks failed0% of 87 checks failed1% of 105 checks failed0% of 33 checks failed

Recent problems

2 Nov, 09:02 UTCPartial outagegoing on, 4 d 12 hOpen incident: Connectivity Issue between ID-CGK (Jakarta) and SG-SIN-2 (Singapore 2)
What can I try?

Having trouble with Linode?

  1. Compare reports from Bhutan and check the latest update above. A quiet chart does not rule out a new or local problem.
  2. Try the service on another device or switch between WiFi and mobile data, if available. If other sites also fail, check your internet provider.
  3. Report a problem with the feature that is failing and the country where you are affected. Submit once; your report appears in the chart.

Reports describe people's experiences. One report alone does not confirm an outage.

Questions about these results

Questions

Is Linode down, or is it just me?

Linode itself reports a problem right now, so it is probably not just you.

How do we know?

We read the official Linode status page and load linode.com from our own probes in several cities. People can also report problems here. Their reports appear separately and may reveal issues before a provider update.

How often do we check?

The status page every 2.5 minutes, day and night, and the website every 5 minutes. We keep 90 days of history: a day we have no reading for shows as "no data yet", never as working.

More in Cloud and hosting

See the live outage feed for Bhutan · Find another service