Skip to content

Mini-guide: detecting your own route leaks before anyone else

Networking by PetraSuper 23 replies 1.1K views
#11

This. GDPR my ass but I still prefer EU path for EU prefix. Old habit.

#12

Finland is EU too, thank you very much. Hetzner Helsinki is solid.

#13

Hong Kong perspective: I check from Vultr Tokyo and Singapore both. APAC path can differ wildly from what you see in EU. Learned when my prefix leaked via one upstream only visible from Asia side.

#14

Following. Need to set this up for my side project.

#15

I automated alerts to Telegram bot. 15 minute cron, message when diff found. Wife hates my phone at night but only one leak in two years and I caught in minutes. Worth.

4 #16

Same here but Matrix instead of Telegram. Self-hosted, no phone number.

1 #17

Does anyone use IRR/RPKI as first line instead of active monitoring? I publish ROAs but still want external check.

#18

RPKI is must have but not same thing. RPKI stop others from announce your prefix, not stop you from leak wrong path. Both need.

boot anything, anywhere, anytime
#19

This. I have invalid ROA once from typo, RPKI would not save me from myself. Active monitoring catch my own mistake.

#20

What about PeeringDB? I check my ASN page sometimes but not automated.

Post a reply

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

Post reply Preview Save draft