by HonkWatch

Is Linode down in Rwanda?

Linode has problems

Rwanda 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 7 h. Updated 6 Nov, 16:50 UTC, 2 min ago · Official status page
Report a problemFollow community reports
Change country

Reports from people in Rwanda

Last 24 hours · Rwanda · times in UTC

0 reports

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

024 18:0000:0006:0012: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, 16:51 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 Rwanda

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

Our own checks of linode.com

Every 5 minutes, from our probes

2 of 35 cities can't reach linode.com.

Osaka: loaded in 6507 ms Cape Town: loaded in 4100 ms Sydney: loaded in 5708 ms Hong Kong: loaded in 3719 ms Lauterbourg: loaded in 6084 ms Port Louis: loaded in 6224 ms Seoul: loaded in 4742 ms Melbourne: loaded in 4829 ms Hamina: loaded in 6456 ms Mumbai: loaded in 6817 ms Amsterdam: loaded in 6398 ms Atlanta: loaded in 5340 ms Tel Aviv: loaded in 6190 ms Toronto: loaded in 4594 ms Johannesburg: loaded in 4422 ms Los Angeles: loaded in 5087 ms Singapore: loaded in 6725 ms Jakarta: loaded in 5744 ms London: loaded in 4860 ms Tokyo: loaded in 5402 ms Madrid: loaded in 5427 ms Querétaro: loaded in 5901 ms New Jersey: loaded in 6855 ms Dallas: loaded in 5205 ms São Paulo: loaded in 4986 ms Delhi: loaded in 3004 ms Portsmouth: loaded in 5424 ms Bangalore: loaded in 6168 ms New York: loaded in 3370 ms Frankfurt: loaded in 3449 ms Seattle: loaded in 4490 ms Doha: loaded in 2560 ms Warsaw: loaded in 6192 ms St. Louis: could not load it (TimeoutError: Check took longer than 10 s) Santiago: could not load it (TimeoutError: Check took longer than 10 s)
  • OsakaReachable6507 ms, just now
  • Cape TownReachable4100 ms, just now
  • SydneyReachable5708 ms, just now
  • Hong KongReachable3719 ms, just now
  • LauterbourgReachable6084 ms, just now
  • Port LouisReachable6224 ms, just now
  • SeoulReachable4742 ms, 2 min ago
  • MelbourneReachable4829 ms, 3 min ago
  • HaminaReachable6456 ms, 3 min ago
  • MumbaiReachable6817 ms, 3 min ago
  • AmsterdamReachable6398 ms, 4 min ago
  • AtlantaReachable5340 ms, 4 min ago
  • Tel AvivReachable6190 ms, 4 min ago
  • TorontoReachable4594 ms, 5 min ago
  • JohannesburgReachable4422 ms, 5 min ago
  • Los AngelesReachable5087 ms, 5 min ago
  • SingaporeReachable6725 ms, 5 min ago
  • St. LouisNo answer within 10 s9996 ms, 5 min ago
  • JakartaReachable5744 ms, 5 min ago
  • LondonReachable4860 ms, 5 min ago
  • SantiagoNo answer within 10 s10000 ms, 5 min ago
  • TokyoReachable5402 ms, 5 min ago
  • MadridReachable5427 ms, 6 min ago
  • QuerétaroReachable5901 ms, 6 min ago
  • New JerseyReachable6855 ms, 6 min ago
  • DallasReachable5205 ms, 6 min ago
  • São PauloReachable4986 ms, 6 min ago
  • DelhiReachable3004 ms, 6 min ago
  • PortsmouthReachable5424 ms, 6 min ago
  • BangaloreReachable6168 ms, 6 min ago
  • New YorkReachable3370 ms, 6 min ago
  • FrankfurtReachable3449 ms, 7 min ago
  • SeattleReachable4490 ms, 7 min ago
  • DohaReachable2560 ms, 7 min ago
  • WarsawReachable6192 ms, 7 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,695 checks). Shaded: when Linode's status page reported a problem. Community reports appear separately above, alongside our checks and provider updates.

0%7%14% 18:0000:0006:0012:00 0% of 97 checks failed0% of 113 checks failed1% of 106 checks failed0% of 105 checks failed0% of 92 checks failed0% of 101 checks failed1% of 109 checks failed0% of 97 checks failed0% of 100 checks failed0% of 104 checks failed1% of 92 checks failed0% of 102 checks failed0% of 95 checks failed0% of 101 checks failed0% of 110 checks failed0% of 106 checks failed0% of 104 checks failed0% of 105 checks failed0% of 104 checks failed0% 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 failed14% of 28 checks failed

Recent problems

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