Incidents reported on status page for Playzor Technologies https://status.playzor.me/ https://d1lppblt9t2x15.cloudfront.net/logos/6c7d1581a41ecd17a1952451a82bad46.png https://status.playzor.me/ en https://status.playzor.me/ Thu, 16 Jul 2026 08:12:40 +0000 https://status.playzor.me/#1f798c9e11f3e578d45acf544da01b76f565f4f9facc254b8d251b7bece68c50 Payment Server went down https://status.playzor.me/ Sat, 04 Jul 2026 17:14:48 +0000 https://status.playzor.me/#27a7fdbab1bbdbf840dc3d47f703966b122137657de63d38bd4e07eda994441b playzor.me went down https://status.playzor.me/ Sat, 04 Jul 2026 17:13:40 +0000 https://status.playzor.me/#83545954e622f07b2729eff0511bab8835a57698986a70e2aaa0fe54418806a8 Central-7-Azure went down https://status.playzor.me/ Sat, 04 Jul 2026 17:13:09 +0000 https://status.playzor.me/#c5ce9ab4feef07a306ef34b680e875be548b7bd2be3aa8a2b28128a7f9fe3dd3 Sa-Singapore-Azure went down https://status.playzor.me/ Sat, 04 Jul 2026 17:12:57 +0000 https://status.playzor.me/#55595a04fa611001d3a81c9372904a03feb08a0ba50e74deaa45ad3cff298dd3 In-Mumbai8-Amazon went down https://status.playzor.me/ Sat, 04 Jul 2026 08:42:10 +0000 https://status.playzor.me/#da8d8eaae74d026501a05dab6f91fd3066e6d7e2be4464431f58725ab9d5a417 Kubernetes-Amazon went down https://status.playzor.me/ Sat, 04 Jul 2026 08:36:07 +0000 https://status.playzor.me/#2149427d0e05d2c932a6001dc91bfe1a7ac2857003fb6f221d11112c4b50d9fa Postgresql-PlanetScale went down https://status.playzor.me/incident/892981 Mon, 11 May 2026 22:30:00 -0000 https://status.playzor.me/incident/892981#8807512a4bd6ae01db153c27fed25e287e3e157078bb9098a46a9790309c5237 Maintenance completed https://status.playzor.me/incident/892981 Mon, 11 May 2026 20:30:00 -0000 https://status.playzor.me/incident/892981#6d423c9bce1322ccbd7e67e3e277ce5fd47cd9fbca22c0544a55d72da2e08b21 Infrastructure Maintenance Update Tonight between 2:00 AM – 4:00 AM IST, we’ll be working on major backend infrastructure improvements for Playzor. There will be no expected downtime during this maintenance window. All servers should remain online and operational while our team performs backend upgrades and optimizations. What we’re improving: • Connecting Playzor with larger-scale infrastructure systems • Strengthening proxy layers for higher traffic handling • Expanding Kubernetes (K8s) and Kafka infrastructure • Adding advanced backend worker optimizations • Improving rate limiting and overall platform stability • Deploying new CI/CD improvements for faster and safer updates We have also recently added 9 new servers dedicated to Kubernetes and Kafka management to improve scalability and performance under heavy load. These upgrades are focused on making Playzor stronger, faster, and capable of handling significantly more pressure without downtime. If you notice anything unusual during the update window, please contact our team or create a support ticket from the checkout/support page. — Playzor Infrastructure Team https://status.playzor.me/incident/841340 Thu, 05 Mar 2026 13:27:00 -0000 https://status.playzor.me/incident/841340#a5e21e043da799dd033511dcd408c64e4e5f32c2c45818553a9ca83f9a58ae59 Earlier today, our engineering team performed a brief backend maintenance procedure that required restarting several core services. During this process, the main landing page was intentionally taken offline for approximately 8 minutes to ensure a clean restart and prevent inconsistent behavior. This was not a system failure or major incident. The downtime was part of routine operational work while we were actively making adjustments on the backend infrastructure. All services have now been fully restored, and the platform is operating normally. We appreciate your patience while this short maintenance was completed. https://status.playzor.me/incident/841348 Thu, 26 Feb 2026 10:36:00 -0000 https://status.playzor.me/incident/841348#9e40687909630f88956d736b3561a48bff624c81988cc9a379b260dfbdbce02f Our engineering team recently deployed a major update to the checkout system on checkout.playzor.me. As part of this upgrade, we introduced several security improvements and backend enhancements to make the checkout process more secure, stable, and reliable. To safely apply these updates, the checkout page was temporarily taken offline for approximately 8 minutes. This downtime was intentional and controlled to ensure the new changes were deployed correctly. The update has now been successfully completed, and the checkout system is fully operational. We acknowledge that this update was deployed without a prior maintenance notice, and we sincerely apologize for the short disruption this may have caused. Going forward, any significant updates or maintenance windows will be announced at least 24 hours in advance to keep everyone informed. Thank you for your understanding and continued support.