Linode vs. Netlify

Compare the status, incidents stats and history between Linode and Netlify

Every service has different practices when updating its status page, so compare these stats with a grain of salt. E.g., one service can be more aggressive when updating its status page than other so that they will have more incidents, but it doesn't mean it is worse than the other.

Linode

Linode current official status is Minor Outage

Statistics

3
Incidents in the last 7 days
7
Incidents in the last 30 days
17
Incidents in the last 90 days

Latest incidents

Ongoing Support Phone Outage

We are currently experiencing issues with our Support phone line. Our team has identified an issue with our upstream provider who is currently investigating. If you need to contact us during this ...

about 2 hours ago Official incident report
Ongoing Service Issue - Managed Databases

Our team is investigating a service issue affecting MongoDB on the Managed Databases service. During this time, users will be unable to provision new MongoDB clusters.

Resolved Service Issue - Lish

We are currently investigating an issue with Lish. You may experience issues loading Lish from Cloud Manager at this time, however Lish via SSH is still accessible.

Netlify

Netlify current official status is Operational

Statistics

3
Incidents in the last 7 days
11
Incidents in the last 30 days
34
Incidents in the last 90 days

Latest incidents

Resolved Increased Errors and Latency on Origin, Standard and High-Performance Edge, API, and Build System

From 21:02 UTC to 21:06 UTC there were increased errors on our Origin Servers, Standard and High-Performance Edge Network, API, and Build System. The team has found the root cause and mitigated the...

Resolved API and Build System Degradation

Beginning at 16:44 UTC, we observed increased latency and errors in our API and build system. The affected components have returned to normal and the team continues to monitor.

Resolved Connection Timeouts on Standard Edge Network Load Balancer.

Starting at 11:29 UTC our legacy TCP load balancer with IP 104.198.14.52 is suffering connection timeouts due to an upstream provider problem. Customers still pointing to this Load Balancer via A r...

Easily monitor all your services providers

Increase the productivity and efficiency of your team. Enable monitoring for your services, and start receiving real-time alerts when your external dependencies have outages.

Start today for FREE