There are ongoing Incidents
This is Extreme Port's status page, here you'll find the current status and incident history of Extreme Port.
Don't agree with what's reported here? Contact us at support@x3me.net.
Delhi Minor incident
Delhi Peering Minor incident
Delhi Peering
60 days ago % Uptime Today
Delhi Network Operational
Delhi Network
60 days ago % Uptime Today
Mumbai Minor incident
Mumbai Peering Minor incident
60 days ago % Uptime Today
Mumbai Network Operational
60 days ago % Uptime Today
Chennai Operational
Chennai Peering Operational
60 days ago % Uptime Today
Chennai Network Operational
60 days ago % Uptime Today
Bangalore Operational
Bangalore Peering Operational
60 days ago % Uptime Today
Bangalore Network Operational
60 days ago % Uptime Today
Kolkata Operational
Kolkata Peering Operational
60 days ago % Uptime Today
Kolkata Network Operational
60 days ago % Uptime Today
Hyderabad Minor incident
Hyderabad Peering Minor incident
60 days ago % Uptime Today
Hyderabad Network Operational
60 days ago % Uptime Today
Pune Operational
Pune Peering Operational
60 days ago % Uptime Today
Pune Network Operational
60 days ago % Uptime Today

Current incidents


Minor incident Traffic degradation of Meta (Facebook) Peering 2 (AS32934)
[Issue]

We have observed a reduction in traffic from Meta (Facebook) Peering 2 (AS32934) (103.77.110.7) compared to the normal traffic volume typically received. The affected traffic has automatically shifted to alternate peering paths.

Please note that our infrastructure is operating normally, and no issues have been identified within our network. All traffic is being successfully delivered through Meta’s alternate nodes, and no service interruption is expected.

This matter has been promptly...

Minor incident Traffic degradation of Global Network Management Inc (Telegram)[AS44907]
[Issue]

We are observing that Global Network Management Inc (Telegram) traffic is currently unreachable for users on most Indian ISPs. This is due to a temporary restriction imposed by the Ministry of Electronics and Information Technology (MeitY), effective until June 22, 2026, as per public advisories.

Official source:- https://timesofindia.indiatimes.com/technology/tech-news/government-blocks-telegram-till-june-22-but-meitys-second-order-targeting-neet-ug-leaks-is/articleshow/131762730.cms

...

Minor incident Traffic degradation of Amazon Peering 1[AS16509]
[Investigating]

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...

Minor incident Traffic degradation of Google Peering 1, 2 & 3 + GooglePNI 1 & 2 (AS15169)
[Monitoring]

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.

Scheduled maintenance Planned Maintenance - Google LLC [AS15169] from 2026-06-05 09:20 IST
[Scheduled]

We have been duly informed by Google (AS15169) regarding an ongoing maintenance activity they will be conducting.

Neighbor IPv4 Address(es):
45.120.248.10
45.120.248.20
45.120.248.31

Neighbor IPv6 Address(es):
2001:df2:1900:1::10
2001:df2:1900:1::20
2001:df2:1900:1::31

Details:
Start Time: 5 June 2026, 9:20:13 AM IST
END time: Not shared by Google

During the scheduled maintenance window, it is anticipated that there will be a temporary interruption in services.

Google systems...

% Uptime
60 days ago Today
Incident & maintenance history
This page is automatically updated every 60 seconds