Use Case #1: TrackBGP Provides Global Visibility into Traffic Issues, Enabling Immediate Mitigation
- If you’re in Europe or North America, do you even know if your Asian or Latin American traffic is hijacked or accidentally diverted?
- Specifically, if you’re a US internet provider and one bad actor in S. Korea announces your prefix the effect might only be seen in South Korea.
- Blackholing of your content in another part of the world can happen. If it is a mistake (ISP makes a mistake) if you start to route traffic to that destination, the destination might drop all the traffic. This can happen purely by mistake, and if it is in another part of the world how would you know?
- Whether the cause of a bad actor or a fat-fingered mistake by you or another party, TrackBGP will alert you immediately.
- Instant alerts lead to quick mitigation of issues that would otherwise linger and cause significant service interruption or (in the case of bad actors hijacking traffic) even worse issues.
Use Case #2: Avoid Breaking Your Network Reachability
- Improper information due to a typo when updating a misconfiguration is far from uncommon.
- If you put in one prefix and try to announce that to the world, you might inadvertently get traffic you don’t expect, or render your network unreachable from the Internet.
- Accidentally announcing a very busy service, can lead to you being inundated with more traffic than your network can handle, effectively launching a DDOS attack against yourself.
- TrackBGP’s insights and alerts provides targeted data that allow you to mitigate this immediately.
Use Case #3: Immediately Mitigate Technical Errors Like Bogons or Martians
- Bogon or Martians prefixes should never be announced . TrackBGP monitors for these errors and policy misconfigurations.
- These errors may not be visible to you for some time.
- The second we tell you would know. We alert you.
Use Case #4: Quickly Fix Withdrawal-of-Route Mistakes
- What would happen if you mistakenly stopped announcing something that should still be active? Withdrawal of routes (effectively de-announcing) are common.
- The result is traffic that would “no-route to host” and be dropped.
- Withdrawals are common but at certain thresholds may indicate mistakes that TrackBGP will quickly and concisely alert you to.
Use Case #5: Communication with Other Networks for Quicker Mitigation
- If a network has accidentally caused you a BGP issue, do you have the proper connections to communicate with them?
- TrackBGP provides lines of communication with other TrackBGP customers.
- This important feature, enabling quicker positive outcomes, is unmatched by legacy BGP tools.
Use Case #6: Identify and Mitigate Problems Outside of Your Network
- If you have multiple transit providers for different users for different reasons (regional performance, price, etc.) there is great value in having insight to knowing your traffic matches your intent.
- Traffic can drop when links in the middle of your upstream providers have issues connecting with other networks.
- In many instances you wouldn’t learn about this until your customers start complaining. Greater BGP visibility can quickly mitigate a problem with transit issues outside of your control.
- TrackBGP not only fixes this via automation, but it knows what GOOD is supposed to look like for your network and tells you when that is not the condition. That is what TrackBGP does. It is such a basic thing, but it is invaluable.