51 Betternow incidents · April 2017 — official updates, affected components, duration and resolution details.
Eine neue Version des Dienstes fügte eine strengere Validierung der API-Anmeldeinformationen hinzu, die einigen Benutzern mit dem 401 HTTP-Antwortcode den Zugriff missbräuchlich verweigerten. Wir haben einen Anstieg der 401 Antworten von 2026-08-12 17:43 CEST gesehen, bis die Validierung um 2026-08-13 08:41 CEST rückgängig gemacht wurde
Automatisch aus der offiziellen Störungsmeldung übersetzt.
We are currently investigating this issue.
https://vipps.statuspage.io/incidents/0qmhyt9df92b according to Vipps a fix has been put into place. We are also seeing the error rate normalize.
This incident has been resolved.
We're experiencing an elevated level errors and are currently looking into the issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Some Swish payments are failing due to an issue with our upstream vendor. More information can be found at https://status.quickpay.net/cmh1pki2m04p95kv5jg6tkw0a
This incident has been resolved.
We are currently investigating this issue.
We have identified an issue at our upstream payment provider and have contacted them so that they can correct the issue. We have temporarily disabled Swish payments until the issue is resolved. Card, MobilePay, Vipps, and bank transfer payments are unaffected.
We are continuing to work on a fix for this issue.
Our upstream payment provider has corrected the issue. The error was live between 10:20 and 15:18. Swish payments have now been enabled again. Our upstream payment provider will contact affected merchants with details about the issue.
This incident has been resolved.
We are currently investigating this issue.
Our services are down due to a Heroku/Salesforce incident. https://status.salesforce.com/generalmessages/10001540 has more information on the outage.
We are seeing service recovery, however the Heroku/Salesforce incident is not resolved. We continue to monitor the system.
Heroku/Salesforce has updated their incident with the following: "Investigations are still ongoing. A permanent fix is in progress, and it will require disabling the configuration change that reintroduces impact." We take this to mean there is a possibility of more downtime before the incident is fully resolved. We will continue to monitor the system.
Heroku/Salesforce continue to work towards resolving the incident. The latest information can be found at https://status.salesforce.com/generalmessages/10001540 We will leave this incident open until the issue is fully resolved on their side. Our services have been operational since 16:21 UTC.
This incident has been resolved.
An error in a deploy caused an increased error rate for API requests to the fundraisers endpoint. The deploy has been rolled back as of 15:22 CEST
We are currently investigating this issue.
Autoscaling has caught up to the increased traffic and it looks like services are recovering
Services are recovered, we continue to monitor traffic levels and error levels
This incident has been resolved.
We are currently investigating this issue.
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.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
We are currently investigating this issue.
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
Swish has resolved their incident. We continue to monitor the error rate for Swish payments. https://status.swish.nu/incidents/1fwn9ny2lsh3
Our monitoring shows a period of downtime between 19:53 and 20:42 CET yesterday, October 28th. This was due to an issue with our upstream provider, the details are here: https://status.heroku.com/incidents/2721
We're seeing longer response times than normal from some regions.
For now it seems our monitoring from North America and South America are seeing the worst response times, while Europe and Asia-Pacific are only slightly elevated.
This looks to be a repeat of yesterday's incident: https://status.heroku.com/incidents/2685
We are seeing response times improve in all regions.
This incident has been resolved.
We're seeing much longer response times than normal from some regions.
We continue to see excessive response times and we're still trying to determine the cause.
Our upstream provider Heroku is reporting problems. Details are at https://status.heroku.com/incidents/2684
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The error rate has returned to normal levels. We continue to monitor the system.
This incident has been resolved.
Clearhaus is reporting issues with an upstream provider https://status.clearhaus.com/incidents/hp85pwr0m3yp
From Clearhaus: "Our upstream provider has confirmed and is aware of a connectivity issue. Currently almost all authorizations, voids and Mastercard credits are impacted"
An update from Clearhaus: "We have seen a significant increase in approval rates and the connectivity is now back to normal. Due to the severity of this issue and the previous sudden change in approval rate we are still actively monitoring this situation." We will continue to monitor this as well.
This incident has been resolved.
We are currently investigating this issue.
Swish has an incident open for this at https://status.swish.nu/incidents/6xqpkqcsy8bb
We are seeing a reduction in error rates and will continue to monitor the system and Swish's incident until it is resolved.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.