# Static A static route is routing information that is manually configured on the routing device. As the name says, this kind of routing information is fixed in the routing table, so it does not change when there is a networking event or a change to the network.\ Witch means if a problem occurs, and there is another path a packet can be sent, it wont be until a worker manually does not change the route. *** ## Advantages and Limitations There are some advantages to static routing, and it can and should be used in some scenarios. However, static routing does have its limitations, and this is why [dynamic routing](https://bata-mladen.gitbook.io/bata-mladen/notes/services/routing-protocols/dynamic) was developed. For example, static routing uses very little CPU and memory resources, since no algorithms are run to determine the next hop. \ On small networks, where there are two or three routers, there are very few options for what route-specific packets should take. Implementing static routing is more than sufficient in such cases, and is often simpler to implement. However, as networks get larger, and potential paths to specific destinations become more numerous, static routing becomes more unwieldy to administrate. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://bata-mladen.gitbook.io/bata-mladen/notes/services/routing-protocols/static.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.