SagePay Outage - March 31, 2010

This is information to SagePay's outage on the 31th 2010.

1. Actual screenshots from their system monitor.



2. What they say is the problem.

A third party provider had issues which stopped them from processing.

3. Has it happened before.

Not in relation to this blog but all reports say often enough.

4. Start and end time of the outage.

Start : 09:50:00
End : 09:59:00
Total : 00:09:00
Running Total : 39:59:36

5. What the follow up report stated.

Nothing as of yet reported.

SagePay Outage - March 28 to March 30, 2010

This is information to SagePay's outage on the March 28th through to March 30th 2010.

1. Actual screenshots from their system monitor.


2. What they say is the problem.

Same as in my last post. Access to historical transactions was not available.

https://support.sagepay.com/forum/Topic10830-40-1.aspx

Yes. A couple of days before.

4. Start and end time of the outage.

Start : 15:40:09, March 28
End : 06:38:51, March 31
Total : 38:58:41
Running Total : 39:50:36

5. What the follow up report stated.

From their forums :

They do not give a reason why it happened or what they are going to do to prevent it in the future.

SagePay Outage - March 25, 2010

This is information to SagePay's outage on the March 25th, 2010.

1. Actual screenshots from their system monitor.



2. What they say is the problem.

Merchants cannot access archived transactions. What this means is that if you are a merchant who does pre-authorisations or any action related to a previous transaction that you cannot use this transaction. This is bad why? Say you identify a transaction that you need to refund as it looks fraudulent. You cannot do so and may get a chargeback because of it.

3. Has it happened before.

Yes. September 2009.

4. Start and end time of the outage.

Start : 14:50:48
End : 15:42:43
Total : 00:51:55
Running Total : 00:51:55

5. What the follow up report stated.

https://support.sagepay.com/forum/Topic10830-40-1.aspx

What it looks like they did was failover onto their back-up system. Historical transactions were then not available as it looks like the back-up system does not have any data in it.

Introduction To SagePay Outages - The Blog Log

If you are reading this you are either a disgruntled SagePay merchant or looking to move to them. My advise is to move or find somewhere else to process. This blog is not meant to be a slam on SagePay but an accurate record of their uptime vrs what they sell to merchants.

If you are a merchant like me then you cannot afford downtime. Downtime = Loss of Sales. Now every company from behomoths like Google to the smallest company will have downtime now and again. It happens. So what. However the amount of downtime SagePay has is simply staggering. For someone doing mission critical processing you would think they would be doing everything in their power to not have multiple 24+ hour outages, partial outages or service degredation. The first one we experienced was in Sept 2009. I found this article that describes the event ( http://www.webpayments.ie/blog/iridium-acquire-189-new-merchants-as-a-result-of-the-sagepay-outage.html?blogger=Dave )

What has prompted me to begin this article is so far in the past seven days (March 24, 2010 - March 31, 2010 ) their has been 4 seperate outages for over 24 hours of down time.

So herein will be a record of SagePay outages for the world to see. I will only post the following :

1. Actual screenshots from their system monitor.
2. What they say is the problem.
3. Has it happened before.
4. Start and end time of the outage.
5. What the follow up report stated.

I will not emo rage but simply use this blog as a log. <- "I am a poet and didn't even know it" quote from Princess Bride, circa some long time ago.

Blog Starting Point - March 24, 2010.