A bad transit provider often shows its problems in latency before anything else. If you ask the right questions early, you can usually spot weak routing, congestion, and poor path diversity before the contract is signed.
The goal is not just to buy Internet access, but to buy stable paths to the networks your traffic actually needs to reach. That means looking past headline bandwidth and checking how the provider performs to the places that matter most.
What to check first
Latency should be one of your first filters, not an afterthought. A provider can offer a good price and still be a poor fit if its routes to major destinations are long, inconsistent, or congested.
Look for these warning signs:
- They talk mostly about bandwidth and price, but avoid discussing latency or route quality.
- They cannot show latency results to your target regions or major ISPs.
- Their answers about peering are vague, especially when you ask about the networks your users actually use.
- They avoid discussing peak-time performance or how latency behaves under load.
A provider with strong routing should be able to explain where latency is lowest, where it may rise, and why.
Questions to ask
Ask direct questions that force the provider to talk about real network behaviour, not sales language. The best answers are specific, measurable, and easy to verify.
| Question | What a good answer sounds like | Red flag answer |
|---|---|---|
| What is your average latency to major ISPs in my target region? | They give numbers, time ranges, and sample routes. | They say it “depends” and give no examples. |
| How do you measure latency and packet loss? | They describe monitoring, probes, and reporting. | They rely only on basic uptime claims. |
| What happens to latency during peak traffic hours? | They explain capacity planning and congestion control. | They claim latency is always the same. |
| Which peers matter most for my traffic? | They name the networks and explain why. | They avoid naming any specific paths. |
| Can I see traceroutes to my key destinations? | They provide real examples. | They refuse or send generic screenshots. |
If they cannot discuss latency in plain numbers, they probably have not built their network around performance.
Red flags before signing
A provider may still look good on paper while hiding poor latency performance. Watch closely for patterns that suggest the service will underperform once traffic starts moving.
- They oversell “global reach” but cannot explain route quality in your region.
- Their network story focuses on capacity only, with no mention of latency or jitter.
- They are vague about transit diversity and whether multiple paths are actually independent.
- They promise “low latency” but have no proof from active measurements.
- Their support team cannot explain why a route takes a specific path.
One especially important warning sign is a provider that treats latency as a marketing phrase instead of an operational metric. That usually means they do not track it seriously.
Simple buyer test
Before you sign, run a basic latency test from locations that match your actual users. Compare results across different ISPs, not just from a single office or cloud region. Ask for traceroutes, then check whether the path is short and direct or full of detours.
A good provider should make it easy to confirm:
- low and stable latency,
- predictable routing,
- and reasonable performance at busy times.
If the provider cannot pass that simple test before the contract, they are unlikely to improve after the contract.
Ready for a latency check before you sign?
If you want a quick review of your current IP transit options, send your topology and target regions to sales@shifthosting.com and get a practical latency-focused assessment before you sign.
