Past Incidents

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.

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

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

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, we observed the high DDoS alert on one of our network.

2. ANALYSIS & ROOT CAUSE: Soon after the issue was observed, the incoming traffic was mitigated on our network.

3. Actions Taken to Resolve the Issue: We have manually disabled the network of the relevant server in our network therefore all the traffic started to functional normally.

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.

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

3. Actions Taken to Resolve the Issue: ISP have suspended / blocked the network in the network therefore all the started to respond normally once ISP took the action from their end.

Maintenance activity is completed. Myaccount is operational now. In case of any issue, please reach out to our cloud team by sending an email to cloud-platform@e2enetworks.com

We are performing an emergency maintenance activity in backend starting from 10:00 PM to 11:00 PM dated 27th June 2021

Myaccount based operations like creation of new nodes/appliances, stop/start of nodes etc. will be affected during the period of maintenance. However, there won't be any affect on any of the existing customer servers/appliances/services. Thank you for your understanding.