asn.dev

Routing security

AS265640 AS265640 - MUNICIPALIDAD DE TANDIL

Unclassified LACNIC

RPKI valid 100% 1 of 1 announcements
RPKI invalid 0 none
No ROA 0 not covered by any ROA
IRR registered 100% 0 missing · 0 other origin
ROAs 2 authorising this AS

Announcements

What this network originates

1 observed

Every prefix observed with AS265640 as its origin, checked against RPKI and the IRR. Problems sort first.

PrefixRPKIIRRVantage points
170.246.78.0/24RPKI validIRR51

RPKI · ROAs

Route origin authorisations

2 ROAs

Signed statements by address holders that AS265640 may originate these prefixes, up to the maximum length shown.

PrefixMax lengthTrust anchor
170.246.78.0/24/24LACNIC
2801:1c:d000::/48/48LACNIC

ROA-based and RPKI-valid-only prefix lists for routers are on asn.ipinfo.app.

RPKI · ASPA

Declared transit providers

No ASPA record This network has not published an ASPA object. ASPA lets a network sign the list of its transit providers, so routers can reject paths that route through anyone else (route leaks). Only a few thousand networks publish one so far, so its absence is normal.

IRR

Registered route objects

2 objects · 1 not announced

Route objects naming AS265640 as origin, across RADb, the RIR registries, ALTDB and NTTCOM. Objects that are registered but not announced come first: a stale object lets anyone who can spoof this origin through an IRR-built filter.

PrefixSourceDescriptionMaintainerChangedRouting
2801:1c:d000::/48LACNICLACNIC generated route6 for MUNICIPALIDAD DE TANDILMNT-AR-MUTA1-LACNIC2026-05-19Not announced
170.246.78.0/24LACNICLACNIC generated route for MUNICIPALIDAD DE TANDILMNT-AR-MUTA1-LACNIC2026-05-19Announced

IRR

AS-sets

The as-set is what upstreams expand to build this network's customer filter. Sets that list AS265640 directly show who expects to carry it.

AS-setWhereRelationship
AS-E1-AUTOMATION-CUSTOMERRADBLists AS265640 as a direct member
AS-SILICA-AR-CUSTOMERSRADBLists AS265640 as a direct member
AS64103:AS-MEMBERSRADBLists AS265640 as a direct member

RPKI from rpki-client, validated 2026-11-08 13:05 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-11-08. Cross-check on bgp.he.net.