I can't see any IP blocks being announced from CityNetHost's AS33785 in any of our BGP feeds, but there are plenty of announcements out of other Egyption ISPs, including AS24863 (LINKdotNET) who seem to be the single upstream transit provider for CityNetHost.
Looks like the BGP withdrawls happened about 07:40 UTC.
I cut them a lot of slack at the moment following all the unrest and government interventions in Internet, mobile networks etc. They provide great service when they're up, so I hope no-one reads too much into this thread... I'm certainly not blaming them for this outage until I hear different
1 1 ms 1 ms <1 ms 192.168.1.1
2 36 ms 33 ms 33 ms ip1-0-209-87.adsl2.static.versatel.nl [87.208.0.
3 38 ms 38 ms 38 ms ge-0-0-0-2120.ncr01rt.versatel.net [18.104.22.168
4 40 ms 38 ms 38 ms ge-2-1-0-0.ncr01ht.versatel.net [22.214.171.124]
5 42 ms 59 ms 43 ms ge2-2-0-620.br01sara.versatel.net [126.96.36.199]
6 41 ms 42 ms 43 ms ams17-core-1.tengigabiteth4-0-0.tele2.net [130.2
7 45 ms 43 ms 43 ms ams-core-1.tengige0-0-0-5.tele2.net [130.244.49.
8 41 ms 39 ms 40 ms ams13-core-1.tengigabiteth2-4.tele2.net [130.244
9 41 ms 40 ms 40 ms Te-3-2.car2.Amsterdam1.Level3.net [188.8.131.52]
10 40 ms 40 ms 40 ms ae-34-52.ebr2.Amsterdam1.Level3.net [184.108.40.206
11 49 ms 49 ms 49 ms ae-48-48.ebr2.London1.Level3.net [220.127.116.11]
12 48 ms 47 ms 47 ms 18.104.22.168
13 55 ms 55 ms 55 ms ae-45-45.ebr1.Paris1.Level3.net [22.214.171.124]
14 57 ms 57 ms 57 ms ae-1-51.edge1.Paris1.Level3.net [126.96.36.199]
15 128 ms 121 ms 121 ms LINKDOTNET.edge1.Paris1.Level3.net [188.8.131.52
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
From the brief investigation work I've done today, CityNetHost has a single upstream transit provider - LINKdotNET, who in turn have two upstream transit providers - Level3 and GlobalCrossing. You appear to be getting to the point where Level3 hand off to LINKdotNET in Paris, but then it appears that you are not making any progress on LINKdotNET's network.
The BGP re-announcements have reached you, hence why you can traceroute to the IP address without dying inside your own ISP's core network.
If you want to PM me the IP address that you are tracing to, I can compare your results to my own from our network in the UK and see what you should be expecting to see after hop 15.
Ultimately though, you are going to need to open a ticket with CityNetHost so that they can work with LINKdotNET to troubleshoot the underlying problem for you.
I can currently see announcements for 184.108.40.206/22, 220.127.116.11/22 and 18.104.22.168/22 coming out of AS33785 and can ping/traceroute to 22.214.171.124 from our network in the UK, which then goes via GlobalCrossing.
Does someone know reliable reasons for such downtimes?
Only CityNetHost will be able to tell you the exact reason for the problems that they have been experiencing, but they are single homed onto LINKdotNET, which means that they rely on a single internet service provider and thus there is an easily identifiable single point of failure.