Egypt fell off the Internet at 22:30 GMT 27 Jan 2011:
Figure 1: Egypt 27 January 2011
Ellipses in these graphs represent servers; boxes represent routers; and arrows show the varying connectivity among them: green is fast, yellow is slow, orange is slower, and red is very slow. Colors of boxes reflect ownership of parts of the network. Times are GMT.
The red octagons are six destinations InternetPerils was watching. None of them responded directly to probes, but routers along the way to each of them normally responded along paths well into Egypt.
Normal RoutingEverything is still normal at 22:15 GMT 27 Jan 2011 (00:15 28 Jan 2011 Egyptian time), as shown in Figure 2:
Failing RoutingFifteen minutes later at 22:30, half of the destinations are unreachable, as shown in Figure 3:
Grey lines to the three top red octagons indicate that nothing is responding any farther along paths to those destinations, which are:
websrv.ahram.org.eg 184.108.40.206The last router responding is 220.127.116.11, on Cogent in Austin, as shown in Figure 4; not very close to Egypt.
There is also still an attempt to route to mail.ouda.org.eg from one camera
through 18.104.22.168, on Verizon in Boston,
as shown in
Figure 5; also not very close to Egypt.
One destination, www.assembly.gov.eg 22.214.171.124, still normally routes through 126.96.36.199 in Egypt at 22:15, as shown in Figure 6:
At 22:30, through one path it gets last response from 188.8.131.52, on Verizon near Dulles Airport in Virginia, as shown in Figure 7:
This rapid loss of routing matches what RIPE saw in BGP route announcements from Egypt dropping to zero between 22:15 and 22:45 27 Jan 2011.
Last Stop GizaThese last two destinations are routed normally through tedata.net in Giza until 22:30: