Welcome to BetterNow's status page. We'll update this page with information about any interruptions in service or planned downtime. This page has been available since the 24th of November, 2013.
BetterNow Platform
Operational
90 days ago
99.99
% uptime
Today
api.betternow.org
?
Operational
90 days ago
99.99
% uptime
Today
Donation Payment Processing
Operational
www.betternow.org
?
Operational
images.yourbetternow.org
?
Operational
AWS ec2-eu-west-1
Operational
AWS cloudFront
Operational
AWS route53
Operational
Heroku
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Related
No incidents or maintenance related to this downtime.
Completed -
The scheduled maintenance has been completed.
Nov 18, 07:15 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Nov 18, 03:15 UTC
Scheduled -
We will upgrade our secondary datastore at this time. There may be up to two short outages lasting approximately 3 minutes during the maintenance period.
Nov 7, 07:09 UTC
Resolved -
This incident has been resolved.
Nov 15, 10:18 UTC
Monitoring -
Our autoscaling has caught up to a spike in requests and the error rate has normalized. We continue to monitor the health of the system.
Nov 15, 09:44 UTC
Investigating -
We are currently investigating this issue.
Nov 15, 07:54 UTC
Completed -
The scheduled maintenance has been completed.
Nov 12, 07:45 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Nov 12, 03:45 UTC
Scheduled -
We will be undergoing scheduled maintenance at this time. There may be up to two short (3 min. or less) periods of downtime during the maintenance period.
Nov 6, 13:43 UTC
Update -
We see an elevated error rate for Swish payments for many merchants. More information can be found on the Swish status page at https://status.swish.nu/incidents/1fwn9ny2lsh3
Nov 8, 08:08 UTC
Investigating -
We are currently investigating this issue.
Nov 8, 08:06 UTC
Identified -
The issue has been identified and a fix is being implemented.
Nov 8, 08:06 UTC