Linode
Cloud hosting for you. Instantly deploy an SSD cloud server running with your choice of Linux distro, resources, and node location.
Homepage: https://linode.com
Status Page: https://status.linode.com
Open Incidents
No open incidents
Scheduled Incidents
No scheduled incidents
Previous Incidents
Support Phone Outage
2017-01-27 23:20:35| Action | Date | Description |
|---|---|---|
| Resolved | 2017-01-27 23:20:00 | No additional issues with our Support phone line have been observed. Please feel free to give us a call if you have any questions or concerns. |
| Monitoring | 2017-01-27 19:08:00 | We have worked with our upstream provider to stabilized our connection, and the phones are now back to normal functionality. We will be monitoring the phone system now for any additional issues. |
| Identified | 2017-01-27 03:28:00 | We're continuing to experience recurring issues with call connectivity on our Support phone line. We've reached out to our upstream phone provider and are working with them to fully investigate and resolve the underlying cause. We will provide updates as they become available. In the meantime, we recommend submitting support requests via ticket at manager.linode.com or via email to support@linode.com. |
| Investigating | 2017-01-27 01:48:00 | We are currently experiencing issues with our Support phone line and are currently investigating. If you need assistance from our Support team, please reach out to us via a support ticket or email support@linode.com. We will provide updates as we have more information. |
Fremont Peering Exchange Maintenance
2017-01-27 17:00:30| Action | Date | Description |
|---|---|---|
| Completed | 2017-01-27 17:00:00 | The scheduled maintenance has been completed. |
| Scheduled | 2017-01-27 16:00:00 | We will be provisioning additional capacity on the Equinix San Jose Internet Peering Exchange starting Friday, January 27 at 11am ET (4pm UTC) in our Fremont node. We do not expect any negative impact to customers traffic during this time.Once the additional capacity is operational, additional direct peering with other popular networks can occur. As a result, our customers will have direct interconnection to popular networks and thereby enabling the user to have high-bandwidth, low-latency interconnection at the Fremont node. |
Network Connectivity Between Frankfurt and Newark
2017-01-25 21:45:50| Action | Date | Description |
|---|---|---|
| Resolved | 2017-01-25 21:45:00 | Connectivity between our Newark and Frankfurt datacenters has remained stable and this issue is now resolved. If you experience any additional connectivity issues, please reach out to our Customer Support Team for assistance. |
| Monitoring | 2017-01-25 16:04:00 | Connectivity between the datacenters has been restored. We'll continue to monitor this situation and will provide updates as necessary. |
| Investigating | 2017-01-25 15:03:00 | We are currently investigating a connectivity issue between our Frankfurt datacenter and our Newark Datacenter. |
Dallas connectivity issues
2017-01-23 12:46:42| Action | Date | Description |
|---|---|---|
| Resolved | 2017-01-24 01:05:00 | At this time the emergency maintenance has concluded and connectivity has remained stable. If you experience any connectivity issues going forward, please reach out to our Customer Support Team for assistance. |
| Monitoring | 2017-01-23 13:01:00 | The module reset has been successful, and we have resilient connectivity restored for customers downstream of the switch affected. We will monitor this for 8 hours before moving to resolved. |
| Identified | 2017-01-23 12:46:00 | We have identified an issue with our connectivity from our DC switching Fabric that while not immediately service impacting, has degraded our ability to provide a resilient service to some customers. We will be taking corrective action shortly to bring the module back online. At that point we will discuss with the vendor about the best way to proceed. The corrective action should be non-impactful for all customers, but customers may notice increased latency. We are due to begin corrective action at 12:50 UTC and finish by 13:05 UTC. |
London
2017-01-20 07:55:14| Action | Date | Description |
|---|---|---|
| Resolved | 2017-01-20 18:14:00 | This incident is resolved. We will be posting a post-mortem shortly. |
| Monitoring | 2017-01-20 12:53:00 | Connectivity to our London datacenter has been fully restored. We'll continue to monitor this situation and provide updates as necessary. |
| Investigating | 2017-01-20 09:18:00 | We are currently experiencing connectivity issues within our London datacenter. Our Network Operations team is aware and is currently investigating. |
| Monitoring | 2017-01-20 08:53:00 | Connectivity has been restored and we are monitoring for any residual issues. |
| Investigating | 2017-01-20 07:55:00 | We are aware of an issue within our London datacenter and are investigating at this time. We will provide additional information as it becomes available. |
Atlanta Transit Capacity Upgrade
2017-01-18 23:05:49| Action | Date | Description |
|---|---|---|
| Completed | 2017-01-20 01:00:00 | The scheduled maintenance has been completed. |
| Scheduled | 2017-01-20 00:00:00 | We will be bringing up an additional IP Transit Provider starting at 7:00pm ET (00:00 UTC), Thursday January 19th in our Atlanta node. We do not expect any negative impact to customers traffic while adding this capacity, as BGP will converge without issue. Once the capacity is online, customers will benefit from the shorter as-paths that we will be receiving from this newly added tier one provider, as well as the additional capacity. |
| Scheduled | 2017-01-18 23:05:00 | We will be bringing up an additional IP Transit Provider starting at 7:00pm ET (00:00 UTC), Thursday January 19th in our Atlanta node. We do not expect any negative impact to customers traffic while adding this capacity, as BGP will converge without issue. Once the capacity is online, customers will benefit from the shorter as-paths that we will be receiving from this newly added tier one provider, as well as the additional capacity. |
Fremont
2017-01-18 21:12:37| Action | Date | Description |
|---|---|---|
| Completed | 2017-01-19 03:30:00 | The scheduled maintenance has been completed. |
| Scheduled | 2017-01-19 03:01:00 | We will be bringing up an additional Internet Peering Exchange - SFMIX San Francisco - starting tonight at 10pm ET (3am UTC Thursday, January 19, 2017) in our Fremont node. We do not expect any negative impact to customers traffic while adding this peering exchange. Once the peering exchange is online customers will eventually benefit from the direct peering relations that Linode will setup with popular networks resulting in low-latency with those networks on the IX. |
| Scheduled | 2017-01-18 21:12:00 | We will be bringing up an additional Internet Peering Exchange - SFMIX San Francisco - starting tonight at 10pm ET (3am UTC Thursday, January 19, 2017) in our Fremont node. We do not expect any negative impact to customers traffic while adding this peering exchange. Once the peering exchange is online customers will eventually benefit from the direct peering relations that Linode will setup with popular networks resulting in low-latency with those networks on the IX. |
Frankfurt
2017-01-16 14:02:52| Action | Date | Description |
|---|---|---|
| Completed | 2017-01-19 03:25:00 | The scheduled maintenance has been completed. |
| Scheduled | 2017-01-19 00:00:00 | We will be performing network maintenance for approximately two hours on Thursday, January 19, 2016 at 00:00 UTC in our Frankfurt datacenter. While we do not expect any downtime during this maintenance, customers may experience brief periods of increased latency or packet loss. We appreciate your patience as we work diligently to make our network more reliable. |
| Scheduled | 2017-01-16 14:02:00 | We will be performing network maintenance for approximately two hours on Thursday, January 19, 2016 at 00:00 UTC in our Frankfurt datacenter. While we do not expect any downtime during this maintenance, customers may experience brief periods of increased latency or packet loss. We appreciate your patience as we work diligently to make our network more reliable. |
Fremont
2017-01-11 20:23:43| Action | Date | Description |
|---|---|---|
| Resolved | 2017-01-11 22:48:00 | This incident has been resolved. Connectivity within our Fremont data center has remained optimal. If you experience any connectivity issues, please reach out to our Customer Support Team for assistance. |
| Monitoring | 2017-01-11 21:05:00 | Connectivity to our Fremont datacenter has been fully restored. We'll continue to monitor this situation and provide updates as necessary. |
| Investigating | 2017-01-11 20:23:00 | We're currently investigating a connectivity issue for a subset of connections to our Fremont datacenter. |
Support Phone Outage
2017-01-10 15:56:21| Action | Date | Description |
|---|---|---|
| Resolved | 2017-01-16 17:53:00 | At this time we have been able to restore the Support phone line. Please feel free to give us a call if you have any questions or concerns. |
| Identified | 2017-01-10 15:56:00 | We're continuing to experience recurring issues with call connectivity on our Support phone line. We've reached out to our upstream phone provider and are working with them to fully investigate and resolve the underlying cause. We will provide updates as they become available.In the meantime, we recommend submitting support requests via ticket at manager.linode.com or via email to support@linode.com. |