Scala Studios - Notice history

At specifically 9AM Central Time we will be continuing development with our onsite network. We apologize for any interruptions this may cause, we are doing this early in the AM to ensure we impact as little traffic as possible.

We understand the frequent issues from upstream isn't making this an easy pill to swallow, but we must continue work on this to ensure we are independent from future network issues once Onsite goes live.

To give context on what onsite will bring for those who may have missed it:

Onsite DDoS Protection will allow us to have a localized Path environment that will be isolated from the global network. This will allow us to attempt to seamlessly, without dropping traffic move between the global network and local network when needed.

Take for example the issues that we have been facing now, these are all from the global network with Onsite we would be-able to push traffic onto our local mitigation stack, effectively isolating us from global network issues, ensuring full uptime. This also works in reverse, if the local network was to go offline for some reason, we would route back onto the global network, while again attempting to not drop any traffic.

This system is extremely complex, and has been under development for a while now, we are speeding up progress but also doing so at the least impactful times, we understand no downtime is ideal, however this must be done in order to ensure we have a fully redundant network. I am sure everyone is tired of these upstream issues, we are too, and we truly believe onsite is the solution we are all looking for.

After the successful testing of our on-site DDoS protection into our network core in the last maintenance, we are moving onto stage 3, which is the beginning of moving production traffic to the protection appliances. We are keeping production traffic to a minimum to ensure no adverse effects in the initial rollout. Over the next few days, we will be shifting more traffic over the appliances. Later communications will be provided when this occurs.

To minimize disruptions, we’ve scheduled the partial deployment during non-peak hours. While brief traffic blips are possible, we’re taking all necessary precautions to limit such disruptions.

One of our upstream providers, Path, is actively restoring their Chicago PoP, and we expect minimal disruptions throughout the process. The only potential brief interruption will occur during the final activation phase when traffic is routed back through Chicago.

We are expecting updates as work continues, this will be the last PoP that needs to be migrated in the US until Phoenix, however Phoenix is TBD and is not expected to be migrated for a while.

Once live, we will transition away from Kansas City (KC), and latency should begin to normalize.