> ## Documentation Index
> Fetch the complete documentation index at: https://docs.onefirewall.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Cloudflare Outage

# Service Impact Notification — Cloudflare Outage and OneFirewall Services

We are writing to update on the service impact caused by today’s outage at **Cloudflare, Inc. (Cloudflare)**. OneFirewall’s platform leverages Cloudflare as a CDN and edge-delivery layer for various public-facing components, and this outage temporarily affected some services.

***

## Background of the Outage

On **Tuesday, 18 November 2025**, Cloudflare experienced a global service incident that disrupted access to several major platforms, including **ChatGPT, X (formerly Twitter), Spotify, Canva**, and others.\
Cloudflare reported that its network — which supports an estimated **\~20% of the web** — encountered an *internal service degradation* triggered by a very large configuration file or unexpected traffic spike affecting its traffic processing pipeline.

Cloudflare also stated there is **no evidence of malicious activity**, and the root cause is still under review.

***

## Impact on OneFirewall Services

Thanks to the resilience of our backend threat-intelligence infrastructure, all **Core Threat Intelligence Services remained fully operational** throughout the incident.

However, because our **public UI and API** rely on Cloudflare’s CDN, customers experienced limited access during the outage.

* **Outage timeframe:** **\[Circa 6hours from 7am UTC]**
* During this window, customers were **unable to receive new IoC feeds** via the public API/UI.
* Once Cloudflare resolved the issue, **all services auto-restored** without any manual action required.

### Service Impact Summary

| Service Area               | Status             |
| -------------------------- | ------------------ |
| Online Documentation       | Impacted           |
| IoC Collection (ingestion) | Partially impacted |
| IoC Distribution (feeds)   | Partially impacted |
| On-Premises Instances      | **Not impacted**   |
| Run-Time Protection        | **Not impacted**   |

***

## What This Means for You

* **No action needed.** Your on-prem or hosted environments require no changes or manual intervention.
* **No data loss.** All IoCs generated during the outage were queued and delivered once connectivity returned.
* **No security degradation.** Real-time protection and backend threat-intelligence engines ran continuously.

***

## Mitigation Steps by OneFirewall

To further enhance resilience and reduce reliance on a single CDN provider, OneFirewall is implementing a **multi-CDN architecture**:

* Traffic will be balanced between **Cloudflare** and **Fastly**.
* Rollout will occur progressively over the **coming weeks**.

This significantly reduces the likelihood that a single provider outage can impact service availability.

***

## FAQ

**🔹 Do I need to do anything on my on-premises instance?**\
No. All systems have already returned to normal without intervention.

**🔹 Was any data, IoC, or feed information lost?**\
No. All feeds generated during the outage were held in queue and delivered automatically once services recovered.

**🔹 Did this outage impact my security coverage?**\
No. All run-time protection and threat-intelligence pipelines operated normally.

**🔹 Will this be prevented in the future?**\
We are mitigating this risk through **multi-CDN redundancy**, significantly reducing the chance of future impact.

***

If you have any questions, please contact your account manager or email **[support@onefirewall.com](mailto:support@onefirewall.com)**.

Thank you for your continued trust in OneFirewall to secure your environment.

**The OneFirewall Team**\
*OneFirewall Alliance Ltd.*