Route Finder server took too long to respond

I have been trying to use the Route Finder to create a route that avoids certain airspaces/FIR’s like the Sudan HSSS, for instance, and I keep getting an error message the the “server took too long to respond”. Am I doing something wrong or is this a known site server issue?
Thank you.

Hi,

Unfortunately this happens in some cases. Avoiding airspaces has a higher chance of returning the error.

This isn’t a quick fix and will probably require a complete redesign of the Route Finder tool, not something that will come soon I’m afraid.

Note however that in many cases, one of the other Suggested Routes next to the Route section might already avoid the airspaces you need. I would normally try selecting from these routes first to see if one of them meets your requirements, and only use the Route Finder if not.

Best regards,

Hi,
I have another problem with this feature. When I do the flight from UUDD to SBBR, there is only one suggested route:
“POKA4M POKAG N858 VEPIS Y219 LAPKI N869 MULZA T174 KORUP Z220 KOBUS P31 RIKLU Z715 KULOK L984 SULUS Z12 COSJE T892 RIDSU Z114 DONAB Y180 DIK UN857 GIMER UT300 PON UN872 ERIGA UZ218 FUJTI LOTEE P600 STG N728 DEMOS UN741 VERAM Q205 TELMU UN741 LIDRO Q205 SNT UN741 NELSO N741 EDUMO UN741 ROLID UZ18 DIDUG”
, but this route includes the airway P600 with a highest altitude restriction FL245, it is not proper with my cruising A346, and when I want to use the route finder, it timeouted. How can I get a right route using the simbrief? Thank you!

Best regards,
Jack