by HonkWatch

Is Linode down in Nepal?

Linode has problems

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

Reports from people in Nepal

Last 24 hours · Nepal · times in UTC

0 reports

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

024 12:0018:0000:0006: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 7 Nov, 06:24 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 Nepal

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 Nepal. The report chart above is filtered to Nepal.

Our own checks of linode.com

Every 5 minutes, from our probes

Our checks from 35 cities: all fine.

Sydney: loaded in 5247 ms Singapore: loaded in 4314 ms Amsterdam: loaded in 4072 ms Querétaro: loaded in 2552 ms Jakarta: loaded in 3100 ms Mumbai: loaded in 4133 ms Cape Town: loaded in 5505 ms Bangalore: loaded in 6274 ms Atlanta: loaded in 4111 ms Los Angeles: loaded in 6234 ms Tokyo: loaded in 5144 ms London: loaded in 2139 ms New Jersey: loaded in 6246 ms Warsaw: loaded in 6048 ms Dallas: loaded in 5678 ms Tel Aviv: loaded in 4960 ms Doha: loaded in 3562 ms St. Louis: loaded in 4342 ms Melbourne: loaded in 3433 ms Osaka: loaded in 4085 ms Madrid: loaded in 4141 ms Hamina: loaded in 3283 ms Delhi: loaded in 2561 ms Seoul: loaded in 4256 ms Johannesburg: loaded in 4495 ms New York: loaded in 4189 ms Frankfurt: loaded in 4048 ms Portsmouth: loaded in 4135 ms Hong Kong: loaded in 2307 ms São Paulo: loaded in 2081 ms Port Louis: loaded in 6321 ms Seattle: loaded in 4724 ms Santiago: loaded in 4130 ms Toronto: loaded in 6234 ms Lauterbourg: loaded in 5463 ms
  • SydneyReachable5247 ms, just now
  • SingaporeReachable4314 ms, 3 min ago
  • AmsterdamReachable4072 ms, 3 min ago
  • QuerétaroReachable2552 ms, 3 min ago
  • JakartaReachable3100 ms, 3 min ago
  • MumbaiReachable4133 ms, 3 min ago
  • Cape TownReachable5505 ms, 3 min ago
  • BangaloreReachable6274 ms, 3 min ago
  • AtlantaReachable4111 ms, 4 min ago
  • Los AngelesReachable6234 ms, 4 min ago
  • TokyoReachable5144 ms, 4 min ago
  • LondonReachable2139 ms, 4 min ago
  • New JerseyReachable6246 ms, 4 min ago
  • WarsawReachable6048 ms, 4 min ago
  • DallasReachable5678 ms, 4 min ago
  • Tel AvivReachable4960 ms, 4 min ago
  • DohaReachable3562 ms, 4 min ago
  • St. LouisReachable4342 ms, 4 min ago
  • MelbourneReachable3433 ms, 4 min ago
  • OsakaReachable4085 ms, 4 min ago
  • MadridReachable4141 ms, 4 min ago
  • HaminaReachable3283 ms, 4 min ago
  • DelhiReachable2561 ms, 4 min ago
  • SeoulReachable4256 ms, 5 min ago
  • JohannesburgReachable4495 ms, 5 min ago
  • New YorkReachable4189 ms, 5 min ago
  • FrankfurtReachable4048 ms, 5 min ago
  • PortsmouthReachable4135 ms, 5 min ago
  • Hong KongReachable2307 ms, 5 min ago
  • São PauloReachable2081 ms, 5 min ago
  • Port LouisReachable6321 ms, 5 min ago
  • SeattleReachable4724 ms, 5 min ago
  • SantiagoReachable4130 ms, 5 min ago
  • TorontoReachable6234 ms, 5 min ago
  • LauterbourgReachable5463 ms, 5 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

Maintenance

  • Scheduled maintenance for Block storage switches - AP-West (Mumbai) (planned) 12 Nov, 11:00 UTC to 12 Nov, 15:00 UTC. Affects AP-West (Mumbai), AP-West (Mumbai) Block Storage · Details
  • Scheduled maintenance for Block storage switches - AP-West (Mumbai) (planned) 16 Nov, 11:00 UTC to 16 Nov, 19:00 UTC. Affects AP-West (Mumbai) · Details
Outage history

Last 9030 days

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

Of the last 90 days, 6 had a partial or major outage, 0 had maintenance only and 84 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,645 checks). Shaded: when Linode's status page reported a problem. Community reports appear separately above, alongside our checks and provider updates.

0%5%10% 12:0018:0000:0006:00 0% 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 117 checks failed0% of 93 checks failed0% of 106 checks failed0% of 95 checks failed1% of 118 checks failed1% of 106 checks failed0% of 106 checks failed0% of 105 checks failed0% of 106 checks failed0% of 106 checks failed0% of 102 checks failed0% of 105 checks failed0% of 107 checks failed0% of 104 checks failed0% of 104 checks failed0% of 106 checks failed0% of 107 checks failed1% of 107 checks failed0% of 106 checks failed0% of 104 checks failed0% of 105 checks failed0% of 105 checks failed0% of 106 checks failed0% of 104 checks failed0% of 104 checks failed0% of 104 checks failed0% of 106 checks failed0% of 106 checks failed0% of 104 checks failed0% of 107 checks failed0% of 103 checks failed0% of 107 checks failed1% of 105 checks failed0% of 107 checks failed0% of 103 checks failed0% of 58 checks failed

Recent problems

2 Nov, 09:02 UTCPartial outagegoing on, 4 d 21 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 Nepal 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 Nepal · Find another service