История сбоев Betternow

1. 13 августа 2026 г. в 07:01 UTCresolved

   Новая версия сервиса добавила более строгую проверку учетных данных API, которая ненадлежащим образом отказала в доступе некоторым пользователям с кодом ответа HTTP 401. Мы наблюдали увеличение 401 ответа с 2026-08-12 17:43 CEST до тех пор, пока валидация не была возвращена в 2026-08-13 08:41 CEST

Автоматический перевод официального обновления инцидента.

1. 19 января 2026 г. в 10:45 UTCinvestigating

   We are currently investigating this issue.

2. 19 января 2026 г. в 10:54 UTCmonitoring

   https://vipps.statuspage.io/incidents/0qmhyt9df92b according to Vipps a fix has been put into place. We are also seeing the error rate normalize.

3. 19 января 2026 г. в 17:32 UTCresolved

   This incident has been resolved.

1. 17 декабря 2025 г. в 18:18 UTCinvestigating

   We're experiencing an elevated level errors and are currently looking into the issue.

2. 17 декабря 2025 г. в 18:27 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 17 декабря 2025 г. в 18:54 UTCresolved

   This incident has been resolved.

1. 16 декабря 2025 г. в 18:14 UTCinvestigating

   We are currently investigating this issue.

2. 16 декабря 2025 г. в 18:23 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 16 декабря 2025 г. в 18:56 UTCresolved

   This incident has been resolved.

1. 22 октября 2025 г. в 08:43 UTCidentified

   Some Swish payments are failing due to an issue with our upstream vendor. More information can be found at https://status.quickpay.net/cmh1pki2m04p95kv5jg6tkw0a

2. 22 октября 2025 г. в 13:12 UTCresolved

   This incident has been resolved.

1. 30 сентября 2025 г. в 13:11 UTCinvestigating

   We are currently investigating this issue.

2. 30 сентября 2025 г. в 13:23 UTCidentified

   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.

3. 30 сентября 2025 г. в 14:01 UTCidentified

   We are continuing to work on a fix for this issue.

4. 30 сентября 2025 г. в 14:04 UTCmonitoring

   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.

5. 30 сентября 2025 г. в 14:41 UTCresolved

   This incident has been resolved.

1. 10 июня 2025 г. в 14:49 UTCinvestigating

   We are currently investigating this issue.

2. 10 июня 2025 г. в 15:45 UTCidentified

   Our services are down due to a Heroku/Salesforce incident. https://status.salesforce.com/generalmessages/10001540 has more information on the outage.

3. 10 июня 2025 г. в 16:23 UTCmonitoring

   We are seeing service recovery, however the Heroku/Salesforce incident is not resolved. We continue to monitor the system.

4. 10 июня 2025 г. в 16:52 UTCmonitoring

   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.

5. 10 июня 2025 г. в 20:36 UTCmonitoring

   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.

6. 11 июня 2025 г. в 05:43 UTCresolved

   This incident has been resolved.

1. 31 марта 2025 г. в 13:33 UTCresolved

   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

1. 30 декабря 2024 г. в 16:46 UTCinvestigating

   We are currently investigating this issue.

2. 30 декабря 2024 г. в 16:54 UTCidentified

   Autoscaling has caught up to the increased traffic and it looks like services are recovering

3. 30 декабря 2024 г. в 16:59 UTCmonitoring

   Services are recovered, we continue to monitor traffic levels and error levels

4. 30 декабря 2024 г. в 17:30 UTCresolved

   This incident has been resolved.

1. 15 ноября 2024 г. в 07:54 UTCinvestigating

   We are currently investigating this issue.

2. 15 ноября 2024 г. в 09:44 UTCmonitoring

   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.

3. 15 ноября 2024 г. в 10:18 UTCresolved

   This incident has been resolved.

1. 8 ноября 2024 г. в 08:06 UTCidentified

   The issue has been identified and a fix is being implemented.

2. 8 ноября 2024 г. в 08:06 UTCinvestigating

   We are currently investigating this issue.

3. 8 ноября 2024 г. в 08:08 UTCinvestigating

   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

4. 8 ноября 2024 г. в 09:45 UTCresolved

   Swish has resolved their incident. We continue to monitor the error rate for Swish payments. https://status.swish.nu/incidents/1fwn9ny2lsh3

1. 29 октября 2024 г. в 05:29 UTCresolved

   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

1. 9 октября 2024 г. в 13:21 UTCinvestigating

   We're seeing longer response times than normal from some regions.

2. 9 октября 2024 г. в 13:33 UTCinvestigating

   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.

3. 9 октября 2024 г. в 13:58 UTCidentified

   This looks to be a repeat of yesterday's incident: https://status.heroku.com/incidents/2685

4. 9 октября 2024 г. в 16:44 UTCmonitoring

   We are seeing response times improve in all regions.

5. 9 октября 2024 г. в 18:35 UTCresolved

   This incident has been resolved.

1. 8 октября 2024 г. в 17:10 UTCinvestigating

   We're seeing much longer response times than normal from some regions.

2. 8 октября 2024 г. в 17:37 UTCinvestigating

   We continue to see excessive response times and we're still trying to determine the cause.

3. 8 октября 2024 г. в 18:13 UTCidentified

   Our upstream provider Heroku is reporting problems. Details are at https://status.heroku.com/incidents/2684

4. 9 октября 2024 г. в 04:15 UTCresolved

   This incident has been resolved.

1. 7 октября 2024 г. в 07:53 UTCinvestigating

   We are currently investigating this issue.

2. 7 октября 2024 г. в 08:09 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 7 октября 2024 г. в 09:59 UTCresolved

   This incident has been resolved.

1. 26 сентября 2024 г. в 11:49 UTCinvestigating

   We are currently investigating this issue.

2. 26 сентября 2024 г. в 12:11 UTCmonitoring

   The error rate has returned to normal levels. We continue to monitor the system.

3. 26 сентября 2024 г. в 16:27 UTCresolved

   This incident has been resolved.

1. 12 сентября 2024 г. в 05:12 UTCidentified

   Clearhaus is reporting issues with an upstream provider https://status.clearhaus.com/incidents/hp85pwr0m3yp

2. 12 сентября 2024 г. в 05:13 UTCidentified

   From Clearhaus: "Our upstream provider has confirmed and is aware of a connectivity issue. Currently almost all authorizations, voids and Mastercard credits are impacted"

3. 12 сентября 2024 г. в 12:18 UTCmonitoring

   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.

4. 12 сентября 2024 г. в 17:49 UTCresolved

   This incident has been resolved.

1. 5 июля 2024 г. в 07:10 UTCinvestigating

   We are currently investigating this issue.

2. 5 июля 2024 г. в 07:11 UTCinvestigating

   Swish has an incident open for this at https://status.swish.nu/incidents/6xqpkqcsy8bb

3. 5 июля 2024 г. в 07:23 UTCmonitoring

   We are seeing a reduction in error rates and will continue to monitor the system and Swish's incident until it is resolved.

4. 5 июля 2024 г. в 09:36 UTCresolved

   This incident has been resolved.

1. 25 апреля 2024 г. в 10:15 UTCinvestigating

   We are currently investigating this issue.

2. 25 апреля 2024 г. в 10:21 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 25 апреля 2024 г. в 11:48 UTCresolved

   This incident has been resolved.

1. 13 марта 2024 г. в 15:31 UTCinvestigating

   We are currently investigating this issue.

2. 13 марта 2024 г. в 15:36 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 13 марта 2024 г. в 16:05 UTCresolved

   This incident has been resolved.