Betternow 장애 기록

1. 2026년 8월 13일 오전 7:01 UTCresolved

   서비스의 새로운 버전은 API 자격 증명의 엄격한 검증을 추가, 이는 401 HTTP 응답 코드와 일부 사용자에 대한 액세스를 거부. 우리는 2026-08-12 17:43 CEST에서 401 응답의 증가를 보았습니다. 유효성까지 2026-08-13 08:41 CEST

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 1월 19일 오전 10:45 UTCinvestigating

   We are currently investigating this issue.

2. 2026년 1월 19일 오전 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. 2026년 1월 19일 오후 5:32 UTCresolved

   This incident has been resolved.

1. 2025년 12월 17일 오후 6:18 UTCinvestigating

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

2. 2025년 12월 17일 오후 6:27 UTCmonitoring

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

3. 2025년 12월 17일 오후 6:54 UTCresolved

   This incident has been resolved.

1. 2025년 12월 16일 오후 6:14 UTCinvestigating

   We are currently investigating this issue.

2. 2025년 12월 16일 오후 6:23 UTCmonitoring

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

3. 2025년 12월 16일 오후 6:56 UTCresolved

   This incident has been resolved.

1. 2025년 10월 22일 오전 8: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. 2025년 10월 22일 오후 1:12 UTCresolved

   This incident has been resolved.

1. 2025년 9월 30일 오후 1:11 UTCinvestigating

   We are currently investigating this issue.

2. 2025년 9월 30일 오후 1: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. 2025년 9월 30일 오후 2:01 UTCidentified

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

4. 2025년 9월 30일 오후 2: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. 2025년 9월 30일 오후 2:41 UTCresolved

   This incident has been resolved.

1. 2025년 6월 10일 오후 2:49 UTCinvestigating

   We are currently investigating this issue.

2. 2025년 6월 10일 오후 3: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. 2025년 6월 10일 오후 4:23 UTCmonitoring

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

4. 2025년 6월 10일 오후 4: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. 2025년 6월 10일 오후 8: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. 2025년 6월 11일 오전 5:43 UTCresolved

   This incident has been resolved.

1. 2025년 3월 31일 오후 1: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. 2024년 12월 30일 오후 4:46 UTCinvestigating

   We are currently investigating this issue.

2. 2024년 12월 30일 오후 4:54 UTCidentified

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

3. 2024년 12월 30일 오후 4:59 UTCmonitoring

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

4. 2024년 12월 30일 오후 5:30 UTCresolved

   This incident has been resolved.

1. 2024년 11월 15일 오전 7:54 UTCinvestigating

   We are currently investigating this issue.

2. 2024년 11월 15일 오전 9: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. 2024년 11월 15일 오전 10:18 UTCresolved

   This incident has been resolved.

1. 2024년 11월 8일 오전 8:06 UTCidentified

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

2. 2024년 11월 8일 오전 8:06 UTCinvestigating

   We are currently investigating this issue.

3. 2024년 11월 8일 오전 8: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. 2024년 11월 8일 오전 9:45 UTCresolved

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

1. 2024년 10월 29일 오전 5: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. 2024년 10월 9일 오후 1:21 UTCinvestigating

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

2. 2024년 10월 9일 오후 1: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. 2024년 10월 9일 오후 1:58 UTCidentified

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

4. 2024년 10월 9일 오후 4:44 UTCmonitoring

   We are seeing response times improve in all regions.

5. 2024년 10월 9일 오후 6:35 UTCresolved

   This incident has been resolved.

1. 2024년 10월 8일 오후 5:10 UTCinvestigating

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

2. 2024년 10월 8일 오후 5:37 UTCinvestigating

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

3. 2024년 10월 8일 오후 6:13 UTCidentified

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

4. 2024년 10월 9일 오전 4:15 UTCresolved

   This incident has been resolved.

1. 2024년 10월 7일 오전 7:53 UTCinvestigating

   We are currently investigating this issue.

2. 2024년 10월 7일 오전 8:09 UTCmonitoring

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

3. 2024년 10월 7일 오전 9:59 UTCresolved

   This incident has been resolved.

1. 2024년 9월 26일 오전 11:49 UTCinvestigating

   We are currently investigating this issue.

2. 2024년 9월 26일 오후 12:11 UTCmonitoring

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

3. 2024년 9월 26일 오후 4:27 UTCresolved

   This incident has been resolved.

1. 2024년 9월 12일 오전 5:12 UTCidentified

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

2. 2024년 9월 12일 오전 5: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. 2024년 9월 12일 오후 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. 2024년 9월 12일 오후 5:49 UTCresolved

   This incident has been resolved.

1. 2024년 7월 5일 오전 7:10 UTCinvestigating

   We are currently investigating this issue.

2. 2024년 7월 5일 오전 7:11 UTCinvestigating

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

3. 2024년 7월 5일 오전 7: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. 2024년 7월 5일 오전 9:36 UTCresolved

   This incident has been resolved.

1. 2024년 4월 25일 오전 10:15 UTCinvestigating

   We are currently investigating this issue.

2. 2024년 4월 25일 오전 10:21 UTCmonitoring

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

3. 2024년 4월 25일 오전 11:48 UTCresolved

   This incident has been resolved.

1. 2024년 3월 13일 오후 3:31 UTCinvestigating

   We are currently investigating this issue.

2. 2024년 3월 13일 오후 3:36 UTCmonitoring

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

3. 2024년 3월 13일 오후 4:05 UTCresolved

   This incident has been resolved.