Incidents reported on status page for Bitaccess https://status.bitaccess.com/ https://d1lppblt9t2x15.cloudfront.net/logos/55d22b47c77b922f6120cdd45525731c.png https://status.bitaccess.com/ en https://status.bitaccess.com/ Thu, 04 Dec 2025 20:40:58 +0000 https://status.bitaccess.com/#5b9938276c4998fc597b8019b94107124ee95952d43581f437b5b5bc61a6846a KYC Services recovered https://status.bitaccess.com/ Fri, 28 Nov 2025 06:58:17 +0000 https://status.bitaccess.com/#79b42f95c202981742c9c3cef0a0e13469a97b182a0565323507cdf4efd04a45 Transaction Processor recovered https://status.bitaccess.com/ Fri, 28 Nov 2025 06:56:14 +0000 https://status.bitaccess.com/#79b42f95c202981742c9c3cef0a0e13469a97b182a0565323507cdf4efd04a45 Transaction Processor went down https://status.bitaccess.com/ Thu, 27 Nov 2025 22:52:56 +0000 https://status.bitaccess.com/#28fe12cf3bd66e6c928ff4dea59091984e9dc523752942f8c383cfc02f2e1a68 Transaction Processor recovered https://status.bitaccess.com/ Thu, 27 Nov 2025 22:45:14 +0000 https://status.bitaccess.com/#28fe12cf3bd66e6c928ff4dea59091984e9dc523752942f8c383cfc02f2e1a68 Transaction Processor went down https://status.bitaccess.com/ Thu, 27 Nov 2025 19:29:17 +0000 https://status.bitaccess.com/#12c8d8a082a1e9005aacfd9939524f24569b522e0765741a6268c4dab9914e56 Transaction Processor recovered https://status.bitaccess.com/ Thu, 27 Nov 2025 19:28:14 +0000 https://status.bitaccess.com/#12c8d8a082a1e9005aacfd9939524f24569b522e0765741a6268c4dab9914e56 Transaction Processor went down https://status.bitaccess.com/ Mon, 24 Nov 2025 16:09:29 +0000 https://status.bitaccess.com/#7a3070b1990263a20826e37b95d13301f036902d83e421ebf2ab7030938a9b87 BTM Operator Panel recovered https://status.bitaccess.com/ Mon, 24 Nov 2025 16:07:28 +0000 https://status.bitaccess.com/#7a3070b1990263a20826e37b95d13301f036902d83e421ebf2ab7030938a9b87 BTM Operator Panel went down https://status.bitaccess.com/ Thu, 20 Nov 2025 04:54:10 +0000 https://status.bitaccess.com/#8eebad479dc6434c9d7f70cf9ab0123cdd43e59a9fca9fcead05adaaba8e4bbc Transaction Processor recovered https://status.bitaccess.com/ Thu, 20 Nov 2025 04:41:07 +0000 https://status.bitaccess.com/#8eebad479dc6434c9d7f70cf9ab0123cdd43e59a9fca9fcead05adaaba8e4bbc Transaction Processor went down https://status.bitaccess.com/ Thu, 20 Nov 2025 04:32:10 +0000 https://status.bitaccess.com/#8fbb6eafe365a427ba85e972b3b5ffa3115d548555a48a03b47c949687c0cc0b Transaction Processor recovered https://status.bitaccess.com/ Thu, 20 Nov 2025 04:07:07 +0000 https://status.bitaccess.com/#8fbb6eafe365a427ba85e972b3b5ffa3115d548555a48a03b47c949687c0cc0b Transaction Processor went down https://status.bitaccess.com/ Thu, 20 Nov 2025 04:00:11 +0000 https://status.bitaccess.com/#0023349ddda4ebf157276462be586047c91ee7b90e7a6bc0aa65ece2b05134eb Transaction Processor recovered https://status.bitaccess.com/ Thu, 20 Nov 2025 03:54:07 +0000 https://status.bitaccess.com/#0023349ddda4ebf157276462be586047c91ee7b90e7a6bc0aa65ece2b05134eb Transaction Processor went down https://status.bitaccess.com/ Thu, 20 Nov 2025 03:39:10 +0000 https://status.bitaccess.com/#047fdf0b5af032c96314af7a598825a41b8b81b6eafb2b51005b778ec2587052 Transaction Processor recovered https://status.bitaccess.com/ Thu, 20 Nov 2025 03:37:07 +0000 https://status.bitaccess.com/#047fdf0b5af032c96314af7a598825a41b8b81b6eafb2b51005b778ec2587052 Transaction Processor went down https://status.bitaccess.com/ Tue, 18 Nov 2025 11:45:45 +0000 https://status.bitaccess.com/#71716f201806cffc6dc51c8e25714c3f53288a5089d39d4731728f524b14338f Cash API recovered https://status.bitaccess.com/ Tue, 18 Nov 2025 11:35:44 +0000 https://status.bitaccess.com/#71716f201806cffc6dc51c8e25714c3f53288a5089d39d4731728f524b14338f Cash API went down https://status.bitaccess.com/ Tue, 18 Nov 2025 05:47:00 +0000 https://status.bitaccess.com/#5b9938276c4998fc597b8019b94107124ee95952d43581f437b5b5bc61a6846a KYC Services went down https://status.bitaccess.com/ Mon, 17 Nov 2025 21:32:01 +0000 https://status.bitaccess.com/#6dc8d1297b23e7bbffd8dd3c60df3b203d8c103892c6eed323baf3284dda8d07 BTM Operator Panel recovered https://status.bitaccess.com/ Mon, 17 Nov 2025 21:16:59 +0000 https://status.bitaccess.com/#6dc8d1297b23e7bbffd8dd3c60df3b203d8c103892c6eed323baf3284dda8d07 BTM Operator Panel went down https://status.bitaccess.com/ Mon, 17 Nov 2025 20:58:02 +0000 https://status.bitaccess.com/#d56d3b03d2cdda6d9e04a347210c53c9a9c17c98849a534ea6596e4d8e99376e BTM Operator Panel recovered https://status.bitaccess.com/ Mon, 17 Nov 2025 20:56:01 +0000 https://status.bitaccess.com/#d56d3b03d2cdda6d9e04a347210c53c9a9c17c98849a534ea6596e4d8e99376e BTM Operator Panel went down https://status.bitaccess.com/ Mon, 17 Nov 2025 20:46:59 +0000 https://status.bitaccess.com/#4d6bc20bc0b71917eb9f24bedb3442582bb42f1dc4030b0ac1015799ae71ae5a BTM Operator Panel recovered https://status.bitaccess.com/ Mon, 17 Nov 2025 20:41:01 +0000 https://status.bitaccess.com/#4d6bc20bc0b71917eb9f24bedb3442582bb42f1dc4030b0ac1015799ae71ae5a BTM Operator Panel went down https://status.bitaccess.com/ Sun, 09 Nov 2025 23:54:19 +0000 https://status.bitaccess.com/#bc1f53e5b95e917d3b0b919935a08fccd08dc809de195418ea5927f89d90019f KYC Services recovered https://status.bitaccess.com/ Sun, 09 Nov 2025 23:53:52 +0000 https://status.bitaccess.com/#bc1f53e5b95e917d3b0b919935a08fccd08dc809de195418ea5927f89d90019f KYC Services went down https://status.bitaccess.com/ Fri, 07 Nov 2025 19:55:33 +0000 https://status.bitaccess.com/#e7d9b7bb80bcf6b78fe3b98192d0e84f0eda4e7a77550c4362e36ef1132faf11 Partner API recovered https://status.bitaccess.com/ Thu, 06 Nov 2025 13:36:23 +0000 https://status.bitaccess.com/#affb0fd3131a6add032df6400ae58761a3e983daab1100e784cbc292dc523289 KYC Services recovered https://status.bitaccess.com/ Thu, 06 Nov 2025 13:33:57 +0000 https://status.bitaccess.com/#affb0fd3131a6add032df6400ae58761a3e983daab1100e784cbc292dc523289 KYC Services went down https://status.bitaccess.com/ Wed, 05 Nov 2025 02:09:05 +0000 https://status.bitaccess.com/#3051e61b9d05df9274a6005d2207c155c087b6710abdccbec1b88ca03b15d6a0 KYC Services recovered https://status.bitaccess.com/ Wed, 05 Nov 2025 02:06:01 +0000 https://status.bitaccess.com/#3051e61b9d05df9274a6005d2207c155c087b6710abdccbec1b88ca03b15d6a0 KYC Services went down https://status.bitaccess.com/ Sun, 26 Oct 2025 08:06:41 +0000 https://status.bitaccess.com/#ac895ed6cf096c3c606ec5d9d5161c1554128d25aae2b48cc9d82efd14db400f Cash API recovered https://status.bitaccess.com/ Sun, 26 Oct 2025 08:04:39 +0000 https://status.bitaccess.com/#ac895ed6cf096c3c606ec5d9d5161c1554128d25aae2b48cc9d82efd14db400f Cash API went down https://status.bitaccess.com/ Mon, 20 Oct 2025 19:37:02 +0000 https://status.bitaccess.com/#1c14ec59e8f6477e980df77e930f6ddded9dde1cf557bf09ff8e1d330cf17030 BTM Kiosk Services recovered https://status.bitaccess.com/ Mon, 20 Oct 2025 19:33:59 +0000 https://status.bitaccess.com/#1c14ec59e8f6477e980df77e930f6ddded9dde1cf557bf09ff8e1d330cf17030 BTM Kiosk Services went down https://status.bitaccess.com/ Mon, 20 Oct 2025 19:25:07 +0000 https://status.bitaccess.com/#0c6eb065706f9ea239fe1721e0013b69b5496479f0bea4ec31da0764f1b8f10a BTM Kiosk Services recovered https://status.bitaccess.com/ Mon, 20 Oct 2025 19:19:09 +0000 https://status.bitaccess.com/#0c6eb065706f9ea239fe1721e0013b69b5496479f0bea4ec31da0764f1b8f10a BTM Kiosk Services went down https://status.bitaccess.com/ Mon, 20 Oct 2025 19:13:17 +0000 https://status.bitaccess.com/#baa4d88c6a3a7457d6a804b44634d45d36940a9edd1aed9938afe48e28088adc BTM Kiosk Services recovered https://status.bitaccess.com/ Mon, 20 Oct 2025 16:34:21 +0000 https://status.bitaccess.com/#baa4d88c6a3a7457d6a804b44634d45d36940a9edd1aed9938afe48e28088adc BTM Kiosk Services went down https://status.bitaccess.com/ Fri, 17 Oct 2025 05:55:33 +0000 https://status.bitaccess.com/#9c9c412efd05dc1ecce277ea2e1e9f8916537da6a7143070523c976942c06a55 Customer Portal recovered https://status.bitaccess.com/ Fri, 17 Oct 2025 05:54:19 +0000 https://status.bitaccess.com/#9c9c412efd05dc1ecce277ea2e1e9f8916537da6a7143070523c976942c06a55 Customer Portal went down https://status.bitaccess.com/ Thu, 09 Oct 2025 19:12:46 +0000 https://status.bitaccess.com/#f14f03662e6d1de00b9bfc6aa5c81879835f04381de80e9135335aec887eb597 KYC Services recovered https://status.bitaccess.com/ Thu, 09 Oct 2025 19:09:17 +0000 https://status.bitaccess.com/#f14f03662e6d1de00b9bfc6aa5c81879835f04381de80e9135335aec887eb597 KYC Services went down https://status.bitaccess.com/ Thu, 09 Oct 2025 17:48:27 +0000 https://status.bitaccess.com/#e7d9b7bb80bcf6b78fe3b98192d0e84f0eda4e7a77550c4362e36ef1132faf11 Partner API went down https://status.bitaccess.com/ Tue, 07 Oct 2025 09:12:29 +0000 https://status.bitaccess.com/#82edd9f963d61066cde3018b5a9519761c26cd719d14eed342d4c33f949809f7 KYC Services recovered https://status.bitaccess.com/ Tue, 07 Oct 2025 09:12:01 +0000 https://status.bitaccess.com/#82edd9f963d61066cde3018b5a9519761c26cd719d14eed342d4c33f949809f7 KYC Services went down https://status.bitaccess.com/ Thu, 02 Oct 2025 16:30:45 +0000 https://status.bitaccess.com/#f82c61b28c80ae2c92d9780d8ebf9f1d552f720d791f2336321265729fd2747f KYC Services recovered https://status.bitaccess.com/ Thu, 02 Oct 2025 16:29:56 +0000 https://status.bitaccess.com/#f82c61b28c80ae2c92d9780d8ebf9f1d552f720d791f2336321265729fd2747f KYC Services went down https://status.bitaccess.com/ Fri, 26 Sep 2025 13:41:05 +0000 https://status.bitaccess.com/#4a0cbaa019da7375c775d086de810f0dfe6cec5eff44b664594f63c495da1708 Transaction Processor recovered https://status.bitaccess.com/ Fri, 26 Sep 2025 13:40:04 +0000 https://status.bitaccess.com/#4a0cbaa019da7375c775d086de810f0dfe6cec5eff44b664594f63c495da1708 Transaction Processor went down https://status.bitaccess.com/ Thu, 25 Sep 2025 09:19:33 +0000 https://status.bitaccess.com/#84afecd7449c1cfa974b41c9dd722f514a72a0f323b05662da941b1fb7903209 Transaction Processor recovered https://status.bitaccess.com/ Thu, 25 Sep 2025 09:17:32 +0000 https://status.bitaccess.com/#84afecd7449c1cfa974b41c9dd722f514a72a0f323b05662da941b1fb7903209 Transaction Processor went down https://status.bitaccess.com/ Tue, 23 Sep 2025 00:42:55 +0000 https://status.bitaccess.com/#e481e63c69d8ec861ef36d0aa5d17495b1848b4677ff76505ac1595bf8c137d1 Transaction Processor recovered https://status.bitaccess.com/ Tue, 23 Sep 2025 00:40:53 +0000 https://status.bitaccess.com/#e481e63c69d8ec861ef36d0aa5d17495b1848b4677ff76505ac1595bf8c137d1 Transaction Processor went down https://status.bitaccess.com/ Mon, 22 Sep 2025 23:21:55 +0000 https://status.bitaccess.com/#baaee1070b7436d843993b92ff94467e7691de62e45133de0903b3d16f8a9d98 Transaction Processor recovered https://status.bitaccess.com/ Mon, 22 Sep 2025 23:20:54 +0000 https://status.bitaccess.com/#baaee1070b7436d843993b92ff94467e7691de62e45133de0903b3d16f8a9d98 Transaction Processor went down https://status.bitaccess.com/ Mon, 22 Sep 2025 22:27:04 +0000 https://status.bitaccess.com/#3c9de393c0ed48fd892b40e1830e02d8873f4404954863d325fd0f9fa3ddb4d0 Transaction Processor recovered https://status.bitaccess.com/ Mon, 22 Sep 2025 22:24:53 +0000 https://status.bitaccess.com/#3c9de393c0ed48fd892b40e1830e02d8873f4404954863d325fd0f9fa3ddb4d0 Transaction Processor went down https://status.bitaccess.com/ Mon, 22 Sep 2025 22:04:56 +0000 https://status.bitaccess.com/#f536aa7135879475a29bdecdee80dbbb1460c1e3df7d3911e75abf7415d3a847 Transaction Processor recovered https://status.bitaccess.com/ Mon, 22 Sep 2025 21:54:53 +0000 https://status.bitaccess.com/#f536aa7135879475a29bdecdee80dbbb1460c1e3df7d3911e75abf7415d3a847 Transaction Processor went down https://status.bitaccess.com/ Sat, 20 Sep 2025 05:42:52 +0000 https://status.bitaccess.com/#2ff96a72264c0b715a7120a056f8417025d9f6fd1f06dab13a0653cd173cb7dd Transaction Processor recovered https://status.bitaccess.com/ Sat, 20 Sep 2025 05:39:51 +0000 https://status.bitaccess.com/#2ff96a72264c0b715a7120a056f8417025d9f6fd1f06dab13a0653cd173cb7dd Transaction Processor went down https://status.bitaccess.com/incident/112284 Wed, 24 Aug 2022 11:27:00 -0000 https://status.bitaccess.com/incident/112284#8aaa41b59eb057ab297088ce8b2f7b86263ab38aab382e482f74b31b5ecbd0dd At approximately 11:17pm GMT on August 23th, 2022 Bitaccess's monitoring services detected DNS lookup errors reaching our production services. After investigation, this was caused by a failure in the systems of a core upstream cloud service provider. The root cause of this issue is an incident at NS1, a very large name service provider (https://ns1status.com/#!/incident/365716). This incident had the downstream effect of impacting Heroku (https://status.heroku.com/incidents/2453), which is a critical service provider to Bitaccess. While Bitaccess has the ability to route traffic across regions at times of service instability, this issue impacted all traffic being routed into an out of the cloud service provider. Both NA and EU regions were impacted. The incident was resolved through no intervention by Bitaccess at approximately 01:08am GMT on August 24, 2022. https://status.bitaccess.com/incident/112284 Wed, 24 Aug 2022 11:27:00 -0000 https://status.bitaccess.com/incident/112284#8aaa41b59eb057ab297088ce8b2f7b86263ab38aab382e482f74b31b5ecbd0dd At approximately 11:17pm GMT on August 23th, 2022 Bitaccess's monitoring services detected DNS lookup errors reaching our production services. After investigation, this was caused by a failure in the systems of a core upstream cloud service provider. The root cause of this issue is an incident at NS1, a very large name service provider (https://ns1status.com/#!/incident/365716). This incident had the downstream effect of impacting Heroku (https://status.heroku.com/incidents/2453), which is a critical service provider to Bitaccess. While Bitaccess has the ability to route traffic across regions at times of service instability, this issue impacted all traffic being routed into an out of the cloud service provider. Both NA and EU regions were impacted. The incident was resolved through no intervention by Bitaccess at approximately 01:08am GMT on August 24, 2022. https://status.bitaccess.com/incident/112284 Wed, 24 Aug 2022 11:27:00 -0000 https://status.bitaccess.com/incident/112284#8aaa41b59eb057ab297088ce8b2f7b86263ab38aab382e482f74b31b5ecbd0dd At approximately 11:17pm GMT on August 23th, 2022 Bitaccess's monitoring services detected DNS lookup errors reaching our production services. After investigation, this was caused by a failure in the systems of a core upstream cloud service provider. The root cause of this issue is an incident at NS1, a very large name service provider (https://ns1status.com/#!/incident/365716). This incident had the downstream effect of impacting Heroku (https://status.heroku.com/incidents/2453), which is a critical service provider to Bitaccess. While Bitaccess has the ability to route traffic across regions at times of service instability, this issue impacted all traffic being routed into an out of the cloud service provider. Both NA and EU regions were impacted. The incident was resolved through no intervention by Bitaccess at approximately 01:08am GMT on August 24, 2022. https://status.bitaccess.com/incident/112284 Wed, 24 Aug 2022 11:27:00 -0000 https://status.bitaccess.com/incident/112284#8aaa41b59eb057ab297088ce8b2f7b86263ab38aab382e482f74b31b5ecbd0dd At approximately 11:17pm GMT on August 23th, 2022 Bitaccess's monitoring services detected DNS lookup errors reaching our production services. After investigation, this was caused by a failure in the systems of a core upstream cloud service provider. The root cause of this issue is an incident at NS1, a very large name service provider (https://ns1status.com/#!/incident/365716). This incident had the downstream effect of impacting Heroku (https://status.heroku.com/incidents/2453), which is a critical service provider to Bitaccess. While Bitaccess has the ability to route traffic across regions at times of service instability, this issue impacted all traffic being routed into an out of the cloud service provider. Both NA and EU regions were impacted. The incident was resolved through no intervention by Bitaccess at approximately 01:08am GMT on August 24, 2022. https://status.bitaccess.com/incident/112284 Wed, 24 Aug 2022 11:27:00 -0000 https://status.bitaccess.com/incident/112284#8aaa41b59eb057ab297088ce8b2f7b86263ab38aab382e482f74b31b5ecbd0dd At approximately 11:17pm GMT on August 23th, 2022 Bitaccess's monitoring services detected DNS lookup errors reaching our production services. After investigation, this was caused by a failure in the systems of a core upstream cloud service provider. The root cause of this issue is an incident at NS1, a very large name service provider (https://ns1status.com/#!/incident/365716). This incident had the downstream effect of impacting Heroku (https://status.heroku.com/incidents/2453), which is a critical service provider to Bitaccess. While Bitaccess has the ability to route traffic across regions at times of service instability, this issue impacted all traffic being routed into an out of the cloud service provider. Both NA and EU regions were impacted. The incident was resolved through no intervention by Bitaccess at approximately 01:08am GMT on August 24, 2022. https://status.bitaccess.com/incident/112284 Wed, 24 Aug 2022 11:27:00 -0000 https://status.bitaccess.com/incident/112284#8aaa41b59eb057ab297088ce8b2f7b86263ab38aab382e482f74b31b5ecbd0dd At approximately 11:17pm GMT on August 23th, 2022 Bitaccess's monitoring services detected DNS lookup errors reaching our production services. After investigation, this was caused by a failure in the systems of a core upstream cloud service provider. The root cause of this issue is an incident at NS1, a very large name service provider (https://ns1status.com/#!/incident/365716). This incident had the downstream effect of impacting Heroku (https://status.heroku.com/incidents/2453), which is a critical service provider to Bitaccess. While Bitaccess has the ability to route traffic across regions at times of service instability, this issue impacted all traffic being routed into an out of the cloud service provider. Both NA and EU regions were impacted. The incident was resolved through no intervention by Bitaccess at approximately 01:08am GMT on August 24, 2022. https://status.bitaccess.com/incident/112284 Wed, 24 Aug 2022 11:27:00 -0000 https://status.bitaccess.com/incident/112284#8aaa41b59eb057ab297088ce8b2f7b86263ab38aab382e482f74b31b5ecbd0dd At approximately 11:17pm GMT on August 23th, 2022 Bitaccess's monitoring services detected DNS lookup errors reaching our production services. After investigation, this was caused by a failure in the systems of a core upstream cloud service provider. The root cause of this issue is an incident at NS1, a very large name service provider (https://ns1status.com/#!/incident/365716). This incident had the downstream effect of impacting Heroku (https://status.heroku.com/incidents/2453), which is a critical service provider to Bitaccess. While Bitaccess has the ability to route traffic across regions at times of service instability, this issue impacted all traffic being routed into an out of the cloud service provider. Both NA and EU regions were impacted. The incident was resolved through no intervention by Bitaccess at approximately 01:08am GMT on August 24, 2022. https://status.bitaccess.com/incident/112284 Wed, 24 Aug 2022 11:27:00 -0000 https://status.bitaccess.com/incident/112284#8aaa41b59eb057ab297088ce8b2f7b86263ab38aab382e482f74b31b5ecbd0dd At approximately 11:17pm GMT on August 23th, 2022 Bitaccess's monitoring services detected DNS lookup errors reaching our production services. After investigation, this was caused by a failure in the systems of a core upstream cloud service provider. The root cause of this issue is an incident at NS1, a very large name service provider (https://ns1status.com/#!/incident/365716). This incident had the downstream effect of impacting Heroku (https://status.heroku.com/incidents/2453), which is a critical service provider to Bitaccess. While Bitaccess has the ability to route traffic across regions at times of service instability, this issue impacted all traffic being routed into an out of the cloud service provider. Both NA and EU regions were impacted. The incident was resolved through no intervention by Bitaccess at approximately 01:08am GMT on August 24, 2022. https://status.bitaccess.com/incident/97010 Wed, 22 Jun 2022 19:10:00 -0000 https://status.bitaccess.com/incident/97010#055e1f2793c2ca4c6a40a5d97ef7d97f9060c8c74c6829899aaea984ba62a799 New login sessions to the operator panel service restored. If you experience issues accessing your dashboard, please logout and login again. A very small number of users will need to be re-invited by another member of their organization. https://status.bitaccess.com/incident/97010 Wed, 22 Jun 2022 12:00:00 -0000 https://status.bitaccess.com/incident/97010#8842f2886e4f5709035361a6a0d9de14d979f0c6b1f8dd4fd8e30455303157e4 Users were unable to login to a new session on op.bitaccess.com