by HonkWatch

Is Linode down in São Tomé and Príncipe?

Linode has problems

São Tomé and Príncipe 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 7 h. Updated 6 Nov, 16:39 UTC, just now · Official status page
Report a problemFollow community reports
Change country

Reports from people in São Tomé and Príncipe

Last 24 hours · São Tomé and Príncipe · times in UTC

0 reports

No community reports in the last 24 hours from São Tomé and Príncipe. 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:39 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 São Tomé and Príncipe

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 São Tomé and Príncipe. The report chart above is filtered to São Tomé and Príncipe.

Our own checks of linode.com

Every 5 minutes, from our probes

Our checks from 34 cities: all fine.

Hamina: loaded in 4545 ms Warsaw: loaded in 5340 ms Cape Town: loaded in 3815 ms Sydney: loaded in 2797 ms Frankfurt: loaded in 4445 ms Amsterdam: loaded in 4657 ms Lauterbourg: loaded in 3549 ms Tel Aviv: loaded in 6387 ms São Paulo: loaded in 2412 ms Los Angeles: loaded in 5092 ms Tokyo: loaded in 5073 ms Doha: loaded in 4520 ms Atlanta: loaded in 5341 ms Jakarta: loaded in 4663 ms London: loaded in 5158 ms Seattle: loaded in 4656 ms Dallas: loaded in 4016 ms Singapore: loaded in 4766 ms New York: loaded in 5304 ms Port Louis: loaded in 5087 ms New Jersey: loaded in 3502 ms Osaka: loaded in 6288 ms St. Louis: loaded in 5522 ms Mumbai: loaded in 2496 ms Santiago: loaded in 6449 ms Portsmouth: loaded in 2162 ms Madrid: loaded in 2358 ms Johannesburg: loaded in 4422 ms Hong Kong: loaded in 5597 ms Melbourne: loaded in 6696 ms Querétaro: loaded in 5754 ms Seoul: loaded in 4750 ms Bangalore: loaded in 3707 ms Toronto: loaded in 2247 ms
  • HaminaReachable4545 ms, just now
  • WarsawReachable5340 ms, 1 min ago
  • Cape TownReachable3815 ms, 1 min ago
  • SydneyReachable2797 ms, 1 min ago
  • FrankfurtReachable4445 ms, 1 min ago
  • AmsterdamReachable4657 ms, 1 min ago
  • LauterbourgReachable3549 ms, 2 min ago
  • Tel AvivReachable6387 ms, 2 min ago
  • São PauloReachable2412 ms, 2 min ago
  • Los AngelesReachable5092 ms, 2 min ago
  • TokyoReachable5073 ms, 2 min ago
  • DohaReachable4520 ms, 2 min ago
  • AtlantaReachable5341 ms, 2 min ago
  • JakartaReachable4663 ms, 2 min ago
  • LondonReachable5158 ms, 2 min ago
  • SeattleReachable4656 ms, 2 min ago
  • DallasReachable4016 ms, 2 min ago
  • SingaporeReachable4766 ms, 2 min ago
  • New YorkReachable5304 ms, 2 min ago
  • Port LouisReachable5087 ms, 2 min ago
  • New JerseyReachable3502 ms, 2 min ago
  • OsakaReachable6288 ms, 2 min ago
  • St. LouisReachable5522 ms, 2 min ago
  • MumbaiReachable2496 ms, 2 min ago
  • SantiagoReachable6449 ms, 4 min ago
  • PortsmouthReachable2162 ms, 4 min ago
  • MadridReachable2358 ms, 4 min ago
  • JohannesburgReachable4422 ms, 4 min ago
  • Hong KongReachable5597 ms, 5 min ago
  • MelbourneReachable6696 ms, 6 min ago
  • QuerétaroReachable5754 ms, 7 min ago
  • SeoulReachable4750 ms, 8 min ago
  • BangaloreReachable3707 ms, 8 min ago
  • TorontoReachable2247 ms, 10 min ago
  • DelhiReachable4074 ms, 20 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,754 checks). Shaded: when Linode's status page reported a problem. Community reports appear separately above, alongside our checks and provider updates.

0%5%10% 18:0000:0006:0012:00 0% of 117 checks failed0% 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 69 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 São Tomé and Príncipe 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 São Tomé and Príncipe · Find another service