bgpreport

Network · data from 2026-11-12

AS49550 NTT2-LT-AS UAB Nacionalinis Telekomunikaciju Tinklas

Registry name: NTT2-LT-AS UAB Nacionalinis Telekomunikaciju Tinklas, LT · not in PeeringDB

2IPv4 routes 0.0% RPKI valid · 0.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
2No ROA 2 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
52Route objects not announced registered with origin AS49550, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS49550, 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.

84.32.18.0/24 No ROA Other origin only 1 0%low visibility 1
84.32.19.0/24 No ROA None 1 0%low visibility 1

AS-SET

AS49550 isn't in PeeringDB, where networks name their 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 56 are in fix.csv.

  • ROA: none2
  • Route object: none2
  • Route object: not announced52
ChangePrefix or setDetailFull-table peers
ROA: none84.32.18.0/24No ROA covers it. Add a ROA for AS49550, maxLength 24.1 of 673
Route object: none84.32.18.0/24Route objects for it name AS33922. Add a route object with origin AS49550 in the RIR database for the space.1 of 673
ROA: none84.32.19.0/24No ROA covers it. Add a ROA for AS49550, maxLength 24.1 of 673
Route object: none84.32.19.0/24No route object for it. Add a route object with origin AS49550 in the RIR database for the space.1 of 673

Route objects not announced

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

84.32.0.0/22RIPEInvalid: origin
84.32.0.0/23RIPEInvalid: origin
84.32.2.0/23RIPEInvalid: origin
84.32.114.0/23RIPEInvalid: origin
84.32.116.0/23RIPEInvalid: origin
84.32.120.0/22RIPEInvalid: origin
84.32.124.0/24RIPEInvalid: origin
84.32.125.0/24RIPEInvalid: origin
84.32.134.0/24RIPEInvalid: origin
84.32.140.0/22RIPEInvalid: origin
84.32.142.0/24RIPEInvalid: origin
88.216.4.0/22RIPEInvalid: origin
88.216.76.0/22RIPEInvalid: origin
88.216.80.0/23RIPEInvalid: origin
88.216.82.0/23RIPEInvalid: origin
88.216.84.0/24RIPEInvalid: origin
88.216.85.0/24RIPEInvalid: origin
88.216.86.0/24RIPEInvalid: origin
88.216.87.0/24RIPENo ROA
88.216.112.0/24RIPEInvalid: origin
88.216.113.0/24RIPEInvalid: origin
88.216.114.0/24RIPEInvalid: origin
88.216.115.0/24RIPEInvalid: origin
88.216.116.0/24RIPEInvalid: origin
88.216.117.0/24RIPEInvalid: origin
88.216.118.0/24RIPEInvalid: origin
88.216.119.0/24RIPEInvalid: origin
88.216.120.0/22RIPEInvalid: origin
88.216.120.0/24RIPEInvalid: origin
88.216.121.0/24RIPEInvalid: origin
88.216.122.0/24RIPEInvalid: origin
88.216.123.0/24RIPEInvalid: origin
88.216.125.0/24RIPEInvalid: origin
88.216.136.0/21RIPEInvalid: origin
88.216.138.0/24RIPEInvalid: origin
88.216.139.0/24RIPEInvalid: origin
88.216.140.0/24RIPEInvalid: origin
88.216.141.0/24RIPEInvalid: origin
88.216.142.0/24RIPEInvalid: origin
88.216.143.0/24RIPEInvalid: origin
88.216.159.0/24RIPEInvalid: origin
88.216.162.0/24RIPEInvalid: origin
88.216.163.0/24RIPENo ROA
88.216.168.0/23RIPEInvalid: origin
88.216.170.0/23RIPEInvalid: origin
88.216.170.0/24RIPEInvalid: origin
88.216.172.0/24RIPENo ROA
88.216.174.0/24RIPEInvalid: origin
88.216.176.0/24RIPEInvalid: origin
88.216.177.0/24RIPEInvalid: origin
88.216.178.0/23RIPEInvalid: origin
2001:4048::/32RIPENo ROA

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.