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, 29 Jan 2026 18:46:39 +0000 https://status.bitaccess.com/#5ed5dfa8460302d4e38bb2b26bd79379e518129aa64de89e455dcbbc55af029b BTM Operator Panel recovered https://status.bitaccess.com/ Thu, 29 Jan 2026 18:39:36 +0000 https://status.bitaccess.com/#5ed5dfa8460302d4e38bb2b26bd79379e518129aa64de89e455dcbbc55af029b BTM Operator Panel went down https://status.bitaccess.com/ Mon, 19 Jan 2026 17:55:09 +0000 https://status.bitaccess.com/#892399903d18b0dddaf55c30be558e9745503fd29fca8501a1b49692d076d12b BTM Kiosk Services recovered https://status.bitaccess.com/ Mon, 19 Jan 2026 17:52:14 +0000 https://status.bitaccess.com/#cba644bb2926dd860a30f37efa3e5264816af14294845d72aec13bb8278645b4 Partner API recovered https://status.bitaccess.com/ Mon, 19 Jan 2026 17:30:14 +0000 https://status.bitaccess.com/#cba644bb2926dd860a30f37efa3e5264816af14294845d72aec13bb8278645b4 Partner API went down https://status.bitaccess.com/ Mon, 19 Jan 2026 17:17:17 +0000 https://status.bitaccess.com/#6937f2401c39f2b4e73a2b52ead97e58507893ef85c0bec451213ab7c2e04739 Partner API recovered https://status.bitaccess.com/ Mon, 19 Jan 2026 16:34:11 +0000 https://status.bitaccess.com/#6937f2401c39f2b4e73a2b52ead97e58507893ef85c0bec451213ab7c2e04739 Partner API went down https://status.bitaccess.com/ Mon, 19 Jan 2026 16:31:51 +0000 https://status.bitaccess.com/#892399903d18b0dddaf55c30be558e9745503fd29fca8501a1b49692d076d12b BTM Kiosk Services went down https://status.bitaccess.com/ Mon, 19 Jan 2026 16:23:20 +0000 https://status.bitaccess.com/#8d8eb43fe209b9cbe96473e8bb9fdd94444add3626e84a72b134abe1fe32ecc2 Partner API recovered https://status.bitaccess.com/ Mon, 19 Jan 2026 16:20:17 +0000 https://status.bitaccess.com/#8d8eb43fe209b9cbe96473e8bb9fdd94444add3626e84a72b134abe1fe32ecc2 Partner API went down https://status.bitaccess.com/ Sun, 18 Jan 2026 08:07:10 +0000 https://status.bitaccess.com/#3f718400cf9c87a2ac4152a0de17aa2e3b19b86283ed491980bc47d8e2ab8b39 Cash API recovered https://status.bitaccess.com/ Sun, 18 Jan 2026 08:04:59 +0000 https://status.bitaccess.com/#3f718400cf9c87a2ac4152a0de17aa2e3b19b86283ed491980bc47d8e2ab8b39 Cash API went down https://status.bitaccess.com/ Sat, 27 Dec 2025 06:15:47 +0000 https://status.bitaccess.com/#b77e19194f47cd999016c79914c66aacf618b5b867a3ad3e67f62bcde432ad1a Transaction Processor recovered https://status.bitaccess.com/ Sat, 27 Dec 2025 06:11:46 +0000 https://status.bitaccess.com/#b77e19194f47cd999016c79914c66aacf618b5b867a3ad3e67f62bcde432ad1a Transaction Processor went down https://status.bitaccess.com/ Sat, 20 Dec 2025 09:09:43 +0000 https://status.bitaccess.com/#266cbcfd2d0d2cd7410c39ea7dbb6a9e96e75ea9e00bd39707b8cea8a194f723 Transaction Processor recovered https://status.bitaccess.com/ Sat, 20 Dec 2025 09:07:42 +0000 https://status.bitaccess.com/#266cbcfd2d0d2cd7410c39ea7dbb6a9e96e75ea9e00bd39707b8cea8a194f723 Transaction Processor went down https://status.bitaccess.com/ Sun, 14 Dec 2025 18:16:09 +0000 https://status.bitaccess.com/#7eedad27d1b3cc5c815c3c742733d8866b1389c192000b4300b36b04331e673d BTM Data services recovered https://status.bitaccess.com/ Sun, 14 Dec 2025 18:14:22 +0000 https://status.bitaccess.com/#7eedad27d1b3cc5c815c3c742733d8866b1389c192000b4300b36b04331e673d BTM Data services went down https://status.bitaccess.com/ Thu, 11 Dec 2025 19:20:48 +0000 https://status.bitaccess.com/#35f0585c7fe2f31174a6cc3b34908710b999a4d0d4f09e606d7d70d61147bbfd Transaction Processor recovered https://status.bitaccess.com/ Thu, 11 Dec 2025 19:19:36 +0000 https://status.bitaccess.com/#35f0585c7fe2f31174a6cc3b34908710b999a4d0d4f09e606d7d70d61147bbfd Transaction Processor went down https://status.bitaccess.com/ Thu, 11 Dec 2025 15:34:28 +0000 https://status.bitaccess.com/#2bd1fdb7897b04eebbc57f50e0a9dfca2b060a827b277273be479d859d8b8381 BTM Operator Panel recovered https://status.bitaccess.com/ Thu, 11 Dec 2025 15:32:30 +0000 https://status.bitaccess.com/#2bd1fdb7897b04eebbc57f50e0a9dfca2b060a827b277273be479d859d8b8381 BTM Operator Panel went down 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/ Thu, 09 Oct 2025 17:48:27 +0000 https://status.bitaccess.com/#e7d9b7bb80bcf6b78fe3b98192d0e84f0eda4e7a77550c4362e36ef1132faf11 Partner API 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