Prism (prismnodes)

THE ONLY OFFICIAL X ACCOUNT OF PRISM - BEWARE OF IMPERSONATION. High performance, quality cloud hosting without breaking the bank @ Prism Cloud.

[Prism (prismnodes) @PrismStatus]

Hey @TerukiTech & @BckyrdBandwidth, we’ve learned that @PrismNode is impersonating us and harassing members of the community in our name. We are not affiliated with them in any way. This is the only official Prism account. Apologies for any harm caused by their messages.

[Prism (prismnodes) @PrismStatus]

Completed: Maintenance has completed successfully https://t.co/hs0rPru2l9

[Prism (prismnodes) @PrismStatus]

Planned: We will be migrating all servers from FRA-7 to FRA-9 so we can perform hardware upgrades on FRA-7.

Servers affected by this migration have received a notice in the panel & will have the option to migrate before the dead https://t.co/hs0rPru2l9

[Prism (prismnodes) @PrismStatus]

In progress: Maintenance is now in progress https://t.co/hs0rPru2l9

[Prism (prismnodes) @PrismStatus]

Identified: Upstream: "We are aware of a network outage affecting Miami. We have isolated the cause to our upstream (DataPacket/CDN77). We have already reached out to them and they're working on a fix. We apologize for the inconv https://t.co/3MiJieNnzO

[Prism (prismnodes) @PrismStatus]

Investigating: Our automated monitoring system detected that MIA-1 stopped responding for more than 5 minutes. This may be due to a possible power, network, or hardware fault. Our technicians have been notified and are investigat https://t.co/3MiJieNnzO

[Prism (prismnodes) @PrismStatus]

Resolved: This incident has been resolved. Caused by block storage cluster failure. https://t.co/5sq9Luz7Yl

[Prism (prismnodes) @PrismStatus]

Investigating: We are currently investigating this incident. https://t.co/5sq9Luz7Yl

[Prism (prismnodes) @PrismStatus]

Resolved: This incident has been resolved. https://t.co/1MdPibQDVf

[Prism (prismnodes) @PrismStatus]

Investigating: We are currently investigating this incident. https://t.co/1MdPibQDVf

[Prism (prismnodes) @PrismStatus]

Completed: Maintenance has completed successfully https://t.co/RVaYkFZrL0

[Prism (prismnodes) @PrismStatus]

Planned: Hello,

We will be performing emergency migrations on the following machines:

Ashburn: ASH-1, ASH-2, ASH-3, ASH-5, ASH-6, ASH-10, ASH-13, ASH-28, ASH-29, ASH-30 Frankfurt: FRA-1, FRA-2, FRA-3, FRA-4, FRA-5, FRA-6 Dallas https://t.co/RVaYkFZrL0

[Prism (prismnodes) @PrismStatus]

In progress: Maintenance is now in progress https://t.co/RVaYkFZrL0

[Prism (prismnodes) @PrismStatus]

Resolved: This incident has been resolved. https://t.co/essIEe3MGy

[Prism (prismnodes) @PrismStatus]

Investigating: We are currently investigating this incident. https://t.co/essIEe3MGy

[Prism (prismnodes) @PrismStatus]

Resolved: This incident has been resolved. https://t.co/OPlwfpPA2j

[Prism (prismnodes) @PrismStatus]

Investigating: We are currently investigating this incident. https://t.co/OPlwfpPA2j

[Prism (prismnodes) @PrismStatus]

Resolved: This incident has been resolved.

This outage was caused by a significant cooler failure which has since been replaced. https://t.co/6DteMvQtUs

[Prism (prismnodes) @PrismStatus]

Investigating: We are currently investigating this incident. https://t.co/6DteMvQtUs

[Prism (prismnodes) @PrismStatus]

Resolved: This incident has been resolved. We do not expect future blips. A postmortem will be posted as soon as we have word on what went wrong from our (legacy) Ashburn upstream. https://t.co/75fNWRRBqm

[Prism (prismnodes) @PrismStatus]

Investigating: We are currently investigating this incident. https://t.co/75fNWRRBqm

[Prism (prismnodes) @PrismStatus]

Identified: Down again. We're working with our upstream provider to resolve this. Estimated resolution is \~5 minutes. https://t.co/75fNWRRBqm