Prism Host - Notice history

Experiencing partially degraded performance

Notice history

Apr 2025

No notices reported this month

Mar 2025

Chicago - Preparation for edge0 Replacement
  • Completed
    March 18, 2025 at 5:53 PM
    Completed
    March 18, 2025 at 5:53 PM

    Our network team is hands-off today. No disruption occurred. We will be posting a maintenance post for when we anticipate replacing edge0 completely. :)

  • In progress
    March 18, 2025 at 2:30 PM
    In progress
    March 18, 2025 at 2:30 PM
    Maintenance is now in progress
  • Planned
    March 18, 2025 at 2:30 PM
    Planned
    March 18, 2025 at 2:30 PM

    Please refer to a very important maintenance announcement that may have an impact on hosting services:

    Preparation for edge0 Replacement – March 18th, 2025

    Services Affected:​ Chicago, Illinois Data Center
    Start Date:​ March 18th, 2025 @ 14:30 UTC
    Estimated End Date:​ March 18th, 2025 @ 18:30 UTC

    Summary​: Preparing for the replacement of edge0, one of our routers that was deprioritized from traversing traffic in a previous maintenance post due to slowly dying resulting in infrequent blips.

    Impact on Customer:​ During this time, our network team will be applying changes to our network core to prepare for the replacement of edge0. Please note that there is an expected blip to occur at least once during this maintenance.

    Updates: We will provide updates on our status page throughout the maintenance. You can subscribe to alerts on our status page. (https://status.prism-host.com)

    If you have any questions, comments, or concerns please reach out to our customer success team & they will assist you whenever possible.

Feb 2025

Networking Core - Addressing Frequent Blips
  • Update
    February 28, 2025 at 1:52 AM
    Completed
    February 28, 2025 at 1:52 AM

    Maintenance for this has been completed today. We've ​found the root cause​ to these Layer 2 issues relating to the ​router appliance​ itself. Luckily we have built the network to be redundant, so we will be ​shifting traffic over to a working router​ while we work on getting this ​defective one replaced​.

    Again this maintenance will continue to take place at ​9:00 AM Central​ time to avoid dropping players in the peak hours of the day. In the mean time ​some changes​ have been made to ​lessen the effects of these spikes​.

    To clarify, we would've had this done today, however the backup router was still in the process of being setup and was paused while Onsite was being developed. We needed a few prerequisites completed from our upstream before we could shift any traffic onto it. Which is why we are continuing this tomorrow as it went too far into prime time today to justify dropping traffic.

  • Completed
    February 27, 2025 at 11:00 PM
    Completed
    February 27, 2025 at 11:00 PM

    Maintenance has completed successfully

  • In progress
    February 27, 2025 at 3:00 PM
    In progress
    February 27, 2025 at 3:00 PM
    Maintenance is now in progress
  • Planned
    February 27, 2025 at 3:00 PM
    Planned
    February 27, 2025 at 3:00 PM

    Hello everyone, our network team ​has identified the root cause of the frequent short drops​ that have plagued the network over the past few days. We understand the ​severity​ of these drops and have ​identified the root cause​. To ​permanently resolve these issues​, we will be conducting ​emergency maintenance​ at ​9:00 AM Central Time​. During this maintenance, you will experience ​brief disruptions​ as mass changes will be done. We apologize in advance for any inconvenience this may pose to you, especially over these past few weeks where we have suffered instability from one of our upstream providers as well as the network maintenance we conducted to upgrade our core late last month. To be frank, the timing could not have been worse.

    For transparency, the issue stems from a ​Layer 2​ issue inside our ​VXLAN-EVPN​ network, which is affecting our spine switches that ​processes essentially all traffic on our network​. As a result, this was felt widespread and not just related to one upstream or one cabinet. This issue appears to have sprung from the preparation of on-boarding our on-prem protection suite into our core. We have been working at a fast pace to get that online and operational in hopes of shifting all traffic over in order to provide stability.

    We know the past few weeks have been difficult, and we recognize the ​importance of a reliable network​ for our customers and are tirelessly working to improve our offerings.

Onsite Development - More Progress
  • Completed
    February 25, 2025 at 7:00 PM
    Completed
    February 25, 2025 at 7:00 PM
    Maintenance has completed successfully
  • In progress
    February 25, 2025 at 3:00 PM
    In progress
    February 25, 2025 at 3:00 PM
    Maintenance is now in progress
  • Planned
    February 25, 2025 at 3:00 PM
    Planned
    February 25, 2025 at 3:00 PM

    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:

    Our 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.

    Warm Regards,
    Prism Host

Feb 2025 to Apr 2025

Next