Current incidents
We would like to inform you that we have observed a degradation in traffic from Microsoft Peering Service 1 (45.120.251.137).
Please note that our infrastructure is operating normally, with no reported issues. All traffic has been successfully rerouted and is being delivered via alternative Microsoft nodes. Therefore, there should be no disruption to your services.
We have promptly escalated this matter to Microsoft and initiated communication with their team to investigate and resolve the...
We have noticed a decrease in traffic from Akamai AANP compared to the typical volume experienced on regular days.
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 issue.
We have noticed a decrease in traffic from Cloudflare Peeing (AS13335) (38.10.0.47) compared to the typical volume experienced on regular days.
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 resolving this issue.
We have noticed a decrease in traffic from Yahoo Peering Service (AS23926) compared to the typical volume experienced on regular days.
It is important to note that our infrastructure is functioning without any reported issues.
We have promptly escalated this matter to Yahoo Peering Service (AS23926) and initiated communication with them to address the situation.
Rest assured; we will provide regular updates regarding the progress of resolving this issue.
Again, 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.
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 resolving this issue.
We have received confirmation from Amazon that the loss of connectivity on the Amazon peering session at Delhi GK location is caused by a physical facility incident affecting infrastructure at the site. As a result, the affected peering service is currently unavailable.
Amazon has advised that remediation efforts are underway and the issue is being treated as a priority. Traffic will be restored once the impacted facility infrastructure has been recovered.
At this time, Amazon has not...
We have received an update from the Google team that they are still actively working on it. We are closely monitoring the situation. At this time, no estimated time of resolution (ETR) has been provided. We will share further updates here as soon as more information becomes available.
Past Incidents
We have been informed by Facebook Inc. (AS32934) of a scheduled maintenance activity on their network.
Affected Peers:
IPv4 Neighbor: 103.77.108.3
IPv6 Neighbor: 2001:df2:1900:2::3
Maintenance Window:
Start Time: 25 June 2026, 21:45 IST
End Time: 26 June 2026, 01:45 IST
Duration: 4 hours
During the scheduled maintenance window, a temporary interruption in connectivity with the above-mentioned Facebook peering sessions may be experienced. Traffic is expected to reroute through...
Traffic has been recovered
We noted a significant decrease in network activity within the Extreme IX infrastructure, primarily attributed to human error during the implementation of network configuration changes.
This unfortunate event adversely impacted all affiliated members and content providers physically connected within Nxtra Data Center DC-1 and DC-2.
The following content providers were affected:
Cloudflare (AS13335)
IPv4 Peer: 45.120.251.38
IPv6 Peer: 2001:df2:1900:3::38
Akamai Technologies (AS20940)
...
Traffic has been recovered
A vendor-scheduled maintenance activity will be carried out on the NLD Delhi–Mumbai link during the above maintenance window.
Customer Impact:
Customers using vPort services over the NLD Delhi–Mumbai link may experience a service interruption of up to 20 minutes during the maintenance window.
Our teams will monitor the activity closely and provide updates as required.
Start Time: 25 June 2026, 00:00 IST
End Time: 25 June 2026, 03:00 IST
Extreme Port Status