asn.dev

Routing security

AS402405 PAWPAYMENTS - PawPayments,

Unclassified ARIN

RPKI valid 100% 2 of 2 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

2 observed

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

PrefixRPKIIRRVantage points
94.249.204.0/24RPKI validIRR1
139.64.146.0/24RPKI validIRR54

RPKI · ROAs

Route origin authorisations

2 ROAs

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

PrefixMax lengthTrust anchor
94.249.204.0/24/24RIPENCC
139.64.146.0/24/24ARIN

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 · 0 not announced

Route objects naming AS402405 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
94.249.204.0/24RIPE—GHOSTNET-MNT2026-04-14Announced
139.64.146.0/24ARINPayment provider infrastructureMNT-PAWPA2026-10-09Announced

IRR

AS-sets

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

AS-setWhereRelationship
AS-OVHRIPELists AS402405 as a direct member
AS-TERRAHOSTRIPELists AS402405 as a direct member
AS30823:AS-AUROLOGICRIPELists AS402405 as a direct member
AS35661:AS-FRA01DERIPELists AS402405 as a direct member
AS56655:AS-GIGAHOSTRIPELists AS402405 as a direct member

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