asn.dev

Routing security

AS265141 RBT Internet

Residential LACNIC

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

Announcements

What this network originates

14 observed

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

PrefixRPKIIRRVantage points
143.255.12.0/23RPKI validNo IRR54
143.255.13.0/24RPKI validNo IRR52
143.255.14.0/24RPKI validNo IRR53
143.255.15.0/24RPKI validNo IRR53
170.0.216.0/22RPKI validNo IRR54
170.0.216.0/24RPKI validNo IRR52
170.78.152.0/22RPKI validNo IRR54
170.246.108.0/22RPKI validNo IRR54
189.90.24.0/22RPKI validNo IRR54
189.90.26.0/23RPKI validNo IRR54
2804:2b38::/32RPKI validIRR30
2804:2b38:d800::/37RPKI validIRR covering30
2804:2b38:e000::/37RPKI validIRR covering30
2804:2b38:e800::/37RPKI validIRR covering30

RPKI · ROAs

Route origin authorisations

26 ROAs

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

PrefixMax lengthTrust anchor
143.255.12.0/22/22LACNIC
143.255.12.0/23/23LACNIC
143.255.13.0/24/24LACNIC
143.255.14.0/23/23LACNIC
143.255.14.0/24/24LACNIC
143.255.15.0/24/24LACNIC
170.0.216.0/22/22LACNIC
170.0.216.0/23/23LACNIC
170.0.216.0/24/24LACNIC
170.0.218.0/23/23LACNIC
170.0.219.0/24/24LACNIC
170.78.152.0/22/24LACNIC
170.246.108.0/22/22LACNIC
170.246.108.0/23/23LACNIC
170.246.110.0/23/23LACNIC
189.90.24.0/22/24LACNIC
2804:2b38::/32/32LACNIC
2804:2b38::/33/33LACNIC
2804:2b38::/34/34LACNIC
2804:2b38:4000::/34/34LACNIC
2804:2b38:8000::/33/33LACNIC
2804:2b38:8000::/34/34LACNIC
2804:2b38:c000::/34/34LACNIC
2804:2b38:d800::/37/37LACNIC
2804:2b38:e000::/37/37LACNIC
2804:2b38:e800::/37/37LACNIC

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

1 objects · 0 not announced

Route objects naming AS265141 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
2804:2b38::/32RADBITX-TRITELECOMMAINT-AS186782023-11-13Announced

IRR

AS-sets

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

AS-setWhereRelationship
AS-8167-BGP-CUSTOMERSRADBLists AS265141 as a direct member
AS-8167_CUSTOMERSRADBLists AS265141 as a direct member
AS-ADYLNET-CUSTOMERSRADBLists AS265141 as a direct member
AS-CTBC-CUSTOMERS126RADBLists AS265141 as a direct member
AS-CTBC-TOOLS-2RADBLists AS265141 as a direct member
AS-E1-AUTOMATION-CUSTOMERRADBLists AS265141 as a direct member
AS-EMBRATELNETRADBLists AS265141 as a direct member
AS-HUGENET-CUSTOMERSRADBLists AS265141 as a direct member
AS-HURRICANERADBLists AS265141 as a direct member
AS-HURRICANEV6RADBLists AS265141 as a direct member
AS-MEGATELECOM-CUSTOMERSRADBLists AS265141 as a direct member
AS-SB-AUTOMATION-CUSTOMERRADBLists AS265141 as a direct member
AS-TELIUM-CUSTOMERSRADBLists AS265141 as a direct member
AS-UFINET-LATAM-BRASILRADBLists AS265141 as a direct member
AS53013:AS-CONERADBLists AS265141 as a direct member

RPKI from rpki-client, validated 2026-10-22 12:01 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-22. Cross-check on bgp.he.net.