Level 3 smokes?
Our diagnostic system for the entire IT infrastructure, built on the basis of Nagios , has just sent SMS to all admins with messages that the DNS service has died. After a brief debriefing, it turned out that the google.com, google.com.ua, google.com, google.de, google.jp domains were not resolved (others were not checked).
Is it only here or has anyone noticed?
Interestingly, is it a communication problem , aplanned shutdown of all (?) Data centers or an organized (unorganized) DDoS attack?
UPD: Apparently (and by minus too) servers work but not from all directions. So the route from ip-ping.ru to 74.125.127.100 (google.com) runs up to 216.239.46.6, after which it ends, but the ping to 74.125.127.100 goes. Ping does not come from us, but the route ends at 4.68.105.34 (ae-21-52.car1.Seattle1.Level3.net) - this address is not in the route from ip-ping.ru. we go from different directions. Apparently the same direction fell)
UPD2: Domain Statistics:
It looks like Google is not to blame, but some (fallen?) Directions.
Who else has this ghkm ... a feature?
UPD3: Looks like the culprit is found. The main channel of our provider looks at Frankfurt. Having examined the traces on the “lying” resources, I found out that very often addresses from the 4.68.23.x subnet are encountered. Apparently the problem is in them. Looks like Level 3 Communications, Inc. having problems with the equipment.
')
UPD4: Earned!)
Citizens minus, even if they said what they disagree.
Is it only here or has anyone noticed?
Interestingly, is it a communication problem , a
UPD: Apparently (and by minus too) servers work but not from all directions. So the route from ip-ping.ru to 74.125.127.100 (google.com) runs up to 216.239.46.6, after which it ends, but the ping to 74.125.127.100 goes. Ping does not come from us, but the route ends at 4.68.105.34 (ae-21-52.car1.Seattle1.Level3.net) - this address is not in the route from ip-ping.ru. we go from different directions. Apparently the same direction fell)
UPD2: Domain Statistics:
| Domain | IP | Open line with ip-ping.ru | Clipping path from us |
|---|---|---|---|
| google.com | 74.125.127.100 | 209.85.255.194 | 4.68.105.34 (ae-21-52.car1.Seattle1.Level3.net) |
| google.com.ua (.ru) | 72.14.221.104 | - | 4.68.23.139 (ae-3-89.edge3.Frankfurt1.Level3.net) |
| google.de | 216.239.59.104 | - | 4.69.139.98 (ae-21-52.car1.London1.Level3.net) |
| google.jp | 72.14.203.104 | 209.85.241.162 | 61.213.169.154 (xe-4-1.a17.tokyjp01.jp.ra.gin.ntt.net) |
It looks like Google is not to blame, but some (fallen?) Directions.
Who else has this ghkm ... a feature?
UPD3: Looks like the culprit is found. The main channel of our provider looks at Frankfurt. Having examined the traces on the “lying” resources, I found out that very often addresses from the 4.68.23.x subnet are encountered. Apparently the problem is in them. Looks like Level 3 Communications, Inc. having problems with the equipment.
')
UPD4: Earned!)
Citizens minus, even if they said what they disagree.
Source: https://habr.com/ru/post/63808/
All Articles