1. Home
  2. Case studies
  3. Cloudflare

Case study · Magento 2 and Cloudflare

100m+ automated requests. We stopped them reaching the store.

Repeated 503 errors made an ecommerce platform look like it had a server problem. The real issue was the volume of automated traffic hitting it. We traced the request patterns, identified more than 100 million automated requests and used Cloudflare to block the unwanted traffic before it reached the application.

100m+Automated requests identified
503Repeated service failures
CloudflareTraffic filtered at the edge
StablePlatform back under control
Client
Ecommerce retailer (name withheld)
Platform
Magento 2
Protection
Cloudflare
Engagement
Diagnosis and protection

The situation

It looked like a server problem. The traffic told a different story.

The store was suffering repeated 503 errors and periods of instability. From the outside, it was easy to assume the answer was more server resource, but that would only have treated the symptom.

We investigated the request volume and patterns reaching the platform. That analysis exposed more than 100 million automated requests putting unnecessary pressure on the application and infrastructure.

Instead of simply scaling the server, we used Cloudflare to stop the unwanted traffic before it reached the store, while keeping legitimate customer traffic moving normally.

The problem

  • Repeated 503 errors affecting site availability
  • Huge volumes of automated traffic reaching the application
  • Legitimate and unwanted requests competing for the same resources
  • No value in simply adding more server capacity without fixing the cause
  • Customer journeys at risk whenever the platform became unstable
  • The source of the pressure needed proving before action was taken
“We did not solve this by throwing more server resource at it. We found what was hitting the site, stopped the unwanted requests before they reached the application and brought the platform back under control.”
Resolve Beyond technical team · Cloudflare traffic protection

The full timeline

From repeated 503s to traffic under control.

The important part was finding the real source of the pressure before changing the infrastructure around it.

  1. The issue

    Repeated 503 errors and an unstable store

    The platform was intermittently unavailable, creating the impression that the server itself was simply underpowered.

  2. Investigation

    We traced what was actually reaching the application

    Request volumes and patterns were analysed so we could separate normal customer behaviour from automated traffic.

  3. The finding

    More than 100 million automated requests identified

    The scale of the unwanted traffic explained why the application was being put under so much pressure.

  4. Cloudflare

    The unwanted traffic was stopped before Magento

    Cloudflare rules were configured around the traffic we had identified, filtering unwanted requests before they consumed application resources.

  5. The outcome

    The store stabilised without a rebuild

    Once the automated pressure was removed, the platform returned to a stable position and could be monitored from a much cleaner baseline.

100m+automated requests
503errors affecting availability
1Cloudflare protection layer
0rebuilds needed

The problem was not solved by adding more capacity. It was solved by identifying the traffic that did not belong and preventing it from reaching the platform in the first place.

What was at stake

  • Repeated 503 errors disrupting the store
  • Automated traffic consuming application resources
  • Customer journeys affected by instability
  • Costly infrastructure changes that would not fix the cause
  • 100m+ automated requests identified
  • Unwanted traffic blocked before Magento
  • Legitimate traffic kept moving normally
  • Platform stability restored
More server power would not have fixed the cause.

The right diagnosis meant we could stop the pressure at the edge, instead of simply giving it more infrastructure to consume.

Talk to us about Cloudflare

The diagnosis

Not a hosting upgrade. A traffic problem solved at the right layer.

Repeated 503s can make infrastructure look like the obvious culprit. In this case, scaling the server would have meant paying for more capacity while the same automated traffic continued to consume it.

By tracing the request behaviour first, we could act on the real problem. Cloudflare became the protection layer in front of the application, filtering unwanted requests before they reached Magento and reducing the pressure where it mattered.

Find the cause before changing the infrastructure

The biggest win was not just blocking traffic. It was proving what was causing the instability, then applying the fix at the point where it could make the biggest difference.

After the fix

Cloudflare became part of the protection around the platform.

Once the unwanted automated traffic was blocked, the store had a much cleaner baseline to operate from and the repeated pressure behind the 503 errors was removed.

The same approach gives us a clearer way to respond when traffic changes again: monitor what is reaching the platform, understand the pattern and adjust protection without immediately reaching for a bigger server.

Cloudflare support can include

  • Traffic analysis and investigation
  • Security and traffic filtering rules
  • DNS, SSL and caching configuration
  • Monitoring and rule refinement
  • Protection around existing platforms, not only new builds
View support options →

Questions

Cloudflare and bot traffic FAQs

Why does my site keep showing 503 errors?

A 503 means the server can't handle the request at that moment. It can be under-sized hosting, but as this case shows, it is often traffic that shouldn't be there at all. We check what is reaching the platform before recommending more capacity.

Can you set up Cloudflare on our existing store?

Yes. We add Cloudflare in front of existing Magento, Shopify, WooCommerce and WordPress platforms, including DNS, SSL, caching and security rules, without rebuilding the site.

Will blocking bots affect real customers or Google?

Rules are built around the traffic we identify, so legitimate customers and search engines keep getting through. We monitor after every change and refine the rules if anything needs adjusting.

Our site is unstable right now. What should we do?

Call 01429 555088 or report a critical issue. Retainer clients get a developer on a critical issue within the hour.

More questions? See our full FAQ →

Talk to us

Traffic hitting harder than it should?

Find out what is really reaching your platform. We can investigate unusual traffic, your Cloudflare configuration and the pressure on your application before you spend money solving the wrong problem.

Critical issue right now? Get a senior developer within the hour →

Hartlepool, UK. Working with clients across the UK, US, Middle East and Asia.