Past Incidents

This is to inform you about a scheduled upgrade activity on our core network switches.

Maintenance Date and window : 6th April 2022 from 0230 hsr to 0400 hsr IST

Downtime: Partial (Fluctuation in the Network for less than 120 sec)

Impact: There is a chance of network fluctuation for our few customers while performing the activity.

Few important impact points related to this maintenance activity

Myaccount Portal: Our E2E Myaccount portal will not be accessible during the downtime.

Compute nodes: There will be a disconnect of the network (both public and private) for a period of 2 minutes or less for all the compute nodes in the Noida (NCR) location.

Volumes (or BlockStorage): There will be a disconnect between the BlockStorage volumes and the nodes they are attached to which may cause I/O error while the volume is being accessed. We recommend verifying the accessibility of the BlockStorage volumes from the concerned node and trying unmounting and mounting the volume again if you face any issue in accessing it post activity. In case unmounting and mounting doesn’t make it accessible, try detaching and attaching the volume again post activity to get it functional again. Please refer here to know more about detaching and attaching BlockStorage volumes. We recommend you unmount the BlockStorage volumes before the activity and remount them once the activity is completed to avoid the aforementioned issues.

Object Storage: The buckets and objects will not be accessible during the downtime period.

We request you to take the above maintenance into consideration & plan your activities accordingly.

Note: If you have a cluster-based setup on your compute nodes, due to this network interruption between nodes, there could be a break in the cluster. We suggest you set it on a standalone mode so that you can resume sync between them post the activity is completed.

For example, if you have a PCS based cluster, DRBD cluster, Mongo Cluster, or any clusters, etc.

We regret the inconvenience caused to you in this regard & look forward to receiving your continued support. If you have any queries, please reach out to us at cloud-platform@e2enetworks.com

We are observing and also reported network reachability issue in our Delhi(NCR) region zone. We are investigating it currently and will keep you posted on further findings.

This is to inform you about a scheduled upgrade activity on our core network switches.

Maintenance Date and window: 8th March 2022 from 01:00 hrs to 05:30 hrs IST

Downtime: 5 minutes of network downtime

Impact: All the resources and services in Noida(NCR) Location will be facing network downtime for 5 min or less. In case of any unexpected challenges while performing the activity will extend the activity up to 10 min to revert back all the changes. All the resources and services will be up and running post the downtime period.

Few important impact points related to this maintenance activity

Myaccount Portal: Our E2E Myaccount portal will not be accessible during the downtime.

Compute nodes: There will be a disconnect of the network (both public and private) for a period of 5 minutes or less for all the compute nodes in the Noida (NCR) location.

Volumes (or BlockStorage): There will be a disconnect between the BlockStorage volumes and the nodes they are attached to which may cause I/O error while the volume is being accessed. We recommend verifying the accessibility of the BlockStorage volumes from the concerned node and trying unmounting and mounting the volume again if you face any issue in accessing it post activity. In case unmounting and mounting doesn’t make it accessible, try detaching and attaching the volume again post activity to get it functional again. Please refer here to know more about detaching and attaching BlockStorage volumes. We recommend you unmount the BlockStorage volumes before the activity and remount them once the activity is completed to avoid the aforementioned issues.

Object Storage: The buckets and objects will not be accessible during the downtime period.

We request you to take the above maintenance into consideration & plan your activities accordingly.

Note: If you have a cluster-based setup on your compute nodes, due to this network interruption between nodes, there could be a break in the cluster. We suggest you set it on a standalone mode so that you can resume sync between them post the activity is completed.

For example, if you have a PCS based cluster, DRBD cluster, Mongo Cluster, or any clusters, etc.

We regret the inconvenience caused to you in this regard & look forward to receiving your continued support. If you have any queries, please reach out to us at cloud-platform@e2enetworks.com