I've used my fair share of Remote IXP's as I do not afford to use local ones. Only thing I'd do in your scenario is to prepend the announcement to the IXP.

Or use the IXP's communities if it has any, to lower the local preference of the route, or not export it to certain peers I don't want going over the IXP (ussualy 0,asn works for most)

Remote IXP's are a pain to manage, and for most production networks I'd suggest to just avoid them unless strictly necessary for some reason.

Regards,

Lungu Ștefan-Gabriel | AS205941.

From: Salvador Bertenbreiter <salvadorb@gmail.com>
Sent: Wednesday, January 7, 2026 6:54 PM
To: routing-wg@ripe.net
Subject: [routing-wg] Techniques to influence inbound (download) traffic across multiple IXPs with /24 prefixes

Hi everyone,

Hope you’re doing well. I’d like to ask how you approach inbound traffic engineering (download traffic) when you’re connected to multiple IXPs (some local, some remote) and you only have small prefixes (e.g., /24), so announcing more/less specifics isn’t really an option.

In that scenario, what methods have worked for you besides simple AS-path prepending (e.g., no prepend on local IX, prepend 1 on the closest remote IXP, prepend 2 on the next, etc.)?

Thanks in advance for any guidance or real-world examples.

--
Salvador