Is CA-Central (Toronto) Linode Kubernetes Engine down?
Current CA-Central (Toronto) Linode Kubernetes Engine status is WARN

We checked the official CA-Central (Toronto) Linode Kubernetes Engine Status Page 4 min. 37 sec. ago. Learn more
Having a problem? Help Allie Gator keep this page accurate!

Report an Issue

Get notified when it's back up with dashboards and notifications

Recent CA-Central (Toronto) Linode Kubernetes Engine Outages and Issues

Follow the recent outages and downtime for CA-Central (Toronto) Linode Kubernetes Engine in the table below.

Start Time

Type

Length

Message

Details

April 24, 2024 06:18 UTC

WARN

ongoing

Service Issue - Linode Kubernetes Engine

See more
Start Time

April 24, 2024 06:18 UTC

Type WARN
Affected Components

Linode Kubernetes Engine - CA-Central (Toronto) Linode Kubernetes Engine

Message

Service Issue - Linode Kubernetes Engine

Details

Investigating - We are currently investigating this issue. Apr 24, 2024 - 06:14 UTC

April 24, 2024 06:03 UTC

WARN

15 minutes

Service Issue - Linode Kubernetes Engine

See more
Start Time

April 24, 2024 06:03 UTC

Type WARN
Affected Components

Linode Kubernetes Engine - CA-Central (Toronto) Linode Kubernetes Engine

Message

Service Issue - Linode Kubernetes Engine

Details

Monitoring - At this time we have been able to correct the issues affecting the LKE service. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please open a Support ticket for assistance. Apr 24, 2024 - 05:58 UTC

April 23, 2024 18:33 UTC

WARN

about 12 hours

Service Issue - Linode Kubernetes Engine

See more
Start Time

April 23, 2024 18:33 UTC

Type WARN
Affected Components

Linode Kubernetes Engine - CA-Central (Toronto) Linode Kubernetes Engine

Message

Service Issue - Linode Kubernetes Engine

Details

Investigating - Our team is investigating an issue affecting the Linode Kubernetes Engine (LKE). We will share additional updates as we have more information. Apr 23, 2024 - 18:31 UTC

April 10, 2024 02:03 UTC

MAINT

about 3 hours

Maintenance for Cloud Manager, API, CLI, Backups Service, and Images

See more
Start Time

April 10, 2024 02:03 UTC

Type MAINT
Affected Components

Linode Kubernetes Engine - US-East (Newark) Linode Kubernetes Engine

Linode Kubernetes Engine - US-Central (Dallas) Linode Kubernetes Engine

Linode Kubernetes Engine - US-West (Fremont) Linode Kubernetes Engine

Linode Kubernetes Engine - US-ORD (Chicago) Linode Kubernetes Engine

Linode Kubernetes Engine - CA-Central (Toronto) Linode Kubernetes Engine

Linode Kubernetes Engine - EU-West (London) Linode Kubernetes Engine

Linode Kubernetes Engine - EU-Central (Frankfurt) Linode Kubernetes Engine

Linode Kubernetes Engine - FR-PAR (Paris) Linode Kubernetes Engine

Linode Kubernetes Engine - AP-South (Singapore) Linode Kubernetes Engine

Linode Kubernetes Engine - AP-Northeast-2 (Tokyo 2) Linode Kubernetes Engine

Linode Kubernetes Engine - AP-West (Mumbai) Linode Kubernetes Engine

Linode Kubernetes Engine - SE-STO (Stockholm) Linode Kubernetes Engine

Linode Kubernetes Engine - US-SEA (Seattle) Linode Kubernetes Engine

Linode Kubernetes Engine - JP-OSA (Osaka) Linode Kubernetes Engine

Linode Kubernetes Engine - IN-MAA (Chennai) Linode Kubernetes Engine

Linode Kubernetes Engine - ID-CGK (Jakarta)

Linode Manager and API

Linode Kubernetes Engine - US-Southeast (Atlanta) Linode Kubernetes Engine

Linode Kubernetes Engine - US-IAD (Washington) Linode Kubernetes Engine

