asn.dev

Routing security

AS267800 AS267800 - TE.SA.M. PERU S.A

Unclassified LACNIC

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

Announcements

What this network originates

3 observed

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

PrefixRPKIIRRVantage points
45.172.8.0/24RPKI validIRR53
45.172.10.0/24RPKI validIRR53
45.172.11.0/24RPKI validIRR53

RPKI · ROAs

Route origin authorisations

3 ROAs

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

PrefixMax lengthTrust anchor
45.172.8.0/24/26LACNIC
45.172.10.0/24/26LACNIC
45.172.11.0/24/26LACNIC

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

3 objects · 0 not announced

Route objects naming AS267800 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
45.172.8.0/24LACNICLACNIC generated route for TE.SA.M. PERU S.AMNT-PE-TPSA14-LACNIC2025-04-26Announced
45.172.10.0/24LACNICLACNIC generated route for TE.SA.M. PERU S.AMNT-PE-TPSA14-LACNIC2025-04-26Announced
45.172.11.0/24LACNICLACNIC generated route for TE.SA.M. PERU S.AMNT-PE-TPSA14-LACNIC2025-04-26Announced

IRR

AS-sets

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

No as-set lists this AS directly.

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