asn.dev

Routing security

AS270442 G15NET LTDA

Residential LACNIC

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

Announcements

What this network originates

6 observed

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

PrefixRPKIIRRVantage points
200.14.124.0/22No ROANo IRR52
200.14.124.0/23No ROANo IRR15
200.14.126.0/23No ROANo IRR15
2804:6c0c::/32No ROANo IRR29
2804:6c0c::/33No ROANo IRR18
2804:6c0c:8000::/33No ROANo IRR18

RPKI · ROAs

Route origin authorisations

0 ROAs

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

No ROA names this AS as an authorised origin.

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

0 objects · 0 not announced

Route objects naming AS270442 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.

No route objects name this AS as origin.

IRR

AS-sets

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

AS-setWhereRelationship
AS-CTBC-CUSTOMERS233RADBLists AS270442 as a direct member
AS-CTBC-TOOLS-4RADBLists AS270442 as a direct member
AS-ITXBRRADBLists AS270442 as a direct member
AS-MEGATELECOM-CUSTOMERSRADBLists AS270442 as a direct member
AS-UFINET-LATAM-BRASILRADBLists AS270442 as a direct member
AS53013:AS-CONERADBLists AS270442 as a direct member

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