E2E Networks
All systems are operational

About This Site

E2E Networks Status shows the real-time operational status of E2E Networks cloud infrastructure and services.

Global

  • Billing Operational

Delhi

  • TIR Operational
  • Networking Operational
  • Nodes Operational
  • Load Balancers Operational
  • E2E Object Storage (EOS) Operational
  • Volumes Operational
  • DbaaS Operational
  • Auto Scale Operational

Chennai Region

  • Networking Operational
  • Nodes Operational
  • Load Balancers Operational
  • Volumes Operational
  • DbaaS Operational
  • Auto Scale Operational
  • TIR Operational
  • E2E Object Storage (EOS) Operational
Operational Performance Issues Partial Outage Major Outage

Past Incidents

Deployment - EOS | Resolved

The EOS deployment is completed. Please reach out to cloud-platform@e2enetworks.com

Deployment - EOS

We are undergoing maintenance activity for EOS services at 5.45 PM The operations on EOS from myaccount portal will be affected during the deployment. However, there won't be any effect on all direct operations

Partial Outage - EOS

We are investigating reports of access issues with EOS and are investigating this - The issue being diagnosed is of errors in uploading new objects. At the same time, existing objects were accessible 12:00 PM September 1 2021

  • The cluster has been stable after the fix and no recurrence of any upload issues on the EOS have been observed

    • September 1st 1:00 PM
  • The cluster has been stable for the last 12 hours and the fixes are made persistent

  • We had an issue in one of our EOS clusters where the cluster was slow in syncing. This led to errors in traffic to those particular nodes. We have deployed a temporary fix to speed up the sync...

    We are also optimising this further to ensure no recurrence of the issue and prioritising sync process IO to eliminate errors. We are currently monitoring the cluster after the fix and its working normally as expected.

    12:30 PM September 1 2021

  • Partial Network Outage - Resolved
    1. INCIDENT DETAILS:

    A. Observations The E2E’s monitoring team received lots of servers unreachable alerts.

    B. Immediate Actions Taken ( * ) • What action we have taken to identify the reported issue? Monitoring team immediately checked the alerts detail and identify that the issue with the selected pools. Therefore they immediately reported the issue to the network team. Network team verify all switches status and logs and did not find any internal issue in the network and reported the same issue to ISP team.

    1. ANALYSIS & ROOT CAUSE: ISP Team confirmed they are observing drop in the traffic and checking it further. They identify the issue with one of the ISP and opened a ticket with them. The identified ISP team confirmed the internal outage from their side and they will be sharing the final RCA in next 1-2 days.

    2. Actions Taken to Resolve the Issue: We have manually disabled the identified ISP in our network therefore all the traffic automatically shifted to another ISP and confirmed from the customers that issue is resolved for them post disabling the ISP in the network.

    Partial Network Outage

    The issues have been resolved by shifting the link to the alternate links and the traffic is normal.