Reason: Datacenter network infrastructure upgrade

Expected Outage: Approximately 5 minutes during a 4 hour window from 12:00AM CST to 4:00 AM CST on 2009-05-21.  Mail attempted to be delivered during this time frame may be delayed longer than 5 minutes due to the retry settings on the sending server.  Typical retry settings are less than 4 hours.

We apologize for any inconvenience this upgrade may cause. If you experience issues related to this outage, please contact support@purity.net.

Payment notification emails that went out this morning showed a $0 amount being charged to the credit card on file.  This was due to some new code that was put in to handle restoring services from suspension and is simply a variable error in the email creation.  The full amount of the invoice was actually charged to your card.  The total payment can be seen by logging into https://manage.purity.net/ and going to the Invoices screen and changing the filter to Paid to view your paid invoices.

Some of our customers may have received warning notices regarding possible suspension of their account due to unpaid invoices.   Please take a look at the notice and if the notice is for an invoice that is due in the next few days (i.e. not due yet) you can disregard it.  If it is for an invoice that is already past its due date, please make payment on the invoice to avoid service interruption.

The issue with the invalid notices has been corrected and should not happen again in the future.

Some customer have reported problems with emails to our trouble ticketing system bouncing since last night.  First, I apologize for any inconvenience this may have caused.

This issue has been fixed and emails to our ticketing system are working again.  Please re-send any emails that bounced so that we can assist you.

This issue was caused by an upgrade to our trouble ticketing system and a configuration error after the upgrade.

Some of you have reported issues with the new Account Manager when using IE7.  I’m happy to let you know that the problem has been fixed…  and it was caused by a single errant comma in the javascript code.  Funny how one little comma can cause so many problems, eh?