← HonkWatch.com

Is Linode down in Fr. S. Antarctic Lands?

Linode has problems

People in Fr. S. Antarctic Lands: 0 reports in the last hour Official page: Partial outage reported, checked 1 min ago Our checks: loads from 35 of 35 places

1 open incident: Connectivity Issue between ID-CGK (Jakarta) and SG-SIN-2 (Singapore 2)3 notices

Partial outage reported by Linode Open incident: Connectivity Issue between ID-CGK (Jakarta) and SG-SIN-2 (Singapore 2). Going on for 5 d 11 h. Updated 7 Nov, 20:26 UTC, 1 min ago · Official status page
Report a problem
Change country

Known issues (from Linode's status page)

Incidents

  • Customer Security Advisory: CVE-2026-98432 (investigating) Since 30 Oct, 18:10 UTC · Details Latest update (2 Nov, 10:55 UTC): While we continue to deploy kernel patches across our infrastructure, we have also deployed network rules that drop IPv4 packets with optional headers on public and VPC interfaces. This eliminates the immediate remote attack vector and protects our infrastructure as well as customer workloads withou
  • Connectivity Issue between ID-CGK (Jakarta) and SG-SIN-2 (Singapore 2) (monitoring, minor impact) Since 25 Oct, 13:54 UTC. Affects ID-CGK (Jakarta), SG-SIN-2 (Singapore 2) · Details Latest update (29 Oct, 09:16 UTC): We will continue to monitor to ensure that the impact has been fully mitigated. Further updates will be provided as we make progress.
  • Service Issue - Block Storage (BR-GRU) (monitoring) Since 28 Oct, 20:17 UTC. Affects BR-GRU (São Paulo) Block Storage · Details Latest update (28 Oct, 20:18 UTC): A fix has been implemented and we are monitoring the results.
Show 1 more incident
  • Customer Security Advisory: Critical F5/NGINX Out-of-Band Vulnerabilities (investigating) Since 22 Oct, 20:08 UTC · Details Latest update (22 Oct, 20:08 UTC): Akamai is aware of the recently published F5/NGINX vulnerabilities (CVE-2026-15176, CVE-2026-97205, and CVE-2026-93479), and our teams are actively investigating their potential impact across our platform and infrastructure. F5 has released out-of-band security patches addressing three critical seve

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 Latest update (7 Nov, 00:54 UTC): We will be performing maintenance on our Block Storage switches in Mumbai on Thursday, November 12th at 11:00 UTC for a duration of 4 hours. Because of our redundant switching infrastructure, we do not expect any downtime during this maintenance. However, a brief period of packet loss or increased l
  • 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 Latest update (7 Nov, 00:56 UTC): We will be performing maintenance on our Block Storage switches in Mumbai on Thursday, November 16th at 11:00 UTC for a duration of 8 hours. Because of our redundant switching infrastructure, we do not expect any downtime during this maintenance. However, a brief period of packet loss or increased l

In Linode's own words, as we read them every 2.5 minutes, last 1 min ago. Read Linode's status page

Reports from people in Fr. S. Antarctic Lands

Last 24 hours · Fr. S. Antarctic Lands · times in UTC

0 reports

No community reports in the last 24 hours from Fr. S. Antarctic Lands. Having trouble? Add your report.

Status page: partial outage, 2 Nov, 09:02 to now 024 00:0006:0012:0018:00 20:30-20:35 UTC: 35 of 35 places loaded it, typical 4284 ms20:35-20:40 UTC: 33 of 33 places loaded it, typical 4543 ms20:40-20:45 UTC: 34 of 34 places loaded it, typical 4534 ms20:45-20:55 UTC: 35 of 35 places loaded it, typical 5219 to 5289 ms20:55-21:00 UTC: 34 of 34 places loaded it, typical 4531 ms21:00-21:05 UTC: 18 of 18 places loaded it, typical 4446 ms21:05-21:10 UTC: 30 of 30 places loaded it, typical 4560 ms21:10-21:20 UTC: 32 of 32 places loaded it, typical 4311 to 4564 ms21:20-21:25 UTC: 33 of 33 places loaded it, typical 4563 ms21:25-21:30 UTC: 29 of 29 places loaded it, typical 4618 ms21:30-21:35 UTC: 33 of 33 places loaded it, typical 5075 ms21:35-21:45 UTC: 35 of 35 places loaded it, typical 3882 to 4202 ms21:45-21:50 UTC: 25 of 25 places loaded it, typical 4684 ms21:50-21:55 UTC: 24 of 24 places loaded it, typical 4840 ms21:55-22:00 UTC: 33 of 33 places loaded it, typical 4403 ms22:00-22:05 UTC: 35 of 35 places loaded it, typical 4553 ms22:05-22:10 UTC: 28 of 28 places loaded it, typical 4775 ms22:10-22:20 UTC: 35 of 35 places loaded it, typical 4296 to 4686 ms22:20-22:25 UTC: 34 of 34 places loaded it, typical 4535 ms22:25-22:30 UTC: 25 of 25 places loaded it, typical 4336 ms22:30-22:35 UTC: 35 of 35 places loaded it, typical 4360 ms22:35-22:40 UTC: 34 of 34 places loaded it, typical 4465 ms22:40-22:50 UTC: 35 of 35 places loaded it, typical 4459 to 4700 ms22:50-22:55 UTC: 33 of 33 places loaded it, typical 4337 ms22:55-23:10 UTC: 35 of 35 places loaded it, typical 4643 to 4958 ms23:10-23:15 UTC: 33 of 33 places loaded it, typical 4604 ms23:15-23:20 UTC: 34 of 34 places loaded it, typical 4366 ms23:20-23:25 UTC: 35 of 35 places loaded it, typical 4543 ms23:25-23:30 UTC: 34 of 34 places loaded it, typical 4496 ms23:30-23:35 UTC: 35 of 35 places loaded it, typical 4234 ms23:35-23:40 UTC: 34 of 34 places loaded it, typical 4637 ms23:40-23:45 UTC: 35 of 35 places loaded it, typical 4705 ms23:45-23:55 UTC: 34 of 34 places loaded it, typical 4506 to 4611 ms23:55-00:00 UTC: 35 of 35 places loaded it, typical 3997 ms00:00-00:05 UTC: 33 of 33 places loaded it, typical 4586 ms00:05-00:10 UTC: 34 of 34 places loaded it, typical 5268 ms00:10-00:25 UTC: 35 of 35 places loaded it, typical 4341 to 4865 ms00:25-00:30 UTC: 34 of 34 places loaded it, typical 4650 ms00:30-00:35 UTC: 35 of 35 places loaded it, typical 4639 ms00:35-00:40 UTC: 34 of 34 places loaded it, typical 4712 ms00:40-00:45 UTC: 35 of 35 places loaded it, typical 5391 ms00:45-00:50 UTC: 34 of 34 places loaded it, typical 4872 ms00:50-01:05 UTC: 35 of 35 places loaded it, typical 4439 to 5148 ms01:05-01:10 UTC: 34 of 34 places loaded it, typical 4753 ms01:10-01:45 UTC: 35 of 35 places loaded it, typical 4468 to 5441 ms01:45-01:50 UTC: 33 of 33 places loaded it, typical 4361 ms01:50-02:05 UTC: 35 of 35 places loaded it, typical 4686 to 4886 ms02:05-02:10 UTC: 34 of 34 places loaded it, typical 4731 ms02:10-02:15 UTC: 35 of 35 places loaded it, typical 4555 ms02:15-02:20 UTC: 34 of 34 places loaded it, typical 4702 ms02:20-02:25 UTC: 35 of 35 places loaded it, typical 5234 ms02:25-02:35 UTC: 34 of 34 places loaded it, typical 4266 to 4400 ms02:35-02:55 UTC: 35 of 35 places loaded it, typical 4096 to 5093 ms02:55-03:05 UTC: 34 of 34 places loaded it, typical 4088 to 4414 ms03:05-03:15 UTC: 35 of 35 places loaded it, typical 4097 to 4546 ms03:15-03:25 UTC: 34 of 34 places loaded it, typical 4252 to 4419 ms03:25-03:30 UTC: 35 of 35 places loaded it, typical 4459 ms03:30-03:35 UTC: 33 of 33 places loaded it, typical 4424 ms03:35-03:45 UTC: 35 of 35 places loaded it, typical 4051 to 4180 ms03:45-03:50 UTC: 34 of 34 places loaded it, typical 4736 ms03:50-03:55 UTC: 35 of 35 places loaded it, typical 4544 ms03:55-04:00 UTC: 34 of 34 places loaded it, typical 4264 ms04:00-04:05 UTC: 35 of 35 places loaded it, typical 4672 ms04:05-04:10 UTC: 34 of 34 places loaded it, typical 4185 ms04:10-04:15 UTC: 35 of 35 places loaded it, typical 4288 ms04:15-04:20 UTC: 34 of 34 places loaded it, typical 4337 ms04:20-04:30 UTC: 35 of 35 places loaded it, typical 4201 to 4202 ms04:30-04:40 UTC: 34 of 34 places loaded it, typical 4232 to 4269 ms04:40-04:50 UTC: 35 of 35 places loaded it, typical 4076 to 4454 ms04:50-04:55 UTC: 34 of 34 places loaded it, typical 4195 ms04:55-05:00 UTC: 35 of 35 places loaded it, typical 4142 ms05:00-05:10 UTC: 34 of 34 places loaded it, typical 4375 to 4669 ms05:10-05:30 UTC: 35 of 35 places loaded it, typical 4218 to 4426 ms05:30-05:45 UTC: 34 of 34 places loaded it, typical 4160 to 4456 ms05:45-05:55 UTC: 35 of 35 places loaded it, typical 4185 to 4458 ms05:55-06:00 UTC: 34 of 34 places loaded it, typical 4278 ms06:00-06:05 UTC: 33 of 33 places loaded it, typical 4697 ms06:05-06:10 UTC: 35 of 35 places loaded it, typical 4050 ms06:10-06:15 UTC: 33 of 33 places loaded it, typical 4548 ms06:15-06:20 UTC: 35 of 35 places loaded it, typical 4130 ms06:20-06:30 UTC: 34 of 34 places loaded it, typical 4152 to 4328 ms06:30-06:35 UTC: 35 of 35 places loaded it, typical 4630 ms06:35-06:40 UTC: 34 of 34 places loaded it, typical 4517 ms06:40-07:05 UTC: 35 of 35 places loaded it, typical 4188 to 4501 ms07:05-07:10 UTC: 33 of 33 places loaded it, typical 4226 ms07:10-07:20 UTC: 35 of 35 places loaded it, typical 3800 to 4204 ms07:20-07:25 UTC: 34 of 34 places loaded it, typical 4234 ms07:25-07:30 UTC: 35 of 35 places loaded it, typical 4212 ms07:30-07:35 UTC: 34 of 34 places loaded it, typical 4292 ms07:35-08:00 UTC: 35 of 35 places loaded it, typical 4223 to 4562 ms08:00-08:05 UTC: 34 of 34 places loaded it, typical 4089 ms08:05-08:10 UTC: 35 of 35 places loaded it, typical 5062 ms08:10-08:15 UTC: 34 of 34 places loaded it, typical 4163 ms08:15-08:25 UTC: 35 of 35 places loaded it, typical 4275 to 4382 ms08:25-08:30 UTC: 33 of 33 places loaded it, typical 4238 ms08:30-08:35 UTC: 35 of 35 places loaded it, typical 4230 ms08:35-08:40 UTC: 34 of 34 places loaded it, typical 3875 ms08:40-08:45 UTC: 35 of 35 places loaded it, typical 4200 ms08:45-08:55 UTC: 33 of 33 places loaded it, typical 4214 to 5049 ms08:55-09:05 UTC: 35 of 35 places loaded it, typical 4146 to 4686 ms09:05-09:15 UTC: 34 of 34 places loaded it, typical 4175 to 4401 ms09:15-09:20 UTC: 31 of 31 places loaded it, typical 5049 ms09:20-09:25 UTC: 35 of 35 places loaded it, typical 4331 ms09:25-09:30 UTC: 34 of 34 places loaded it, typical 4323 ms09:30-09:45 UTC: 35 of 35 places loaded it, typical 4228 to 4765 ms09:45-09:50 UTC: 34 of 34 places loaded it, typical 4298 ms09:50-09:55 UTC: 35 of 35 places loaded it, typical 5062 ms09:55-10:05 UTC: 34 of 34 places loaded it, typical 4106 to 4222 ms10:05-10:10 UTC: 35 of 35 places loaded it, typical 4362 ms10:10-10:15 UTC: 34 of 34 places loaded it, typical 4504 ms10:15-10:20 UTC: 21 of 21 places loaded it, typical 4274 ms10:20-10:30 UTC: 35 of 35 places loaded it, typical 4088 to 4137 ms10:30-10:40 UTC: 34 of 34 places loaded it, typical 4096 to 4690 ms10:40-10:50 UTC: 35 of 35 places loaded it, typical 4722 to 5561 ms10:50-10:55 UTC: 33 of 33 places loaded it, typical 5342 ms10:55-11:00 UTC: 35 of 35 places loaded it, typical 4673 ms11:00-11:05 UTC: 34 of 34 places loaded it, typical 5145 ms11:05-11:20 UTC: 35 of 35 places loaded it, typical 4447 to 4811 ms11:20-11:25 UTC: 33 of 33 places loaded it, typical 4779 ms11:25-11:35 UTC: 35 of 35 places loaded it, typical 4824 to 4881 ms11:35-11:40 UTC: 20 of 20 places loaded it, typical 4799 ms11:40-11:45 UTC: 35 of 35 places loaded it, typical 4496 ms11:45-11:50 UTC: 34 of 34 places loaded it, typical 5018 ms11:50-12:00 UTC: 35 of 35 places loaded it, typical 4516 to 4652 ms12:00-12:10 UTC: 34 of 34 places loaded it, typical 4981 to 5043 ms12:10-12:15 UTC: 35 of 35 places loaded it, typical 4550 ms12:15-12:20 UTC: 33 of 33 places loaded it, typical 4897 ms12:20-12:25 UTC: 35 of 35 places loaded it, typical 5033 ms12:25-12:35 UTC: 34 of 34 places loaded it, typical 4599 to 4956 ms12:35-12:45 UTC: 35 of 35 places loaded it, typical 4854 to 5067 ms12:45-12:50 UTC: 34 of 34 places loaded it, typical 4752 ms12:50-12:55 UTC: 35 of 35 places loaded it, typical 4699 ms12:55-13:00 UTC: 34 of 34 places loaded it, typical 4760 ms13:00-13:05 UTC: 35 of 35 places loaded it, typical 4934 ms13:05-13:10 UTC: 34 of 34 places loaded it, typical 5270 ms13:10-13:15 UTC: 35 of 35 places loaded it, typical 5059 ms13:15-13:20 UTC: 34 of 34 places loaded it, typical 4857 ms13:20-13:30 UTC: 35 of 35 places loaded it, typical 4744 to 4775 ms13:30-13:35 UTC: 33 of 33 places loaded it, typical 4763 ms13:35-13:40 UTC: 35 of 35 places loaded it, typical 4399 ms13:40-13:50 UTC: 34 of 34 places loaded it, typical 4529 to 4674 ms13:50-14:05 UTC: 35 of 35 places loaded it, typical 4690 to 5035 ms14:05-14:10 UTC: 34 of 34 places loaded it, typical 4969 ms14:10-14:45 UTC: 35 of 35 places loaded it, typical 4348 to 4958 ms14:45-14:55 UTC: 34 of 34 places loaded it, typical 4659 to 4685 ms14:55-15:10 UTC: 35 of 35 places loaded it, typical 4632 to 4942 ms15:10-15:20 UTC: 34 of 34 places loaded it, typical 4230 to 4634 ms15:20-15:35 UTC: 35 of 35 places loaded it, typical 4589 to 4730 ms15:35-15:40 UTC: 34 of 34 places loaded it, typical 4756 ms15:40-16:00 UTC: 35 of 35 places loaded it, typical 4581 to 5451 ms16:00-16:05 UTC: 34 of 34 places loaded it, typical 4506 ms16:05-16:15 UTC: 35 of 35 places loaded it, typical 4497 to 4655 ms16:15-16:20 UTC: 34 of 34 places loaded it, typical 4278 ms16:20-16:40 UTC: 35 of 35 places loaded it, typical 4269 to 4879 ms16:40-16:50 UTC: 34 of 34 places loaded it, typical 4867 to 4877 ms16:50-16:55 UTC: 35 of 35 places loaded it, typical 4937 ms16:55-17:00 UTC: 33 of 33 places loaded it, typical 4592 ms17:00-17:10 UTC: 35 of 35 places loaded it, typical 4228 to 4399 ms17:10-17:15 UTC: 33 of 33 places loaded it, typical 4779 ms17:15-17:20 UTC: 34 of 34 places loaded it, typical 4667 ms17:20-17:30 UTC: 35 of 35 places loaded it, typical 4609 to 5012 ms17:30-17:40 UTC: 34 of 34 places loaded it, typical 4542 to 4786 ms17:40-17:50 UTC: 35 of 35 places loaded it, typical 4293 to 5130 ms17:50-17:55 UTC: 34 of 34 places loaded it, typical 4858 ms17:55-18:05 UTC: 35 of 35 places loaded it, typical 4200 to 4390 ms18:05-18:20 UTC: 34 of 34 places loaded it, typical 4124 to 4740 ms18:20-18:30 UTC: 35 of 35 places loaded it, typical 4331 to 4935 ms18:30-18:35 UTC: 34 of 34 places loaded it, typical 4331 ms18:35-18:50 UTC: 35 of 35 places loaded it, typical 4236 to 4817 ms18:50-19:00 UTC: 34 of 34 places loaded it, typical 4672 to 4760 ms19:00-19:05 UTC: 35 of 35 places loaded it, typical 4469 ms19:05-19:25 UTC: 34 of 34 places loaded it, typical 4397 to 4753 ms19:25-19:30 UTC: 35 of 35 places loaded it, typical 4245 ms19:30-19:35 UTC: 33 of 33 places loaded it, typical 4965 ms19:35-19:40 UTC: 35 of 35 places loaded it, typical 4707 ms19:40-19:45 UTC: 34 of 34 places loaded it, typical 4122 ms19:45-19:50 UTC: 33 of 33 places loaded it, typical 4622 ms19:50-19:55 UTC: 35 of 35 places loaded it, typical 4641 ms19:55-20:00 UTC: 33 of 33 places loaded it, typical 4644 ms20:00-20:05 UTC: 35 of 35 places loaded it, typical 4545 ms20:05-20:10 UTC: 33 of 33 places loaded it, typical 4699 ms20:10-20:15 UTC: 35 of 35 places loaded it, typical 4430 ms20:15-20:20 UTC: 34 of 34 places loaded it, typical 4284 ms20:20-20:25 UTC: 35 of 35 places loaded it, typical 4215 ms20:25-20:30 UTC: 19 of 19 places loaded it, typical 4818 ms Typical response time of the places that loaded it, at most 5561 ms

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

Tinted columns: when Linode's status page showed a partial outage, a major outage, as we read it every 2.5 minutes; the times are when we saw it, not when the provider posted it. Strip under the bars: how many places loaded linode.com in each 5 minutes, of those that checked, and the line under it their typical response time. Any answer from the website counts as loaded, even an error page. Website checks don't test sign-in, payments or every feature. Tinted columns and our checks are worldwide; the bars count reports from Fr. S. Antarctic Lands only.

Latest checks, 20:25-20:30 UTC: 19 of 19 places loaded it, typical 4818 ms.

Report totals as of 7 Nov, 20:28 UTC

Report a problem with Linode

Choose where you are, then tap what isn't working. Tapping a problem sends your report; no account needed.

What isn't working? Tap one to send

Anonymous · one report per service per hour. This adds your experience to the chart; the provider is not contacted.

Compare worldwide reports · Other services in Fr. S. Antarctic Lands

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 Fr. S. Antarctic Lands. The report chart above is filtered to Fr. S. Antarctic Lands.

Our own checks of linode.com

Every 5 minutes, from our probes

Our checks from 35 cities: all fine.

Singapore: loaded in 5816 ms Amsterdam: loaded in 4108 ms Jakarta: loaded in 5748 ms Querétaro: loaded in 3457 ms Mumbai: loaded in 5123 ms Bangalore: loaded in 4214 ms Cape Town: loaded in 5605 ms Atlanta: loaded in 5116 ms Tokyo: loaded in 3742 ms London: loaded in 4288 ms Los Angeles: loaded in 4818 ms Warsaw: loaded in 4049 ms New Jersey: loaded in 4514 ms Dallas: loaded in 6623 ms Doha: loaded in 4360 ms Tel Aviv: loaded in 5370 ms St. Louis: loaded in 4305 ms Melbourne: loaded in 5909 ms Osaka: loaded in 5884 ms Delhi: loaded in 4331 ms Madrid: loaded in 4414 ms Hamina: loaded in 4183 ms Frankfurt: loaded in 5181 ms Johannesburg: loaded in 6480 ms New York: loaded in 3125 ms Hong Kong: loaded in 3741 ms Seoul: loaded in 3379 ms Portsmouth: loaded in 4215 ms Lauterbourg: loaded in 2275 ms Seattle: loaded in 3484 ms Port Louis: loaded in 3694 ms São Paulo: loaded in 2670 ms Santiago: loaded in 5020 ms Toronto: loaded in 5187 ms Sydney: loaded in 5627 ms
  • SingaporeReachable5816 ms, 2 min ago
  • AmsterdamReachable4108 ms, 2 min ago
  • JakartaReachable5748 ms, 2 min ago
  • QuerétaroReachable3457 ms, 2 min ago
  • MumbaiReachable5123 ms, 2 min ago
  • BangaloreReachable4214 ms, 2 min ago
  • Cape TownReachable5605 ms, 2 min ago
  • AtlantaReachable5116 ms, 2 min ago
  • TokyoReachable3742 ms, 3 min ago
  • LondonReachable4288 ms, 3 min ago
  • Los AngelesReachable4818 ms, 3 min ago
  • WarsawReachable4049 ms, 3 min ago
  • New JerseyReachable4514 ms, 3 min ago
  • DallasReachable6623 ms, 3 min ago
  • DohaReachable4360 ms, 3 min ago
  • Tel AvivReachable5370 ms, 3 min ago
  • St. LouisReachable4305 ms, 3 min ago
  • MelbourneReachable5909 ms, 3 min ago
  • OsakaReachable5884 ms, 3 min ago
  • DelhiReachable4331 ms, 3 min ago
  • MadridReachable4414 ms, 3 min ago
  • HaminaReachable4183 ms, 3 min ago
  • FrankfurtReachable5181 ms, 4 min ago
  • JohannesburgReachable6480 ms, 4 min ago
  • New YorkReachable3125 ms, 4 min ago
  • Hong KongReachable3741 ms, 4 min ago
  • SeoulReachable3379 ms, 4 min ago
  • PortsmouthReachable4215 ms, 4 min ago
  • LauterbourgReachable2275 ms, 4 min ago
  • SeattleReachable3484 ms, 4 min ago
  • Port LouisReachable3694 ms, 4 min ago
  • São PauloReachable2670 ms, 4 min ago
  • SantiagoReachable5020 ms, 4 min ago
  • TorontoReachable5187 ms, 4 min ago
  • SydneyReachable5627 ms, 4 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

Recent problems

2 Nov, 09:02 UTCPartial outagegoing on, 5 d 11 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 Fr. S. Antarctic Lands 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.

Other services in Cloud and hosting

Each card shows that service's own status, not Linode's. A problem listed here does not mean Linode has one.

See the live outage feed for Fr. S. Antarctic Lands · Find another service