Routing security

AS34066 TELAPPLIANT-AS

Unclassified RIPE NSP

RPKI valid 100% 11 of 11 announcements

RPKI invalid 0 none

No ROA 0 not covered by any ROA

IRR registered 100% 0 missing · 0 other origin

ROAs 6 authorising this AS

Announcements

What this network originates

11 observed

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

Prefix	RPKI	IRR	Vantage points
77.240.48.0/20	RPKI valid	IRR	51
77.240.48.0/21	RPKI valid	IRR	53
77.240.56.0/21	RPKI valid	IRR	53
78.158.48.0/20	RPKI valid	IRR	51
78.158.48.0/21	RPKI valid	IRR	53
78.158.56.0/21	RPKI valid	IRR	53
185.158.56.0/22	RPKI valid	IRR	51
185.158.56.0/23	RPKI valid	IRR	53
185.158.58.0/23	RPKI valid	IRR	53
193.104.103.0/24	RPKI valid	IRR	53
193.104.131.0/24	RPKI valid	IRR	53

RPKI · ROAs

Route origin authorisations

6 ROAs

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

Prefix	Max length	Trust anchor
77.240.48.0/20	/24	RIPENCC
78.158.48.0/20	/24	RIPENCC
185.158.56.0/22	/24	RIPENCC
193.104.103.0/24	/24	RIPENCC
193.104.131.0/24	/24	RIPENCC
2a03:7600::/32	/48	RIPENCC

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

47 objects · 36 not announced

Route objects naming AS34066 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.

