asn.dev

Routing security

AS44123 TELAVOX

Hosting RIPE Content

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

Announcements

What this network originates

15 observed

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

PrefixRPKIIRRVantage points
130.117.193.0/24No ROANo IRR52
130.117.194.0/24No ROANo IRR52
130.117.204.0/24No ROAIRR other origin52
2a00:1690::/32No ROAIRR30
80.83.208.0/20No ROAIRR53
80.83.212.0/24No ROAIRR53
80.83.213.0/24No ROAIRR52
80.83.214.0/24No ROAIRR53
80.83.215.0/24No ROAIRR53
80.83.216.0/24No ROAIRR1
80.83.217.0/24No ROAIRR1
80.83.220.0/24No ROAIRR53
130.117.196.0/22No ROAIRR52
130.117.200.0/22No ROAIRR52
193.32.132.0/24No ROAIRR52

RPKI · ROAs

Route origin authorisations

0 ROAs

Signed statements by address holders that AS44123 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

22 objects · 8 not announced

Route objects naming AS44123 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
80.83.208.0/24RIPE—MNT-TELAV012021-03-29Not announced
80.83.209.0/24RIPE—MNT-TELAV012021-03-29Not announced
80.83.210.0/24RIPE—MNT-TELAV012021-03-29Not announced
80.83.211.0/24RIPE—MNT-TELAV012021-03-26Not announced
80.83.218.0/24RIPE—MNT-TELAV012021-03-29Not announced
80.83.219.0/24RIPE—MNT-TELAV012021-03-29Not announced
80.83.221.0/24RIPE—MNT-TELAV012021-03-29Not announced
130.117.205.0/24RADBRoute Registered for Cogent Communications Customer - Telavox ABMAINT-AS1742024-08-08Not announced
80.83.208.0/20RIPE+-------------------------------------------+MNT-TELAV012009-01-26Announced
80.83.212.0/24RIPE—MNT-TELAV012021-03-29Announced
80.83.213.0/24RIPE—MNT-TELAV012021-03-29Announced
80.83.214.0/24RADBTELAVOX CRQ000002316363MAINT-AS122522023-11-13Announced
80.83.214.0/24RIPE—MNT-TELAV012021-03-29Announced
80.83.215.0/24RADBTELAVOXCRQ000002316363MAINT-AS122522023-11-13Announced
80.83.215.0/24RIPE—MNT-TELAV012021-03-29Announced
80.83.216.0/24RIPE—MNT-TELAV012021-03-29Announced
80.83.217.0/24RIPE—MNT-TELAV012021-03-29Announced
80.83.220.0/24RIPE—MNT-TELAV012021-03-29Announced
130.117.196.0/22RADBRoute Registered for Cogent Communications Customer - Telavox ABMAINT-AS1742024-05-15Announced
130.117.200.0/22RADBRoute Registered for Cogent Communications Customer - Telavox ABMAINT-AS1742024-05-15Announced
193.32.132.0/24RIPE—MNT-NO-ERATE-12025-03-18Announced
2a00:1690::/32RIPETVX-SE-IPv6-NETMNT-TELAV012013-04-18Announced

IRR

AS-sets

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

AS-setWhereRelationship
AS-TELAVOXPeeringDBDeclared by the operator as its own set
AS-CITYLINKRIPELists AS44123 as a direct member
AS-KDDCUSTOMER2RADBLists AS44123 as a direct member
AS-RIKSNETRIPELists AS44123 as a direct member
AS-TDCNETNORIPELists AS44123 as a direct member
AS-TELAVOXRIPELists AS44123 as a direct member
AS-TELIANORWAY-CUSTRIPELists AS44123 as a direct member
AS-TMX-PERU-TRANSITRADBLists AS44123 as a direct member
AS-TOMBII-STHIXRIPELists AS44123 as a direct member
AS13335:AS-CUSTOMERSARINLists AS44123 as a direct member
AS16150:AS-CUSTOMERSRIPELists AS44123 as a direct member
AS30781:AS-JAGUAR-CUST-FRRIPELists AS44123 as a direct member
AS3246:AS-CUSTOMERSRIPELists AS44123 as a direct member

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