Infraly, LLC - Notice history

As of 3:53 PM ET, all traffic has returned to normal levels. We are still awaiting a response from a carrier to provide more insight as all records show it was external from our network.

The system has rebooted, and we are currently investigating logs as to why the machine crashed. We have updated the software as a precaution for kernel errors. The machine is back online and operating as expected. We will provide more updates if needed.

The on-site task was completed swiftly by a data center technician to pull out a bad optic. We are still evaluating why additional failover measures did not enact quicker and will provide additional information as needed. All services are operational and stable at the current moment, and our team will be marking this incident as resolved.

System rebooted by itself. It is currently rebooting back into the operating system. Once fully loaded, we will continue investigating the logs to understand why the server did so.

Our team has implemented a fix and restarted the FTP service. You should now be able to connect. If you have any questions, please contact our client relations team via live chat, ticket, or phone.

We've now been monitoring for a few hours since toggling traffic over NTT for the Path endpoint due to increased latency while being routed over GTT. All Path-routed services have remained stable since then and are operating as expected. We will continue to monitor over the next 24 hours, but will be marking this incident as resolved. Thank you all for your patience over the last day! If you have any questions or concerns, please reach out to our client relations team via live chat, ticket, or phone.

Transit traffic to Path has been routed over different carriers than GTT (higher latency due to preference of routing to NY) and HE (instability throughout the last 24 hours). Latency has returned to normal levels with this change, and all services are continuing to operate as expected. We will continue to monitor over the next 24 hours. If you have any issues, please contact our client relations team via livechat, ticket, or phone.

Traffic is routed via GTT to Path. We are seeing an increase in latency as a result. Working on re-routing to Chicago and not via NY to reduce latency. We will provide an update when successful. Path-only prefixes are online and operating as expected.

Path BGP session is now routed off Hurricane Electric and over another carrier. We don't expect any more issues now to occur once we reroute Path-only prefixes. We will be routed back Path-only prefixes at 2:05 PM ET. You may experience a drop in connection then, but it should reestablish quickly after as the routes are being changed.

Traffic is routed via GTT to Path. We are seeing an increase in latency as a result. Working on re-routing to Chicago and not via NY to reduce latency. We will provide an update when successful. Path-only prefixes are online and operating as expected.

Our team has been monitoring for the past hour since routing back over the BGP session as it has been back online for 7+ hours. Based on our knowledge right now, we believe the connection issues were caused by Hurricane Electric transit problems, which caused the drop originally earlier this morning. As of right now, we have concluded all Path-only services are online and stable. If you need are encountering issues, please reach out to our client relations team via livechat, ticket, or phone.

All Path-only prefixes are back on Path connection. Routes appear to be clean now. If you are encountering any issues, don’t hesitate reaching out to our client relations team via livechat, ticket, or phone.

Routes appear to have been clean on Path BGP connection for the past 5+ hours. We will be routing back Path-only prefixes at 11:00 AM ET. You may experience a drop in connection then, but it should reestablish quickly after as the routes are being changed.

This incident has been resolved. We have completed our investigation and attributed it to a stuck backup process that overloaded the machine's CPU usage. After remotely logging in and killing that process, the machine still refused to respond, in which a reboot command was executed. The machine rebooted and came back online with no errors afterward.

Virtualizor has started to respond again on CHI-P-VPS-4. We will continue monitoring.

After a few hours of monitoring, we have concluded this service to be stable. Our team will proactively monitor and implement necessary changes to ensure stability on this machine. If you have any questions, don't hesitate reaching out to our client relations team via live chat, ticket, or phone.

Issue has been identified and we have implemented a fix to resolve this matter. We will continue monitoring the situation and provide updates.

This incident has been resolved. Our team will continue to monitor.

Appears to have been a blimp in LiteSpeed webserver. Our teams are implementing a fix now and will continue monitoring.