Historia awarii Proxyrack

We are currently investigating the issue

Performance is looking more stable

This incident has been resolved.

We are currently investigating the issue

Performance is looking more stable

This incident has been resolved.

We are currently investigating the issue

Performance is looking more stable

This incident has been resolved.

We are currently investigating the issue

Performance is looking more stable

This incident has been resolved.

We are currently investigating the issue

Performance is looking more stable

This incident has been resolved. Was a once off hiccup with the DNS.

We are currently investigating the issue

Performance is looking more stable

Datacenter has reported that the issues are resolved and they will continue monitoring.

The issues over the past 48 hours were all related to our datacenter and unfortunately out of our control. This was their response: > `Ok we were able to track down the events, yesterday there was a power issue in the datacenter and this morning one of our fibers went down. We have turned on a new port with a new carrier inside that DC to avoid this ever happening again.` ‌ We will be looking at new options for redundancy to prevent this in the future.

We are currently investigating the issue

Resolving duplicate incident for this component.

The issues over the past 48 hours were all related to our datacenter and unfortunately out of our control. This was their response: > `Ok we were able to track down the events, yesterday there was a power issue in the datacenter and this morning one of our fibers went down. We have turned on a new port with a new carrier inside that DC to avoid this ever happening again.` ‌ We will be looking at new options for redundancy to prevent this in the future.

There appears to be an ongoing power / network issue with the datacenter we use - http://rackdog.com/ They are aware of this and are trying to fix it asap. We do apologise for this irregular downtime.

We are continuing to investigate this issue.

Working as expected now.

The issues over the past 48 hours were all related to our datacenter and unfortunately out of our control. This was their response: > `Ok we were able to track down the events, yesterday there was a power issue in the datacenter and this morning one of our fibers went down. We have turned on a new port with a new carrier inside that DC to avoid this ever happening again.` ‌ We will be looking at new options for redundancy to prevent this in the future.

We are currently investigating this issue.

Test completed

We are currently investigating this issue.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

There were a few hours of downtime with Static USA Datacenter proxies today. This issue has already been resolved and our team is monitoring the service to make sure that the proxies continue to work as normal.

There has been bursts of poor performance over the past few days and here is a quick update; One of the datacenters we use decided to suspend 30+ of our servers for almost no apparent reason and then re-enabled them once they realized they made a mistake. Then our orchestration software started to stack our processes on just a few servers instead of spreading it evenly. This all resulted in bursts of poor performance over the past few days. Everything is running much smoother now and we're continuing to monitor for any further disruptions. We really appreciate everyones support and will be utilizing multiple datacenters moving forward to prevent these kinds of disruptions in the future.

This incident has been resolved.

We are currently investigating this issue.

This issue has been resolved.

We are currently investigating this issue. You may experience intermediate connection issues or not be able to connect to Unmetered Residential proxies.

We are continuing to investigate this issue.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We are currently investigating this issue.

This incident has been resolved.

We are currently investigating this issue.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We are currently investigating this issue.

This incident has been resolved.

We are currently investigating the issue

A fix has been implemented and we are monitoring the results

This incident has been resolved.

We are currently investigating the issue

This incident has been resolved.

We are currently investigating the issue

We are continuing to investigate this issue.

This incident has been resolved.