bgpreport

Network · data from 2026-11-12

AS5392 Telnet

Registry name: TELNET-ITALY TELNET S.r.l., IT · PeeringDB

6IPv4 routes 16.7% RPKI valid · 16.7% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
5RPKI invalid 0 origin · 5 maxLength
0No ROA 5 with no route object for this origin
5Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS5392, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS5392, 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.
195.36.0.40/30 Invalid: maxLength Nonecovered by 195.36.0.0/18 1 0%low visibility 1
195.36.6.33/32 Invalid: maxLength Nonecovered by 195.36.0.0/18 1 0%low visibility 1
195.36.7.0/24 Invalid: maxLength Nonecovered by 195.36.0.0/18 1 0%low visibility 1
195.36.10.0/24 Invalid: maxLength Nonecovered by 195.36.0.0/18 1 0%low visibility 1
195.36.32.0/19 Invalid: maxLength Nonecovered by 195.36.0.0/18 1 0%low visibility 1
195.36.0.0/18 Valid RIR databaseRIPE 673 100% 66
2a00:1988::/32 Valid RIR databaseRIPE 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS5392: RIPE::AS-TELNET. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS5392 isn't in the set, or no route object for AS5392 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS5392 in itNot covered
RIPE::AS-TELNET RIPE 31120 Yes 2

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.

  • ROA: maxLength5
  • Route object: none5
ChangePrefix or setDetailFull-table peers
ROA: maxLength195.36.0.40/30ROA 195.36.0.0/18 AS5392 has maxLength 18; the route is a /30. Raise the maxLength, or add a ROA for 195.36.0.40/30.1 of 673
Route object: none195.36.0.40/30No route object for it. A route object for 195.36.0.0/18 with origin AS5392 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS5392 in the RIR database for the space.1 of 673
ROA: maxLength195.36.6.33/32ROA 195.36.0.0/18 AS5392 has maxLength 18; the route is a /32. Raise the maxLength, or add a ROA for 195.36.6.33/32.1 of 673
Route object: none195.36.6.33/32No route object for it. A route object for 195.36.0.0/18 with origin AS5392 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS5392 in the RIR database for the space.1 of 673
ROA: maxLength195.36.7.0/24ROA 195.36.0.0/18 AS5392 has maxLength 18; the route is a /24. Raise the maxLength, or add a ROA for 195.36.7.0/24.1 of 673
Route object: none195.36.7.0/24No route object for it. A route object for 195.36.0.0/18 with origin AS5392 covers it (filters allowing more-specifics accept it). Add a route object with origin AS5392 in the RIR database for the space.1 of 673
ROA: maxLength195.36.10.0/24ROA 195.36.0.0/18 AS5392 has maxLength 18; the route is a /24. Raise the maxLength, or add a ROA for 195.36.10.0/24.1 of 673
Route object: none195.36.10.0/24No route object for it. A route object for 195.36.0.0/18 with origin AS5392 covers it (filters allowing more-specifics accept it). Add a route object with origin AS5392 in the RIR database for the space.1 of 673
ROA: maxLength195.36.32.0/19ROA 195.36.0.0/18 AS5392 has maxLength 18; the route is a /19. Raise the maxLength, or add a ROA for 195.36.32.0/19.1 of 673
Route object: none195.36.32.0/19No route object for it. A route object for 195.36.0.0/18 with origin AS5392 covers it (filters allowing more-specifics accept it). Add a route object with origin AS5392 in the RIR database for the space.1 of 673

Route objects not announced

Every route object with origin AS5392 is announced.

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.