Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

A deeper look into DataPasa: BGP Routing, Russian linked upstreams, and a Paraguayan individual

124»

Comments

  • @usuariomega said:

    https://abir.org.br/coca-cola-brasil-lanca-novas-embalagens/

    @deafcon said: This photo is kinda wild to me.

    It's brazilian portuguese.

    In Canada, we get a bonus 5ml.

    Thanked by 2usuariomega datapasa
  • darkmasterdarkmaster Member
    edited August 4

    Fair enough. A few things worth conceding on the record before this wraps up.

    Retracting:

    • Hop 8 (10.101.17.3, +6 ms) does not prove a tunnel. @Alyx is right that RFC1918 in inter provider transfer nets is normal, and latency shows distance, not topology. The tunnel exists, since @datapasa said so himself earlier, but not because of my traceroute.
    • RIPE object remarks are freetext. They are not part of RPKI or BGP filtering. Overstated that one.
    • Passive IX peering with Aeza, Rostelecom, MegaFon, VimpelCom is not the same as being upstream for them, and framing consumer ISP peerings as "high risk pipelines" was wrong. @uk_netshield asked for a single prefix where Netshield is upstream for Aeza. I checked RIS and HE.net myself. There is none visible. Withdrawn.

    What I still think is worth having on the record:

    Russian UBO, Belarusian origin, UK Ltd, prior Honduras "tax optimization" leg, HK acquirer, Paraguayan residency, German metal, single homed via a UK registered LIR. That is structurally the same fingerprint OFAC designated at Aeza International Ltd on 1 July 2025. I am not claiming @datapasa is Aeza. I am saying the shape of the setup is indistinguishable from the shape that got sanctioned, and most of that shape came from @datapasa's own answers in this thread, not from my forensics.

    For a cheap sandbox this is irrelevant. For anyone touching regulated data or long lived production it isn't. Everyone can decide their own risk tolerance.

    Thanks to @uk_netshield, @Alyx, @AS203446, @jsg for the technical corrections, and to @datapasa for actually engaging with the corporate history. That part I do appreciate.

    Thanked by 4Alyx zGato jsg forest
  • AlyxAlyx Member, Host Rep
    edited August 4

    @darkmaster Wow, I did not expect a response like this on LET.
    Credit where credit is due, I highly respect that you where open about the feedback.

Sign In or Register to comment.