Prefix	Source	Description	Maintainer	Changed	Routing
77.240.48.0/24	RIPE	—	`TELAPPLIANT-MNT`	2017-11-09	Not announced
77.240.49.0/24	RIPE	—	`TELAPPLIANT-MNT`	2017-11-09	Not announced
77.240.50.0/24	RIPE	—	`TELAPPLIANT-MNT`	2017-11-09	Not announced
77.240.51.0/24	RIPE	—	`TELAPPLIANT-MNT`	2017-11-09	Not announced
77.240.52.0/24	RIPE	—	`TELAPPLIANT-MNT`	2017-11-09	Not announced
77.240.53.0/24	RIPE	—	`TELAPPLIANT-MNT`	2017-11-09	Not announced
77.240.54.0/24	RIPE	—	`TELAPPLIANT-MNT`	2017-11-09	Not announced
77.240.55.0/24	RIPE	—	`TELAPPLIANT-MNT`	2017-11-09	Not announced
77.240.56.0/24	RIPE	—	`TELAPPLIANT-MNT`	2017-11-09	Not announced
77.240.57.0/24	RIPE	—	`TELAPPLIANT-MNT`	2017-11-09	Not announced
77.240.58.0/24	RIPE	—	`TELAPPLIANT-MNT`	2017-11-09	Not announced
77.240.59.0/24	RIPE	—	`TELAPPLIANT-MNT`	2017-11-09	Not announced
77.240.60.0/24	RIPE	—	`TELAPPLIANT-MNT`	2017-11-09	Not announced
77.240.61.0/24	RIPE	—	`TELAPPLIANT-MNT`	2017-11-09	Not announced
77.240.62.0/24	RIPE	—	`TELAPPLIANT-MNT`	2017-11-09	Not announced
77.240.63.0/24	RIPE	—	`TELAPPLIANT-MNT`	2017-11-09	Not announced
78.158.49.0/24	RIPE	—	`TELAPPLIANT-MNT`	2016-12-07	Not announced
78.158.50.0/24	RIPE	—	`TELAPPLIANT-MNT`	2016-12-07	Not announced
78.158.51.0/24	RIPE	—	`TELAPPLIANT-MNT`	2016-12-07	Not announced
78.158.52.0/24	RIPE	—	`TELAPPLIANT-MNT`	2016-12-07	Not announced
78.158.53.0/24	RIPE	—	`TELAPPLIANT-MNT`	2016-12-07	Not announced
78.158.54.0/24	RIPE	—	`TELAPPLIANT-MNT`	2016-12-07	Not announced
78.158.55.0/24	RIPE	—	`TELAPPLIANT-MNT`	2016-12-07	Not announced
78.158.56.0/24	RIPE	—	`TELAPPLIANT-MNT`	2016-12-07	Not announced
78.158.57.0/24	RIPE	—	`TELAPPLIANT-MNT`	2016-12-07	Not announced
78.158.58.0/24	RIPE	—	`TELAPPLIANT-MNT`	2016-12-07	Not announced
78.158.59.0/24	RIPE	—	`TELAPPLIANT-MNT`	2016-12-07	Not announced
78.158.60.0/24	RIPE	—	`TELAPPLIANT-MNT`	2016-12-07	Not announced
78.158.61.0/24	RIPE	—	`TELAPPLIANT-MNT`	2016-12-07	Not announced
78.158.62.0/24	RIPE	—	`TELAPPLIANT-MNT`	2016-12-07	Not announced
78.158.63.0/24	RIPE	—	`TELAPPLIANT-MNT`	2016-12-07	Not announced
185.158.56.0/24	RIPE	—	`TELAPPLIANT-MNT`	2017-11-09	Not announced
185.158.57.0/24	RIPE	—	`TELAPPLIANT-MNT`	2017-11-09	Not announced
185.158.58.0/24	RIPE	—	`TELAPPLIANT-MNT`	2017-11-09	Not announced
185.158.59.0/24	RIPE	—	`TELAPPLIANT-MNT`	2017-11-09	Not announced
2a03:7600::/32	RIPE	NET-TELAPPLIANT-V6	`TELAPPLIANT-MNT`	2016-09-12	Not announced
77.240.48.0/20	RIPE	TELAPPLIANT-RT-1	`TELAPPLIANT-MNT`	2007-02-26	Announced
77.240.48.0/21	RIPE	—	`TELAPPLIANT-MNT`	2022-02-01	Announced
77.240.56.0/21	RIPE	—	`TELAPPLIANT-MNT`	2022-02-01	Announced
78.158.48.0/20	RIPE	Net-Telapp-MCR	`TELAPPLIANT-MNT`	2015-01-26	Announced
78.158.48.0/21	RIPE	—	`TELAPPLIANT-MNT`	2022-02-01	Announced
78.158.56.0/21	RIPE	—	`TELAPPLIANT-MNT`	2022-02-01	Announced
185.158.56.0/22	RIPE	—	`TELAPPLIANT-MNT`	2016-12-05	Announced
185.158.56.0/23	RIPE	—	`TELAPPLIANT-MNT`	2022-02-01	Announced
185.158.58.0/23	RIPE	—	`TELAPPLIANT-MNT`	2022-02-01	Announced
193.104.103.0/24	RIPE	—	`TELAPPLIANT-MNT`	2021-02-12	Announced
193.104.131.0/24	RIPE	—	`TELAPPLIANT-MNT`	2021-02-12	Announced

IRR

AS-sets

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

AS-set	Where	Relationship
`AS-TELAPPLIANT`	PeeringDB	Declared by the operator as its own set
`AS-GBLXEU`	RIPE	Lists AS34066 as a direct member
`AS-LIQUID-LINXPEERS`	RIPE	Lists AS34066 as a direct member
`AS-LONAP-CONNECTED`	RIPE	Lists AS34066 as a direct member
`AS-LONAP-MLP`	RIPE	Lists AS34066 as a direct member
`AS-MANDA-LINX-PEERS-V4`	RIPE	Lists AS34066 as a direct member
`AS-TELAPPLIANT`	RIPE	Lists AS34066 as a direct member
`AS12703:AS-PEERS`	RIPE	Lists AS34066 as a direct member
`AS1273:AS-CWW`	RIPE	Lists AS34066 as a direct member
`AS1273:AS-CWW-V6`	RIPE	Lists AS34066 as a direct member
`AS29075:AS-PEERS:AS-LINX`	RIPE	Lists AS34066 as a direct member
`AS29169:AS-PEERS4`	RIPE	Lists AS34066 as a direct member
`AS29169:AS-PEERS6`	RIPE	Lists AS34066 as a direct member
`AS31122:AS-ALL-PEERS`	RIPE	Lists AS34066 as a direct member

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