How luroConnect restored stability and powered growth for Tennishub.in
India's top-rated tennis store kept going down with recurring Cloudflare 524 timeouts. luroConnect found the root cause, eliminated the outages, and reversed an 18-month decline in orders.
- Industry
- Tennis e-commerce
- Store
- tennishub.in
- Online since
- 2013
- Platform
- Magento
- Infrastructure
- AWS (customer-owned account)
- Go-live
- May 2025
- Development partner
- Techsevin
Results at a glance
- +39%
- Orders growth since go-live vs pre-luroConnect 3-month avg
- 1,038
- Peak monthly orders Jan 2026
- 11
- Months on platform May 2025 – Mar 2026
About Tennishub.in
Tennishub.in is India's top-rated tennis e-commerce website, operating since 2013. A destination for professionals and amateurs alike, it carries premium brands including Wilson and Yonex. Their distinctive offering includes custom stringing to a customer's chosen tension, along with preferred grip and logo — all as part of a single purchase.
The challenge
The site was hosted on AWS and managed jointly by an in-house team and agency partner Techsevin. A recurring problem had emerged: the website would frequently go down with a Cloudflare 524 timeout error, requiring a full server reboot to restore service. Every outage meant lost orders and frustrated customers.
Techsevin had attempted to mitigate the problem by blocking traffic from countries outside India, since Tennishub's primary market is domestic. However, this approach backfired: Google's crawlers were also being blocked, threatening search rankings and organic visibility.
The team needed a solution that could:
- Eliminate or dramatically reduce site downtime
- Identify the root cause of the recurring failures
- Protect the site from malicious traffic without impacting legitimate crawlers
- Give the development team actionable diagnostic information
The luroConnect approach
Techsevin, a luroConnect partner, brought Tennishub.in to luroConnect. The first step was to onboard Tennishub.in onto the luroConnect stack, deployed within the client’s own AWS account. With the site running on our stack, the team then examined the nginx logs and identified bursts of anomalous traffic that correlated with each outage event, confirming a denial-of-service pattern familiar from prior engagements.
Phase 1 · BOT detection & blocking
luroConnect began observing and blocking BOTs, using regular expressions to target specific malicious user agents. Hit counts from these BOTs dropped significantly — but sporadic downtime continued.
Phase 2 · Memory & CPU investigation
Analysis revealed that some outages coincided with Out of Memory (OOM) alerts in php-fpm. luroConnect reconfigured php-fpm with higher memory limits, which eliminated the OOM errors but surfaced a new constraint: CPU exhaustion. PHP access and slow logs showed that certain php-fpm requests were not completing and continued consuming high CPU. To maintain uptime while debugging, additional servers were immediately provisioned using luroConnect's horizontally scalable architecture.
Phase 3 · Root cause identification
Using php-fpm slow log traces and luroConnect's ability to cross-reference nginx, PHP access, and slow logs, individual problem requests were isolated. These hits — consuming disproportionate time and memory — were arriving in clusters, triggering the OOM conditions. A specific cart-building defect was identified: certain cart contents caused the collectTotals() method to fire multiple times within a single stack trace, due to callbacks from multiple vendor plugins. Affected users were left in a broken session they could not recover from.
Phase 4 · Stabilisation & protection
While the development team addressed the underlying code, luroConnect implemented a 60-second request timeout. Individual problem requests could no longer consume enough resources to crash the server. Affected visitors still saw an error on that specific request, but the website remained fully available for all other users — eliminating the outage pattern entirely.
“Hosting with luroConnect feels different. They are able to give us information to help debug such issues that no hosting provider does. For debugging this problem we may have to change code to write logs to understand the problem. Even then, we may not have come to these observations as quickly as luroConnect did.”
Mehul Goswami Techsevin
Results: order growth since go-live
The business impact of platform stability has been measurable. The chart below shows monthly order volumes from October 2023 through March 2026. The downward trend in the 18 months before go-live — driven directly by the outage problem — reversed once Tennishub.in moved to luroConnect in May 2025.
“We used to frequently get complaints about slow site. Once we have onboarded on luroConnect, our support calls have reduced and we can actually see a trend in increasing sales that we hope continues. I would highly recommend luroConnect to host a Magento website.”
Ashutosh Dave eCommerce Manager, Tennishub.in