asn.dev

Routing security

AS203367 ASN-SAILWEB SAILWEB SRL

Unclassified RIPE

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

Announcements

What this network originates

4 observed

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

PrefixRPKIIRRVantage points
2a0d:2740::/29RPKI validNo IRR1
193.142.196.0/22RPKI validNo IRR52
2a07:2c0::/29RPKI validIRR30
185.137.84.0/22RPKI validIRR52

RPKI · ROAs

Route origin authorisations

4 ROAs

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

PrefixMax lengthTrust anchor
185.137.84.0/22/22RIPENCC
193.142.196.0/22/22RIPENCC
2a07:2c0::/29/29RIPENCC
2a0d:2740::/29/29RIPENCC

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 AS203367 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
185.137.84.0/22RIPESailweb SrlIT-SAILWEB-1-MNT2024-02-14Announced
2a07:2c0::/29RIPESailweb SrlIT-SAILWEB-1-MNT2024-02-19Announced

IRR

AS-sets

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

AS-setWhereRelationship
AS-AUXILIUMRIPELists AS203367 as a direct member
AS-RETELITRIPELists AS203367 as a direct member
AS-SAILWEBRIPELists AS203367 as a direct member

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