Incidents reported on status page for Miura Pay https://status.miurapay.cloud/ https://d1lppblt9t2x15.cloudfront.net/logos/e452523be8fe3a84e1606b65fc42a500.png https://status.miurapay.cloud/ en https://status.miurapay.cloud/incident/911171 Thu, 04 Jun 2026 04:00:17 -0000 https://status.miurapay.cloud/incident/911171#008f8ce361f08665f22fcd67f968495322806af4206f6192409778db8db4b823 Maintenance work will be performed on services related to your environment. While downtime is not anticipated, brief service interruptions may occur. https://status.miurapay.cloud/ Thu, 14 May 2026 10:48:19 +0000 https://status.miurapay.cloud/#87afddde7f4c741ef6c76d73ee3754524567c5cbe433930fe612efd6d128da74 Ascend Portal API recovered https://status.miurapay.cloud/ Thu, 14 May 2026 10:47:37 +0000 https://status.miurapay.cloud/#87afddde7f4c741ef6c76d73ee3754524567c5cbe433930fe612efd6d128da74 Ascend Portal API went down https://status.miurapay.cloud/ Sat, 09 May 2026 07:12:26 +0000 https://status.miurapay.cloud/#1608e4dd81c4b71577dd8b260fd54377a1a43b320b35a8c852ebd83315b5bf18 Ascend RKI API recovered https://status.miurapay.cloud/ Sat, 09 May 2026 05:44:05 +0000 https://status.miurapay.cloud/#1608e4dd81c4b71577dd8b260fd54377a1a43b320b35a8c852ebd83315b5bf18 Ascend RKI API went down https://status.miurapay.cloud/incident/890801 Sat, 09 May 2026 04:00:22 -0000 https://status.miurapay.cloud/incident/890801#b8734a7ead188813ebd14abed5105c28032cbd556f347370e88b7b80697f9c94 Maintenance work will be performed on services related to your environment. While downtime is not anticipated, brief service interruptions may occur. https://status.miurapay.cloud/ Tue, 05 May 2026 19:03:48 +0000 https://status.miurapay.cloud/#1a7d4461e393316afb8781f11bbae9cbf7201a3e063db3394d8200e62abcce53 Ascend Distribution API recovered https://status.miurapay.cloud/ Tue, 05 May 2026 19:03:37 +0000 https://status.miurapay.cloud/#790feeba1750e746737d46102a89e27419b28129eb7a3d497ae2be02df890998 Ascend Payments API recovered https://status.miurapay.cloud/ Tue, 05 May 2026 19:03:20 +0000 https://status.miurapay.cloud/#1a7d4461e393316afb8781f11bbae9cbf7201a3e063db3394d8200e62abcce53 Ascend Distribution API went down https://status.miurapay.cloud/ Tue, 05 May 2026 19:03:19 +0000 https://status.miurapay.cloud/#790feeba1750e746737d46102a89e27419b28129eb7a3d497ae2be02df890998 Ascend Payments API went down https://status.miurapay.cloud/incident/873060 Tue, 21 Apr 2026 14:00:59 -0000 https://status.miurapay.cloud/incident/873060#2b520a4bb10af0ada251ddd05e08aa15e6a890081fc806a11a9da5d185cffab6 We will be deploying updates to the production environment as part of a planned maintenance window. These updates include new functionality and platform improvements. Impact: No downtime is expected. Services will remain available throughout the maintenance window. The system will be closely monitored during the deployment. https://status.miurapay.cloud/ Sun, 12 Apr 2026 06:50:36 +0000 https://status.miurapay.cloud/#6b95a3e9ca88803d78fc14b0c244aece5f837af527271f3d1cfe98fc67a1d817 Ascend Distribution API recovered https://status.miurapay.cloud/ Sun, 12 Apr 2026 06:50:18 +0000 https://status.miurapay.cloud/#6b95a3e9ca88803d78fc14b0c244aece5f837af527271f3d1cfe98fc67a1d817 Ascend Distribution API went down https://status.miurapay.cloud/incident/867009 Fri, 10 Apr 2026 04:00:27 -0000 https://status.miurapay.cloud/incident/867009#09e5861e9168704e65de39559e9fef86e9d3afc781dab73cad5a602ed3d7960e Maintenance work will be performed on services related to your environment. While downtime is not anticipated, brief service interruptions may occur. https://status.miurapay.cloud/ Wed, 01 Apr 2026 10:46:27 +0000 https://status.miurapay.cloud/#e18653e4f2e38fb859228c207a715e420c86c0b271a7277e36370e55651e6861 Ascend Distribution API recovered https://status.miurapay.cloud/ Wed, 01 Apr 2026 10:46:14 +0000 https://status.miurapay.cloud/#cbf5b9cb6459fe1645e9b24fa9abcf8e89de2c655843d9ad51b3e51c51ec011e Ascend Payments API recovered https://status.miurapay.cloud/ Wed, 01 Apr 2026 10:46:05 +0000 https://status.miurapay.cloud/#f56723768578cfc4f52805383e23eec31bf597ea39d43bc9a26b3bb5109f40fa Ascend Portal API recovered https://status.miurapay.cloud/ Wed, 01 Apr 2026 10:45:23 +0000 https://status.miurapay.cloud/#e18653e4f2e38fb859228c207a715e420c86c0b271a7277e36370e55651e6861 Ascend Distribution API went down https://status.miurapay.cloud/ Wed, 01 Apr 2026 10:45:14 +0000 https://status.miurapay.cloud/#cbf5b9cb6459fe1645e9b24fa9abcf8e89de2c655843d9ad51b3e51c51ec011e Ascend Payments API went down https://status.miurapay.cloud/ Wed, 01 Apr 2026 10:45:07 +0000 https://status.miurapay.cloud/#f56723768578cfc4f52805383e23eec31bf597ea39d43bc9a26b3bb5109f40fa Ascend Portal API went down https://status.miurapay.cloud/ Tue, 24 Mar 2026 19:06:13 +0000 https://status.miurapay.cloud/#a296c6367cc51f301d242c6bed9cc62be636fe027b93b6545113b34bc419188b Ascend Payments API recovered https://status.miurapay.cloud/ Tue, 24 Mar 2026 19:05:43 +0000 https://status.miurapay.cloud/#a296c6367cc51f301d242c6bed9cc62be636fe027b93b6545113b34bc419188b Ascend Payments API went down https://status.miurapay.cloud/incident/845310 Fri, 13 Mar 2026 04:00:41 -0000 https://status.miurapay.cloud/incident/845310#9a0c25d47f9803b5ef47c2589abcf5e76b5162756742214c01bf37d16aa18e49 While there is minimal expected downtime, we are sending this as a notice that work will be performed related to your services. https://status.miurapay.cloud/incident/845312 Fri, 13 Mar 2026 02:00:00 -0000 https://status.miurapay.cloud/incident/845312#ca73e1839378d64b2eaeb1c54142cc9d192680b4701b767df1bf151fc6878539 While there is minimal expected downtime, we are sending this as a notice that work will be performed related to your services. https://status.miurapay.cloud/incident/835086 Fri, 27 Feb 2026 10:42:00 -0000 https://status.miurapay.cloud/incident/835086#61506c33163542ec02fff1a78096e7d7bc73551b5e41e23b1f10cb149e967449 🚨 Production Incident Notification **Title:** Production Incident – RKI requests rejected due to temporary service constraint within the RKI provider’s platform **Date:** 27 February 2026 **Duration:** 26 February 2026 08:42 UTC – 27 February 2026 10:42 UTC (≈ 26h) **Status:** Mitigated (running on backup provider infrastructure) **Incident Summary** Starting at 08:42 UTC on 26 February 2026, terminals began experiencing errors when attempting to retrieve RKI keys via Ascend. The issue was caused by a temporary service constraint within the RKI provider’s platform, resulting in new RKI requests being rejected. The issue was identified on 27 February 2026 following investigation triggered by terminal error reports and support queries. **Impact** - Terminals attempting Remote Key Injection (RKI) during the incident window were unable to retrieve keys - Existing terminals already provisioned were not affected - No data loss or security impact occurred **Cause** The external RKI provider experienced a temporary service constraint affecting their primary RKI endpoint. This resulted in rejection of new RKI requests during the incident window. The provider returned application-level error responses indicating request rejection. These differed from the connectivity error conditions currently monitored by Ascend, and therefore did not immediately trigger automated alerts. Monitoring has since been expanded to detect these additional error conditions. **Resolution** The RKI service provider was contacted to investigate and restore full service. To restore operational continuity, Miura re-routed RKI traffic to the provider’s backup infrastructure. This mitigation was completed on 27 February 2026 at 10:42 UTC, after which RKI operations resumed. While operating on the backup infrastructure: - Response times may be slightly slower than normal - In some cases, for re-injections, retries may be required if an initial attempt fails The RKI provider is currently working to restore full service on the primary infrastructure, with an estimated recovery timeframe of 2–3 days. **Return to Primary Infrastructure** The RKI provider is currently working to restore their primary infrastructure, with an estimated recovery timeframe of 2–3 days. Once the provider confirms the primary endpoint is fully operational, Miura will perform validation testing and then switch traffic back from the backup server to the primary server. **Next Steps / Preventive Actions** - Monitoring has been extended to detect a broader range of provider-level error conditions, with alerts now configured in Miura internal monitoring channels - The Ascend status page will be updated to include dedicated monitoring of the RKI service - Miura is working closely with the RKI provider to: - Confirm root cause - Restore primary infrastructure - Ensure long-term service stability - Monitoring and alerting coverage is being reviewed to further strengthen early detection capabilities https://status.miurapay.cloud/incident/821729 Fri, 06 Feb 2026 10:53:00 -0000 https://status.miurapay.cloud/incident/821729#2268d41a19d2249a79c3537a25286b8b8303e8799577908b9ce0d763da3a0c33 🚨 **Production Incident Notification** **Title:** Production Incident – RKI endpoint unavailable **Date:** 6 February 2026 **Duration:** 05:28–10:53 UTC (≈ 5h 25m) **Status:** Resolved **Incident Summary** At 05:28 UTC, terminals started experiencing errors when trying to retrieve RKI keys via Ascend. The errors persisted until 10:53 UTC, at which point the service recovered without manual intervention. **Impact** - Terminals were unable to retrieve RKI keys during the incident window - No data loss was observed **Cause** The incident coincided with a planned maintenance window conducted by the external RKI service provider, scheduled from 05:00–08:00 UTC. Advanced notification of the scheduled maintenance should have been provided by Miura, 48 hours in advance of the scheduled window. This did not take place The service disruption extended beyond the planned maintenance window. At the time of writing, Miura is awaiting the RKI service provider’s incident report to confirm the root cause and explain the extended impact. **Resolution** The issue resolved automatically once the RKI service provider completed their maintenance activities. No changes or manual intervention were required on the Ascend side. **Next Steps / Preventive Actions** - Any future, planned, maintenance windows impacting any component in the contracted service, will be added to the Ascend maintenance schedule 👉 https://status.miurapay.cloud/maintenance - Wherever possible, maintenance notifications will be communicated at least 48 hours in advance - Customers can click “Get updates” on the maintenance page to start receiving notifications - Once received, the incident report will be reviewed to: - Confirm root cause - Validate whether additional mitigations or monitoring are required on our side https://status.miurapay.cloud/incident/817680 Wed, 04 Feb 2026 06:30:00 -0000 https://status.miurapay.cloud/incident/817680#b573b4e2b515e2eb6b16122891b4a9066629eac60f0b67879e8af2fb76a764cf We will be deploying updates to the production environment as part of a planned maintenance window. These updates include new functionality and platform improvements. Impact: No downtime is expected. Services will remain available throughout the maintenance window. The system will be closely monitored during the deployment. https://status.miurapay.cloud/incident/716982 Wed, 03 Sep 2025 11:00:00 -0000 https://status.miurapay.cloud/incident/716982#d0cbb061fde5f43d115759a13cff6b04eb5b8a22cc7c5dea72a0075172358b03 Maintenance completed https://status.miurapay.cloud/incident/716982 Wed, 03 Sep 2025 10:00:00 -0000 https://status.miurapay.cloud/incident/716982#612ab9e99074d3616adc266156b3517f8af9b70b8a67a73d3b679e12f0d37c2c We will be adding an additional server to our production environment to increase system resilience. Impact: No downtime is expected. Services will remain available throughout the maintenance window. This upgrade will ensure smoother recovery in case of hardware or service restarts. https://status.miurapay.cloud/incident/716981 Tue, 02 Sep 2025 09:44:00 -0000 https://status.miurapay.cloud/incident/716981#aadb91dc18a8fe5d249bfa61ade5a77615d6278c2fc0d90c91a2afce15f5a853 On 2 September 2025 at 06:32 SAST, the Portal API status endpoint was briefly unavailable (~36 seconds). The system recovered automatically, and no further action was required. We have identified that the issue occurred when one of our servers restarted, leaving limited capacity to run all services at once. Next Steps: We are adding additional capacity to prevent this from recurring.