Betternow 中断历史

1. 2026年8月13日 UTC 07:01resolved

   该服务的新版本增加了对API证书的更严格的验证,这不适当地拒绝一些拥有401HTTP响应码的用户访问. 从2026-08-12 17:43到2026-08-13 08:41 CEST恢复验证前,我们看到了401个回复

自动翻译自官方事件更新。

1. 2026年1月19日 UTC 10:45investigating

   We are currently investigating this issue.

2. 2026年1月19日 UTC 10:54monitoring

   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日 UTC 17:32resolved

   This incident has been resolved.

1. 2025年12月17日 UTC 18:18investigating

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

2. 2025年12月17日 UTC 18:27monitoring

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

3. 2025年12月17日 UTC 18:54resolved

   This incident has been resolved.

1. 2025年12月16日 UTC 18:14investigating

   We are currently investigating this issue.

2. 2025年12月16日 UTC 18:23monitoring

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

3. 2025年12月16日 UTC 18:56resolved

   This incident has been resolved.

1. 2025年10月22日 UTC 08:43identified

   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日 UTC 13:12resolved

   This incident has been resolved.

1. 2025年9月30日 UTC 13:11investigating

   We are currently investigating this issue.

2. 2025年9月30日 UTC 13:23identified

   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日 UTC 14:01identified

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

4. 2025年9月30日 UTC 14:04monitoring

   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日 UTC 14:41resolved

   This incident has been resolved.

1. 2025年6月10日 UTC 14:49investigating

   We are currently investigating this issue.

2. 2025年6月10日 UTC 15:45identified

   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日 UTC 16:23monitoring

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

4. 2025年6月10日 UTC 16:52monitoring

   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日 UTC 20:36monitoring

   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日 UTC 05:43resolved

   This incident has been resolved.

1. 2025年3月31日 UTC 13:33resolved

   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日 UTC 16:46investigating

   We are currently investigating this issue.

2. 2024年12月30日 UTC 16:54identified

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

3. 2024年12月30日 UTC 16:59monitoring

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

4. 2024年12月30日 UTC 17:30resolved

   This incident has been resolved.

1. 2024年11月15日 UTC 07:54investigating

   We are currently investigating this issue.

2. 2024年11月15日 UTC 09:44monitoring

   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日 UTC 10:18resolved

   This incident has been resolved.

1. 2024年11月8日 UTC 08:06identified

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

2. 2024年11月8日 UTC 08:06investigating

   We are currently investigating this issue.

3. 2024年11月8日 UTC 08:08investigating

   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日 UTC 09:45resolved

   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日 UTC 05:29resolved

   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日 UTC 13:21investigating

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

2. 2024年10月9日 UTC 13:33investigating

   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日 UTC 13:58identified

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

4. 2024年10月9日 UTC 16:44monitoring

   We are seeing response times improve in all regions.

5. 2024年10月9日 UTC 18:35resolved

   This incident has been resolved.

1. 2024年10月8日 UTC 17:10investigating

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

2. 2024年10月8日 UTC 17:37investigating

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

3. 2024年10月8日 UTC 18:13identified

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

4. 2024年10月9日 UTC 04:15resolved

   This incident has been resolved.

1. 2024年10月7日 UTC 07:53investigating

   We are currently investigating this issue.

2. 2024年10月7日 UTC 08:09monitoring

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

3. 2024年10月7日 UTC 09:59resolved

   This incident has been resolved.

1. 2024年9月26日 UTC 11:49investigating

   We are currently investigating this issue.

2. 2024年9月26日 UTC 12:11monitoring

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

3. 2024年9月26日 UTC 16:27resolved

   This incident has been resolved.

1. 2024年9月12日 UTC 05:12identified

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

2. 2024年9月12日 UTC 05:13identified

   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日 UTC 12:18monitoring

   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日 UTC 17:49resolved

   This incident has been resolved.

1. 2024年7月5日 UTC 07:10investigating

   We are currently investigating this issue.

2. 2024年7月5日 UTC 07:11investigating

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

3. 2024年7月5日 UTC 07:23monitoring

   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日 UTC 09:36resolved

   This incident has been resolved.

1. 2024年4月25日 UTC 10:15investigating

   We are currently investigating this issue.

2. 2024年4月25日 UTC 10:21monitoring

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

3. 2024年4月25日 UTC 11:48resolved

   This incident has been resolved.

1. 2024年3月13日 UTC 15:31investigating

   We are currently investigating this issue.

2. 2024年3月13日 UTC 15:36monitoring

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

3. 2024年3月13日 UTC 16:05resolved

   This incident has been resolved.