We have noticed a decrease in traffic from Cloudflare Peeing 2 (AS13335) (103.77.108.11) compared to the typical volume experienced on regular days.
And the traffic has been shifted to alternate peering.
It is important to note that our infrastructure is functioning without any reported issues.
We have promptly escalated this matter to Cloudflare and initiated communication with them to address the situation.
Rest assured, we will provide regular updates regarding the progress of...

We have noticed a decrease in traffic from Akamai PNI 1 (AS20940) (45.120.248.19) compared to the typical volume experienced on regular days.

And the traffic has been shifted to alternate peering.
It is important to note that our infrastructure is functioning without any reported issues.

We have promptly escalated this matter to Akamai and initiated communication with them to address the situation.

Rest assured, we will provide regular updates regarding the progress of resolving this...

The incident was initially caused by a device failure on Cloudflare’s side. Although the faulty router has been replaced, traffic restoration remains pending due to an ongoing issue with another major peering partner at the same data center.

Cloudflare has not provided an ETA for traffic normalization at this time.

Our network remains operational, with no issues identified on our end. We continue to coordinate with Cloudflare and will share further updates as they become available.

We have received a further update from the Google team regarding the ongoing impact in the Delhi (DEL) metro region.

Recovery remains dependent on the restoration of power and local conditions at the affected third-party facility. Google has confirmed that there is currently no confirmed restoration timeline.

At present, Google Peering 3 and Google PNI 1 remain affected, while other Google connectivity and traffic paths continue to recover and operate normally.

We are continuing to...