asn.dev

Routing security

AS42514 SIGNAL-AS Signal Service LLC

Unclassified RIPE Enterprise

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

Announcements

What this network originates

10 observed

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

PrefixRPKIIRRVantage points
2a02:2648::/29RPKI validIRR33
46.22.240.0/20RPKI validIRR56
89.232.180.0/22RPKI validIRR56
94.102.16.0/20RPKI validIRR56
95.141.176.0/20RPKI validIRR56
128.204.160.0/19RPKI validIRR56
153.80.172.0/22RPKI validIRR56
178.17.128.0/20RPKI validIRR56
185.12.84.0/22RPKI validIRR56
213.166.76.0/22RPKI validIRR56

RPKI · ROAs

Route origin authorisations

10 ROAs

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

PrefixMax lengthTrust anchor
46.22.240.0/20/20RIPENCC
89.232.180.0/22/22RIPENCC
94.102.16.0/20/20RIPENCC
95.141.176.0/20/20RIPENCC
128.204.160.0/19/19RIPENCC
153.80.172.0/22/22RIPENCC
178.17.128.0/20/20RIPENCC
185.12.84.0/22/22RIPENCC
213.166.76.0/22/22RIPENCC
2a02:2648::/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

10 objects · 0 not announced

Route objects naming AS42514 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
46.22.240.0/20RIPESIGNAL SERVICESIGNAL-MNT2010-12-01Announced
89.232.180.0/22RIPESIGNAL SERVICESIGNAL-MNT2022-02-02Announced
94.102.16.0/20RIPESIGNAL SERVICESIGNAL-MNT2008-10-23Announced
95.141.176.0/20RIPESIGNAL SERVICESIGNAL-MNT2009-06-08Announced
128.204.160.0/19RIPESIGNAL SERVICESIGNAL-MNT2011-10-12Announced
153.80.172.0/22RIPESIGNAL SERVICESIGNAL-MNT2026-04-28Announced
178.17.128.0/20RIPESIGNAL SERVICESIGNAL-MNT2010-03-22Announced
185.12.84.0/22RIPESIGNAL SERVICESIGNAL-MNT2012-12-05Announced
213.166.76.0/22RIPESIGNAL SERVICESIGNAL-MNT2023-07-12Announced
2a02:2648::/29RIPESIGNAL SERVICESIGNAL-MNT2018-09-26Announced

IRR

AS-sets

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

AS-setWhereRelationship
AS-SIGNALTVPeeringDBDeclared by the operator as its own set
AS-BLOCK-SETRIPELists AS42514 as a direct member
AS-BLOCKED-RURIPELists AS42514 as a direct member
AS-HURRICANERADBLists AS42514 as a direct member
AS-HURRICANEV6RADBLists AS42514 as a direct member
AS-KURSKNETRIPELists AS42514 as a direct member
AS-MF-MGSMRIPELists AS42514 as a direct member
AS-ROSTELECOMRIPELists AS42514 as a direct member
AS-SIGNALTVRIPELists AS42514 as a direct member
AS-SIGNALTV-V6RIPELists AS42514 as a direct member
AS3491:AS-CUSTOMERS-EURADBLists AS42514 as a direct member

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