Over the last 2 years, we've had ~4 major outages on their platform. The last of these was so severe we're moving everything back off and over to aws.
If we set the bar at events that break customers who have taken reasonable steps to be geographically distributed, 4 over two years is horrible. Things here are cascading router failure, BGP misconfiguration or external hijack, major peering dispute, bad push to critical systems. If these aren't rare, it's likely to be avoidable failures caused by the provider. Sometimes the earlier types of problems hit here too --- fiber cuts between regional data centers can be major problems if more things run on that fiber than expected; it's always fun to learn redundant fiber is in the same bundle, and usually that's learned when the bundle is cut.
I guess my account got pwned.
They asked how I'd pay for these - $900 worth I think - since I didn't have a valid card in their system (the previous one expired since I last used Packet). I told them to stop the VMs and allow me to reset my credentials. I also asked them to investigate their logs and geolocate all the users that logged into my account. I was also curious they actually let someone log into the account from a new IP (without notifying me) and also allowed them to run instances without a valid card.
They blocked my account, which also blocked this support thread. So I started a new thread from an alternative e-mail address to resolve the issues.
I never heard from them again.