asn.dev

Routing security

AS44746 SILA5-AS

Unclassified RIPE NSP

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

Announcements

What this network originates

5 observed

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

PrefixRPKIIRRVantage points
91.213.179.0/24No ROAIRR51
2a05:b880::/29RPKI validIRR30
91.202.156.0/22RPKI validIRR51
91.214.88.0/22RPKI validIRR51
185.19.252.0/22RPKI validIRR51

RPKI · ROAs

Route origin authorisations

4 ROAs

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

PrefixMax lengthTrust anchor
91.202.156.0/22/22RIPENCC
91.214.88.0/22/22RIPENCC
185.19.252.0/22/22RIPENCC
2a05:b880::/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

5 objects · 0 not announced

Route objects naming AS44746 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
91.202.156.0/22RIPESatli Primary RouteLDG44746-MNT2015-02-06Announced
91.213.179.0/24RIPEMain router Tranemo KommunMNT-IMS-ADMIN2009-08-21Announced
91.214.88.0/22RIPESatli Primary RouteLDG44746-MNT2015-02-06Announced
185.19.252.0/22RIPESatli Primary RouteLDG44746-MNT2015-02-24Announced
2a05:b880::/29RIPESat mainroutev6LDG44746-MNT2015-09-14Announced

IRR

AS-sets

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

AS-setWhereRelationship
AS-SHLABPeeringDBDeclared by the operator as its own set
AS-RIKSNETRIPELists AS44746 as a direct member
AS-SHLABRIPELists AS44746 as a direct member
AS-TELE2-SERIPELists AS44746 as a direct member
AS3246:AS-CUSTOMERSRIPELists AS44746 as a direct member

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