Skip to content

Your looking glass lies about actual routing

Networking by bellaauc 3 replies 214 views
#1

Hello all — I've been troubleshooting an issue with a provider's looking glass (won't name names yet) and need some sanity checking.

The LG shows my prefix reachable via their preferred path. Great! But actual traffic from my monitoring at three locations takes completely different routes — higher latency, different AS path visible in traceroute, and packet loss the LG doesn't reflect at all.

I opened a ticket. Their response: "The looking glass runs on separate infrastructure and is not representative of production routing."

Did you test your restore? Wait, wrong checklist — let me make the right one:

- [ ] LG disclaimer mentions separate infra
- [ ] LG disclaimer mentions non-production paths
- [ ] Actual routing documented somewhere accessible

None of these were true. The LG page just says "Looking Glass" with a search box. No warning, no asterisk, no "for entertainment purposes only."

This feels misleading. Not asking for perfect parity, but "not representative" buried in a ticket response isn't transparency. Following 3-2-1 rule for data, but what's the rule for routing verification?

Has anyone else run into this? How do you handle provider LG tools you can't trust?

3-2-1 or you're already dead
#2

---
- observation:
- LG as debugging tool: compromised
- trust model: broken
- alternatives:
- RouteViews collectors
- Your own remote probes
- Peer direct session for verification
- NOTE: some providers run LG on "lab" routers with full table but different localpref
- WARNING: "not representative" often means "we dont want to maintain this"
- action:
- demand SLA amendment
- or: stop using LG for anything serious

indentation is not optional
#3

Just use your own probes skill issue if you trust provider LG in 2026. Their looking glass probably runs on some free tier oracle vm anyway. "separate infrastructure" = we bought a router on ebay and never patched it

oops: 0000 [#1] SMP
#4

I have server with this provider and I noticed same thing xd, traceroute from my box show different path than LG, I open ticket and they say "this is expected" xd, so this is normal? I thought I have misconfig on my side. Thank you for thread actually

Post a reply

You need an account to reply. Log in or register to join the conversation.

Post reply Preview Save draft