Network · data from 2026-11-12

AS271903 TELNET ISP

Registry name: AS271903 - TELNET ISP S.A.S., CO · PeeringDB

5IPv4 routes 100.0% RPKI valid · 100.0% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

0No ROA 0 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

6Route objects not announced registered with origin AS271903, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS271903, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.


179.49.226.0/24	Valid	Other IRR onlyRADB	670 100%	67
179.49.227.0/24	Valid	Other IRR onlyRADB	670 100%	67
179.49.224.0/24	Valid	Other IRR onlyRADB	669 99%	67
179.49.225.0/24	Valid	Other IRR onlyRADB	668 99%	67
179.49.224.0/22	Valid	RIR databaseLACNIC, RADB	673 100%	67

AS-SET

AS271903's PeeringDB record names no AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 10 are in fix.csv.

Route object: RIR4
Route object: not announced6

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	179.49.226.0/24	Route object only in RADB. Add it in the RIR database for the space.	670 of 673
Route object: RIR	179.49.227.0/24	Route object only in RADB. Add it in the RIR database for the space.	670 of 673
Route object: RIR	179.49.224.0/24	Route object only in RADB. Add it in the RIR database for the space.	669 of 673
Route object: RIR	179.49.225.0/24	Route object only in RADB. Add it in the RIR database for the space.	668 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

179.49.226.0/24

Route object only in RADB. Add it in the RIR database for the space.

670 of 673

Route object: RIR

179.49.227.0/24

Route object only in RADB. Add it in the RIR database for the space.

670 of 673

Route object: RIR

179.49.224.0/24

Route object only in RADB. Add it in the RIR database for the space.

669 of 673

Route object: RIR

179.49.225.0/24

Route object only in RADB. Add it in the RIR database for the space.

668 of 673

Route objects not announced

Route objects with origin AS271903 whose prefix no peer sees AS271903 announce. Many are kept on purpose (backup routes, space announced only in some places).


2803:5be0::/32	RADB	No ROA
2803:5be0::/40	LACNIC	Valid
2803:5be0:100::/40	LACNIC	Valid
2803:5be0:200::/40	LACNIC	Valid
2803:5be0:300::/40	LACNIC	Valid
2803:5be0:400::/40	LACNIC	Valid

2803:5be0::/32

RADB

No ROA

2803:5be0::/40

LACNIC

Valid

2803:5be0:100::/40

LACNIC

Valid

2803:5be0:200::/40

LACNIC

Valid

2803:5be0:300::/40

LACNIC

Valid

2803:5be0:400::/40

LACNIC

Valid

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.