Linode Kubernetes Engine - AP-Southeast (Sydney) Linode Kubernetes Engine

Linode.com

Message

Maintenance for Cloud Manager, API, CLI, Backups Service, and Images

Details

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Apr 10, 2024 - 02:00 UTC

January 09, 2024 14:33 UTC

MAINT

about 2 hours

Maintenance for Node Balancer and LKE

See more
Start Time

January 09, 2024 14:33 UTC

Type MAINT
Affected Components

NodeBalancers - US-IAD (Washington) NodeBalancers

NodeBalancers - US-ORD (Chicago) NodeBalancers

NodeBalancers - CA-Central (Toronto) NodeBalancers

NodeBalancers - EU-West (London) NodeBalancers

NodeBalancers - EU-Central (Frankfurt) NodeBalancers

NodeBalancers - AP-South (Singapore) NodeBalancers

NodeBalancers - AP-Northeast-2 (Tokyo 2) NodeBalancers

NodeBalancers - AP-West (Mumbai) NodeBalancers

Linode Kubernetes Engine - US-East (Newark) Linode Kubernetes Engine

Linode Kubernetes Engine - US-Central (Dallas) Linode Kubernetes Engine

Linode Kubernetes Engine - US-West (Fremont) Linode Kubernetes Engine

Linode Kubernetes Engine - US-Southeast (Atlanta) Linode Kubernetes Engine

Linode Kubernetes Engine - US-IAD (Washington) Linode Kubernetes Engine

Linode Kubernetes Engine - US-ORD (Chicago) Linode Kubernetes Engine

Linode Kubernetes Engine - CA-Central (Toronto) Linode Kubernetes Engine

Linode Kubernetes Engine - EU-West (London) Linode Kubernetes Engine

Linode Kubernetes Engine - EU-Central (Frankfurt) Linode Kubernetes Engine

Linode Kubernetes Engine - FR-PAR (Paris) Linode Kubernetes Engine

Linode Kubernetes Engine - AP-South (Singapore) Linode Kubernetes Engine

Linode Kubernetes Engine - AP-Northeast-2 (Tokyo 2) Linode Kubernetes Engine

Linode Kubernetes Engine - AP-West (Mumbai) Linode Kubernetes Engine

Linode Kubernetes Engine - AP-Southeast (Sydney) Linode Kubernetes Engine

Linode Kubernetes Engine - IN-MAA (Chennai) Linode Kubernetes Engine

Linode Kubernetes Engine - ID-CGK (Jakarta)

NodeBalancers - JP-OSA (Osaka) NodeBalancers

NodeBalancers - SE-STO (Stockholm) NodeBalancers

NodeBalancers - US-SEA (Seattle) NodeBalancers

NodeBalancers - US-East (Newark) NodeBalancers

NodeBalancers - US-Central (Dallas) NodeBalancers

NodeBalancers - US-West (Fremont) NodeBalancers

NodeBalancers - US-Southeast (Atlanta) NodeBalancers

NodeBalancers - FR-PAR (Paris) NodeBalancers

NodeBalancers - AP-Southeast (Sydney) NodeBalancers

NodeBalancers - IN-MAA (Chennai) NodeBalancers

Linode Kubernetes Engine - SE-STO (Stockholm) Linode Kubernetes Engine

Linode Kubernetes Engine - US-SEA (Seattle) Linode Kubernetes Engine

Linode Kubernetes Engine - JP-OSA (Osaka) Linode Kubernetes Engine

Message

Maintenance for Node Balancer and LKE

Details

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jan 09, 2024 - 14:30 UTC

2024-04-24 14:08:39 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-04-24 14:08:39 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-04-24 14:08:39 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-04-24 14:08:39 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-04-24 14:08:39 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

Sign Up for More CA-Central (Toronto) Linode Kubernetes Engine History

StatusGator has about 9 years of CA-Central (Toronto) Linode Kubernetes Engine status history.

3 status changes in the last 24 hours

CA-Central (Toronto) Linode Kubernetes Engine status, last 24 hours:

