E2E Networks
We have identified the google DNS is not able to resolve. We are checking it further with our engineers and update on the same.
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
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
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.
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.
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.
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.
ANALYSIS & ROOT CAUSE: Soon after the issue was observed, the incoming traffic was mitigated on our network.
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.
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.
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.
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.
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.