3:00 PM
9:00 PM
3:00 AM
9:00 AM
3:00 PM
3:00 PM
3:00 AM
3:00 PM
  • Up: 4 hours

  • Warn: 20 hours

  • Down: 0 minutes

  • Maintenance: 0 minutes

CA-Central (Toronto) Linode Kubernetes Engine Outage and Status History

We've been monitoring CA-Central (Toronto) Linode Kubernetes Engine outages since March 21, 2015.
Here's the history of service outages we've observed from the CA-Central (Toronto) Linode Kubernetes Engine Status Page:

  • Up

  • Warn

  • Down

  • Maintenance

Instant enriched data from
3,580 status pages

About Our CA-Central (Toronto) Linode Kubernetes Engine Status Page Integration

CA-Central (Toronto) Linode Kubernetes Engine is a Cloud Infrastructure and Hosting solution that StatusGator has been monitoring since March 2015. Over the past about 9 years, we have collected data on on more than 1,944 outages that affected CA-Central (Toronto) Linode Kubernetes Engine users. When CA-Central (Toronto) Linode Kubernetes Engine publishes downtime on their status page, they do so across 115 components and 6 groups using 4 different statuses: up, warn, down, and maintenance which we use to provide granular uptime metrics and notifications.

More than 100 StatusGator users monitor CA-Central (Toronto) Linode Kubernetes Engine to get notified when it's down, is under maintenance, or has an outage. This makes it one of the most popular cloud infrastructure services monitored on our platform. We've sent more than 25,500 notifications to our users about CA-Central (Toronto) Linode Kubernetes Engine incidents, providing transparency and peace of mind. You can get alerts by signing up for a free StatusGator account.

If CA-Central (Toronto) Linode Kubernetes Engine is having system outages or experiencing other critical issues, red down notifications appear on the status page. In most cases, it means that core functions are not working properly, or there is some other serious customer-impacting event underway.

Warn notifications are used when CA-Central (Toronto) Linode Kubernetes Engine is undergoing a non-critical issue like minor service issues, performance degradation, non-core bugs, capacity issues, or problems affecting a small number of users.

CA-Central (Toronto) Linode Kubernetes Engine posts separate notifications for planned maintenance work. StatusGator will notify subscribers when CA-Central (Toronto) Linode Kubernetes Engine enters a pre-planned maintenance window, keeping you up to date.

Since CA-Central (Toronto) Linode Kubernetes Engine publishes a feed of proactive maintenance events on their status page, StatusGator will collect information about these events. Maintenance events for all your services can be viewed within StatusGator as a unified feed.

When CA-Central (Toronto) Linode Kubernetes Engine posts issues on their status page, we collect the main headline message and include that brief information or overview in notifications to StatusGator subscribers.

When CA-Central (Toronto) Linode Kubernetes Engine has outages or other service-impacting events on their status page, we pull down the detailed informational updates and include them in notifications. These messages often include the current details about how the problem is being mitigated, or when the next update will occur.

Because CA-Central (Toronto) Linode Kubernetes Engine has several components, each with their individual statuses, StatusGator can differentiate the status of each component in our notifications to you. This means, you can filter your status page notifications based on the services, regions, or components you utilize. This is an essential feature for complex services with many components or services spread out across many regions.

Frequently Asked Questions

Can’t find your question? Email us to arrange a time to discuss. We’d love to chat!

CA-Central (Toronto) Linode Kubernetes Engine Down?

Are you experiencing issues with CA-Central (Toronto) Linode Kubernetes Engine? Sign up to receive notifications when CA-Central (Toronto) Linode Kubernetes Engine publishes outages.

CA-Central (Toronto) Linode Kubernetes Engine Down or not working? Never be taken by surprise again.

StatusGator tells you when your cloud services have problems or their statuses change. We monitor the official status pages of more than 3,580 cloud services in real-time, aggregate the data, and send you alerts via email, Slack, Teams, SMS, and more.

Looking for recent downtime and outages of CA-Central (Toronto) Linode Kubernetes Engine?

Sign up for StatusGator and see all historical information about CA-Central (Toronto) Linode Kubernetes Engine outages and performance issues. Get free, instant notifications when CA-Central (Toronto) Linode Kubernetes Engine goes down.